Timeline Layering and Parallelism Framework

Overview

This document defines the current framework for keeping Caeldon’s timeline layered and naturally overlapping rather than reading as one species or one region becoming historically active only after another is finished.

It exists to preserve the setting’s sense of a whole inhabited planet. The goal is not to force every people into the same date bands, but to prevent the larger chronology from feeling like a drafting artifact in which history happens to one shelf at a time.

Layering Rule

The timeline should normally be built in layered historical bands rather than as a flat sequence of unrelated event types.

The strongest current layering model is:

planetary and regional differentiation
species stabilization and broad ancestry fields
heartland shaping and early civilizational foundings
branch, lineage, lifeway, and design-lineage differentiation
regional interfaces and first contacts
divergences, hardenings, and secondary formations
mature contact systems, corridor orders, and institutional precedents
site-specific conflict and memory afterlives where needed

This layering matters because it keeps the timeline legible. A species should usually not jump directly from existence to dense state-like history, and a region should usually not jump directly from geographic mention to mature diplomatic or legal complexity.

Branch history follows the same rule. A living branch, lifeway, or design lineage should usually have a broad historical band: ancestral field, stabilized baseline, first heartland or order, secondary divergence, absorption or vanishing, or medieval visible layer. The people-facing version of that model is defined in Species Branch and Civilization Framework.

Parallelism Rule

The timeline should also feel historically concurrent rather than species-batched.

No broad era should imply that only one people was developing unless that is explicitly intended. When a new species, civilization, or region is added, the practical question should be what other peoples are doing during the same band, not only what comes after it.

The broad maintenance rules are:

prefer overlapping civilizational waves over clean succession waves
keep long globally quiet bands rare unless isolation, catastrophe, or geography strongly justify them
let regions mature on different schedules, but make those schedules visibly coexist
avoid the feeling that one species had history first and the others only began later because the project had not yet reached them
Silence Needs Explanation: if a species, region, or civilization is quiet across a long otherwise active historical span, that absence should usually have an in-world reason such as isolation, low density, catastrophe, archival loss, political thinness, or limited contact consequence rather than reading as an unwritten gap

Practical Date Guidance

The timeline should remain workable for later normalization.

That means:

prefer rough date ranges over unnecessary year-precision
avoid building too many hard causal chains that depend on exact short gaps unless the exactness matters
preserve relative order first and tighten exact language only where needed
use later audit and rebalance passes freely if the setting begins to feel too serialized or too empty in one band

This makes later correction feasible. A world of broad overlapping ranges is much easier to normalize than a world of brittle exact comparative dates embedded everywhere.

Expansion Guidance

Future timeline work should treat parallelism as an active design task.

When adding a major new species line, the work should usually ask what older species, side-line peoples, elder inheritances, or neighboring regions are doing in the same historical band. When adding a new regional history, the work should usually ask what species-level and civilizational-level structures already exist around it. When an era begins to feel underfilled, the preferred fix is often to add overlap rather than to force one existing line to carry the whole historical weight alone.

This framework is therefore compatible with later audit and date-shifting. The chronology should be stable enough to build on, but not treated as sacred if later work shows that the planetary history feels too serialized or too thin in one span.