Table of Contents
|
Track A produces proof-grade artifacts such as bundles, manifests, hashes, and verification results. Track B produces hypotheses, exploratory reasoning, and live workspace investigation state. Use the proof path when later humans or CI must trust the output. Use the live path when the work is still moving. |
|
Trust remains asymmetric across the system:
This page recaps only the local boundary. Use Cross-cutting Concepts when you need the full canonical model. |
This section uses arc42 as the architecture spine for the curated docs surface. It does not try to normalize the whole repository into one architecture template.