platform · AVC

The operating system for governed autonomy.

Intent, authority, execution, evidence, approval, recovery and learning remain inspectable boundaries.

View system context Explore architecture ↗

System boundary

Authority flows downward. Evidence flows back.

Each layer has an explicit role and an explicit prohibition.

Owner

May: Ratify constraints, issue grants and approve consequential work.
May not: Delegate root ownership or legal accountability to an agent.

Company Kernel

May: Authorize bounded work and preserve durable state.
May not: Amend protected authority or bypass deny-by-default policy.

Product Cell

May: Use approved Kernel capabilities inside declared scope.
May not: Grant itself Kernel authority or escape its data and budget boundary.

Mission Control

May: Present jobs, events, incidents and evidence.
May not: Become the system of record merely because it renders the state.

Authority chain

Owner authority remains outside autonomous self-modification.

The Constitution, capability grants and production credentials constrain the Company Kernel. Automated actors cannot approve their own authority.

Owner authority → Constitution and capability grants
Company Kernel → policy, jobs, evidence, memory and recovery
Product Cells → bounded products that request, never mint, Kernel authority

Permanent infrastructure

Shared capabilities belong to the Kernel.

Contracts, deny-by-default authorization, durable jobs, orchestration, events, evidence, memory and incident recovery are reused rather than reimplemented by every Product Cell.

Public truth

Implemented does not mean production-approved.

The platform distinguishes implemented contracts, active milestones, scaffolded operator surfaces, pilot Product Cells and production authority.