Nonconformance Reporting Procedure
|
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. |
Canonical Question: When a calibration reveals a page's content or structure is genuinely out of tolerance — not just incomplete, but wrong — what's the required response, and where does it get recorded?
Nonconformance Reporting Procedure
Distinct from routine recalibration: most calibration reports document normal, expected refinement — tightening wording, adding evidence, closing an open item. A Nonconformance is different: it documents a specific finding that something was actually incorrect, not merely underdeveloped. Examples from this project's own history: Effects' original "primary reason for civilizational collapse" overclaim; The Cost of Control's original universal-downfall claim; the SMW namespace bug, a real, live structural failure. Nonconformance is for findings of this weight, not ordinary tightening.
Meta
Nonconformance Reporting Procedure
| Type | Meta & Framework |
|---|---|
| Functional Layer | Governance |
| Application Layer | Framework Infrastructure |
| Category | Meta & Framework |
| Version | 0.2 |
| Maturity | Experimental |
| Last Calibration | 2026-07-20 |
| Status | Permanent Beta |
| Description | Defines what counts as a nonconformance finding (as distinct from routine recalibration), where it gets recorded, and how it's tracked via drift_report_status through resolution. |
Menu
Core Principles
- Reality gets final vote
- See the Game. Refuse the Game. Build Better.
- Permanent Beta
Navigation
Related
Where Nonconformance Gets Recorded
- Content nonconformance (a page's claim was found substantively wrong) → logged as a standard Calibration Report, per Calibration Report Standard Format, on the page's own Calibration Log or Talk page (per Calibration Log: When to Create One) — with `drift_report_status` set to reflect the open finding immediately upon discovery, before the fix is made, not after.
- Structural/technical nonconformance (a template, mechanism, or piece of infrastructure was found broken) → logged in Known Site Issues & Fixes, per its existing format.
- Both cases → the finding must appear in the Master Index the moment the status is set, not only once resolved — the index is built from live `drift_report_status` data, so setting the field correctly is the indexing step.
`drift_report_status` — Finalized Options
This field is a list (multiple values may apply simultaneously, semicolon-separated) — a page can have an open breadcrumb and a disputed nonconformance finding at the same time, and both should be recorded, not forced into one value.
| Value | Meaning |
|---|---|
| `Breadcrumb-Open` | An active Development Breadcrumb exists on this page, not yet resolved. See Breadcrumb Philosophy. |
| `Nonconformance-Open` | A nonconformance finding has been logged and not yet resolved, contained to this page only. |
| `Nonconformance-Open-With-Dependencies` | A nonconformance finding has been logged and this page has dependents (per Template:Calibration Dependent) that may also need review. Seeing this value is the Ripple Review trigger — no separate lookup required to know a wider review may be needed. |
| `Disputed` | A finding exists but its validity or resolution is actively contested. |
| `None open` | Nothing currently open. Valid only alone — cannot be combined with any other value, since "none open" and "X is open" are contradictory. |
Required Elements of a Nonconformance Finding
| Element | Purpose |
|---|---|
| What was claimed/built vs. what was actually true/correct | States the gap precisely, not vaguely. |
| How it was found | Traceability — round-robin, direct questioning, a bug hunt, real-world test? |
| Severity — does it affect other pages via `depends_on`? | Determines whether `Nonconformance-Open` or `Nonconformance-Open-With-Dependencies` is the correct value. |
| `drift_report_status` set immediately, before the fix is made | Makes the nonconformance visible in real time, not only in retrospect. |
| Resolution, once made, as a follow-up dated entry (append-only — never edit the original finding) | Preserves the record of the failure itself, not just the fix. See Reality Override Game#Partial Update as Camouflage. |
Relationship to Other Standards
This page defines what a nonconformance is and how it's tracked. It does not redefine the report format itself (see Calibration Report Standard Format) or the breadcrumb mechanism (see Breadcrumb Philosophy and Breadcrumb Tracking) — it connects both to a shared field so both are visible from one place.
Calibration Dependencies
- Known Site Issues & Fixes
- Calibration Report Standard Format
- Breadcrumb Philosophy
- Breadcrumb Tracking
- Calibration Dependencies: Standards and Process
See the Game. Refuse the Game. Build Better.
Page Transparency & Calibration
- Calibration Log & Decision Records (via Talk Page) — This page uses Talk-only calibration tracking. Full history of reviews, version changes, calibration decisions, and any governance reasoning behind structural decisions all live on the same Talk page, per Calibration Log: When to Create One and Decision Records: Governance Memory. Not every Calibration Log entry is a Decision Record — scan the Talk page's headings for entries specifically marked as decisions; the link itself being active only confirms this page has calibration history, not that a formal decision was ever recorded.
- View Current Page History — Complete edit history.
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.
Structural Connections
- Slave Owner Game
- Hidden Mastery
- Foundational Statement
- One-Way Nature of the Sovereign Games
- Slave Owner Game/Tactics
- Slave Owner Game/Effects
- Slave Owner Game/Response
- Slave Owner Game/Examples
- Slave Owner Game/Applications
- Slave Owner Game/Costs to the Player
Calibration Dependent
Pages that list this page as a load-bearing dependency:
| Page | Priority | Instrument Grade | Last Updated | Cycle Status | Drift Status |
|---|---|---|---|---|---|
| Milestone: Pre-Calibration Check Confirmed Under Adversarial Stress Test | Core | Confirmed | 2026-07-14 | Current | None open |
| Breadcrumb Tracking | Core | Experimental | 2026-07-20 | Current | Breadcrumb-Open |
| Known Site Issues & Fixes | Core | Development | 2026-07-20 | Current | Breadcrumb-Open |
| Calibration Report Standard Format | Core | Experimental | 2026-07-20 | Current | Breadcrumb-Open |
| Admin:Maintenance Dashboard | Core | Experimental | 2026-07-19 | Current | Breadcrumb-Open |
| Page Structure Calibration Checklist | Core | Development | 2026-07-14 | Current | Breadcrumb-Open |
| Feature Request Log | Supporting | Experimental | 2026-07-14 | Current | None open |
| Calibration Failure Log | Supporting | Experimental | 2026-07-24 | Current | Breadcrumb-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: Known Site Issues & Fixes • Calibration Report Standard Format • Breadcrumb Philosophy • Breadcrumb Tracking • 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:
- The Sovereign Games Framework — Overall framework philosophy and operating principles
- Permanent Beta — Core maintenance and continuous improvement standard
- Reference Standards — Principles for traceable, confirmed standards
- Calibrating Conceptual Instruments — Methodology for evaluating and refining pages
- Civilizational Traceability Hierarchy — How standards should connect to reality across levels
- Diagnostic Inversion Test — Mandatory self-application standard
- Reality Game — Foundational reality-alignment tool
- Reality Override Game — Standing discipline against protecting an existing model rather than updating it
- Observable Behavior Rule — Standing principle that diagnostics evaluate observable actions, mechanisms, and consequences, not internal motive, belief, or intent
- One-Way Nature of the Sovereign Games — Anti-capture design principles
- The Royal Cubit Civilization (Strategy) — Long-term civilizational vision and metrology metaphor
- Conceptual Instruments — Overall direction and metrology metaphor
- Breadcrumb Philosophy — Standing discipline for making unresolved questions and provisional decisions explicit
- Calibration Dependencies: Standards and Process — Rule that visible and hidden dependency lists must match, and that dependencies describe genuine reliance
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
- Admin:Maintenance Dashboard - This dashboard shows pages that require calibration or review.
- Nonconformance Reporting Procedure — What counts as a nonconformance and where it routes.
- Known Site Issues & Fixes — Technical/mechanism bugs.
- Calibration Failure Log — Calibration-design failures.
- Breadcrumb Tracking — Live index of open Development Breadcrumbs.
- Decision Records: Governance Memory — Why governance/structural decisions exist, plus its Index.
- Insights and Future Layers — Unexpected benefits and project-wide future ideas.
- Feature Request Log — Genuinely desired features that were attempted and confirmed not currently possible with available tools. Index-only; full write-ups and discussion live on Talk.
- Calibration Report Standard Format - Standardrized reporting formatting.
Page Reference
| Title | Nonconformance Reporting Procedure |
|---|---|
| URL | https://www.thesovereigngames.com/wiki/Nonconformance_Reporting_Procedure |
| Description | Defines what counts as a nonconformance finding, where it gets recorded, and how it's tracked via drift_report_status through resolution. |
| Category | Meta & Framework |