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

Accept WP-0012-T04: ledger UI treatment

Browse source 
Registration form drops the ledger input entirely -- Trust Service
auto-computes the canonical /phases/{id}/ledger reference at
registration time, no human types it in v0. Schema field itself is
unaffected (still present, still federation-ready). Drill-down shows
only the raw reference + a live-data link when it resolves to this
instance; the existing Ledger entries table on phase_detail.html is
untouched and stays exactly as prominent.

All four T02-T04 decisions now feed T05's spec addendum draft.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
tegwick 2026-08-03 20:10:59 +02:00
parent 2b473c9501
commit bcba48ec51
2 changed files with 26 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

2
README.md
View file

@ -85,7 +85,7 @@ The concept's §13 now defines a **Global Contingency Share Determination Rule**
| [TREV-WP-0009](workplans/TREV-WP-0009-target-revenue-control-plane.md) | Target Revenue Control Plane — interactive UI for the `binky` tenant, incl. interactive Development Credit entry creation (`specs/TargetRevenueControlPlaneConcept.md`) — **finished**, all 4 tasks done. **T04 (interactive UI, `src/target_revenue/service/control_plane_app.py`) built on vendored `whynot-design` web components** rather than from scratch, per an explicit feasibility check |
| [TREV-WP-0010](workplans/TREV-WP-0010-development-effort-calculator.md) | Development Effort Calculator — **finished**, all 3 tasks done. Applied to the three real pilot candidates (`history/260730-EffortCalculator-CandidateApplication.md`) — every calculator-derived Initial Target came out materially lower than the earlier hand-picked placeholders, two of three carrying explicit warnings recommending manual review |
| [TREV-WP-0011](workplans/TREV-WP-0011-railiance-reef-deployment.md) | Deploy Trust Service + Control Plane to the Railiance reef, fronted by `revenue.coulomb.social` — active; T01 (deployment-pattern decision, human gate) next. Deployment alone does not authorize a real Phase go-live — that remains WP-0008-T05 |
| [TREV-WP-0012](workplans/TREV-WP-0012-phase-provenance-and-policy-modeling.md) | Phase provenance, ledger reference, and degeneration-policy modeling — active; T01–T03 done. **T02 accepted 2026-07-30**: `milestone_release` gains required `repo_hub`/`repo_hub_uri`/`repo_id`/`repo_name`, `phase.base_phase_id` optional for successive Phases; hub↔URI mapping lives in the hosted Trust Service, not this repo. **T03 accepted 2026-07-30**: `specs/policies/` + `specs/profiles/` subdirectories (one file per policy/profile, id+revision frontmatter), rendered read-only via a new lightweight server-side markdown route — not state-hub's Observable Framework build. T04 (ledger UI treatment, human gate) next |
| [TREV-WP-0012](workplans/TREV-WP-0012-phase-provenance-and-policy-modeling.md) | Phase provenance, ledger reference, and degeneration-policy modeling — active; T01–T04 done. **T02**: `milestone_release` gains required `repo_hub`/`repo_hub_uri`/`repo_id`/`repo_name`, `phase.base_phase_id` optional for successive Phases; hub↔URI mapping lives in the hosted Trust Service, not this repo. **T03**: `specs/policies/` + `specs/profiles/` subdirectories (one file per policy/profile, id+revision frontmatter), rendered read-only via a new lightweight server-side markdown route. **T04 accepted 2026-08-03**: registration form drops the `ledger` input (auto-computed), drill-down shows only the raw reference + live-data link. T05 (spec addendum draft) next |
| [TREV-WP-0013](workplans/TREV-WP-0013-remission-credit-automation.md) | Remission Credit automation (degeneration policy execution) — active; T01–T03 `wait` on WP-0012-T03's policy-spec-file decision. Nothing currently computes or writes `remission-credit` ledger entries |
| [TREV-WP-0014](workplans/TREV-WP-0014-control-plane-extensions-breach-attestation-ui.md) | Control Plane UI: Extension Registry, Breach Records, Conversion Attestation — active; T01 next. Backend for all three already exists (WP-0006); UI-only work, not blocked on WP-0012 |

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

@ -240,9 +240,11 @@ sequencing (item f, chat 2026-07-30).
```task
id: TREV-WP-0012-T04
status: todo
status: done
priority: medium
human_accept_required: true
human_accepted_by: Bernd
human_accepted_at: "2026-08-03"
state_hub_task_id: "a1cf0180-2dc7-44bb-a34f-99b5e92f5144"
```
@ -263,6 +265,28 @@ preference. Decide:
it automatically now that it is always the ledger's host in Stage 0 —
distinct from the schema question of whether the field stays.
**Result (accepted 2026-08-03):**
- The Phase registration form (`phase_new.html`) drops the `ledger`
input entirely. The Trust Service auto-computes and assigns the
canonical `/phases/{id}/ledger` reference at registration time — no
human ever types it in v0. The schema field itself is untouched by
this decision (still present, still federation-ready for a future
Phase whose ledger genuinely lives elsewhere) — this is a Control
Plane UI simplification, not a schema change, and needs no
addendum-level review of its own.
- The drill-down view shows only the raw `ledger` reference/URI as
stored in the manifest, plus — only when it resolves to this same
Trust Service instance — a link to `GET /phases/{id}/ledger`'s live
JSON. No new rendering of ledger *data*: `phase_detail.html`'s existing
Ledger entries table already covers that and stays exactly as
prominent as it is today; this decision only concerns the otherwise-
invisible raw reference string, reachable via a small "ledger
reference" link/disclosure on `phase_detail.html` rather than a
top-level field.
All four T02–T04 decisions now feed T05's spec addendum draft.
```task
id: TREV-WP-0012-T05
status: todo