Canonize work-record flavor and residual default-exclusion.
All checks were successful
CI Smoke / host-smoke (push) Successful in 1s
CI Smoke / container-smoke (push) Successful in 3s
Python Tests / pytest (push) Successful in 26s

STATE-WP-0092-T01: flavor is a closed bucket on workplans and tasks;
residuals are a flavor, not a kind, and are omitted from default open
views until demand or risk promotes them. depends_on is the workplan
frontmatter edge.
This commit is contained in:
codex 2026-09-14 15:28:58 +02:00
parent b5e4b1d97c
commit ffad21146f
6 changed files with 132 additions and 28 deletions

View file

@ -102,9 +102,10 @@ curl -s -X PATCH "http://127.0.0.1:8000/tasks/<task_id>" \
**Close:**
1. Update workplan file task statuses to reflect progress
2. If finishing a workplan: hand off **residuals** as live work records first
(intake with `origin: residual` + `origin_ref: <WP-id>`, or a next workplan /
decision / engagement). Do not park leftovers only in prose or `SCOPE.md`.
Canon: `canon/standards/work-record-types_v0.1.md` § Residuals.
(intake with `origin: residual` + `origin_ref: <WP-id>`, or a next workplan
with `flavor: residual`). Do not park leftovers only in prose or `SCOPE.md`.
Do not implement residuals unless promoted. Canon:
`canon/standards/work-record-types_v0.1.md` § Flavor.
3. Log: `POST /progress/` with a summary of what changed (name handoff ids)
4. After workplan file changes, run:
```bash
@ -206,6 +207,8 @@ owner: codex
topic_slug: ...
created: "YYYY-MM-DD"
updated: "YYYY-MM-DD"
flavor: planning | implementation | refactoring | extension | residual
depends_on: [] # workplan ids this plan waits on (STATE-WP-0092)
state_hub_workstream_id: "<uuid>" # written by fix-consistency — do not edit
---
```
@ -233,9 +236,10 @@ Status progression: `todo` → `progress` → `done`; use `wait` for waiting/blo
**Residuals when finishing:** actionable leftovers become live work records
before `status: finished` — usually an intake (`origin: residual`,
`origin_ref: CUST-WP-NNNN`) or a spawned workplan. Residual is a *role*,
not a kind. Fleet list lives on State Hub, not in `SCOPE.md`. Canon:
`canon/standards/work-record-types_v0.1.md` § Residuals.
`origin_ref: CUST-WP-NNNN`) or a spawned workplan with `flavor: residual`.
Residual is a **flavor**, not a kind. Default hub open-workplan views omit
residuals; do not implement them unless demand or risk promotes the flavor.
Canon: `canon/standards/work-record-types_v0.1.md` § Flavor.
To create a new workplan:
1. Write the file following the format above