Corrections & Retractions

A publication that publishes receipts must itself accept correction. This is the policy.

What we correct

We correct any of the following on receipt of a credible challenge:

• Factual errors in any published claim, including claims about our own systems
• Unsupported attributions (e.g., a Gartner statistic we cited but cannot trace to a primary source)
• Conformance scores or registry entries that proved incorrect after submission
• Doctrine misstatements — the published doctrine is not always identical to the most recent Council ruling, and discrepancies are corrections
• Outdated status labels (e.g., a "specified" component that has begun running, or vice versa)

What we do not silently change

Sealed artifacts (RFCs, blueprints, receipts) are versioned, not edited. A sealed v2.0 document remains accessible after v2.1 is published. The chronicle hash chain prevents silent rewriting of the past.

If a correction requires changing what a sealed artifact said, the correction is itself a new artifact (an amendment, a retraction, or a v-bump) that references the original.

How to submit a correction

1. Email contest@governedai.ai with subject "CORRECTION: [page or artifact]"
2. Include: the specific claim being challenged, your evidence, and how you would phrase a correct version
3. If you wish to remain anonymous, say so; we route under a public ID without your name

What happens next

1. Triage (24 hours). Builder confirms receipt and assigns a contest-ID.
2. Review (≤7 days). Builder + Auditor evaluate. The Auditor may request more evidence.
3. Verdict. One of: ACCEPTED (correction made, page updated, RDL entry logged); PARTIALLY_ACCEPTED (some changes made, others declined with rationale); DECLINED (with public rationale); ESCALATED (to Sovereign for D3-class decisions).
4. Public log. Every contestation produces a public Council ledger entry at /chronicle/contests/<contest-id>, regardless of verdict.

Conformance disputes

If you are an AI system operator who disputes a GDTK conformance score we have published about your system, the same procedure applies, with one addition: you may submit a re-test bundle (the same GDTK-100 cases run on the version of your system you wish to be scored). Re-test results are published alongside the original.

What we will not do

• We will not remove correction requests from the public log.
• We will not retract a correction once it is accepted, except by amending forward (a correction-of-the-correction).
• We will not negotiate the contestation procedure off-record. The procedure is public; the verdicts are public.