Jump to content

Decision Records: Governance Memory: Difference between revisions

From The Sovereign Games
Structural pre-cal only. Fixed GameModule placement, canonical param, inline comments, mandatory templates + order, Resource visibility. Dates untouched. Nonconformances logged first. Content calibration still pending.
Line 2: Line 2:
|status = Active Development
|status = Active Development
}}
}}
= Decision Records: Governance Memory =
'''Calibration Reports and Calibration Logs record how a page's content and status changed. Decision Records record why a governance rule, taxonomy category, or structural convention exists in its current form — including the alternatives that were rejected and why.''' The purpose of a Decision Record can be stated in one question: '''was this actually considered, or just never questioned?''' Without an answer to that question preserved somewhere, a future contributor who disagrees with a rule has no way to tell the difference.


{{GameModule
{{GameModule
| type = Meta & Framework
| type = Meta & Framework <!-- options: Meta & Framework, Core Diagnostic, Builder & Sovereignty, Calibration & Accountability, Practical Application, Sovereign Strategies, Strategic Actionable Plans, Hidden Mastery, Framework Guidelines -->
| category = [[:Category:Meta & Framework|Meta & Framework]]
| category = [[:Category:Meta & Framework|Meta & Framework]] <!-- must match an existing Category page -->
| Functional Layer = Governance
| Calibration Type = Governance <!-- displays as Functional Layer. options: Governance, Diagnostic Layer, Builder Layer, Calibration Layer, Application Layer, Strategic Layer, Framework Infrastructure, Maintenance, Meta Principle -->
| Application Layer = Framework Infrastructure
| Application Layer = Framework Infrastructure <!-- options: Multi-Layer, Framework Infrastructure, Individual, Institutional -->
| Version = 0.2
| Version = 0.2
| Maturity = Development
| Maturity = Development <!-- options: Experimental, Development, Confirmed, Field Validated, Reference Standard Candidate -->
| Last Updated = 2026-07-14
| Last Updated = 2026-07-14 <!-- static only. Must match review_date. FORBIDDEN: magic words -->
| description = Defines what a Decision Record is, when one is required, where it lives, and how to write one — the governance memory layer explaining why rules exist, not just what they are.
| description = Defines what a Decision Record is, when one is required, where it lives, and how to write one — the governance memory layer explaining why rules exist, not just what they are.
}}
}}
= Decision Records: Governance Memory =
'''Calibration Reports and Calibration Logs record how a page's content and status changed. Decision Records record why a governance rule, taxonomy category, or structural convention exists in its current form — including the alternatives that were rejected and why.''' The purpose of a Decision Record can be stated in one question: '''was this actually considered, or just never questioned?''' Without an answer to that question preserved somewhere, a future contributor who disagrees with a rule has no way to tell the difference.


== Decision Record Principles ==
== Decision Record Principles ==
These are not procedures — they are the philosophy the procedures below exist to serve. A Decision Record should:
These are not procedures — they are the philosophy the procedures below exist to serve. A Decision Record should:
* Preserve reasoning, not advocate for it.
* Preserve reasoning, not advocate for it.
* Record rejected alternatives fairly enough that a future contributor can understand why they were attractive in the first place.
* Record rejected alternatives fairly enough that a future contributor can understand why they were attractive in the first place.
Line 31: Line 29:


== What a Decision Record Is ==
== What a Decision Record Is ==
A Decision Record captures, for one specific structural decision:
A Decision Record captures, for one specific structural decision:
* A unique ID
* A unique ID
Line 42: Line 39:


== When a Decision Record Is Required ==
== When a Decision Record Is Required ==
'''Trigger test:''' Would a future contributor reasonably ask "why does this rule exist?" if they read only the current page, with no other context? If yes, a Decision Record is required. If the change is wording, sequencing, formatting, or a correction of an actual error, it is not.
'''Trigger test:''' Would a future contributor reasonably ask "why does this rule exist?" if they read only the current page, with no other context? If yes, a Decision Record is required. If the change is wording, sequencing, formatting, or a correction of an actual error, it is not.


