Skip to content

[Tracking] Documentation truth-up epic — execution checklist #77

Description

@Polichinel

Tracking issue for the Documentation truth-up epic (#70). Work the stories in order; check each off as its PR merges to development.

Execution order

Dependency notes

S1 ─┬─► S2 ─┬─► S3 ──► S5 ─┐
    │       └─► S4         ├─► S6
    └───────────►          ┘
  • S1 gates everything (it's needs-decision — get the maintainer call first).
  • S2 before S3 and S4 (both link/align to the orientation doc).
  • S3 before S5 (S5 builds on the README's package-structure + terminology).
  • S6 last — it validates S2–S5 and must land green.

Conventions

  • Docs-only epic — no code/behavior changes; the S6 guardrail is the only non-prose addition.
  • Each story is its own PR → development, with the usual ritual (ruff/tests green; CI; merge; manual issue close since auto-close doesn't fire on development merges).
  • Out of scope (do not fold in here): Document post-delivery correction procedure for wrong assignments (C-22) #15 (operational data-correction procedure — needs FAO input), the C-40/frames migration, the historical cross_repo_integration_report.md / reconciliation_migration.md.

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentationepicA large capability spanning multiple stories

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions