Architecture decision records
What you'll find here
Durable design decisions, kept separately from mutable reference material. Reference docs describe current behavior; ADRs explain why the shape exists, what tradeoffs were accepted, and how the decision can be retracted.
Each ADR is a contract.
Status · Context · Decision · Consequences · Alternatives · Retraction. Retraction is the path to changing the design — not silent drift.
Records
Accepted0001Record MVP runner scopeThe MVP runner path is a deterministic provider-backed certification path by default.Accepted0002Provider transport & mode familiesProvider adapters and transports are separate. OpenAI Responses, Anthropic Messages, and Chat Completions are distinct families.Accepted0003Secret handlingCraik stores references, not secret values. Local persistence rejects unredacted payloads.Accepted0004Policy envelope shapeThe stable governance boundary for any task-scoped action context. Capability grants are separate records.Accepted0005Receipts & handoffs as public contractsBoth are schema-validated, redacted, and safe to cite from docs, operator views, and recovery flows.Accepted0006Package & runtime layoutRuntime modules are grouped by concern under
runtime.* packages. No package grows beyond 15 sibling modules.Accepted0007Credential & identity architectureTyped credential profiles · OIDC operator identity · workload identity and RFC 8693 token exchange · identity on every receipt.