Related languages & specifications
EML is not the only thing built here. These are the sibling language and specification projects from the same workshop — each with its own frozen release, its own stated boundaries, and its own page. They share one working rule with EML: a layer that an AI is allowed to sit on top of has to be deterministic, and has to fail loudly rather than guess.
Canonical Authoritative Intermediate Representation
Canonical Authoritative Intermediate Representation
A program does not have to be owned by one text surface. Text, graph, grid, natural language, AI candidates, tensors and governance are projections of one authoritative computational ontology.
- P* ≠ P_i — the authoritative ontology is never any single one of its surfaces
- AI and UI edits become candidate proposals, never silent commits
- v1.0 frozen: cair-mvp==1.0.0, /api/v1, 105 stable operations, 88 regression tests
Interpretation-Complete Numeral Specification
Interpretation-Complete Numeral Specification
`0.91` is not a number. It is a surface string whose semantics have not been declared — it can be 0.91, (0,91) or (0,9,1), and no amount of prefixing fixes that.
- Surface symbol ≠ parse structure ≠ canonical value ≠ judgment rules
- Comparison is allowed to fail: LT / EQ / GT / INCOMPARABLE / UNRESOLVED / INVALID
- v1.0 frozen: 4 profiles, 8 built-in schemas, transport v1, 227 tests, spec hash pinned
Multi-layer Numerical Visualization Protocol
Multi-layer Numerical Visualization Protocol
A number being correctly represented is not the same as a number being correctly understood. Every display is a projection — MNVP makes that projection declare what it kept, what it dropped, and whether it is still faithful.
- SemanticallyCorrect(x) ⇏ CognitivelyAccessible(x) — two different layers
- Every render emits an omission manifest and a fidelity report, or it fails
- v1.0 frozen: 4 profiles, 7 digest-pinned visual profiles, 5 targets, 266 tests
More will follow — this area is a registry, not a fixed list. Every project below is currently a research and engineering archive: their technical contracts are frozen and hash-pinned, but their release artifacts name no public repository and declare no public license, so none of these pages offers downloads. ICNS and MNVP are two tiers of one pipeline — ICNS decides what a numeral is, MNVP decides how it may be shown — and they are kept separate here because the releases keep them separate.