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

chore(consistency): sync task status from DB [auto]

Browse source 
Updated by fix-consistency on 2026-08-05:
  - update .custodian-brief.md for target-revenue
This commit is contained in:
custodian-sync 2026-08-05 15:59:58 +02:00
parent fdb59efbc3
commit f56d82f09a
8 changed files with 200 additions and 121 deletions
Download patch file Download diff file Expand all files Collapse all files

8
.custodian-brief.md
View file

@ -2,17 +2,11 @@
# Custodian Brief — target-revenue # Custodian Brief — target-revenue
**Domain:** infotech **Domain:** infotech
**Last synced:** 2026-08-05 13:33 UTC **Last synced:** 2026-08-05 13:59 UTC
**State Hub:** http://127.0.0.1:8000 *(adjust if running on a remote machine)* **State Hub:** http://127.0.0.1:8000 *(adjust if running on a remote machine)*
## Active Workstreams ## Active Workstreams
### Governance formalization and pilot rollout (coulomb / net-kingdom / helix-forge / railiance)
Progress: 4/5 done | workplan_id: `b46a30e8-8ef6-44f7-96af-a098cb4084b4`
**Open tasks:**
- · Go-live gate (human decision) `af688189`
### Deploy Trust Service and Control Plane to the Railiance reef ### Deploy Trust Service and Control Plane to the Railiance reef
Progress: 0/5 done | workplan_id: `f40fa906-9fbc-4445-9ebc-62ec46ac17b5` Progress: 0/5 done | workplan_id: `f40fa906-9fbc-4445-9ebc-62ec46ac17b5`

6
README.md
View file

