status · AVC

Current truth across the AVC system.

Implemented, active, pilot, blocked and production states remain distinct.

View system context Explore current direction ↗

Capability	Authority	Risk	Evidence
contracts	Implemented	Authoritative schemas	Repository source
mission-control	Observe	Scaffolded surface	Mock and adapter boundaries
local-node	Local operator	Alpha	Launcher and runbook evidence
leadrescue	Prepare	Pilot validation	Qualification and proposal receipts

Subsystem	State	Boundary
Trusted contracts	Implemented	Contracts authoritative
Policy and durable jobs	Implemented	Repository verified
Mission Control	Scaffolded	Not a complete control surface
Local Node Alpha	Active	Milestone evidence in progress
LeadRescue	Pilot validation	Not production-approved
Production infrastructure	Not approved	External gates remain

Status contract

Every claim belongs to an exact source and time.

The status surface distinguishes implemented, scaffolded, pilot, blocked and production-approved states.

Current maturity

Core contracts lead; public control surfaces follow.

Trusted contracts, policy, durable jobs and Kernel services are implemented. Mission Control remains scaffolded, and production infrastructure is not production-approved.

Release boundary

A green preview is not full repository approval.

Cloudflare build evidence, exact-head AVC CI, browser QA and rollback evidence remain separate gates.