Skip to main content

Multi-State Generation Plan

This plan defines how TraderX evolves through numbered states with explicit convergence checkpoints.

Objectives​

  • keep each transition reproducible from specs,
  • keep generated branches compareable and publishable,
  • isolate FR/NFR deltas per state,
  • preserve a clear set of recommended jump-off points (C0-C3).

Transition Mechanics​

  1. Update target state pack (spec.md, plan.md, tasks.md, system/**).
  2. Generate parent state.
  3. Apply ordered patch set (specs/<state>/generation/patches/*.patch) for derived changes.
  4. Regenerate architecture docs.
  5. Run state smoke tests + global gates.
  6. Publish code snapshot branch.

Current Convergence-First Model​

Publish Model​

  • Canonical authoring stays in this branch (specs/**, .specify/**, pipeline/docs).
  • Generated code snapshots are published to code/generated-state-* branches.
  • Publish ancestry follows previous only.
  • Dotted-line parents are docs lineage only.

Required Governance for Convergence States​

  • catalog/state-catalog.json must carry convergence metadata.
  • system/convergence-rationale.md must exist and be updated when convergence state content/metadata changes.
  • CI gates must pass before publish.

Reference Commands​

bash pipeline/refresh-state-docs.sh
bash pipeline/verify-spec-coverage.sh
bash pipeline/publish-generated-state-branch.sh <state-id> --push