About

The publishing entity, and how the doctrine is changed and released.

What this is

The Governed Autonomy Institute is the publishing entity of the Governed Autonomy Doctrine. It publishes one artifact: this doctrine, versioned and revised in the open. It is not a consultancy, not a certification body, not a membership organization, and not a vendor. It sells nothing on these pages.

This document states the Institute's change and release process. Review recommendations, approved drafting directions, adopted doctrine, assessment results and permission to publish are distinct records.

How changes are accepted and released

The Institute accepts proposed changes and evaluates them through committee review. Reviews record evidence, objections, dissent and a reasoned disposition. The Executive Director approves releases. Accepted changes are published in numbered versions, with minor releases such as 4.1 and 4.2 and major changes issued as v5 or later. Public feedback may continue between releases; a fixed extended public review period is not a prerequisite for release.

R25 Preserve change dispositions and releases

R25 is the Institute’s own process requirement. It is separate from the deployment baseline (R01 to R18) and the Assessment Companion (R19 to R24).

Each substantive proposal shall retain its source and locator, finding, evidence class and limitation, affected requirement and prior criterion, disposition, rationale, objections or dissent, owner, approver and date, target release, relevant validation evidence, implementation status and verification result.

Dispositions are incorporated, accepted pending implementation, rejected with reason, deferred with a condition, or duplicate with a surviving identifier. A review recommendation alone shall not constitute adoption. A substantive change to authority or assurance shall not be closed merely by labeling it editorial.

Feedback is accepted at any time. The Institute reviews each proposed change and records its disposition. The Executive Director releases accepted changes as minor versions. A change is major, and issues a new major version, when it alters the text or meaning of a Law, the Planes or Pillars, or the scope of the mandatory runtime baseline.

Every proposed change shall receive a stable proposal identifier and appear on the public change log on the day received, with a non-identifying summary. Institute members shall review the entries directly on the site. The public log is the Proposal Log. A private attachment may protect sensitive evidence, but shall not replace the visible issue, review and disposition record. Each substantive proposal shall close with one of the five dispositions above, a visible reason and affected requirement; a duplicate shall name its surviving identifier. Accepted pending implementation and deferred entries shall retain an owner, condition or dependency, and visible status until resolved. A received entry is not adopted doctrine. The log records changes to the doctrine; presentation, formatting, links and citations are corrected directly and are not logged.

The RFC review-window process is retired. RFC 001 revision 2 remains an unchanged historical proposal, linked to its v4 successors. Historical deadlines record the former process; they impose no current window, consultation period or release gate.

Review and approval

The Institute records the issue, evidence, alternatives, objections, dissent and reason for its decision. Public entries use non-identifying summaries and accountable institutional roles.

Review effort follows the change. Verified corrections need source and replacement checks. Contested requirements need the evidence, alternatives and dissent that bear on the decision. A review of an already resolved issue requires new relevant evidence or an identified defect; review rounds are not a substitute for a disposition.

The Institute acts as a committee of its members. Before publication, the committee checks the release text against approved decisions and release claims. The Executive Director approves the exact release text and claims, or returns specific changes. Approval of requirements or a draft does not itself publish the release. Feedback intake is continuous. The Institute uses no review windows or version-lock dates.

Version and evidence record

Each release identifies its version, status, approval record, publication date, immutable text snapshot, change summary and artifact manifest. Current pages are aliases to the approved release; exact citations identify a release and section. Historical RFC revisions remain explicitly historical proposals. Stable requirement identifiers are not reused for unrelated meanings, and replacement relationships are recorded when text changes or is retired.

Public attribution remains organizational. The public release record identifies accountable roles without naming individuals. Detailed private source evidence can remain private while a non-identifying public summary records the technical issue, disposition and resulting change.

The public mirror is generated from the approved built site and is never maintained as a second hand-edited doctrine. Publication, evidence for a tested assessment method and conformance claims about a deployment remain separate decisions. A DOI can improve citation, but is not a prerequisite for release.

Editorial independence

The doctrine names no vendors, recommends no products, and accepts no sponsorship. Authorship and publication are held by the entity, not by named individuals. Consultancies and vendors may apply, cite, or map to the doctrine freely under its published terms; none of them, and no commercial relationship, has editorial influence over what the doctrine says. Where the doctrine's claims converge with other published work, the convergence is documented on the standards pages rather than claimed as priority; where the doctrine has been wrong, the correction is recorded in the changelog.

Provenance

The doctrine was first published as a standalone page on 18 March 2026 under its former name, the AI Harness Doctrine, and was renamed the Governed Autonomy Doctrine in August 2026. The publication record and the changelog carry the dated history.

Contact

Feedback and proposed changes: [email protected]. Everything else: [email protected]. Corrections are welcome and, when substantive, are recorded in the changelog with the version that lands them. To cite the doctrine, see How to Cite.