Governance Records

◉Canonical

---

Purpose

Governance records preserve proposal context, voting outcomes, execution records, and rationale when those records come from verifiable governance sources.

Record Contents

• Proposal records
• Vote records
• Execution records
• Reason codes
• Off-chain context
• On-chain traceability where possible

Importance

Records connect governance decisions to operational execution and public accountability.

Draft Record Rules

Governance records should not be summarized as approval unless the decision source is known and reviewable. Draft notes, planning requests, and local validation reports can support context, but they do not replace governance records.

Governance records should identify:

• proposal or decision identifier;
• decision body or authority;
• voting or approval result if applicable;
• scope approved;
• conditions and limitations;
• execution receipt requirement;
• supersession or rollback reference;
• publication status.

Publication Boundary

This page does not approve governance authority or execution. Public governance claims require verified records and coordinator/governance review.

Decision Record Chain

A governance record should connect a proposal to its scope, reviewer, approving authority, decision state, executor, and receipt. The minimum chain is:

proposal -> review -> decision -> authorized action -> execution receipt -> follow-up

A rejected or withdrawn proposal stops before authorization. A conditional decision records the unmet conditions. An approved decision without an authorized executor remains unexecuted. A receipt that differs from the decision requires escalation and cannot be silently treated as successful completion.

Public records may omit protected deliberation or security details, but must preserve the decision scope, authority basis, status, material conditions, and known limitations.