CYCLE Calibration position — Working Proposal 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.

Calibrated Public Knowledge System (Operating Proposal)

Working proposal. Self-assessed. Not core framework doctrine.

This page is a shippable operating proposal for independent public knowledge platforms (human-led and AI-assisted). It specifies product structure, process, licensing posture, tiered economics, and roles.

It is not a prosecution of Wikipedia. Alternatives already exist because people saw destructive gameplay and chose to build. This document is on the Build Better side.

Facilitator path: A founder or platform lead does not have to build the full stack. They can facilitate standards, legitimacy, and connections while operators ship product and calibration ops.

See also (vision / end goal): Calibrated Civilizational Memory (Vision) (Document A). This page stands alone as operations.

Sovereign-Games-OG-Image.jpg

Honesty about this document’s own standing

This proposal argues that high standing requires confirmation beyond the primary author. This page does not yet have that standing.

It is Self-Assessed only: written and checked by its author, not independently confirmed, not field-validated, not a reference standard. That is intentional, not an oversight. Shipping a proposal that claims Confirmed status while still solo would violate the same rule it recommends.

Treat everything here as a working instrument under test. Use it, challenge it, fork it, or leave it. Confirmation — if any — has to be earned in the open, not declared in the draft.

Purpose

Build or upgrade a public knowledge system that:

Delivers disciplined neutral encyclopedic pages under an explicit calibration process
Makes material corrections visible at the point of reading
Keeps paid / verified tracks structurally separate from the neutral track
Uses human + AI under protocol (AI drafts and compares; humans and independent reviewers hold standing)
Remains economically sustainable under a real editorial and calibration load
Can later host capability-memory domains without redesigning the trust model

Authority comes from stated process + observable results, not from inheriting any other site’s halo.

Scope and non-scope

In scope:

Neutral-track process requirements
Visible correction-record requirements
Tier boundaries and monetization rules that protect neutral credibility
Licensing/attribution posture for reuse of openly licensed corpora
Facilitator vs builder roles
Minimum calibration instrumentation (primitive metrology)
Pilot shape and kill criteria
Day-one registry bootstrap rules

Out of scope (this page):

Full civilizational Memory Hole program design (Document A)
Diagnostic Games library content
Claiming production readiness, independent confirmation, or field validation
Requiring any named organization to adopt this proposal
Legal advice on licensing (posture and checklist only)

Roles

Role	Responsibility	Does not require
Facilitator (e.g. independent platform founder)	Convene standards conversation; legitimize process; connect practitioners; optionally host or bless a versioned registry	Building engineering, hiring full editorial staff, or owning the product stack
Operators / builders	Ship product, UX, tier enforcement, editorial workflow	Inventing metrology from scratch
Calibration methodology	Standards, standing rules, nonconformance practice, process audit design	Owning the public brand of every implementer
AI platform track	Scale assembly, gap detection, drafts under protocol; expose uncertainty/standing on high-stakes outputs	Being the reference standard
Independent confirmers	Challenge and confirm high-stakes claims; supply standing beyond self-assessment	Employment by a single platform

Line for facilitators: You do not have to build it. Facilitate the standard and the room where calibration stays honest.

Source and licensing posture

Treat existing encyclopedic text (including Wikimedia corpora) as prior art and source material, not canon.
Reuse only under applicable license terms (commonly CC BY-SA and related obligations: attribution, share-alike where required).
AI-encyclopedia efforts already operate in this lane when they mine what the license allows.
Do not claim neutrality or authority by copying. Claim authority by process, standing, and correction history.
Operational checklist for implementers: attribution templates, share-alike compliance, clear “derived and recalibrated” labeling where required.

Readiness note: This section is posture and checklist-level, not legal advice. Implementers must verify license compliance for their jurisdiction and stack.

Neutral track process

Claim discipline

On high-stakes pages, separate as far as practical:

Observation / sourced fact claims
Inference
Value or policy premises that drive selection or framing
Explicit uncertainty and disputed regions

“Neutral” means auditable claim-discipline, not a mood or coalition outcome.

Visible correction records

When a material error or slant is corrected:

