Poesis
Candidate Standard Model · Solution Partial
Specifications — Generative System Model.
Define systems and governance with a shared, extensible language.
GSM 1.0 source content specifies eight primitives, Archetypes, DNA grammar and the Ascription lifecycle. Document-set publication is pending. Processor conformance and neutral stewardship are separate adoption steps; OASIS candidacy is not endorsement.
Values
Value delivered by the product
- Value Implemented
Reduce bespoke semantic translation.
Reuse shared vocabulary and profiles when connecting tools that implement compatible contracts.
Supported by Capabilities(2)
Supported by Features(1)
- Value Implemented
Make portability requirements explicit.
Compare migration routes against declared conformance requirements. Complete transfer still depends on nonconformant DRAFT preservation and independent endpoint compatibility.
Supported by Capabilities(1)
Realized through Use cases(1)
- Value Partial
Adapt grammar through evidence.
Address demonstrated modeling limits through planned, reviewed extensions with explicit compatibility decisions.
Supported by Capabilities(1)
Supported by Features(4)
- Value Partial
Build toward neutral stewardship.
Pursue consortium stewardship through a visible model and reviewed evolution, with ownership, licensing and publication stated separately.
Supported by Capabilities(1)
Supported by Features(6)
Features
Implemented and planned features
- Feature Implemented
Eight systemic primitives
Describe structures, mechanisms, ports, interactions, types and governance through eight defined GSM primitives, a fixed core for scoped system modeling.
Addresses Pain points(1)
Supports Values(3)
Serves Use cases(1)
Used by Actor types(2)
- Feature Implemented
DNA grammar
Express governance through Directives that open scope, Norms that state evaluable constraints and Ascriptions that carry governed snapshots. Processors implement enforcement.
Addresses Pain points(1)
Supports Values(3)
Serves Use cases(1)
Used by Actor types(2)
- Feature Implemented
Archetyping
Define domain vocabulary and constraints with governed JSON Schema Archetypes and version-pinned references interpreted under GSM.
Addresses Pain points(1)
Supports Values(4)
Serves Use cases(2)
Used by Actor types(3)
- Feature Implemented
Systemic Ascription lifecycle
Normative immutable-snapshot lifecycle with review, activation, suspension, terminal states, graded validation, sibling-draft correction and differentiated cascades.
Addresses Pain points(1)
Supports Values(3)
Serves Use cases(1)
Used by Actor types(2)
- Feature Planned
Enhanced Directives and Norms model
Extend governance expression through tested cases and accepted Change Proposals, with explicit compatibility decisions for each grammar change.
Addresses Pain points(1)
Supports Values(2)
Serves Use cases(1)
Used by Actor types(2)
Roadmap
Where Specifications is going.
Recorded version: v1.0. Historical release labels do not establish the current feature scope above.
- v1.0 Implemented Recorded release: Normative content frozen — Systemic Primitives, DNA grammar, Archetyping, lifecycle (publication of the document set pending)
- v1.1 Planned Planned milestone: Enhanced Directives and Norms model
Implemented and Planned qualify the features in each milestone. Recorded releases and planned milestones preserve history, not delivery dates or hosted availability. See the Milestones & Versions register.
Qualities
What Specifications claims about how it behaves.
- Named conformance profiles Partial Conformance is stated against a profile
Definition interchange is scoped to a declared profile. A processor conforms to profiles it names, not to the model as a whole.
- Testable requirements Planned Requirements are meant to be executed
Interchange requirements are written to be testable. A conformance suite and compatible consumers still need acceptance.
Usage
Use cases involving Specifications
- Use case Implemented
Agree a reusable domain typing contract
Agree a versioned vocabulary and its constraints with adopters, using examples and counterexamples to expose incompatible interpretations.
Supported by Features(1)
Addresses Pain points(1)
Realizes Values(3)
Performed by Actor types(3)
- Use case Implemented
Read and model a governance decision
Interpret the primitive, typing, governance-grammar and lifecycle clauses relevant to a proposed decision, identifying permitted representations and constraints without claiming that a processor enforces them.
Supported by Features(4)
Addresses Pain points(1)
Realizes Values(3)
Performed by Actor types(2)
- Use case Planned
Incorporate an accepted grammar extension
Incorporate an approved grammar change with explicit compatibility and migration boundaries.
Supported by Features(1)
Addresses Pain points(1)
Realizes Values(2)
Performed by Actor types(2)