The review queue where an AI-proposed or member-authored Fact shows its diff, source, and confidence, collects N reliability-weighted confirmations, and graduates Provisional→Canonical — unifying the contribution pipeline (G-013/G-057), the consensus mechanic (G-059), moderation, and data quality (G-026/G-012). Design drafted below; parameters remain open.
Why this matters
Entry 032 names this the keystone. Four decided-but-disconnected threads meet on one surface, and the make-or-break "confirm-is-a-swipe" gesture (G-059) physically lives here. Reviewers never see wikitext — only structured cards.
Proposed design
The review unit — a Pending Op (the card)
Everything flows through one atomic object: a pending operation on a Fact, rendered as a card showing the triple (subject·predicate·object), the citation + tier badge (Entry 020: canon/provider/fan/unsourced), the origin (AI-proposed with confidence | member-authored | provider-import), the source prose snippet it was extracted from (G-062 linking), and the Layer 10 state it is trying to enter.
Four actions, deliberately: Confirm, Reject (with reason tag: unsourced / contradicts-canon / misattributed / duplicate), Fix (corrects inline, forking a competing Pending Op — see duels), and Skip / "I don't know" (first-class and unpunished; forcing judgment manufactures noise).
Lifecycle state machine (Layer 10)
| State | Meaning | Advances by |
|---|---|---|
| Speculative | fan inference, no hard source | reaching citation floor |
| Pre-Release | sourced but pre-canon (leaks/trailers) | source release → grace period (Entry 024) |
| Provisional | imported or freshly proposed | N reliability-weighted confirmations |
| Canonical | confirmed, load-bearing | — (until contradicted) |
| Historical / Retconned | superseded | losing a merge-conflict duel (G-012) |
The queue is the machinery of the Provisional → Canonical transition — the high-volume, gamifiable edge. Code enforces the transition; humans supply only judgment (Entry 022).
Eligibility (the gates are themselves quality levers)
- Consumption-credentialed (Layer 10): in-universe Facts are reviewable only by members who consumed the work. Provider-sourced Facts (e.g. a release date) are reviewable ungated.
- Reliability-weighted (G-059 spine): vote weight scales with demonstrated accuracy, not enthusiasm.
- Recusal: cannot confirm a Fact you proposed, or review a dispute you are party to.
- Power-tiered throttle (Entry 024): per-window action caps as anti-flood.
Consensus graduation + the math
Graduation requires N reliability-weighted confirmations, where N flexes: higher for contested or high-citation-tier Facts, lower for provider imports, and relaxed when the reviewer pool is thin (a niche franchise cannot field 5 confirmations). Vote weights derive from each reviewer's gold-card accuracy (G-059); a Fact graduates when summed weight clears a threshold rather than on a raw headcount. Cold-start: weight everyone near-equally and lean on provider-tier citations until calibration data thickens.
Merge-conflict duels
Two competing values for the same subject·predicate pair are paired into a duel card: reviewers see both with sources; the higher reliability-weighted + higher-citation-tier value wins; the loser becomes Historical/Retconned with full provenance (nothing deleted, per G-012/G-018). Unresolvable splits escalate to a LoreLine discussion (Entry 010), not an edit war.
Versioning & provenance
Every graduation writes a versioned changeset (G-012) with the reviewer set attached (G-018). The queue is therefore also the audit log and the source of the impact-echo and first-finder credit (G-059).
Open decisions
- The exact N thresholds and weight curve; the cold-start relaxation function.
- Reason-tag taxonomy on Reject and how tags feed moderation (G-001) vs. quality.
- How grace-period timing (Layer 10, time-zone semantics) gates Pre-Release cards.
- Queue scoping/pacing vs. anti-flood (Entry 024) so it never becomes a backlog.
Related
- Entry 032 — bridge strategy naming this the keystone
- Entry 022 — AI/ML role split (propose / dispose / enforce)
- Entry 020 — citation strength tiers
- Entry 024 — anti-flood posture
- G-057 — prose-to-Fact authoring (feeds the queue)
- G-059 — gamified consensus confirmation (the mechanic + reliability spine)
- G-013 — Commons proposal workflow (predecessor gate)
- G-012 — canon version control · G-018 — revision history & rollback
- G-026 — Fact-graph data quality (the guardrail)
- G-061 — notifications (review outcomes) · G-064 — experiment harness