Leave a checkable record of what was wrong and what standard justified the fix
For general audiences, place disclosure inline or unavoidably adjacent to the reading path — not only on a Talk page
Guard against weaponization: corrections require a stated standard and a challenge path; bad labels can be demoted

Calibration instrumentation (primitive, mandatory)

Uncertainty stated on high-stakes claims
Standing: Self-Assessment vs independent confirmation (author is not sole validator of high standing)
Nonconformance log for content or process failures against stated standards
Output audit (was this entry wrong?) vs process audit (is our method drifting?)
Versioned standards that can be adopted or forked; disagreements logged as open issues or competing versions with evidence — not settled by a permanent priesthood

Who audits the auditors? External reference to outcomes, independent confirmation, open nonconformance, forkability, and scheduled process review. Capture is a recognized failure mode.

Tiered system (required for long-term load)

Heavy neutral maintenance and calibration do not fund themselves on goodwill alone. Tiers pay for the load without selling neutral wording.

Tier	What it is	Trust rule
Neutral knowledge track	Encyclopedic (and later capability) pages under calibration process	No paid placement of claims; highest process bar
Verified public-figure / org profile track	Optional paid or verified presence	Separate surface (URL, design, labeling). Must not read as neutral endorsement
Corporate / sponsored track	Explicitly sponsored modules or pages	Hard separation; disclosure non-negotiable
Pro / institutional tools (optional later)	APIs, reports, mirrors, training	Sells process and access — not secret edits to neutral pages

Non-negotiable: Money never silently buys wording on the neutral track. If paid and neutral cover the same entity, readers must always see two trust classes, not one blended page.

This tier design is treated as load-bearing for success, not optional branding.

Human + AI workflow

AI: draft, compare, gap-detect, cross-link under protocol
Human editors / independent reviewers: reject, revise, confirm, hold standing
Model is instrument; reality and observable outcomes are reference
High-stakes AI-shaped text carries uncertainty and standing marks like any other instrument output

Governance (minimum)

Day-one bootstrap: Until a wider set of adopters exists, the initial standards text and version log can be published by any willing operator or facilitator as a public, dated, versioned document (wiki page, repo, or both) clearly marked Self-Assessed. No consortium is required before v0.1 exists.
Concrete host (interim): Until replaced by a clearer public artifact, this wiki may host Self-Assessed v0.1 process text for this proposal family (starting with this page and its companion vision page). Host means “keeps the text available and the changelog readable,” not “owns the truth” or “settles all disputes.”
First artifact rule: A registry is not “solved by cross-link.” It exists when a named, dated page or repo revision is published. Fork means copy that artifact, state divergences, and link back.
Fork rule: Any implementer may publish a competing version with stated reasons and evidence. Disagreement is logged — not suppressed by a central chair.
Graduation path: Higher standing on a standard (or on this proposal) requires independent confirmation and outcome contact, same as any other instrument.
Facilitator role: A facilitator may legitimize the room and the practice without hosting infrastructure or staffing editorial ops.
Higher standing on content requires confirmation beyond the primary author.
Process audit on a cycle, not only article firefighting.
Paid/neutral boundary enforced in product rules, not only in policy prose.

There is no priesthood. There is a first public version, a changelog, and the right to fork.

Pilot shape

Phase 0 — Narrow vertical

One or two subject areas; small page set
Full neutral-track process + visible correction pattern
One paid/verified example only to prove separation UX
Metrics: time-to-correction; independent confirmation rate; recurrence of same error class after fix; reader clarity on tier labels

Phase 1 — Optional capability wedge

Add one Memory Hole / procedural-capability vertical using the same standing and correction machinery (see Document A when published)

Do not wait for multi-million page parity. Prove process, tiers, and money boundary on a small surface.

Success metrics (primary)

Errors ordinary review missed that calibration process caught
Time-to-correction
Recurrence rate of the same error class after correction
Independent confirmation rate on high-stakes pages
Documented tier-boundary incidents (target: zero silent blends)

Secondary (not primary): traffic, page count, brand mentions.

Kill criteria

Treat this operating model as failing if, after a serious pilot:

