# ANVAYA Vision Traceability Matrix

This matrix is the canonical bridge from manifesto and architecture claims to
RFC-backed status. It tracks direction, not implementation completion.

## Label Taxonomy

| Label | Meaning |
| --- | --- |
| stable | Normative and accepted for the current design layer. |
| evidence-backed prototype | Demonstrated in code or proof transcript, but not necessarily final representation. |
| provisional | Semantics or representation intentionally not frozen yet. |
| planned | Part of the target blueprint, pending accepted RFC and implementation. |
| rejected | Considered and intentionally excluded. |
| superseded | Replaced by a later RFC or document. |

## Matrix

| Claim | Label | RFC Home | Evidence / Notes |
| --- | --- | --- | --- |
| ANVAYA is clean-slate, not a Linux distribution | planned | RFC 0006, RFC 0017 | Architecture target-state. |
| No ambient authority | evidence-backed prototype | RFC 0001, RFC 0004, RFC 0005 | Current QEMU proof covers local capability failure paths. |
| Delegation cannot amplify authority | evidence-backed prototype | RFC 0001, RFC 0004, RFC 0005 | Transcript includes no-amplification checks. |
| Parent/derivative revocation | evidence-backed prototype | RFC 0001, RFC 0005 | Bounded local table proof. |
| Production CSpace and software handle representation | stable | RFC 0007, RFC 0010 | RFC 0007 accepts per-task CSpaces, slot/generation/lineage metadata, format `0x1` software `u64` handles, IPC import/export, revocation, stale failure, and software fallback behind RFC 0010 opaque handles. |
| CHERI/hardware-specific CSpace encoding | planned | RFC 0007, RFC 0014, RFC 0015 | CHERI can harden the accepted software model later, but sealed-handle ABI and board-specific storage remain future profile work. |
| CHERI-backed enforcement | planned | RFC 0014 | Target-state only, not current evidence. |
| Formally verified Nucleus | planned | RFC 0016 | Current evidence is QEMU transcript, not formal proof. |
| Nucleus owns four core services | stable | RFC 0006, RFC 0010 | RFC 0006 accepts the Nucleus ownership boundary; RFC 0010 accepts the first syscall ABI for capability, IPC, memory, trap, interrupt, startup, cancellation, version, error, and audit hooks. |
| QEMU RV64GC first-light boot | evidence-backed prototype | RFC 0003, RFC 0012 | Historical CI and local smoke evidence. |
| Timer/trap boot contract | planned | RFC 0012 | Extends beyond historical RFC 0003. |
| Bounded DTB inventory | evidence-backed prototype | RFC 0013, RFC 0005 | Full FDT remains planned. |
| Capability-backed memory isolation slice | evidence-backed prototype | RFC 0001, RFC 0007, RFC 0008, RFC 0010 | v0.2 QEMU proof covers frame cap, map/unmap, missing authority denial, requested-right denial, invalid/zero page-permission denial, cross-CSpace frame revocation, all-staged-space mapping invalidation, stale mapping failure, and fault record. |
| First userspace/Nucleus syscall contract | stable | RFC 0010 | Accepted syscall table defines inputs, outputs, rights, failures, audit events, and implementation status for version/startup, capability, IPC, memory, task/trap/interrupt, wait/cancel, and proof/debug calls. |
| Production memory manager with hardware paging | planned | RFC 0008 | Hardware page-table switching, allocator policy, copy rules, and TLB behavior remain planned. |
| Scheduler semantics | planned | RFC 0011 | Architecture sketch only today. |
| Userspace process ABI | planned | RFC 0017 | Reserved directories only. |
| Init/service registry | planned | RFC 0018 | Needed before broad services. |
| Device manager and drivers | planned | RFC 0019 | Tied to HAL/DTB expansion. |
| Content-addressed storage | planned | RFC 0020 | Manifesto and architecture target-state. |
| WASM runtime and ANVAYA WASI | planned | RFC 0021 | Needed for 0.3 milestone. |
| App package manifest and SDK | planned | RFC 0022 | Must precede stable SDK extraction. |
| AECs as first-class AI context | stable | RFC 0002, RFC 0023 | RFC 0002 accepts AECs as the AI-native accountability and policy object above lower processes/tasks; AECs do not replace all processes. Runtime implementation remains planned. |
| AEC runtime implementation | planned | RFC 0002, RFC 0017, RFC 0023, RFC 0024, RFC 0027 | No in-tree AEC registry, broker-created AEC, approval service, or audit service exists yet. |
| Intelligence Broker | planned | RFC 0024 | OS-managed service, not kernel-managed model serving. |
| Cognitive sandboxing boundary | stable | RFC 0002, RFC 0023 | RFC 0002 accepts world-model planning as side-effect-free; detailed approval binding and implementation remain RFC 0023 work. |
| Cognitive sandboxing implementation | planned | RFC 0023, RFC 0027 | World-model service, approval-binding tests, and audit-backed action-substitution denial are not implemented yet. |
| Complete audit trail | planned | RFC 0027 | Needs privacy/redaction semantics. |
| Human override and hardware escape | planned | RFC 0026 | Requires board-profile evidence. |
| Constitutional constraints | planned | RFC 0026 | Governance categories need normative model. |
| Post-quantum crypto default | planned | RFC 0028 | Architectural default; full production hardening by 1.0. |
| Device mesh and cross-device capability delegation | planned | RFC 0030 | Pairing, distributed capability delegation, remote revocation, offline behavior, and sync semantics. |
| Energy Broker | planned | RFC 0031 | Joule budgets, carbon inputs, scheduler policy interaction, attestation, and exhaustion behavior. |
| Security response process | planned | RFC 0029 | Bootstrap authority must be explicit. |

## Contradiction Fixups Applied / Required

- Applied: replace broad “AECs replace processes” wording with “AECs are the first-class
  AI execution abstraction above process/task substrate.”
- Applied: replace direct kernel model-management wording with “models are
  OS-managed through the Intelligence Broker with kernel-enforced capabilities.”
- Required until implementation evidence exists: mark CHERI hardware-specific
  encoding, formal verification, hardware escape, PQC hardening, full userspace process loader,
  AEC runtime implementation, and cognitive-sandboxing implementation as
  planned until matching evidence exists.
- Applied: treat RFC 0003 as historical first-light; use RFC 0012 for timer/trap boot
  contract.