Skip to main content

GC v1.2.0

Release baseline and boundary transition

GC v1.2.0 is the current umbrella pinning record. It does not turn the umbrella into a monolithic specification, and it does not activate the accepted RFC-0001 public boundary.

Released specification pins

Agent Dossier v1.1.0, Agent Matrix v1.4.0, and ONS v1.3.0 are the three released specification pins presented by the pending boundary model.

Historical runtime pin

The v1.2.0 manifest also pins APO v1.1.0. RFC-0001 reclassifies APO as a reference-runtime candidate; the historical manifest is not rewritten as though that transition had already been active.

Outside the baseline

Agent Team Protocol v0.1.0 is emerging pre-release work and is not included in GC v1.2.0.

Install the published validation tools

Package versions are independent of the GC v1.2.0 specification pins. Pin the package version so validation evidence remains reproducible.

Python

python -m pip install governance-commons==0.2.0
gc-validate --spec ons manifest.json

Published Python 0.2.0 supports ONS and Capability Contract validation. It does not include the Dossier validator now present in source.

JavaScript / TypeScript

npm install governance-commons@0.1.1
npx gc-validate --spec ons manifest.json

Published npm 0.1.1 is the current registry artifact and exposes ONS validation. npm 0.2.0 has not been published.

Review validation scope and claim boundaries →

RFC-0001 activation state

  • Accepted: 2026-10-01. A-1 through A-5 implementation is authorized.
  • Not active: activation still requires all G-1 through G-5 conditions to verify.
  • Known open: the Agent Dossier schemas are present at the repository's default GitHub Pages address, but the canonical governancecommons.org URLs return 404 according to the last recorded 2026-10-07 check; current custom-domain and canonical URL status must be reverified before closure; APO has not met A-1 provenance/drift requirements; Agent Matrix still references unreleased Agent Dossier v1.4.0 on current main.
  • Publication: Python governance-commons 0.2.0 is published. npm 0.2.0 is not present in the registry; npm 0.1.1 remains latest even though the workflow now uses Trusted Publishing/OIDC.