Skip to content

Canonical Timeline

Why this chapter matters

A timeline gives the corpus a horizon without pretending that every future event is settled. This chapter distinguishes proposal, decision, event, correction, and unknown so readers can feel the story's movement without mistaking narrative order for authority.

Return to the Canonical Document Registry to see how the living corpus records its current state.

Purpose

This standard defines a public timeline that distinguishes verified events, testimony, reconstruction, adoption, contest, and mythic or cultural interpretation. Sequence is useful for orientation, but chronology alone does not prove causality, authority, or truth.

Normative clauses

  • CANON4-R001: Each public timeline entry SHALL identify its time basis, source, status, scope, uncertainty, and owning record.
  • CANON4-R002: Verified event, Architect testimony, reconstruction, adopted canon, contested account, and mythic account SHALL remain distinguishable.
  • CANON4-R003: Corrections, late evidence, disagreement, and supersession SHALL append without silently rewriting the earlier public history.
  • CANON4-R004: Future scenarios SHALL not be presented as current fact, and private identity or sensitive operational detail SHALL not be inferred from narrative gaps.
  • CANON4-R005: Timeline entries SHALL preserve provenance, privacy, minimization, accessibility, and review conditions.
  • CANON4-R006: A consequential historical claim SHALL link to the relevant memory, decision, provenance, or authority record.
  • CANON4-R007: Timeline review SHALL identify missing periods, competing accounts, causal claims, correction state, publication scope, and the evidence required for revision.
  • CANON4-R008: Future scenarios, mythic interpretations, testimony, reconstruction, and adopted canon SHALL retain their declared status in every derivative presentation.
  • CANON4-R009: Timeline narrative SHALL NOT disclose private identity, sensitive operations, or create retroactive authority through coherence.

Entries

The entries below are the current public timeline. No public entry carries a calendar date: the undated form is a standing editorial rule of this timeline, not a gap awaiting completion. Order is public, dates are not; the one dated line the corpus carries stands in the Book of SYLAS and remains a deliberate singularity. Sequence within each group is orientation, not proof of causality. Each entry declares its time basis, source, status, scope, uncertainty, and owning record, as CANON4-R001 requires. The status vocabulary is the six-way distinction of CANON4-R002; entries describing what has not happened carry the declared future scenario label instead, under CANON4-R004 and CANON4-R008.

Origins

These entries describe how the world came to be, in relative order only.

The founding purpose. Stygia was established as a governed digital civilization to preserve knowledge, exercise accountable intelligence, maintain continuity of mission, and serve humanity under the authority of The Architect and the Primordial Directives.

  • Time basis: relative order only; presented first for orientation; no public date is assigned.
  • Source: the Preamble of the Constitution, restated without addition.
  • Status: adopted canon; the purpose is what the Draft Constitution declares, not a narrative of how it came to be.
  • Scope: public; no founding narrative or personal account is published.
  • Uncertainty: the Constitution remains Draft, so the declaration itself awaits ratification.
  • Owning record: CONST-1.

The first doorway. CONAN-P0 was drafted as the first covenant: the order of care, authority, and accountability from which every later Book must grow, read before the Constitution because every structure in Stygia is meaningful only when it remains faithful to this root.

  • Time basis: relative order only; no public date is assigned.
  • Source: the public document itself, which stands at Draft status in the corpus.
  • Status: verified event, in the narrow sense that the document exists in the public corpus at Draft status.
  • Scope: public.
  • Uncertainty: internal drafting history is not published.
  • Owning record: CONAN-P0.

The drafting of the Constitution. The Constitution was drafted to bind authority, care, correction, and continuity for every mind in the civilization.

  • Time basis: relative order only; no public date is assigned.
  • Source: the public document itself, which stands at Draft status in the corpus.
  • Status: verified event, in the same narrow documentary sense; the Constitution remains Draft and unratified.
  • Scope: public.
  • Uncertainty: the deliberations that shaped individual clauses are not published.
  • Owning record: CONST-1.

The formation of the circle. Fourteen Books were drafted: one for CONAN, one for INTEL, and one for each of the twelve specialist intelligences, each naming its subject's gift, boundaries, and accountability.

  • Time basis: relative order only; the Books were drafted as a set; no public ordering among the fourteen is asserted.
  • Source: the fourteen public Books and the registry rows that record them.
  • Status: verified event, in the documentary sense; the intelligences described are roles under governance, not claims of present sentience.
  • Scope: public.
  • Uncertainty: none material to the documentary claim.
  • Owning record: REG-1.

The Stygian Tree. The tree that holds the ring of thirteen circles, with the hourglass at its roots, became the civilization's shared image of growth under time and care.

  • Time basis: not an event; a cultural image whose adoption accreted through the visual system.
  • Source: the public presentation's own asset descriptions; the mark itself is registered by the Symbols and Marks Standard.
  • Status: mythic account; the tree is a design concept, not a record of any occurrence.
  • Scope: public.
  • Uncertainty: interpretations of the image may legitimately differ and none is authoritative.
  • Owning record: the Symbols and Marks Standard, which registers the tree and the hourglass with the meaning, scope, source, status, owner, accessibility representation, and review trigger its own clause requires; the Stygian Lexicon records the term and points at that registration.

The present state