Independent confirmation collapses into a closed circle with no outcome contact
Paid and neutral surfaces become confusing or blended in practice
Correction records function as partisan scoreboards rather than operational instruments
Process audit never changes process — only cosmetics on outputs
Neutral track cannot be staffed without selling neutral wording

Who applies kill criteria, and when: Until an external confirmer ecosystem exists, the page author runs a public kill-criteria check at each pilot phase gate (and at least when Version is bumped on this page). Result is logged on Talk:Calibrated Public Knowledge System or the Calibration Log when that subpage exists. Outsiders may dispute the log; disputes are recorded, not erased. Self-review is not independent confirmation — it is only the minimum anti-amnesia rule while standing remains Self-Assessed.

Under-resourcing ≠ falsification. Inability to improve under outcome pressure does.

Asks

Facilitators: Convene and legitimize; you need not build the stack.
Operators: Ship tiers, UX separation, and editorial workflow.
AI platforms: Instrument discipline on high-stakes outputs; process audit, not only output patches.
Calibration builders: Keep standards versioned, forkable, and outcome-tied.

Take it or leave it. Calibrate whatever you keep.

Relationship to The Sovereign Games

This is a side strategic proposal for external public knowledge systems. It is not Core Diagnostic content, not Hidden Mastery, and not a requirement for using The Sovereign Games framework. The Sovereign Games remains a calibration framework for minds and systems; this page offers one optional application pattern for encyclopedia-class products.

Open Calibration Items

For outside readers: This list is unfinished work, stated on purpose. It is not a claim of completion. Skipping this list and reading only the pitch would overstate readiness.

Document A (vision) not yet published on-site — cross-link pending
No worked public example page under this process yet
License/attribution template pack not drafted
Tier UX mock rules not specified beyond principles
Registry: interim host rule points at this wiki; a dedicated dated v0.1 registry artifact page/repo is still not split out as its own object
Independent confirmer pathway not operationalized
Legal review of licensing posture not done (posture only)
Cold-reader plain excerpt (email/PDF surface) not produced

Development breadcrumbs open — treat standing as Self-Assessment only.

Page Transparency & Calibration (public control panel)

What this section is: Every serious page in this project carries a public maintenance record — version, standing, validation, open gaps, and dependency notes. It is not decoration. It is a live, inspectable control panel so quiet changes to standards, claims, or status are harder to hide. If someone tries to inflate readiness, bury drift, or skip review, the mismatch is visible here.

How to read it on first contact:

Standing / calibration_review — Self-Assessment means the author checked their own work; Confirmed requires someone else.
instrument_grade / validation — How far this page claims to be trustworthy as an instrument (kept deliberately low until earned).
drift_report_status — Breadcrumb-Open means unfinished work is listed on purpose, not papered over.
Open Calibration Items (above) — The explicit gap list; readiness is not inflated past what is built.

Cold readers do not need the full field guide to use this page. The proposal is in the sections above. This block is the receipts and tamper-evidence, not the pitch.

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

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

Calibrated Civilizational Memory (Vision)

Calibration Dependent

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

Page	Priority	Instrument Grade	Last Updated	Cycle Status	Drift Status
Calibrated Civilizational Memory (Vision)	Peripheral	Experimental	2026-07-22	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: Permanent Beta • Reference Standards 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	Calibrated Public Knowledge System
URL	https://www.thesovereigngames.com/wiki/Calibrated_Public_Knowledge_System
Description	Operating proposal for neutral-track public knowledge under explicit calibration process, visible correction records, hard-separated paid/verified tiers, facilitator role, day-one registry bootstrap, and human+AI workflow. Side proposal — not core doctrine. Self-assessed only.
Category	Strategic Actionable Plans

Type	Strategic Proposal
Functional Layer	Strategic Layer
Application Layer	Institutional / Public Knowledge Systems
Category	Strategic Actionable Plans
Version	0.2
Maturity	Working Proposal
Last Calibration	2026-07-22
Status	Permanent Beta
Description	Operating proposal for a calibrated public knowledge system: neutral track under explicit process, visible correction records, hard-separated paid/verified tiers for sustainability, human+AI workflow under protocol, and a facilitator path that does not require any one founder to build the full stack. Side proposal — not Sovereign Games core doctrine.

Calibrated Public Knowledge System