Line 54: Line 50:


== Where Decision Records Live (Hybrid Model) ==
== Where Decision Records Live (Hybrid Model) ==
 
'''1. Central Index — [[Decision Records: Governance Memory/Index]]'''
'''1. Central Index — [[Decision Records: Governance Memory/Index]]'''
A single, chronological, scannable list of every Decision Record, by ID. Each entry: ID, date, short title, page(s) concerned, link to full record. Browsing/search only — never long-form content.
A single, chronological, scannable list of every Decision Record, by ID. Each entry: ID, date, short title, page(s) concerned, link to full record. Browsing/search only — never long-form content.


'''2. Per-Page Subpages — `PageName/Decision Records`''' (naming locked: matches `/Calibration Log` convention exactly)
'''2. Per-Page Subpages — `PageName/Decision Records`''' (naming locked: matches `/Calibration Log` convention exactly)
Full content lives on a subpage attached to the governance page it primarily concerns.
Full content lives on a subpage attached to the governance page it primarily concerns.


Line 64: Line 59:


== ID Format ==
== ID Format ==
Every Decision Record receives a sequential ID: '''DR-0001, DR-0002, DR-0003...''', assigned in the order created, never reused even if a record is later superseded or rejected. Pages may reference a decision by ID alone (e.g. "see DR-0004") once the record exists, rather than restating its full title.
Every Decision Record receives a sequential ID: '''DR-0001, DR-0002, DR-0003...''', assigned in the order created, never reused even if a record is later superseded or rejected. Pages may reference a decision by ID alone (e.g. "see DR-0004") once the record exists, rather than restating its full title.


== How to Write a Decision Record ==
== How to Write a Decision Record ==
<pre><nowiki>
<pre><nowiki>
=== DR-XXXX: [Short, specific title] ===
=== DR-XXXX: [Short, specific title] ===
Line 86: Line 79:


