corporate · AVC

Build capability in dependency order.

Verified contracts and local runtime precede products, agents and broader autonomy.

  1. 01
    Foundations 1–4.5Contracts, policy, durable jobs, Kernel services, events and recovery.
    complete
  2. 02
    Local Node AlphaPersistent local product, bounded operator bridge and verified packaging.
    active
  3. 03
    LeadRescue validationCommercial validation after the local operating slice is usable.
    queued
  4. 04
    Production foundationDurable adapters, secrets, monitoring, backup and restore.
    queued
Company sequence

Capability expands only after the previous operating boundary holds.

The current active milestone is AVC Local Node Alpha.

  1. Foundation 1–4.5

    Contracts, policy, jobs, Kernel services, events, incidents and recovery are implemented.

    passed
  2. Local Node Alpha

    Persistent local service, bounded operator bridge, live state and Windows artifact.

    active
  3. LeadRescue validation

    Commercial testing begins after the local vertical slice is usable.

    pending
  4. Production foundation

    Durable adapters, secrets, deployment, monitoring, backup and restore.

    pending
  5. Controlled autonomy

    Delegation expands through measured reliability, compliance and recovery evidence.

    pending
Dependency order

The Kernel and Local Node precede broader commercial autonomy.

Foundation controls, persistent local operation and exact-head verification are required before LeadRescue validation expands.

Vertical slices

Complete operating loops outrank disconnected scaffolds.

A milestone includes runtime behavior, observability, evidence, recovery, packaging and documentation rather than only source code.

Promotion

Implemented, verified, released and production-approved remain distinct.

Each roadmap transition requires the evidence appropriate to its environment and authority.