Skip to main content

Reference runtime

Agent Project Orchestrator

APO is not a specification. Under RFC-0001 it remains a reference-runtime candidate until its vendored Agent Dossier schemas have release provenance and automated drift detection.

Execution runtime candidatev1.1.0CandidateUndeclared in repository

Status

Historically pinned in GC v1.2.0

Project-level task graphs, dispatch, handoffs, recovery, telemetry, and audit.

Capabilities

What this component covers.

  • Goal intake and task graph compilation
  • Governed dispatch and handoff controls
  • Recovery and resource-budget enforcement
  • Structured telemetry and evidence output

Use path

Make a scoped, versioned claim.

  1. Treat APO as an implementation choice, not a GC conformance target.
  2. Inspect its runtime and packaging limitations before use.
  3. Do not claim reference-runtime status until RFC-0001 A-1 is satisfied.

Evidence boundary

Declare only what the evidence supports.

No umbrella conformance badge is available for APO. Runtime tests demonstrate behavior in the repository; they do not certify an adopter.

Read validation and declaration guidance →