Split TREV-WP-0009 into Control Plane (WP-0009) and Effort Calculator (WP-0010)
The two deliverables have independent formula/rights decisions and implementation arcs; keeping them in one workplan blurred that they can be reviewed and sequenced separately, even though the Control Plane's Phase-registration flow is expected to consume the Calculator's output once both exist. WP-0009 (Target Revenue Control Plane): keeps the original workstream ID, retitled and re-tasked to 3 focused tasks - rights-model decision (human gate), backend auth/audit layer, interactive UI flows. WP-0010 (Development Effort Calculator, new): 3 tasks - formula decision (human gate), implementation, application to the real candidate repos already identified in WP-0008. No real Phase declaration in either workplan's scope. Updated both concept documents' workplan cross-references and README.md's summary table accordingly.
This commit is contained in:
parent
5cca55fcc9
commit
7c2e33bc31
6 changed files with 214 additions and 141 deletions
|
|
@ -2,7 +2,7 @@
|
|||
|
||||
Status: Concept v0.1
|
||||
Date: 2026-07-30
|
||||
Workplan: `workplans/TREV-WP-0009-control-plane-and-effort-calculator.md`
|
||||
Workplan: `workplans/TREV-WP-0009-target-revenue-control-plane.md`
|
||||
Primary artifacts: `specs/TrustServiceProductRequirementsDocument.md`, `src/target_revenue/service/app.py`, `specs/TRSL-Governance.md` §1 (Licensor identity), `scripts/trf_onboard.py`
|
||||
|
||||
**Scope note:** this is a concept, not an implementation. It defines what
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue