Architecture Decision Records
This directory contains the architecture decision records (ADRs) for the Universal Agent Runtime project. ADRs document significant decisions that affect the project's structure, dependencies, or public interface.
Index
| ADR | Title | Date | Status |
|---|---|---|---|
| ADR-007 | React is the canonical first-party frontend | 2026-07-11 | Accepted |
| ADR-0001 | Record architecture decisions | 2026-07-14 | Accepted |
| ADR-0002 | Dual-license the runtime under AGPL and the SDKs under MIT | 2026-07-13 | Superseded by ADR-0017 |
| ADR-0003 | Set a 60% coverage baseline on day one | 2026-07-13 | Accepted |
| ADR-0004 | Introduce a central UarError enum | 2026-07-13 | Accepted |
| ADR-0005 | Migrate configuration to config-rs with schemars and secrecy | 2026-07-13 | Accepted |
| ADR-0006 | Adopt SLSA Level 3 and OSV/Grype for supply-chain security | 2026-07-13 | Accepted |
| ADR-0007 | Release the SDKs as 1.0.0 under MIT | 2026-07-13 | Accepted |
| ADR-0008 | Emit a RAG citation stream | 2026-07-13 | Accepted |
| ADR-0009 | Vendor @a2ui/web_core and @a2ui/react and build a UAR-owned renderer | 2026-07-13 | Accepted |
| ADR-0010 | Build the A2UI renderer on webcore with React and shadcn/ui | 2026-07-13 | Accepted |
| ADR-0011 | Host a unified docs portal with Docusaurus and add visual regression | 2026-07-14 | Accepted |
| ADR-0012 | Transport-free AG-UI adapter reachable from the embedded runtime | 2026-07-22 | Accepted |
| ADR-0013 | Embedded run-policy resolution + embedded admin surface | 2026-07-24 | Accepted |
| ADR-0014 | Backfill the effective-run-policy model route from the registry default | 2026-07-24 | Accepted |
| ADR-0015 | Embedded conversation-policy admin surface + effective-config resolver | 2026-07-24 | Accepted |
| ADR-0016 | Seed the embedded session from host-supplied conversation history | 2026-07-25 | Accepted |
| ADR-0017 | Relicense the runtime from AGPL-3.0-only to MIT | 2026-08-07 | Accepted |
ADR-007 and ADR-0007 are distinct retained identifiers. The former predates
the padded numbering convention and is not renamed because existing references
depend on its historical filename.
Process
- When a significant architectural decision is needed, draft an ADR using the template in ADR-0001.
- Open the ADR for review in the same PR that implements the decision.
- Mark the ADR as
Acceptedwhen the PR is merged. - If a decision is superseded, mark the old ADR as
Supersededand link to the new ADR.