Design decisions

Architecture Decision Records (ADRs) capture the choices that shape model-ledger: the context, the decision, the alternatives considered, and the consequences — including the costs accepted on purpose. They are short, dated, and immutable; a reversed decision gets a new ADR that supersedes the old one rather than an edit.

#	Decision	Status
0001	Model the inventory as an event log, not a registry	Accepted
0002	Everything is a DataNode; the graph builds itself	Accepted
0003	Agents are the primary interface; the SDK is tool-shaped	Accepted
0004	Framework-agnostic core; regulations are pluggable profiles	Accepted
0005	Storage-agnostic via the LedgerBackend protocol	Accepted
0006	Discovery and validation are two subsystems; bridge, don't delete	Accepted

The narrative that ties these together is the Architecture page.