Architecture Decision Records

An ADR records a decision that establishes or alters a contract another component depends on: CRD shapes, the Decision JSON, header semantics, the snapshot format, extension seams, evaluation order, toolchain policy. Ordinary implementation details do not get an ADR.

Conventions

• One decision per file, named NNNN-kebab-title.md, zero-padded to four digits, numbered sequentially. Numbers are never reused.
• Headings, in order: # ADR-NNNN: Title, ## Status, ## Context, ## Decision, ## Consequences, ## Alternatives considered.
• Status is Draft, Accepted, or Superseded by ADR-XXXX.
• Reversals get a new ADR; the old one's Status line is updated. ADRs are never retro-edited beyond the Status line and typo fixes.

Index

#	Title	Status
0001	routeD is a decision layer, not a gateway	Accepted
0002	Rust for all runtime components; ONNX for local inference	Accepted
0003	Security constraints are evaluated before cost optimization	Accepted
0004	Extension seams	Accepted
0005	Cargo workspace layout and containerized toolchain	Accepted
0006	Classifier seam and degradation semantics	Accepted
0007	Header trust model: untrusted headers only restrict	Accepted
0008	Single-source policy compiler and canonical snapshot hash	Accepted
0009	Cost model, currency and token estimation	Accepted
0010	Policy precedence	Accepted
0011	Golden decisions live in examples/	Accepted
0012	Inline forwarder and streaming	Accepted
0013	Telemetry schema	Accepted
0014	Operator reconciliation and snapshot distribution	Accepted
0015	Admission validation	Accepted
0016	Artifact resolution and the ONNX model contract	Accepted
0017	ext_proc processing contract	Accepted
0018	Feedback records and the learned router contract	Accepted
0019	Supply chain and release engineering	Accepted
0020	Decision API authentication seam	Accepted
0021	Mutual TLS for snapshot distribution	Accepted
0022	Cosign signature verification for model artifacts	Accepted