Lore & Canon Policy

Lore should have a clear status so staff and players can tell whether an idea is exploratory or established.

• Concept — an idea being explored; not canon.
• Draft — developed material under review; not canon.
• Approved — accepted by the required reviewers but not necessarily published or implemented yet.
• Published / Live — established canon available for normal use.
• Superseded — replaced by newer approved material.
• Retconned — deliberately removed or changed through an approved canon decision.

The Lore Team is the specialist authority for canon consistency. Significant or world-changing decisions may require Story Administration or wider Administration approval. Holding a higher staff rank does not remove the need to obtain specialist Lore input where a decision materially affects canon.

New lore should be reviewed in proportion to its impact. Minor flavour and clarification should not require the same process as a major faction, settlement, race rewrite or world event. Player-submitted lore should be assessed for compatibility, scale, fairness and roleplay value rather than whether a staff member would personally have written it differently.

Where a lore concept requires a physical build, the Lore Team should define what the location or object is, why it exists, where it belongs and any important cultural or visual requirements. The Build Team then determines how to represent that brief effectively in Minecraft.

A Lore member may create a concept build, but a substantial permanent build still requires normal Build review. Build staff may create physical concepts, but a change that establishes or alters lore requires Lore review before it becomes permanent.

Retcons should be used cautiously and should not occur merely because a new writer dislikes older work. Before materially changing established canon, Uros should consider characters, factions, settlements and long-running stories built around it and preserve continuity where reasonably possible.

Events that establish major new canon, permanently change recognised locations, introduce major factions or entities, or resolve significant world plots require appropriate Lore review. Player choices in events should be allowed to influence outcomes where they remain plausible within the agreed event scope.

Approved public lore should be reflected in the Knowledge Archives where appropriate. Draft material must not be presented as confirmed canon, and major published changes should be updated so players are not expected to rely on outdated information.

Lore review should distinguish an actual canon conflict from personal creative preference. Cross-team disagreement should first be resolved between the relevant specialists, then Team Leads, then the relevant Section Administrator where necessary.