Skip to main content

Validation & declarations

Say exactly what was checked.

A Governance Commons claim names one specification, one version, one subject, one validation method, and the evidence retained. The umbrella itself is not an adoption or certification target.

Current automated support

TargetPublished supportPublic claim boundary
Agent DossierCurrent Python source contains structural dossier validation, with candidate-wheel CI at commit 5987cd9. Published Python 0.2.0 does not expose the Dossier target.Until a newer Python package is published, use the exact source commit and label the evidence source-based rather than registry-installed.
ONSPython 0.2.0 and npm 0.1.1 expose ONS validation, but current toolkit rules identify ONS v1.4.0 while the latest ONS repo release is v1.3.0.Do not treat the toolkit/release mismatch as proof of ONS v1.3.0 conformance.
Agent MatrixRepository source validator and tests; no shared published gc-validate target.Label evidence manual or provisional and record the exact commit used.
APORuntime tests and local validation commands.APO is a reference-runtime candidate, not a specification or conformance target.
ATPPre-release schema and conformance tests.No public badge or released conformance claim.
Governance RecordPython governance-commons 0.2.0.Validation checks the record contract; it does not grant authority or certify the underlying action.

Evidence levels

Automated, manual, and provisional are different claims.

  • Automated: a published validator explicitly supports the named target and version.
  • Manual: documented checks were performed by an identified reviewer without a supported published validator.
  • Provisional: useful implementation evidence exists, but version alignment, validator coverage, or release maturity remains unresolved.
Certification boundary: Governance Commons does not operate a certification program. Maintainer review of a declaration is a completeness check, not independent re-validation or endorsement.