Architecture

The overview is the page to read first: an arc42-shaped account of what the tool is for, what stands around it, how it is decomposed, what holds across every component, and what iteration 0 leaves as known limits. The pages after it cover single components, what the tool guarantees, and what is currently in scope to build.

The engine’s decomposition into components is recorded in the decision records: ADR-0004 maps the component vocabulary onto packages under src/affirmatrix, and the per-module docstrings name the component each module realizes.

• Architecture overview
• What drift detection covers
• The case store
• The requirements reader
• The content extractor
• The outcome extractor
• The affirmation store’s write face
• The affirmation store’s read face
• The graph builder
• Drift derivation
• The affirmation recorder
• The package gate
• Proof scope
• The evidence package
• The proof verifier
• Command line and configuration
• Iteration-0 backlog