Principles
The axioms that govern construction and conformance.
The canon distinguishes eight adopted principles (P-01–P-08) and twelve racecar positions (R-01–R-12). Each principle has one home in architecture/PRINCIPLES.md and an argument in its own architecture node. AXIOMS.md is the generated reduced baseline. The declaration tree carries rules, groups, and settings, with language-specific bindings kept separate from framework-neutral positions.
Adopted Axioms
P-01 through P-08
Eight adopted axioms form the inherited foundation of the canon. Their authoritative formulations and arguments live in architecture/PRINCIPLES.md and the corresponding architecture/Pxx-* nodes. AXIOMS.md is a generated reduction, not an independently edited authority. The source bundle identifies this as a closed set; individual wording should be taken from the source tree rather than reconstructed from summaries.
Racecar Positions
R-01 through R-12
Twelve explicit racecar positions extend the adopted canon. Among their governing commitments are deterministic enforcement rather than LLM judgment in the constant loop, repository-owner authority over ship decisions, state placement by persistence contract, surface separation, layering, and deployment discipline. Each argument belongs to its own architecture/Rxx-* node. The committed principles file remains the authoritative wording.
Declaration Tree
Rules, groups, and settings
The architecture tree is both a human-readable argument and a machine-readable declaration system. Nodes declare their kind in frontmatter against the tree's own ontology. Rules, groups, and settings form a containment structure, with the parent relationship recorded by the tree. A principle belongs here when it remains valid across implementation languages; Python-specific bindings are recorded as bindings, not promoted into universal axioms.