Decision records

Repo-local architecture decision records: decisions about this repository — component names and boundaries, module decomposition, API shapes, build and documentation choices.

Horizon rule. These records hold implementation-horizon decisions. Decisions at the level of the design itself — concepts, invariants, direction — belong to the project’s design record, which lives in the research workspace this tool grew out of and is not carried here. An ADR may describe what that record establishes, in its own words; it should not cite it by number, because a reader of this repository cannot follow the pointer.

• 0001. Project name: affirmatrix
• 0002. Mono-repo with a federated document set
• 0003. The commitment layer owns hash derivation as metadata-agnostic primitives
• 0004. Engine component map and package decomposition
• 0005. Hash encoding and domain separation
• 0006. Test-tree ownership: developer tests, verification tests, fixtures
• 0007. Case-local identifiers in preimages; absolute IRIs in serialization
• 0008. Writes land in place; the tool never runs git
• 0009. The affirmation store is a sidecar commit lineage; committing is affirming
• 0010. The command-line adapter may read repositories; the library still runs no git
• 0011. C constructs located by Doxygen: the span each hash covers
• 0012. Evidence edges have their own link states
• 0013. Test evidence comes from run bundles; the case stores none of it
• 0015. The command-line adapter reads the case history to say who recorded an affirmation
• 0016. A node record carries the revision its content hashes were extracted at