Status board reference
Repository inputs, identity rules, derived states, and failure behavior for the status board.
woostack-status computes a fresh view from Git, Graphite, and canonical GitHub data. It maintains no separate board or development ledger. Linear, Plane, and GitHub projects, issues, and work items are optional specification, plan, and fix artifacts.
Display shapes
The repository graph defines two display shapes:
- Stacks/features: Graphite-connected branches and PRs above the resolved integration base, grouped by declared plan/dependency context when available.
- Standalone work: a non-stacked branch/PR or bounded task with direct repository evidence.
A row exists because repository work exists, not because an artifact exists. Canonical repository, ref, commit SHA, PR number, head/base, and ancestry establish identity; titles and branch names are display text.
Derivation
Each status run:
- resolves the canonical repository, integration base, local branches/worktrees, and Graphite ancestry;
- fully reads candidate PRs, checks, reviews, unresolved threads, merge evidence, and timestamps;
- derives work/review/merge state from that complete snapshot;
- optionally reads exact caller-supplied Linear, Plane, or GitHub artifacts and joins only through independently verified repository/PR identity; and
- prints the current board, terminal counts, blockers, staleness, and one next action per row.
The canonical status conventions own the precise state derivation and output contract.
Authority and failure boundaries
- The active user-approved workflow defines scope and acceptance.
- Git and GitHub own source-control, PR, review, and merge truth.
- Linear, Plane, or GitHub artifacts may explain an explicitly linked spec, plan, or fix but cannot create a row, grant permission, or override repository evidence. For Plane, the repository project is reported as repository association only, exposing specification aggregate lifecycle and child increment states without presenting project lifecycle as delivery state.
- Local diagnostic reports are supporting evidence only.
Missing Graphite may degrade to Git ancestry plus GitHub with disclosure. Missing GitHub evidence
makes affected rows
unknownorblocked. Missing provider access affects only explicitly requested artifact enrichment. Status never synchronizes or mutates artifacts.
The board is a fresh repository view, not a third record system. Re-run it whenever source-control or review state changes.