coulomb/target-revenue
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Complete WP-0012-T01: Phase lifecycle use-cases document

Browse source 
specs/PhaseLifecycleUseCases.md enumerates all nine use cases from the
workplan systematically, grounded in the actual schema, code, and the
three real pilot-candidate manifests rather than abstractly. Two
findings surfaced beyond the original scope: first-Phase and
successive-Phase provenance turn out to be one shared modeling
question (both feed T02), and breach-record publication already has a
decided Operator+ rights tier per the Control Plane concept doc while
extension registration/canonicalization does not — recorded as an
explicit open question for WP-0014-T01 instead of an assumption.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
tegwick 2026-07-30 20:01:47 +02:00
parent bff644a4d4
commit 8e545fa965
3 changed files with 259 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

13
workplans/TREV-WP-0012-phase-provenance-and-policy-modeling.md
View file

@ -32,7 +32,7 @@ reviewed (T05).
```task
id: TREV-WP-0012-T01
status: todo
status: done
priority: high
state_hub_task_id: "2871b8ff-b845-4ed4-aaa1-8fdfd1f601b7"
```
@ -62,6 +62,17 @@ state_hub_task_id: "2871b8ff-b845-4ed4-aaa1-8fdfd1f601b7"
— call out explicitly that this use case has *no* UI surface by
design, so it doesn't get silently forgotten as "not yet built").
**Result:** `specs/PhaseLifecycleUseCases.md` written, covering all nine
use cases. Two findings worth flagging beyond the original scope: (a) use
case 2 (successive Phases) and use case 1 (first Phase) turned out to
share one underlying provenance model rather than being separate
concerns, so T02 below covers both together; (b) cross-checking
`specs/TargetRevenueControlPlaneConcept.md` §2's rights table while
writing use cases 6–7 found that breach-record publication already has a
decided rights tier (Operator+) but extension registration/canonicalization
does not — that's now recorded as an explicit open question for
WP-0014-T01 rather than something to assume while building that UI.
```task
id: TREV-WP-0012-T02
status: todo