Gap Register
G-018Public

Revision history, rollback, page protection

Tier 2 — Structurally thin, not launch-blocking
Status
Open — not started
Owner
Creator
Why now
Every page (Fact node, Commons entry, Home work, LoreLine) needs version history, rollback semantics, and protection levels.
Depends on
G-013

Version history and rollback authority across surfaces; protection levels; touches Commons proposal model.

Why this matters

Every page (Fact graph node, Commons entry, Home work, LoreLine) needs version history, rollback semantics, and protection levels. Touches the Commons proposal model — who can roll back what and under what authority must be explicit.

Page protection in particular is a governance question disguised as a technical one. Wikipedia’s tiered protection levels and the rules surrounding them are an entire subdomain of project policy.

Related

  • G-013 — Commons proposal workflow specifics
  • G-012 — Canon version control over time

Your read on this

Anonymous reactions are accepted; signing in lets you change yours.