Reference
Nine surfaces, one compiler.
Each extension is a language in its own right: its own grammar, its own validation rules, its own versioned artifact. They share one expression language and one compile pipeline, and together they compile into one semantic graph.
9
Surfaces
4
Implemented
5
Validated
5
Backend crates
The catalogue
Every surface, and where it stands
Extension, name, what it models, and whether an in-tree backend reads its artifact. Every link goes to the surface's page: a real example, the compiled artifact, and the rendered reference.
| Extension | Surface | What it models | Status | Backends |
|---|---|---|---|---|
| .mox | Domain model | Structure, relationships and behaviour | Backend | 3 backends
|
| .ddd | Application design | Services, repositories and aggregate roots | Validated | 0 — none in tree |
| .actor | Authorisation | Actors, capabilities and obligations | Backend | 1 backend
|
| .dmn | Decision model | Decision requirements and decision services | Backend | 1 backend
|
| .evt | Event contract | Versioned events, channels and subscriptions | Validated | 0 — none in tree |
| .uc | Use case pattern | Subjects, actors and successions | Validated | 0 — none in tree |
| .cmmn | Case management | Cases, plans and sentry criteria | Backend | 1 backend
|
| .ifml | Interaction flow | Views, navigation and CLI commands | Validated | 0 — none in tree |
| .deploy | Deployment | Components, profiles and targets | Validated | 0 — none in tree |
The names in this table are not typed into this page. They come fromsite/data/surfaces.json, which the site generator derives from the crates that exist in the tree and from the evidence behind each claim.
Reading the status
Implemented and validated are different claims
Both words mean the compiler checks the surface. Only one of them means something downstream consumes what it compiles.
An in-tree backend consumes the artifact today. The Backends column names the crate, and that crate reads the versioned JSON — never the grammar, never the syntax tree. Implemented means there is a second implementation downstream that has to agree with the compiler about the model's shape.
The surface parses, resolves, validates and lowers to its artifact — but no in-tree backend consumes that artifact yet.The artifact is still real: it is generated from the example by the released binary, committed under site/data/artifacts/, and validated bypherolang artifact check. What is missing is the downstream consumer, not the compiler or the checks.
What is on a page
Evidence, not screenshots
Each surface page is built the same way, from the same generated sources.
Every page quotes lines from the CI-tested example that produced its artifact, prints the first lines of that artifact byte for byte, and links the rendered reference. The example comes from examples/support/; the artifact comes fromsite/data/artifacts/. Neither is copied into the page's source.
The quote is checked at build time: the cited range must still end on a closing brace and leave every delimiter balanced, or the build fails. A source edit that moves a block cannot silently leave the website quoting the wrong lines.