One thesis.
Five expressions.
Every language here starts from the same place: structured declaration over imperative code. The result is always a sovereign artifact — something complete in itself, owned by whoever holds it, executable without infrastructure.
Five domains. Five syntaxes. One underlying conviction.
REACH + OCTO
WorkflowRuntime Executable Adaptive C# Handler + On-demand Contextual Task Orchestrator
A DSL where intent is the program — declare what to reach into, Claude compiles it to typed C#, live systems answer.
REACH reaches into one source at a time. OCTO coordinates multiple arms simultaneously, surfaces a contextual decision interface, and reserves human judgment at the moment it belongs there — not as a safety check, as the design.
Mere
AppsWorkbook Format for Apps
A file format for reactive applications — declarative screens, state, computed values, and behavior.
A .mp.html file is a complete, self-contained, executable artifact. Open it — it runs. Send it — it travels. The file is the app.
RECALL
PublishingStructured Publishing Language
COBOL-inspired publishing language for the web — declare pages, compile to self-contained HTML.
Separates content from presentation. Produces sovereign, portable documents. What COBOL would have built for the web.
EMBER
AgentsEmergent Behavior Expression Runtime
A language for AI agents — structured intent declaration for agentic pipelines.
Declares agent behavior, intent, and orchestration as readable markup. Powers Project Phoenix — the agentic greenfield pipeline.
CAL
StrategyCascade Analysis Language
A DSL where the cascade is the program — 12 keywords, 3 formulas, structured intelligence source code.
Traces how failure and success propagate across six organizational dimensions, scores the result, and produces a deterministic decision.
What they share
These aren't five separate projects. They're five dialects of the same philosophy.
Declarative over imperative
Every language describes what something is, not how to execute it. The computer follows instructions. These languages give the instructions shape.
Sovereign artifacts
Output is always a self-contained artifact — a CAL analysis, an EMBER pipeline, a RECALL document, a Mere workbook. Each one owns its own meaning.
AI as the primary author
Each language is designed as a generation target. Bounded vocabulary, unambiguous semantics, no escape hatches. A model produces consistent, valid output reliably.
Human-readable by constraint
The same constraints that make AI generation reliable make the output readable to humans. Minimalism serves both audiences simultaneously — by accident, not by design.
CAL — how do we reason about cascades? EMBER — how do AI agents declare intent? RECALL — how do documents become artifacts? Mere — how do files become applications? REACH + OCTO — how does intent become a live system reach?
The pattern continues. The next one is already implied.