TEMPLATE

Timeline:

ID: TIMELINE_

Filling guide

• Minimal (sector-level or single-thread timeline, not a central conflict): Scope + Related Entities + Related Systems / Regions + Period Overview + Key Actors + Timeline + Notes
• Standard (multi-year conflict or crisis with its own internal logic): + Canon Status + Crisis Drivers + Continuity Notes
• Full (timeline central to the current or upcoming plot): + dedicated deep-dive subsections for pivotal threads, where every entry is genuinely unique and the full field set is warranted
• Delete this block when done.

Field density rule (applies to every event entry, at every tier)

• Every individual event entry must carry at least one substantive line: either a Summary, or both Immediate cause and Outcome. This is the minimum for an entry to justify existing as its own bullet rather than being folded into a wave.
• Beyond that minimum, every other field is situational — fill it only if there’s something worth saying. Notes especially is never mandatory; skip it rather than pad it with restated information.
• The fields listed under each event type are a default set, not an exhaustive schema. Add a situational field (e.g. Order: for a command directive) only on the entry that actually needs it — don’t retrofit it onto every entry of that type.
• A wave of similar routine events (mass secessions after the same crisis, a string of raids by the same aggressor) gets one shared cause/context line, then a compact list of affected systems (name + region only). List entries in a wave are exempt from the minimum-content rule above, since the shared line already carries it. Give an event its own full entry, subject to the minimum above, only when it differs from the group pattern.
• State Formation entries follow the same minimum logic: include at least Members or a line on why the formation matters — a bare name is not enough.
• Delete this block when done.

Scope

Short description of what this timeline covers. (e.g. “Secessions and internal collapse of FPC, 2450–2455”)

Canon Status

• Reliability: High / Medium / Low / Draft
• Granularity: Annual / Monthly / Daily / Mixed
• Last major review:
• Notes: <what is fixed canon, what is provisional>

Related Entities

• (add key states, factions, regions)

Related Systems / Regions

• (only major ones, not all)

Period Overview

1–3 paragraphs max:

• what is happening overall
• why it matters
• what kind of conflict it is (civil war, fragmentation, proxy war, etc.)

Key Actors

List every actor with an active stake in this timeline — most timelines have at least one.

• FPC:

  • Goal:
  • Situation:

• SRH:

  • Goal:
  • Situation:

Crisis Drivers

• <structural cause, e.g. fleet losses, fiscal pressure, legitimacy crisis>
• <active cause, e.g. invasion, blockade, constitutional dispute>

Continuity Notes

• Prior causes:
• Concurrent timelines:
• Downstream effects:

---

Timeline

2450

Secessions (example)

Federal abandonment during the First Contact War triggers a wave of secessions across peripheral sectors:

• Sirat System (Bison-Bose Sector)
• Dostoevsky System (Bison-Bose Sector)
• Nuevo Santiago System (Ultima Thule) — later becomes an important local authoritarian power

Break a system out into its own full entry only when something distinguishes it:

• Mu Aquilae System
  • Event: Secedes from FPC
  • Region:
  • Outcome: Secession accompanied by unification talks between Fort Patton, Fort Pershing, Columbus and Saratoga.

Political Events

• Event name
  • Location:
  • Actors:
  • Summary:
  • Immediate cause:
  • Outcome:
  • Notes:

Military Events

• Battle of
  • Location:
  • Forces:
  • Summary:
  • Immediate cause:
  • Outcome:
  • Strategic effect:

State Formation

• • Event: Formation
  • Members:
  • Alignment:
  • Notes:

---

2451

Political Events

• …

Military Events

• …

Secessions

• …

State Formation

• …

---

2452

(same structure)

---

Notes

Freeform:

• uncertainties
• TODOs
• inconsistencies
• terminology decisions
• events that need reconciliation with other timelines