Timeline / Chronology
Status
Section titled “Status”Partial — structure established, most dates and sequence details not yet determined.
| Phase | What happens | Status |
|---|---|---|
| 1 — Before Earth | Born on Lunaris Prime (proposed); becomes Keeper of the Lunar Vault | Canonical (Keeper role); Proposed (Lunaris Prime origin, not owner-confirmed) |
| 2 — The accident | Aboard the Lunar Wanderer, a shortcut through an uncharted debris field damages the hull shielding | Proposed (authored account); the true cause remains Open/Unresolved |
| 3 — The landing | Emergency landing on Earth; the Vault is salvaged | Settled as authored; exact date not determined |
| 4 — Partnership | SOLMEME intercepts the broadcast; the monthly-shipment arrangement forms — the first contributor relationship, not the only kind | Proposed |
| 5 — Ecosystem growth | SOL Launchpad projects and the Vault Defender community join as further contributor threads | Proposed |
| 6 — Present day | Ongoing monthly SOLMEME shipments; Sol Mamy recognizes the same worldview she already lives by in Earth’s on-chain systems (see Stories — Why she eventually builds SOLMAMY) | Proposed |
| 7 — SOLMAMY’s creation (future, in-story) | Sol Mamy applies her worldview using Earth’s own tools, building toward what becomes SOLMAMY | Proposed. Real-world note: this is a story beat, not a claim that the real SOLMAMY company exists yet — see Canon Principles — story world vs. real world, and Brand Book — Foundation — Status |
New events (a game launch, a major story beat, a new character’s introduction) are added as new rows to this table, each carrying its own status. Do not insert an event without also stating whether it’s Canonical or Proposed.
Not yet determined
Section titled “Not yet determined”Absolute or relative dates for Phases 1–2; any event between Phase 2 and Phase 5 beyond what’s listed.
Part of the SOLMEME Brand Documentation System. Content status (Canonical/Proposed/Open/etc.) is this book’s own axis; ownership/rights are separate — see OWNERSHIP_AUTHORITY.md at the documentation system’s root.