== Relationship to Other Mechanisms ==
== Relationship to Other Mechanisms ==
{| class="wikitable"
{| class="wikitable"
! Mechanism !! Question Answered
! Mechanism !! Question Answered
Line 104: Line 96:


== Worked Precedent ==
== Worked Precedent ==
[[Standards: Types and Calibration Obligations/Decision Records]] predates this page and should be treated as the de facto first per-page Decision Records subpage — retroactively conforming to this standard (adding IDs, Consequences fields, and updated Status values) is a follow-up task, not required immediately.
[[Standards: Types and Calibration Obligations/Decision Records]] predates this page and should be treated as the de facto first per-page Decision Records subpage — retroactively conforming to this standard (adding IDs, Consequences fields, and updated Status values) is a follow-up task, not required immediately.


'''See the Game. Refuse the Game. Build Better.'''
'''See the Game. Refuse the Game. Build Better.'''
{{RelatedPages}}
{{Standalone Transparency}}
{{Standalone Transparency}}
{{Calibration Maintenance}}
{{Calibration Dependent}}
{{Calibration Dependent}}
{{Calibration Dependencies Display}}
{{Calibration Dependencies Display}}
{{Calibration Maintenance}}
{{Framework Reference}}
{{Calibration Procedure Reference}}
{{Tracking Logs Reference}}


[[Category:Meta & Framework]]
[[Category:Meta & Framework]]
[[Category:Site Maintenance]]
[[Category:Site Maintenance]]


<div style="display:none;">
{{Resource
{{Resource
| Title = Decision Records: Governance Memory
| Title = Decision Records: Governance Memory
Line 123: Line 119:
| Category = Meta & Framework
| Category = Meta & Framework
}}
}}
</div>


{{Admin Page Status
{{Admin Page Status
<!-- Do Not Remove commented out Reference Options -->
<!-- === CORE STATUS === -->
<!-- options: Done, Needs review, Not started -->
| categorization = Done
| categorization = Done
<!-- options: Self-Assessment, Confirmed Rating -->
| calibration_review = Self-Assessment
| calibration_review = Self-Assessment
<!-- options: Experimental, Development, Confirmed, Field Validated, Reference Standard Candidate -->
| instrument_grade = Development
| instrument_grade = Development
<!-- options: Low, Moderate, High -->
| validation = Low
| validation = Low
| calibration_rationale = Single-round review (ChatGPT, Grok) incorporated in full — all substantive suggestions adopted (Principles, Consequences, expanded Status, IDs, supersession handling, governance-reasoning-not-truth guardrail). Title changed per project owner's synthesis of Grok's two options. Not yet tested: Index page doesn't exist, retrofit of the precedent page not yet done.
| calibration_rationale = Structural pre-cal only. Fixed GameModule placement, canonical Calibration Type param, added inline option comments, added missing mandatory templates, corrected order, made Resource visible. Dates left unchanged per pre-cal rule. Content calibration not performed.
| review_confidence = High
| review_confidence = High <!-- options: High, Moderate, Low -->
| review_date = 2026-07-14
| review_date = 2026-07-14 <!-- static only. Must match Last Updated. Untouched in structural pre-cal. -->
| reviewed_by = Sovereign
| reviewed_by = Sovereign
<!-- options: Core, Supporting, Peripheral -->
| priority = Core
| priority = Core
| review_threshold = 60
| review_threshold = 60
<!-- options: Yes, No, Not checked -->
| has_backlinks = Not checked
| has_backlinks = Not checked
<!-- options: Yes, Has red links, No, Not checked -->
| outbound_links_valid = Not checked
| outbound_links_valid = Not checked
<!-- options: Yes, No -->
| in_outline = No
| in_outline = No
<!-- options: Yes, No -->
| in_category_outline = No
| in_category_outline = No
<!-- options: Done, Needs review, Not started -->
| templates_complete = Done
| templates_complete = Done
<!-- options: Meets standard, Needs work, Not checked -->
| formatting_standard = Meets standard
| formatting_standard = Meets standard
<!-- options: Applied, Not applicable, Needs work -->
| symmetry_check = Not applicable
| symmetry_check = Not applicable
<!-- options: Yes, No, Not applicable -->
| self_report_flagged = No
| self_report_flagged = No
<!-- options: Yes, Needs work, Not checked -->
| terminology_consistent = Yes
| terminology_consistent = Yes
<!-- options: Confirmed by other party, Self-assessed only -->
| standing_check = Self-assessed only
| standing_check = Self-assessed only
<!-- options (multiple allowed, semicolon-separated): Breadcrumb-Open, Nonconformance-Open, Nonconformance-Open-With-Dependencies, Resolved-Unverified, Disputed, None open. "None open" valid ONLY alone. -->
| drift_report_status = None open
| drift_report_status = None open
| depends_on = Breadcrumb Philosophy; Standards: Types and Calibration Obligations/Decision Records; Calibration Log: When to Create One
| depends_on = Breadcrumb Philosophy; Standards: Types and Calibration Obligations/Decision Records; Calibration Log: When to Create One
}}
}}

Revision as of 17:32, 20 July 2026

CYCLE Calibration position — Active Development

This page is a conceptual instrument under Permanent Beta. It declares a real calibration position, not a finished product waiting to ship. Checking continues; an edit is only required when evidence demands it. Stage: Seed to Fruit.

Feedback welcome — especially clarity, failure modes, and calibration gaps. Use discussion or Contribute.



Decision Records: Governance Memory

Calibration Reports and Calibration Logs record how a page's content and status changed. Decision Records record why a governance rule, taxonomy category, or structural convention exists in its current form — including the alternatives that were rejected and why. The purpose of a Decision Record can be stated in one question: was this actually considered, or just never questioned? Without an answer to that question preserved somewhere, a future contributor who disagrees with a rule has no way to tell the difference.



Sovereign-Games-OG-Image.jpg

Meta

Decision Records: Governance Memory

Type Meta & Framework
Functional Layer Governance
Application Layer Framework Infrastructure
Category Meta & Framework
Version 0.2
Maturity Development
Last Calibration 2026-07-14
Status Permanent Beta
Description Defines what a Decision Record is, when one is required, where it lives, and how to write one — the governance memory layer explaining why rules exist, not just what they are.

Core Principles

  • Reality gets final vote
  • See the Game. Refuse the Game. Build Better.
  • Permanent Beta

Navigation

Related


Decision Record Principles

These are not procedures — they are the philosophy the procedures below exist to serve. A Decision Record should:

  • Preserve reasoning, not advocate for it.
  • Record rejected alternatives fairly enough that a future contributor can understand why they were attractive in the first place.
  • Distinguish observed facts from judgment calls.
  • Make later recalibration possible rather than freezing debate.
  • Be concise enough that future contributors will actually read it.

A Decision Record documents governance reasoning, not objective truth. Its existence means "we know why we currently do this" — not "this debate is closed forever." Treating a Decision Record as evidence a matter can no longer be questioned would itself be a Reality Override pattern.

What a Decision Record Is

A Decision Record captures, for one specific structural decision:

  • A unique ID
  • What was decided
  • Significant contributors to each position taken (not necessarily every participant)
  • What alternatives were considered and rejected, and specifically why
  • The consequences of the decision — what else it affects or requires
  • Current status
  • Date

When a Decision Record Is Required

Trigger test: Would a future contributor reasonably ask "why does this rule exist?" if they read only the current page, with no other context? If yes, a Decision Record is required. If the change is wording, sequencing, formatting, or a correction of an actual error, it is not.

Concretely, required when a change:

  • Establishes, renames, or retires a taxonomy category or Type.
  • Adopts or rejects a proposed rule, threshold, or formula.
  • Resolves a genuine disagreement between contributors or reviewers, especially one where the losing position had real merit worth preserving.
  • Changes a structural convention other pages are expected to follow.

Not required for: typo fixes, rewording for clarity, routine field updates, or anything already fully explained by a normal Calibration Report.

Where Decision Records Live (Hybrid Model)

1. Central Index — Decision Records: Governance Memory/Index A single, chronological, scannable list of every Decision Record, by ID. Each entry: ID, date, short title, page(s) concerned, link to full record. Browsing/search only — never long-form content.

2. Per-Page Subpages — `PageName/Decision Records` (naming locked: matches `/Calibration Log` convention exactly) Full content lives on a subpage attached to the governance page it primarily concerns.

For decisions spanning multiple pages: the record lives on whichever page is most directly responsible for enforcing the decision, with a cross-reference added to other pages involved, and the Index entry notes all affected pages.

ID Format

Every Decision Record receives a sequential ID: DR-0001, DR-0002, DR-0003..., assigned in the order created, never reused even if a record is later superseded or rejected. Pages may reference a decision by ID alone (e.g. "see DR-0004") once the record exists, rather than restating its full title.

How to Write a Decision Record

=== DR-XXXX: [Short, specific title] ===
'''Decision:''' [What was actually decided — one sentence]
'''Status:''' Proposed / Adopted / Superseded / Rejected / Open — Unresolved
'''Significant contributors:''' [Major positions and who held them — not necessarily every participant]
'''Reasoning:''' [Why the adopted position won]
'''Alternatives considered:''' [What else was proposed, and specifically why it was set aside]
'''Consequences:''' [What this decision requires or affects elsewhere — other pages, future conventions, follow-up work]
'''Date:''' YYYY-MM-DD
'''Superseded by:''' [DR-XXXX, date — only if applicable]

"Open — Unresolved" is a valid, complete status — not every decision needs forced closure. A deliberately preserved disagreement (see the severity/disclosure tension in Standards: Types and Calibration Obligations) is a complete record on its own; the record's job is to preserve reasoning on both sides, not manufacture resolution. See Breadcrumb Philosophy.

Superseding a Decision Record: never delete or overwrite a superseded record's content. Mark its status "Superseded," add the superseding record's ID and date, and leave the original content fully intact as historical record — consistent with the append-only principle used throughout this project (Talk page Calibration Reports, page history).

Relationship to Other Mechanisms

Mechanism Question Answered
Versioning When did it change?
Calibration Report How did it change?
Calibration Log What's its current calibration state?
Decision Record Why does this rule exist?
Breadcrumb What is still unresolved?

Decision Records are historical, like Calibration Reports — but narrower: a Calibration Report documents one review pass on one page; a Decision Record documents one structural decision, possibly debated across multiple passes, pages, or contributors before resolving (or deliberately not resolving).

Worked Precedent

Standards: Types and Calibration Obligations/Decision Records predates this page and should be treated as the de facto first per-page Decision Records subpage — retroactively conforming to this standard (adding IDs, Consequences fields, and updated Status values) is a follow-up task, not required immediately.

See the Game. Refuse the Game. Build Better.



Structural Connections


Page Transparency & Calibration

This page is under continuous calibration in line with the Permanent Beta principle.


Public Discussion Welcome

Questions, suggestions, feedback, disagreement, and proposed improvements are welcome on the Talk page.

Light rules:

  • Prefer evidence and concrete examples over slogans.
  • Apply Diagnostic Inversion Test when criticizing — the same standard to this page that you would apply elsewhere.
  • Distinguish observation from conclusion.
  • Calibration entries and Decision Records are maintenance records; public discussion belongs in ordinary Talk threads.
  • This framework remains in Permanent Beta. Better calibration is always in scope.



Calibration Dependent

Pages that list this page as a load-bearing dependency:

Page Priority Instrument Grade Last Updated Cycle Status Drift Status
Insights and Future Layers Core Experimental 2026-07-14 Current Breadcrumb-Open
Calibration Report Standard Format Core Experimental 2026-07-20 Current Breadcrumb-Open
Decision Records: Governance Memory/Index Core Development 2026-07-14 Current Breadcrumb-Open
Standards: Types and Calibration Obligations Core Development 2026-07-20 Current Breadcrumb-Open
Page Structure Calibration Checklist Core Development 2026-07-14 Current Breadcrumb-Open
Calibration Failure Log Supporting Experimental 2026-07-24 Current Breadcrumb-Open
Standards: Types and Calibration Obligations/Decision Records Supporting Development 2026-07-14 Current None open

If this page is edited substantively, review the list above per the Ripple Review rule — see Calibration Dependencies: Standards and Process#Rule: Core-Priority Changes Trigger Mandatory Ripple Review.


Calibration Dependencies

Pages this page relies on as load-bearing dependencies: Breadcrumb Philosophy Calibration Log: When to Create One Calibration Report Standard Format Page Structure Calibration Checklist If incorrect, edit the `depends_on` field in Admin Page Status — do not edit this section directly, it is auto-generated.



Calibration References

This page is calibrated against the following core standards and reference materials:



Page Construction & Maintenance References

How we construct, maintain, and utilize each page as a self-admin control panel.

  • Distributed Instrumentation — the architectural principle behind why this page (and every page) carries its own live instrumentation, rather than relying on a separate central dashboard.
  • Page Structure Calibration Checklist — the Step 0 structural pass every page should pass before content calibration begins; this page's own structure should be checkable against it.
  • Template:New Page Seed — the seed template this page's basic structure was built from.
  • Calibration Log: When to Create One — the decision procedure this page's own Talk-only vs. dedicated-log status was decided against.
  • Framework Features Reference — maintains consistency and traceability across the framework's structural features while avoiding unnecessary maintenance overhead; consult before introducing a new structural pattern this page might otherwise duplicate.



Calibration Procedure

In development. See Calibration Procedure for current status. No formal step-by-step procedure exists yet beyond the practices demonstrated across individual pages developed during the initial creation of this project.



Tracking & Log Pages




Page Reference

Title Decision Records: Governance Memory
URL https://www.thesovereigngames.com/wiki/Decision_Records:_Governance_Memory
Description Defines what a Decision Record is, when one is required, where it lives, and how to write one — the governance memory layer explaining why rules exist.
Category Meta & Framework