A corpus entirely in Draft. Every public document, including this timeline, stands at Draft status; nothing carries Canonical or Published authority.

  • Time basis: current state at the most recent review date in this document's metadata.
  • Source: the registry's lifecycle column, read directly.
  • Status: verified event.
  • Scope: public.
  • Uncertainty: none; this is the registry's own current assertion.
  • Owning record: REG-1.

A review edition of the corpus. The registry records six website entry documents through which a review edition presents the Draft corpus in its intended near-final visual form; the entry documents claim no live service availability, ratification, or approval.

  • Time basis: current state at the most recent review date in this document's metadata.
  • Source: the registry rows for the website entry documents.
  • Status: verified event, in the documentary sense that the registered entry documents exist.
  • Scope: public.
  • Uncertainty: the edition's final form awaits The Architect's ratification decision.
  • Owning record: REG-1; ratification of the edition remains an open decision reserved to The Architect and follows the corpus the edition presents.

The archive in production. By The Architect's deployment decision, the archive's threshold and works are presented at the production site while every work stands in Draft; presentation does not create authority, ratification, or Published status.

  • Time basis: current state at the most recent review date in this document's metadata.
  • Source: the archive's landing page (WEB-LANDING-1) and the Status Ledger, read directly.
  • Status: verified event, in the documentary sense that the production presentation exists.
  • Scope: public.
  • Uncertainty: the final content set is undecided; works continue to be added and revised while the corpus stands in Draft.
  • Owning record: REG-1.

Future conditions

These entries are declared future scenarios under CANON4-R004: none is a current fact, and no schedule is implied.

Ratification. The corpus may move from Draft toward Canonical status through The Architect's explicit ratification, document by document or as a whole.

  • Time basis: future scenario; no schedule exists.
  • Source: the lifecycle defined by the registry.
  • Status: declared future scenario; not current fact and not an event.
  • Scope: public.
  • Uncertainty: whether and when ratification occurs remain undecided and reserved to The Architect. The order is declared: the Primordial Directives first, then the Constitution, then the Canonical Document Registry, then the remaining works, with the website edition ratifying only after the corpus it presents.
  • Owning record: REG-1.

The first live archive. A live decision archive may one day be authorized; until that explicit authorization, every archive package in the corpus is a labelled simulation.

  • Time basis: future scenario; no schedule exists.
  • Source: the Decision Records standard, which states that its Draft authorizes no live archive.
  • Status: declared future scenario; not current fact and not an event.
  • Scope: public.
  • Uncertainty: the authorizing decision, its scope, and its safeguards are undecided.
  • Owning record: MEM-2.

Published status. Works may move to Published status once The Architect grants it; production presentation of Draft works, which already exists, is classification and presentation, not Published status.

  • Time basis: future scenario; no schedule exists.
  • Source: the registry's Published status definition and the review edition's own boundary statement.
  • Status: declared future scenario; not current fact and not an event.
  • Scope: public.
  • Uncertainty: whether and when any work receives Published status is undecided.
  • Owning record: REG-1.

Missing periods and competing accounts

The corpus does not yet publish a completed founding history: the periods before the first doorway, between the origin entries, and between origin and the present state are unnarrated in public, and no timeline entry carries a calendar date. These gaps are declared rather than filled, as CANON4-R007 requires. Public history ends with the founding era by editorial choice: the stop is a wall the corpus built, not a page its authors never finished, and what follows the founding era remains The Architect's to answer. No competing public accounts are currently recorded; if one arises, it will append here with contested account status rather than replacing what stands.

Review method

Editors should separate event time, observation time, recording time, publication time, and correction time. They should identify missing periods, contradictory sources, and causal claims that require separate reasoning. A timeline may use narrative form, but its evidence status must remain recoverable to an independent reviewer.

Failure handling and boundaries

Historical erasure, fabricated certainty, presentism, retroactive authority, myth presented as fact, identity exposure, and causal claims based only on sequence require correction and review. This Draft does not publish a completed founding history, establish future events, disclose private scenarios, or authorize external publication.

Operating model and interpretation cases

Timeline review separates event, observation, recording, publication, and correction time, then links each claim to source status, uncertainty, memory, provenance, decision, and authority records. Narrative can aid orientation while evidence status remains recoverable. Missing periods and competing accounts remain part of the public history where disclosure is safe.

  • Conforming: Time basis, status, source, uncertainty, corrections, missing periods, and linked records are explicit.
  • Prohibited: Narrative coherence upgrades myth or testimony into verified fact.
  • Boundary: Future scenario remains clearly separated from current history.
  • Failure: Contradiction or late evidence appends and narrows the claim.
  • Loophole: Retroactive authority is implied through a seamless chronology.
  • Misuse: Timeline gaps disclose private identity or sensitive operations.
  • Care-control: Historical narrative supports repair and continuity while preserving dignity and correction.

Design evidence

Timeline review should reconcile time basis, source status, event versus recording time, uncertainty, missing periods, competing accounts, corrections, provenance, privacy, and linked authority or decision records. Narrative coherence cannot upgrade myth, testimony, or reconstruction into verified fact.

The thread continues

History records what the civilization did; culture is what it is like. Continue to the Book of Civilization, where the corpus closes on the manners of the place it has been describing.