Architectural Decision Records
These ADRs document the load-bearing decisions behind the Veridex Agent Fabric — why the runtime is event-sourced, why context is a budgeted resource, why memory has tiers, how the policy and approval systems compose, and how the monorepo is split.
The pages here are public, sanitised summaries. Each one ends with a link to the original
ADR in the internal docs/architecture/decisions/ tree for teams who want the full reasoning,
alternatives, and references.
| # | Title | Topic |
|---|---|---|
| 0049 | Event-Sourced, Policy-Gated Runtime Loop | Runtime |
| 0050 | Context Compilation & the Effective Window | Context |
| 0051 | Tiered Memory with Homeostatic Lifecycle | Memory |
| 0052 | Tool Sandboxing & Safety Classes | Tools |
| 0053 | Policy Engine — Priority-Ordered Rule Composition | Policy |
| 0054 | Human-in-the-Loop Approvals with Checkpoint/Resume | Approvals |
| 0055 | Checkpoint Persistence & Resumability | Durability |
| 0056 | Immutable Event Log & Signed Audit Emitter | Audit |
| 0057 | MCP Transport Security Hardening | Transports |
| 0058 | A2A & ACP Transport Design | Transports |
| 0059 | React Hooks Architecture | UI |
| 0060 | Framework Adapter Strategy | Interop |
| 0061 | Multi-Tenancy & Control Plane | Governance |
| 0062 | Stateful Evaluation Harness | Quality |
| 0063 | Monorepo Package Split | Packaging |
All decisions are Accepted unless otherwise noted on the individual page.