From a concept to a published release
The system keeps knowledge representation, community opinion, reviewer authority and publication separate.
Define
Create or select a stable concept. Give it inclusion/exclusion boundaries, not merely a label.
Represent
Register artifacts: a structured JSON definition, SHACL shape, RAAML XMI, or argument model.
Bind
Declare a specific semantic relationship between a concept and an artifact version or element.
Propose
Represent every change as an explicit typed proposal with its own revision hash.
Deliberate
Gather comments, examples, community votes and three counted independent reviews.
Publish
Apply the accepted change in one transaction; store a content-addressed, immutable release manifest.
What is deliberately not automated?
RAAML XMI is stored as a native artifact. This prototype does not claim a complete RAAML parser or semantic validator. An adapter marked manual-review returns not_implemented instead of a fabricated pass. JSON Schema validation is implemented with Ajv.
Likewise, a reviewed artifact attachment says what a community accepted, not that its underlying safety argument or logical model is true.
Try the form builder ↗