Docs live with the system that enforces them
This page is the public map. Implementation detail stays in the owning repo, with the system that enforces it.
The architecture
The whole pipeline as five stations — intake, corpus, encoding loop, RuleSpec, graph — then the compile seal and the surfaces it powers. One example, § 2017's “30 per centum”, runs the whole way.
Repository ownership
The repo split is part of the documentation model: engineering docs live in the repo that owns the code or contract, and a doc moves only when the owning system moves.
axiom-corpus
Corpus source text, anchors, hierarchy, tables, hashes, and source claims.
axiom-encode
Encoder prompts, harness validation, proof validation, oracles, eval suites, and methods notes.
axiom-rules-engine
RuleSpec language, compiler, runtime, test runner, and executable semantics.
rulespec-*
Jurisdiction RuleSpec corpora: checked-in .yaml rules and companion .test.yaml cases.
axiom.org
Public site, Axiom app shell, docs index, and cross-system presentation.