Proposal Log — Governed Autonomy Doctrine

Governed Autonomy Institute

Feedback is accepted at any time at [email protected]. Each proposed change receives a stable identifier and appears here on the day it is received, with a non-identifying summary. The Institute reviews it and records one disposition and the reason. The Executive Director releases accepted changes as minor versions, unless the change is major under the rule in About. This log records changes to the doctrine. Presentation, formatting, links and citations are corrected directly and are not logged. A received entry is not adopted doctrine. A private attachment may protect sensitive evidence but never replaces the visible issue, review and disposition. See how changes are accepted and released.

Summary

Entries by status as of the latest update to this page.
Status	Entries
Received (no disposition yet)	6
Incorporated	8
Accepted pending implementation	1
Deferred with a condition	0
Rejected with reason	0
Duplicate with a surviving identifier	0

This log opened on 1 November 2026. Entries are listed in order received.

Open entries

Entries not yet incorporated. Accepted and deferred entries keep an owner or condition and stay visible until resolved.
ID	Area	Summary	Status	Owner, condition or next step
CHG-0009	Standards mappings	Mappings to external standards still cite RFC 001 criteria (C1.1 and similar) next to a notice that they are historical.	Accepted pending implementation	Owner: web team and Executive Director. Condition: each mapping restated against R01 to R18 using the recorded successor map, with source quotations verified against the primary source.
CHG-0010	Pillars	The pillar-to-requirement links are an editorial aid, not normative.	Received	Awaiting confirmation by the Institute: keep as labeled navigation aids, or remove.
CHG-0011	Release rule	Whether wording changes that preserve the meaning of a Law should count as a major version.	Received	Awaiting a decision of the Executive Director on the wording of the R25 major-version rule.
CHG-0012	R16 evidence	Detecting a deleted, altered or reordered record should not depend on a secret held by the operator of the governing system, not only on a verifier other than the acting agent.	Received	Under Institute review against the v4 baseline.
CHG-0013	R03, R07	Each governed action should be bound to an authorization issued by the mission originator outside the agent, its prompt and its self-authored state.	Received	Under Institute review against the v4 baseline.
CHG-0014	R10 revocation	Withdrawal of an upstream grant should invalidate authority derived from it in downstream systems before the next governed effect, as a stated bound rather than a profile-declared one.	Received	Under Institute review against the v4 baseline.
CHG-0015	Assessment, Law 5	Verification of required human approval should examine recorded approval rates and decision latency per authorizer, so that habitual approval cannot satisfy it.	Received	Under Institute review against the v4 baseline.

All entries

Every entry, with its disposition and reason.
ID	Received	Area	Summary	Disposition	Reason and result
CHG-0001	2026-11-01	Law 2	Some pages still described Law 2 as control during execution, the v3.6 wording.	Incorporated	Aligned with v4: protected enforcement before each effect, with pre-commit rechecks when material conditions can change.
CHG-0002	2026-11-01	Maturity	Pages described maturity as deciding which controls apply now and which are deferred, or how far autonomy can extend, and used the retired name and Level labels.	Incorporated	Restated: the baseline (R01 to R18) applies to every deployment, and the Organizational Maturity Evaluation defers no requirement and licenses nothing.
CHG-0003	2026-11-01	Doctrine text	Quotations and slogans attributed to the doctrine did not appear in v4.	Incorporated	Replaced with paraphrases of, or links to, the v4 Laws and action classes. RFC 001 wording is attributed to RFC 001.
CHG-0004	2026-11-01	RFC 001	RFC 001 was described as open for comment, and the v3.6 changelog referred to a revision 3 that was never published.	Incorporated	RFC 001 revision 2 is a historical proposal preserved as published, linked to its v4 successors. The Conformance Layer glossary entry points to the Assessment Companion.
CHG-0005	2026-11-01	Release rule	Two different rules stated what makes a release major.	Incorporated	One rule, taken from the R25 wording, used wherever the rule is stated.
CHG-0006	2026-11-01	R25	The identifier R25 appeared without a definition, and the public change log was stated as an obligation before it existed.	Incorporated	R25 defined as the Institute’s own process requirement, separate from R01 to R18 and R19 to R24. This log is the public change log.
CHG-0007	2026-11-01	The Laws	The Laws were called non-negotiable, though the doctrine names three non-negotiables.	Incorporated	Laws described as foundational principles.
CHG-0008	2026-11-01	Threat Surface	A claim that the Threat Surface predated external guidance conflicted with the changelog.	Incorporated	Replaced with a dated statement: the section was added in v3.0 (11 to 12 May 2026). The mapping records convergence, not independence of origin.
CHG-0009	2026-11-01	Standards mappings	Mappings to external standards still cite RFC 001 criteria (C1.1 and similar) next to a notice that they are historical.	Accepted pending implementation	Owner: web team and Executive Director. Condition: each mapping restated against R01 to R18 using the recorded successor map, with source quotations verified against the primary source.
CHG-0010	2026-11-01	Pillars	The pillar-to-requirement links are an editorial aid, not normative.	Received	Awaiting confirmation by the Institute: keep as labeled navigation aids, or remove.
CHG-0011	2026-11-01	Release rule	Whether wording changes that preserve the meaning of a Law should count as a major version.	Received	Awaiting a decision of the Executive Director on the wording of the R25 major-version rule.
CHG-0012	2026-10-30	R16 evidence	Detecting a deleted, altered or reordered record should not depend on a secret held by the operator of the governing system, not only on a verifier other than the acting agent.	Received	Under Institute review against the v4 baseline.
CHG-0013	2026-10-30	R03, R07	Each governed action should be bound to an authorization issued by the mission originator outside the agent, its prompt and its self-authored state.	Received	Under Institute review against the v4 baseline.
CHG-0014	2026-10-30	R10 revocation	Withdrawal of an upstream grant should invalidate authority derived from it in downstream systems before the next governed effect, as a stated bound rather than a profile-declared one.	Received	Under Institute review against the v4 baseline.
CHG-0015	2026-10-30	Assessment, Law 5	Verification of required human approval should examine recorded approval rates and decision latency per authorizer, so that habitual approval cannot satisfy it.	Received	Under Institute review against the v4 baseline.