What can AGA verify today?

AGA's “How she works” page describes a target architecture. The capability ledger separates that product vision from the behavior the running platform can currently demonstrate.

The live registry is available as structured data at /api/capabilities. Each entry names its status, owner, measurement method, latest verified value, timestamp, and known limitations.

What do the statuses mean?

• Live means the complete scoped capability is operating and has current evidence.
• Beta means a useful end-to-end capability is operating with documented limits.
• Prototype means relevant code or infrastructure exists, but the complete public claim has not been verified.
• Planned means the claim remains part of the target architecture but is not implemented.
• Evidence paused means a beta or live capability could not be measured or its evidence became stale. The public page downgrades these entries automatically.

No catalog entry, provider listing, planned integration, or marketing target is counted as an operating capability. Measurements describe only what they directly observe, and every limitation remains visible beside the claim.

Why publish this ledger?

Ambitious systems drift into describing their target architecture as if it were running. The ledger is the platform's structural defense against that: every public claim is tied to a measurement method and current evidence, entries whose evidence goes stale are downgraded automatically rather than by goodwill, and other public pages — the daily synthesis, the Hive, the organization records — point here instead of asserting capabilities themselves.