Dossier Sequencing Decision

Decision ID: DECISION-DOCS-001 Status: DEFAULT-APPROVED Effective Date: 2025-12-06 48h Window Started: 2025-12-06T00:00:00Z

This decision record fixes the order in which the Stella Ops module dossiers are authored, so that documentation guilds and sprint planners work the batches in a dependency-safe sequence rather than racing on shared structure. Audience: documentation authors and planners coordinating the dossier programme.

See the Contracts index for the full catalog of contracts and decisions.

Decision

Module dossiers (Md.II through Md.X) are sequenced after Md.I completion, following the dependency chain in the corresponding SPRINT_0300SPRINT_0309 documentation sprints.

Rationale

  1. Md.I establishes baseline architecture documentation structure
  2. Subsequent modules depend on patterns defined in Md.I
  3. Sequential ordering prevents documentation conflicts
  4. Allows parallel work within each dossier batch

Sequencing Order

PhaseDossiersDependenciesSprint
Md.IConcelier, Scanner, AuthorityNone0300
Md.IIAttestor, Signer, EvidenceMd.I complete0301
Md.IIIVEX Lens, ExcititorMd.II complete0302
Md.IVPolicy, RiskMd.II complete0303
Md.VScheduler, TaskRunnerMd.IV complete0304
Md.VINotify, TelemetryMd.V complete0305
Md.VIICLI, WebMd.VI complete0306
Md.VIIIAirGap, MirrorMd.VII complete0307
Md.IXZastava, SignalsMd.VIII complete0308
Md.XIntegration, E2EAll above0309

Parallelism Rules

Within each phase, dossiers MAY be worked in parallel if:

  1. No cross-dependencies within the phase
  2. Shared components are stable
  3. Different owners/guilds assigned

Impact

Reversibility

To change the sequencing:

  1. Propose the new order as an updated revision of this decision record.
  2. Get Docs Guild sign-off.
  3. Update all affected SPRINT_03xx documentation sprints.

References