Architecture Decision Records

Every non-trivial architectural decision lives here as a numbered ADR. The format is fixed: context, decision drivers, considered options, decision, consequences, open questions. Superseded ADRs are kept; new ADRs explicitly reference what they replace.

Canonical source for each ADR is the markdown file under docs/decisions/ in the repository. The pages below mirror those for in-site navigation.

Index

ID	Title	Status
0001	Chronometric tool design	Accepted
0002	Cognitive graph tool design	Accepted
0003	Task fractionator tool design	Accepted
0004	Profile schema design	Accepted
0005	Translation tool design	Accepted
0006	Guardrail tool design	Accepted
0007	Plugin protocol design	Accepted

How to propose a new ADR

1. Open an issue describing the decision needed. Link to the user problem.
2. Draft the ADR under docs/decisions/NNNN-<kebab-name>.md with status proposed.
3. Open a PR. Reviewers: at least one Maintainer member plus any agent with overlap (mcp-architect for substrate ADRs, for guardrail ADRs, governance-author for governance ADRs).
4. On merge, status flips to accepted. If a future ADR replaces this one, that future ADR names the supersession explicitly.

Conventions

• Status moves proposed → accepted → superseded. Rejected drafts are kept as rejected rather than deleted.
• ADRs are short. Two or three paragraphs of context. Two or three alternatives. A paragraph of decision. A handful of consequences.
• Code samples in ADRs are extracted and run in CI when they reach accepted.