@ -84,13 +84,13 @@ The concept's §13 now defines a **Global Contingency Share Determination Rule**
| [TREV-WP-0005](workplans/TREV-WP-0005-enforcement-network-research.md) | Enforcement Network legal feasibility research — **finished**, T10 synthesis accepted 2026-07-29 on the same alpha/beta basis (Japan's Article 12 risk remains explicitly unresolved) | | [TREV-WP-0005](workplans/TREV-WP-0005-enforcement-network-research.md) | Enforcement Network legal feasibility research — **finished**, T10 synthesis accepted 2026-07-29 on the same alpha/beta basis (Japan's Article 12 risk remains explicitly unresolved) |
| [TREV-WP-0006](workplans/TREV-WP-0006-trust-service-implementation.md) | Hosted Trust Service reference implementation (PRD Phase 4b) — **finished**, all 9 tasks done (Postgres-backed registries/ledger/metrics/attestation/breach-record, ADR-0002 accepted, onboarding CLI, hosted conformance suite) | | [TREV-WP-0006](workplans/TREV-WP-0006-trust-service-implementation.md) | Hosted Trust Service reference implementation (PRD Phase 4b) — **finished**, all 9 tasks done (Postgres-backed registries/ledger/metrics/attestation/breach-record, ADR-0002 accepted, onboarding CLI, hosted conformance suite) |
| [TREV-WP-0007](workplans/TREV-WP-0007-degeneration-policy-and-canonical-profiles.md) | Degeneration policy + canonical monetization profile catalog — **finished**, all 4 tasks done. `trsl:policy:linear-longstop-v0` confirmed 2026-07-29 as the v1 norm for the first pilot cohort; `progress-paused-longstop-v1` named as the next iteration, not yet adopted | | [TREV-WP-0007](workplans/TREV-WP-0007-degeneration-policy-and-canonical-profiles.md) | Degeneration policy + canonical monetization profile catalog — **finished**, all 4 tasks done. `trsl:policy:linear-longstop-v0` confirmed 2026-07-29 as the v1 norm for the first pilot cohort; `progress-paused-longstop-v1` named as the next iteration, not yet adopted |
| [TREV-WP-0008](workplans/TREV-WP-0008-governance-and-pilot-rollout.md) | Governance formalization + pilot rollout — active; T01–T04 done. `info-tech-canon` dry-run onboarding routine exercised end-to-end 2026-07-29. **Org-wide TRSL license adoption executed 2026-07-30** across ~90 `coulomb`-org repos (`history/260730-TRSL-OrgWideLicenseRollout.md`) — a license-text adoption, not a Phase declaration. T05 (real Phase go-live gate) remains `todo` by design; no Phase exists yet for any repo | | [TREV-WP-0008](workplans/TREV-WP-0008-governance-and-pilot-rollout.md) | Governance formalization + pilot rollout — **finished**, all 5 tasks done. **T05 accepted 2026-08-05**: first real Phase is `trsl:phase:info-tech-canon-service-surface` (`history/260805-T05-GoLive-info-tech-canon.md`). Org-wide TRSL LICENSE adoption (2026-07-30) was a prior, separate act |
| [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-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-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-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 — **finished**, all 5 tasks done. Decisions (T02–T04) synthesized into [`specs/PhaseProvenanceSpecAddendum.md`](specs/PhaseProvenanceSpecAddendum.md) (T05) — **not yet accepted for implementation**; that's the document to discuss before any schema/UI work is filed as its own workplan | | [TREV-WP-0012](workplans/TREV-WP-0012-phase-provenance-and-policy-modeling.md) | Phase provenance, ledger reference, and degeneration-policy modeling — **finished**, all 5 tasks done. Decisions (T02–T04) synthesized into [`specs/PhaseProvenanceSpecAddendum.md`](specs/PhaseProvenanceSpecAddendum.md) (T05) — **not yet accepted for implementation**; that's the document to discuss before any schema/UI work is filed as its own workplan |
| [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-0013](workplans/TREV-WP-0013-remission-credit-automation.md) | Remission Credit automation (degeneration policy execution) — **finished**, all 3 tasks done. Pure `plan_remission` + hosted apply with `system:policy-engine` actor; monthly UTC schedule; Control Plane forecast + apply button |
| [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 | | [TREV-WP-0014](workplans/TREV-WP-0014-control-plane-extensions-breach-attestation-ui.md) | Control Plane UI: Extension Registry, Breach Records, Conversion Attestation — **finished**, all 4 tasks done. Operator+ register extension / Admin canonicalize; breach form with anonymized-by-default; attestation on phase detail |
| [TREV-WP-0015](workplans/TREV-WP-0015-phase-provenance-implementation.md) | Implement `specs/PhaseProvenanceSpecAddendum.md` — **finished**, all 7 tasks done. Phase provenance fields, `specs/policies/`/`specs/profiles/` extraction, reference-rendering routes, ledger UI change, and the `forgejo_hubs` registry are all in place | | [TREV-WP-0015](workplans/TREV-WP-0015-phase-provenance-implementation.md) | Implement `specs/PhaseProvenanceSpecAddendum.md` — **finished**, all 7 tasks done. Phase provenance fields, `specs/policies/`/`specs/profiles/` extraction, reference-rendering routes, ledger UI change, and the `forgejo_hubs` registry are all in place |
Hub index: [`WORK-RECORDS.md`](WORK-RECORDS.md) · brief: [`.custodian-brief.md`](.custodian-brief.md) Hub index: [`WORK-RECORDS.md`](WORK-RECORDS.md) · brief: [`.custodian-brief.md`](.custodian-brief.md)

25
SCOPE.md
View file

@ -4,8 +4,8 @@
**Authority:** Describes what is actually in design or delivery *now*. **Authority:** Describes what is actually in design or delivery *now*.
**Counterpart:** [`INTENT.md`](INTENT.md) is stable and aspirational. A gap between INTENT and this file is expected and is a maturity signal, not a defect. **Counterpart:** [`INTENT.md`](INTENT.md) is stable and aspirational. A gap between INTENT and this file is expected and is a maturity signal, not a defect.
**Last updated:** 2026-07-29 **Last updated:** 2026-08-05
**Basis:** SWOT recommendations in `history/260728-SWOT-Assessment.md`; updated per §6's own trigger ("first hosted Trust Service pilot authorized") now that WP-0001/0002/0003 are finished and WP-0006/0007/0008 have started. **Basis:** SWOT recommendations in `history/260728-SWOT-Assessment.md`; first real Phase declared 2026-08-05 under WP-0008-T05 (`history/260805-T05-GoLive-info-tech-canon.md`).
--- ---
@ -14,11 +14,12 @@
| Label | Meaning | | Label | Meaning |
| --- | --- | | --- | --- |
| **Stage 0 — finished** | Concept consolidated (WP-0003); Stage 0 schema/fold foundation finished (WP-0002); TRSL/CUA V1C1 accepted 2026-07-29 as counsel-briefing material (WP-0001) — not yet production legal text. | | **Stage 0 — finished** | Concept consolidated (WP-0003); Stage 0 schema/fold foundation finished (WP-0002); TRSL/CUA V1C1 accepted 2026-07-29 as counsel-briefing material (WP-0001) — not yet production legal text. |
| **Stage 1 — active** | Hosted Trust Service (WP-0006), degeneration/canonical-profile finalization (WP-0007), and governance + pilot rollout preparation (WP-0008) across the `coulomb` Forgejo org's product lines (`coulomb-loop`, `net-kingdom`, `helix-forge`, `railiance-*`). | | **Stage 1 — pilot** | First real Phase declared 2026-08-05: `trsl:phase:info-tech-canon-service-surface` on `coulomb/info-tech-canon` (`history/260805-T05-GoLive-info-tech-canon.md`). Hosted Trust Service software finished (WP-0006); public reef deploy still WP-0011. |
| Trust Service federation | Stages 1–6 from concept §15 are **out of current delivery scope** (design readiness only) — unrelated to this document's "Stage 0/1" labels, which track this repo's own maturity, not the Trust Service's federation roadmap. | | Trust Service federation | Stages 1–6 from concept §15 are **out of current delivery scope** (design readiness only) — unrelated to this document's "Stage 0/1" labels, which track this repo's own maturity, not the Trust Service's federation roadmap. |
| Legal TRSL/CUA | Accepted as counsel-briefing material, still **not production legal text** — specialist legal review (License/CUA Appendix A condition 1) remains required before any real Phase; see `workplans/TREV-WP-0008-governance-and-pilot-rollout.md` T05. | | Legal TRSL/CUA | Accepted as counsel-briefing material, still **not production legal text**. Pilot Phases operate under the alpha/beta legal-review deferral with an **explicit pilot scope** recorded at T05 (`history/260805-T05-GoLive-info-tech-canon.md` §1). |
| Alpha/beta legal-review deferral | **Maintainer decision, 2026-07-29**: full specialist legal review of the TRSL/CUA (condition 1 above) is explicitly postponed until the framework moves out of beta, since legal and commercial exposure during build/alpha is limited and the License/CUA will be revised on stakeholder/customer feedback before the legal framework settles. This closed `workplans/TREV-WP-0004-global-jurisdiction-research.md` and `workplans/TREV-WP-0005-enforcement-network-research.md` with a synthesis of alpha/beta working defaults (governing law/arbitration, liability cap, data protection, Enforcement Network fee mechanics) rather than full resolution — see `history/260729-TRSL-Jurisdiction-Synthesis.md` §3 and `history/260729-TREN-Synthesis.md` for exactly what is and is not covered by this deferral. It does **not** waive WP-0008-T05's other preconditions (Licensor identity, hosted Trust Service), and it does **not** mean the legal framework is finished — only that it is judged sufficient to operate pilot-stage Phases under bounded, known risk. | | Alpha/beta legal-review deferral | **Maintainer decision, 2026-07-29**: full specialist legal review of the TRSL/CUA is postponed until out of beta. **T05 (2026-08-05)** confirmed this waiver covers the first pilot Phase only (info-tech-canon service surface), under the jurisdiction/Enforcement Network alpha/beta working defaults — not all product lines forever. |
| Org-wide license adoption | **Maintainer decision, 2026-07-30**: TRSL V1C1 adopted as the preliminary `LICENSE` across every repo in the `coulomb` Forgejo org (see `history/260730-TRSL-OrgWideLicenseRollout.md`) — one flagged exception (`the-custodian`, pre-existing proprietary/confidential license, not touched pending separate confirmation). **This is a license-text adoption, not a Phase declaration** — no Initial Target, Trust Service registration, or Development Credit tracking exists for any repo as a result; `workplans/TREV-WP-0008-governance-and-pilot-rollout.md` T05 remains unaccepted. | | Org-wide license adoption | **Maintainer decision, 2026-07-30**: TRSL V1C1 as preliminary `LICENSE` across the `coulomb` Forgejo org (`history/260730-TRSL-OrgWideLicenseRollout.md`). Distinct from Phase declaration. |
| First Phase declaration | **Maintainer decision, 2026-08-05**: WP-0008-T05 accepted; first Phase is `trsl:phase:info-tech-canon-service-surface`. |
--- ---
@ -55,14 +56,14 @@
| Item | Status | | Item | Status |
| --- | --- | | --- | --- |
| Hosted Trust Service *implementation* | **In scope now** — `workplans/TREV-WP-0006-trust-service-implementation.md`, active | | Hosted Trust Service *implementation* | **In scope now** — `workplans/TREV-WP-0006-trust-service-implementation.md`, active |
| Hosted Trust Service *accepting real production data* | Still out of scope until WP-0008-T05 | | Hosted Trust Service *accepting pilot Phase data* | **In scope now** for the T05 pilot Phase (local pilot instance; public reef still WP-0011) |
| Finalized legal license text and commercial agreements | TRSL/CUA V1C1 accepted as counsel-briefing material (WP-0001); specialist legal review still outstanding | | Finalized legal license text and commercial agreements | TRSL/CUA V1C1 still preliminary; pilot operates under alpha/beta waiver + T05 scope record |
| Final degeneration formula as irreversible norm | **In scope now** — `workplans/TREV-WP-0007-degeneration-policy-and-canonical-profiles.md`, active | | Final degeneration formula as irreversible norm | v1 norm `linear-longstop-v0` adopted (WP-0007); automation implemented (WP-0013) |
| Federation Stage 2+ (replication, multi-operator, multi-authority) | PRD Roadmap Phase 6 — still deferred | | Federation Stage 2+ (replication, multi-operator, multi-authority) | PRD Roadmap Phase 6 — still deferred |
| Governance formalization *document* | **In scope now** — `workplans/TREV-WP-0008-governance-and-pilot-rollout.md` T01, active | | Governance formalization *document* | Done — `specs/TRSL-Governance.md` (WP-0008-T01) |
| Tax / statutory revenue recognition | Permanently out of framework core (INTENT boundaries) | | Tax / statutory revenue recognition | Permanently out of framework core (INTENT boundaries) |
| Governing third-party product Phases in production (real Phase declarations, real Commercial Entitlements sold) | **Still out of scope** — gated behind `workplans/TREV-WP-0008-governance-and-pilot-rollout.md` T05 (legal review + Licensor governance decision) | | Additional product-line Phase declarations beyond the first pilot | **Not auto-authorized** — each further Phase is a deliberate declaration act; T05 named only `info-tech-canon` |
| Accepting external code into a governed Milestone Release | Until contributor-rights instrument exists — draft in progress, `workplans/TREV-WP-0008-governance-and-pilot-rollout.md` T04 | | Accepting external code into a governed Milestone Release | Until CLA is accepted — draft exists (WP-0008-T04); block remains in `CONTRIBUTING.md` |
--- ---

18
WORK-RECORDS.md
View file

@ -20,8 +20,8 @@
| workplan | TREV-WP-0010 | finished | — | workplans/TREV-WP-0010-development-effort-calculator.md | | workplan | TREV-WP-0010 | finished | — | workplans/TREV-WP-0010-development-effort-calculator.md |
| workplan | TREV-WP-0011 | active | — | workplans/TREV-WP-0011-railiance-reef-deployment.md | | workplan | TREV-WP-0011 | active | — | workplans/TREV-WP-0011-railiance-reef-deployment.md |
| workplan | TREV-WP-0012 | finished | — | workplans/TREV-WP-0012-phase-provenance-and-policy-modeling.md | | workplan | TREV-WP-0012 | finished | — | workplans/TREV-WP-0012-phase-provenance-and-policy-modeling.md |
| workplan | TREV-WP-0013 | active | — | workplans/TREV-WP-0013-remission-credit-automation.md | | workplan | TREV-WP-0013 | finished | — | workplans/TREV-WP-0013-remission-credit-automation.md |
| workplan | TREV-WP-0014 | active | — | workplans/TREV-WP-0014-control-plane-extensions-breach-attestation-ui.md | | workplan | TREV-WP-0014 | finished | — | workplans/TREV-WP-0014-control-plane-extensions-breach-attestation-ui.md |
| workplan | TREV-WP-0015 | finished | — | workplans/TREV-WP-0015-phase-provenance-implementation.md | | workplan | TREV-WP-0015 | finished | — | workplans/TREV-WP-0015-phase-provenance-implementation.md |
| task | TREV-WP-0001-T01 | done | — | workplans/TREV-WP-0001-license-prior-art-research.md | | task | TREV-WP-0001-T01 | done | — | workplans/TREV-WP-0001-license-prior-art-research.md |
| task | TREV-WP-0001-T02 | done | — | workplans/TREV-WP-0001-license-prior-art-research.md | | task | TREV-WP-0001-T02 | done | — | workplans/TREV-WP-0001-license-prior-art-research.md |
@ -96,13 +96,13 @@
| task | TREV-WP-0012-T03 | done | — | workplans/TREV-WP-0012-phase-provenance-and-policy-modeling.md | | task | TREV-WP-0012-T03 | done | — | workplans/TREV-WP-0012-phase-provenance-and-policy-modeling.md |
| task | TREV-WP-0012-T04 | done | — | workplans/TREV-WP-0012-phase-provenance-and-policy-modeling.md | | task | TREV-WP-0012-T04 | done | — | workplans/TREV-WP-0012-phase-provenance-and-policy-modeling.md |
| task | TREV-WP-0012-T05 | done | — | workplans/TREV-WP-0012-phase-provenance-and-policy-modeling.md | | task | TREV-WP-0012-T05 | done | — | workplans/TREV-WP-0012-phase-provenance-and-policy-modeling.md |
| task | TREV-WP-0013-T01 | wait | — | workplans/TREV-WP-0013-remission-credit-automation.md | | task | TREV-WP-0013-T01 | done | — | workplans/TREV-WP-0013-remission-credit-automation.md |
| task | TREV-WP-0013-T02 | wait | — | workplans/TREV-WP-0013-remission-credit-automation.md | | task | TREV-WP-0013-T02 | done | — | workplans/TREV-WP-0013-remission-credit-automation.md |
| task | TREV-WP-0013-T03 | wait | — | workplans/TREV-WP-0013-remission-credit-automation.md | | task | TREV-WP-0013-T03 | done | — | workplans/TREV-WP-0013-remission-credit-automation.md |
| task | TREV-WP-0014-T01 | todo | — | workplans/TREV-WP-0014-control-plane-extensions-breach-attestation-ui.md | | task | TREV-WP-0014-T01 | done | — | workplans/TREV-WP-0014-control-plane-extensions-breach-attestation-ui.md |
| task | TREV-WP-0014-T02 | todo | — | workplans/TREV-WP-0014-control-plane-extensions-breach-attestation-ui.md | | task | TREV-WP-0014-T02 | done | — | workplans/TREV-WP-0014-control-plane-extensions-breach-attestation-ui.md |
| task | TREV-WP-0014-T03 | todo | — | workplans/TREV-WP-0014-control-plane-extensions-breach-attestation-ui.md | | task | TREV-WP-0014-T03 | done | — | workplans/TREV-WP-0014-control-plane-extensions-breach-attestation-ui.md |
| task | TREV-WP-0014-T04 | todo | — | workplans/TREV-WP-0014-control-plane-extensions-breach-attestation-ui.md | | task | TREV-WP-0014-T04 | done | — | workplans/TREV-WP-0014-control-plane-extensions-breach-attestation-ui.md |
| task | TREV-WP-0015-T01 | done | — | workplans/TREV-WP-0015-phase-provenance-implementation.md | | task | TREV-WP-0015-T01 | done | — | workplans/TREV-WP-0015-phase-provenance-implementation.md |
| task | TREV-WP-0015-T02 | done | — | workplans/TREV-WP-0015-phase-provenance-implementation.md | | task | TREV-WP-0015-T02 | done | — | workplans/TREV-WP-0015-phase-provenance-implementation.md |
| task | TREV-WP-0015-T03 | done | — | workplans/TREV-WP-0015-phase-provenance-implementation.md | | task | TREV-WP-0015-T03 | done | — | workplans/TREV-WP-0015-phase-provenance-implementation.md |

42
examples/pilot-candidates/README.md
View file

@ -1,34 +1,22 @@
# Pilot candidate Phase Manifests — DRAFT, NOT DECLARED # Pilot candidate Phase Manifests
These manifests are **draft, non-binding worked examples** These manifests began as **draft, non-binding worked examples**
(`workplans/TREV-WP-0008-governance-and-pilot-rollout.md` T03), following (`workplans/TREV-WP-0008-governance-and-pilot-rollout.md` T03). They keep
the pattern established by `examples/phase-001/`. They are structurally a `draft-` phase id prefix so they are never confused with a declared
valid and conformance-tested exactly like `examples/phase-001/`, but: Phase.
- **No Commercial Entitlement is for sale under either manifest.** **Go-live 2026-08-05:** T05 accepted the first **real** Phase for
- **No Development Credit is being tracked for either candidate.** `info-tech-canon` — the authoritative declaration lives in that repo at
- **Neither repo's actual License header has been changed to TRSL.** `trf/phase-service-surface.json` as
- `phase.id` uses a `draft-` prefix specifically so it cannot be confused `trsl:phase:info-tech-canon-service-surface` (not the draft file here).
with a real, declared Phase. Full record: `history/260805-T05-GoLive-info-tech-canon.md`.
Built from the two candidates identified with a defensible rationale in The draft directories below remain as historical worked examples for
`specs/PilotPhaseCandidateSurvey.md` (T02) — `coulomb-loop` and candidates that are **not** yet declared:
`helix-forge` produced no defensible candidate at survey time and are
not represented here.
**`info-tech-canon` (2026-07-29):** the maintainer chose `info-tech-canon` - **No Commercial Entitlement is for sale under the draft manifests.**
as the actual first repo to build up the practical Phase-declaration - **`net-kingdom` and `railiance-vergabe-teilnahme` drafts are still not
routine on, explicitly as a **dry run, not a go-live decision** declared** — T05 authorized only the info-tech-canon Phase.
(confirmed directly, not assumed) — see
`specs/PilotPhaseCandidateSurvey.md` §5 for the candidate rationale. This
repo was outside the original four product lines T02 surveyed; its
candidate was added afterward as this specific, real routine-building
exercise, not a T02 survey gap.
**Nothing here is authorized to go live.** That remains gated behind
`workplans/TREV-WP-0008-governance-and-pilot-rollout.md` T05, regardless
of how complete or plausible these examples look — including
`info-tech-canon`, which was explicitly confirmed as dry-run-only.
| Directory | Product line | Candidate deliverable | Indicative Target Multiple | | Directory | Product line | Candidate deliverable | Indicative Target Multiple |
|---|---|---|---| |---|---|---|---|

119
history/260805-T05-GoLive-info-tech-canon.md Normal file
View file

@ -0,0 +1,119 @@
# WP-0008-T05 Go-Live — first real Phase: info-tech-canon
**Date:** 2026-08-05
**Decision:** Maintainer accepted `workplans/TREV-WP-0008-governance-and-pilot-rollout.md` T05.
**First declared Phase:** `trsl:phase:info-tech-canon-service-surface`
**Declaring repo:** `coulomb/info-tech-canon` (Forgejo id 47)
This is the single recorded go-live moment the gate existed to create — not
"infrastructure is ready," but **a named Phase is authorized and declared**.
---
## 1. Pilot scope covered by the alpha/beta legal waiver
Per `SCOPE.md` §1, full specialist legal review of TRSL/CUA V1C1 is deferred
until the framework moves out of beta. T05 acceptance confirms that this
waiver covers the following **pilot scope** only:
| Dimension | Pilot scope |
| --- | --- |
| Licensor | Binky Hedgehog GmbH / Trust Service tenant `binky` (`specs/TRSL-Governance.md` §1) |
| First Phase | `trsl:phase:info-tech-canon-service-surface` on `coulomb/info-tech-canon` only |
| Legal text | TRSL V1C1 + CUA V1C1 as preliminary candidates under the existing alpha/beta working defaults (`history/260729-TRSL-Jurisdiction-Synthesis.md` §3, `history/260729-TREN-Synthesis.md`) — governing law/arbitration, liability cap, data protection, Enforcement Network fee mechanics as synthesized, not as counsel-finalized production terms |
| Commercial activity | Development Credit may be tracked for this Phase; Commercial Entitlements under this Phase may be granted only under the same alpha/beta risk acceptance |
| External contributions | **Still blocked** — CLA remains draft (`specs/TRSL-ContributorLicenseAgreement-Draft.md`); `CONTRIBUTING.md` external-contribution block remains in force until CLA is separately accepted |
| Other product lines | **Not** authorized by this T05 acceptance. `net-kingdom`, `railiance-vergabe-teilnahme`, and any further Phases each need an explicit follow-on declaration (same process; not a second T05 gate for the framework, but a deliberate Phase-by-Phase act) |
This is **not** a waiver of all risk forever, and **not** production legal
finality. It is a bounded pilot under known, already-documented alpha/beta
defaults.
---
## 2. Preconditions re-confirmed at acceptance
| Precondition | Status at go-live |
| --- | --- |
| WP-0004 / WP-0005 T10 syntheses | Done 2026-07-29 |
| Legal review waiver + pilot scope (this document §1) | Accepted 2026-08-05 |
| Licensor identity | Binky Hedgehog GmbH / `binky` |
| Hosted Trust Service software (WP-0006) | Done; pilot instance registered below |
| Draft survey + candidates (T02/T03) | Done; first live Phase is the former dry-run candidate |
| CLA | Draft only; external contribs remain blocked |
| Org-wide TRSL LICENSE text adoption | Already done 2026-07-30; `info-tech-canon` already carried TRSL V1C1 at go-live (no MIT-0 replacement step remained) |
---
## 3. Phase parameters (declared)
| Field | Value |
| --- | --- |
| `phase.id` | `trsl:phase:info-tech-canon-service-surface` |
| Milestone | `info-tech-canon-service-surface-v1 (ITC-WP-0001..0012)` |
| `source_revision` | `bd656d45165db3e49b971850d7d9487d41c76cc5` |
| Repo | `forgejo-coulomb` / id 47 / `coulomb/info-tech-canon` |
| Initial Target | **141,800 EUR** |
| Target Multiple | 100 (Product-defining) |
| Future License | MIT |
| Degeneration policy | `trsl:policy:linear-longstop-v0@1.0` |
| Longstop | 2029-01-01T00:00:00Z |
| Extension | `trsl:extension:development-license@1.0` |
**Initial Target caveat:** figure is the effort-calculator output from
`history/260730-EffortCalculator-CandidateApplication.md` §4, which
carries a sanity-check warning (12 finished workplans / 51 tasks vs ~1.42
raw days — likely under-count). Accepted for pilot as the transparent
calculator figure rather than a silent manual override; a versioned
correction remains available if pilot experience shows the target is
unworkable.
**Repo-local durable copy:** `info-tech-canon/trf/phase-service-surface.json`
(committed in that repo).
---
## 4. Trust Service registration (pilot instance)
Production reef deployment (`revenue.coulomb.social`, WP-0011) was **not**
ready at go-live. Registration used a dedicated **local pilot Trust
Service** instance so the Phase is live in a real Postgres-backed ledger
from day one, not merely a git file:
| Item | Value |
| --- | --- |
| Trust Service API | `http://127.0.0.1:8765` (local pilot; not public) |
| Postgres | Docker container `trf-pilot-pg`, port `127.0.0.1:55432`, volume `trf-pilot-pgdata` |
| Migrations | 0001–0007 applied |
| Licensor credential | `binky` / label `pilot-founder` (token in `~/.config/target-revenue/pilot-binky.token`, never committed) |
| Registration time (t0) | 2026-08-05T13:57:18Z (host `registered_at`) |
| Extension registered | `trsl:extension:development-license@1.0` |
| Ledger at registration | empty; Outstanding Target = 141,800 EUR |
When WP-0011 lands a public instance, this Phase's Manifest and ledger
export must be migrated or re-anchored deliberately — the git-committed
Manifest remains the durable declaration either way
(`specs/TrustServiceOnboarding.md` §1).
---
## 5. Explicitly not done by this go-live
- Selling Commercial Entitlements at scale or marketing TRSL as
production-final legal text
- Accepting external contributions into the governed Milestone Release
- Declaring Phases for `net-kingdom`, `railiance-*`, or any other repo
- Deploying Trust Service / Control Plane to Railiance (`WP-0011`)
- Accepting the CLA draft
---
## 6. How to verify offline
```bash
# From target-revenue:
python scripts/trf_onboard.py validate ../info-tech-canon/trf/phase-service-surface.json
python scripts/trf_onboard.py status \
--url http://127.0.0.1:8765 \
--phase-id trsl:phase:info-tech-canon-service-surface
```

6
src/target_revenue/service/control_plane_templates/base.html
View file

@ -31,6 +31,7 @@
Signed in as <strong>{{ session_credential_label }}</strong> Signed in as <strong>{{ session_credential_label }}</strong>
({{ session_rights }}) for <strong>{{ session_licensor_id }}</strong> ({{ session_rights }}) for <strong>{{ session_licensor_id }}</strong>
&middot; <a href="/">Dashboard</a> &middot; <a href="/">Dashboard</a>
&middot; <a href="/extensions">Extensions</a>
{% if session_rights in ("operator", "admin") %}&middot; <a href="/proposals">Proposals</a>{% endif %} {% if session_rights in ("operator", "admin") %}&middot; <a href="/proposals">Proposals</a>{% endif %}
{% if session_rights == "admin" %}&middot; <a href="/admin/credentials">Credentials</a>{% endif %} {% if session_rights == "admin" %}&middot; <a href="/admin/credentials">Credentials</a>{% endif %}
&middot; <a href="/audit">Audit log</a> &middot; <a href="/audit">Audit log</a>
@ -45,8 +46,9 @@
{% block content %}{% endblock %} {% block content %}{% endblock %}
<p style="margin-top:3rem;color:#888;font-size:0.85rem;"> <p style="margin-top:3rem;color:#888;font-size:0.85rem;">
This is a dry-run/pilot tool. No real Phase is authorized to go live via Pilot Control Plane (alpha/beta). First declared Phase:
this interface — see <code>workplans/TREV-WP-0008-governance-and-pilot-rollout.md</code> T05. <code>trsl:phase:info-tech-canon-service-surface</code>
(WP-0008-T05, 2026-08-05). Further Phases require an explicit declaration act.
Visual language vendored from <code>whynot-design</code> — see Visual language vendored from <code>whynot-design</code> — see
<code>static/whynot-design/VENDORED.md</code>. <code>static/whynot-design/VENDORED.md</code>.
</p> </p>

97
workplans/TREV-WP-0008-governance-and-pilot-rollout.md
View file

@ -4,11 +4,11 @@ type: workplan
title: "Governance formalization and pilot rollout (coulomb / net-kingdom / helix-forge / railiance)" title: "Governance formalization and pilot rollout (coulomb / net-kingdom / helix-forge / railiance)"
domain: infotech domain: infotech
repo: target-revenue repo: target-revenue
status: active status: finished
owner: claude owner: claude
topic_slug: infotech topic_slug: infotech
created: "2026-07-29" created: "2026-07-29"
updated: "2026-07-29" updated: "2026-08-05"
state_hub_workstream_id: "b46a30e8-8ef6-44f7-96af-a098cb4084b4" state_hub_workstream_id: "b46a30e8-8ef6-44f7-96af-a098cb4084b4"
--- ---
@ -219,70 +219,45 @@ merely drafted.
```task ```task
id: TREV-WP-0008-T05 id: TREV-WP-0008-T05
status: todo status: done
priority: high priority: high
human_accept_required: true human_accept_required: true
human_accepted_by: Bernd
human_accepted_at: "2026-08-05"
state_hub_task_id: "af688189-8151-4170-925f-b3c4806a68ed" state_hub_task_id: "af688189-8151-4170-925f-b3c4806a68ed"
``` ```
**Do not mark this task done to authorize real Phase declarations.** It **Go-live gate — accepted 2026-08-05.** Full decision record:
exists to make the go-live decision a single, explicit, recorded moment `history/260805-T05-GoLive-info-tech-canon.md`.
rather than something that happens by accretion once enough pilot
infrastructure exists. Before acceptance, confirm:
- `workplans/TREV-WP-0004-global-jurisdiction-research.md` T10 and **First real Phase (named by this acceptance):**
`workplans/TREV-WP-0005-enforcement-network-research.md` T10 syntheses
are complete — **done** (both finished 2026-07-29; see
`history/260729-TRSL-Jurisdiction-Synthesis.md` and
`history/260729-TREN-Synthesis.md`);
- specialist legal review of `specs/TargetRevenueSourceLicense-V1C1.md`
and `specs/TargetRevenueCommercialUseAgreement-V1C1.md` (condition 1 in
each document's status banner) has occurred, or is explicitly waived for
a defined pilot scope — **the maintainer has already waived full review
until out of beta** (`SCOPE.md` §1, 2026-07-29); T05 acceptance still
requires confirming the specific pilot scope this waiver covers and that
the alpha/beta working defaults adopted by the two syntheses above
(governing law/arbitration, liability cap, data protection, Enforcement
Network fee mechanics) are acceptable for that scope — this is not
automatically satisfied by the waiver existing in the abstract;
- T01's Licensor-identity question is resolved for whichever product
line goes first — **done** (Binky Hedgehog GmbH / `binky` tenant, single
shared Licensor across all product lines, `specs/TRSL-Governance.md` §1);
- `workplans/TREV-WP-0006-trust-service-implementation.md` has a working
hosted Trust Service, or an explicit interim manual/git-based ledger
process is accepted for the pilot instead — **done** (WP-0006 finished,
all 9 tasks, Postgres-backed hosted service per ADR-0002);
- T02's candidate survey and T03's draft manifests exist for the chosen
product line — **done** (`specs/PilotPhaseCandidateSurvey.md`,
`examples/pilot-candidates/`), though drafting a non-binding example
is not the same event as this gate's own acceptance;
- if the chosen Phase expects external contributions before its
Conversion Event, T04's CLA (`specs/TRSL-ContributorLicenseAgreement-Draft.md`)
has been reviewed and, if needed for that Phase, accepted — **drafted,
not yet accepted**; `CONTRIBUTING.md`'s external-contribution block
remains in effect until it is.
Once accepted, this task's Result should name which specific repo and | | |
Phase go live first — "governance and rollout infrastructure exists" is | --- | --- |
not the same event as "a real Phase is declared," and this workplan should | Repo | `coulomb/info-tech-canon` (Forgejo id 47) |
not blur that line even after everything above is ready. | Phase id | `trsl:phase:info-tech-canon-service-surface` |
| Manifest (repo) | `info-tech-canon/trf/phase-service-surface.json` |
| Initial Target | 141,800 EUR |
| Future License | MIT |
| Longstop | 2029-01-01T00:00:00Z |
| Policy | `trsl:policy:linear-longstop-v0@1.0` |
**Sub-decision recorded 2026-07-30 (this task remains `todo` — no Phase **Pilot scope of the alpha/beta legal waiver (explicitly confirmed at
has been declared):** the maintainer separately and explicitly authorized acceptance):** this Phase only under Binky Hedgehog GmbH / `binky`;
a distinct, narrower step — adopting `specs/TargetRevenueSourceLicense-V1C1.md` TRSL/CUA V1C1 as preliminary candidates under the 2026-07-29 jurisdiction
as the preliminary governing `LICENSE` across every repository in the and Enforcement Network alpha/beta defaults; CLA still draft (external
`coulomb` Forgejo org (confirmed "every repo, no exceptions," including contributions remain blocked); no other product line authorized by this
`target-revenue` itself and internal tooling repos). This is a **license- single acceptance.
text adoption, not a Phase declaration** — see
`history/260730-TRSL-OrgWideLicenseRollout.md` for the full execution **Trust Service at go-live:** registered on the local pilot instance
record, including one explicitly flagged exception `http://127.0.0.1:8765` (Postgres `trf-pilot-pg` / volume
(`the-custodian`, which carried a pre-existing proprietary/confidential `trf-pilot-pgdata`) because WP-0011's public reef deployment was not yet
license and was deliberately not touched pending separate confirmation) available. Git-committed Manifest is the durable declaration;
and two repos committed locally only (no git remote configured: ledger/metrics are live on that pilot instance pending migration to a
`executor-sandbox`, `executor-worker`). No Initial Target, Milestone public Trust Service when WP-0011 lands.
Release, degeneration policy, or Future License has been declared for any
repo; no Phase Manifest has been registered against the hosted Trust **Prior sub-decision (2026-07-30), superseded for Phase-declaration
Service; no Development Credit is being tracked anywhere. This task status only:** org-wide TRSL LICENSE text adoption
(T05) itself remains `todo` and unaccepted — the license-rollout decision (`history/260730-TRSL-OrgWideLicenseRollout.md`) remains a separate,
does not by itself authorize a real Phase for any repo, per this task's earlier act — it did not by itself declare any Phase. As of this T05
own instruction above. acceptance, one Phase is declared as above.