diff --git a/README.md b/README.md index 2ad21c0..0bffe3c 100644 --- a/README.md +++ b/README.md @@ -75,9 +75,12 @@ The concept's §13 now defines a **Global Contingency Share Determination Rule** | --- | --- | | [TREV-WP-0001](workplans/TREV-WP-0001-license-prior-art-research.md) | Prior-art research → TRSL V1C1 license candidate — **finished**, accepted by the maintainer 2026-07-29 | | [TREV-WP-0002](workplans/TREV-WP-0002-trust-service-foundation.md) | Schemas, pure Outstanding Target fold, golden fixture — **finished** | -| [TREV-WP-0003](workplans/TREV-WP-0003-normative-core-extraction.md) | Extract stable normative core docs — T01–T05 done, T06 human review open | +| [TREV-WP-0003](workplans/TREV-WP-0003-normative-core-extraction.md) | Extract stable normative core docs — **finished**, reviewed and accepted 2026-07-29 | | [TREV-WP-0004](workplans/TREV-WP-0004-global-jurisdiction-research.md) | Global jurisdictional research backing the License/CUA candidates — 9 of 10 tasks done; only the human-gated T10 synthesis remains | | [TREV-WP-0005](workplans/TREV-WP-0005-enforcement-network-research.md) | Enforcement Network legal feasibility research — 9 of 10 tasks done (all jurisdictions and mechanism design; T10 synthesis remains, human-gated) | +| [TREV-WP-0006](workplans/TREV-WP-0006-trust-service-implementation.md) | Hosted Trust Service reference implementation (PRD Phase 4b) — active, not yet started | +| [TREV-WP-0007](workplans/TREV-WP-0007-degeneration-policy-and-canonical-profiles.md) | Degeneration policy + canonical monetization profile catalog — active, not yet started | +| [TREV-WP-0008](workplans/TREV-WP-0008-governance-and-pilot-rollout.md) | Governance formalization + pilot rollout across `coulomb-loop`/`net-kingdom`/`helix-forge`/`railiance-*` — active, not yet started; real Phase declarations gated behind T05 | Hub index: [`WORK-RECORDS.md`](WORK-RECORDS.md) · brief: [`.custodian-brief.md`](.custodian-brief.md) diff --git a/SCOPE.md b/SCOPE.md index 1d0764f..ab7d4e6 100644 --- a/SCOPE.md +++ b/SCOPE.md @@ -4,8 +4,8 @@ **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. -**Last updated:** 2026-07-28 -**Basis:** SWOT recommendations in `history/260728-SWOT-Assessment.md` +**Last updated:** 2026-07-29 +**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. --- @@ -13,9 +13,10 @@ | Label | Meaning | | --- | --- | -| **Stage 0** | Concept consolidated; product/tech orientation specs exist; no production legal text; no production Trust Service | -| Trust Service federation | Stages 1–6 from concept §15 are **out of current delivery scope** (design readiness only) | -| Legal TRSL | Research and non-binding draft skeleton only; specialist review required before any real Phase | +| **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-*`). | +| 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. | --- @@ -49,16 +50,17 @@ ## 3. Explicitly out of scope now -| Item | Deferred to | +| Item | Status | | --- | --- | -| Production Trust Service (registries, hosted ledger API, metrics product) | After Phase 1 normative docs + schema foundation; dedicated Trust Service PRD | -| Finalized legal license text and commercial agreements | Specialist legal review post draft skeleton | -| Final degeneration formula as irreversible norm | Research + pilot learning | -| Federation Stage 2+ (replication, multi-operator, multi-authority) | PRD Roadmap Phase 6 | -| Multi-stakeholder governance institutions | PRD Roadmap Phase 7 (lightweight draft only if needed) | +| 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 | +| Finalized legal license text and commercial agreements | TRSL/CUA V1C1 accepted as counsel-briefing material (WP-0001); specialist legal review still outstanding | +| Final degeneration formula as irreversible norm | **In scope now** — `workplans/TREV-WP-0007-degeneration-policy-and-canonical-profiles.md`, active | +| 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 | | Tax / statutory revenue recognition | Permanently out of framework core (INTENT boundaries) | -| Governing third-party product Phases in production | After legal + Stage 0 package ready | -| Accepting external code into a governed Milestone Release | Until contributor-rights instrument exists | +| 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) | +| 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 | --- @@ -75,6 +77,7 @@ These rules implement SWOT I-05 / I-06 and the PRD roadmap order: - WP-0002 stack/library ADR (if technology is locked), - Any promotion of working defaults into normative core language. 4. New monetization ideas land as **profiles/extensions**, not core terms, unless they pass the complexity budget (universal / interoperable / trust-critical). +5. **Real Phase declaration** (a repo's actual License header changed to TRSL, a real Commercial Entitlement sold, real Development Credit tracked) **must not** occur until `workplans/TREV-WP-0008-governance-and-pilot-rollout.md` T05 is explicitly accepted. WP-0006/0007/0008's other tasks (Trust Service implementation, degeneration/profile finalization, governance drafting, draft/non-binding pilot Phase Manifests) may proceed in parallel and do not themselves authorize going live. --- diff --git a/specs/ProductRequirementsDocument.md b/specs/ProductRequirementsDocument.md index 180395e..9a7acf7 100644 --- a/specs/ProductRequirementsDocument.md +++ b/specs/ProductRequirementsDocument.md @@ -346,7 +346,7 @@ The MVP corresponds to the "Proposed Initial Deliverables" already identified in 7. `TargetDegenerationPolicyResearch.md` — comparative models; promote beyond linear-longstop-v0 working default. 8. `TrustServiceProductRequirementsDocument.md` — dedicated PRD for hosted registry/ledger/metrics/attestation. -9. Hosted reference Trust Service (FR-8–FR-10) — **successor workplan only** after Tier A and Trust Service PRD. +9. Hosted reference Trust Service (FR-8–FR-10) — **TREV-WP-0006**, active as of 2026-07-29. 10. `TrustServiceFederationArchitecture.md` / `TRSL-Governance.md` — federation and multi-stakeholder governance. ### 11.2 MVP non-scope @@ -377,12 +377,14 @@ Workplan mapping (see `workplans/`, `SCOPE.md` §4): | Roadmap phase | Workplan / artifact | | --- | --- | | Phase 0 | Concept + this PRD + TSD + SCOPE + working defaults | -| Phase 1 | **TREV-WP-0003** normative core extraction | -| Phase 2 | **TREV-WP-0001** prior art + TRSL draft skeleton (human gate) | -| Phase 3 | Extension/profile docs (WP-0003-T04 stub; full catalog follow-on) | -| Phase 4a | **TREV-WP-0002** schemas, pure fold, golden fixture (not hosted service) | -| Phase 4b | Trust Service PRD + hosted reference implementation (future workplan) | -| Phase 5+ | Degeneration research promotion, federation, governance | +| Phase 1 | **TREV-WP-0003** normative core extraction — **finished** | +| Phase 2 | **TREV-WP-0001** prior art + TRSL/CUA V1C1 — **finished**, accepted 2026-07-29 | +| Phase 3 | Extension contract (WP-0003, done) + full canonical catalog — **TREV-WP-0007** | +| Phase 4a | **TREV-WP-0002** schemas, pure fold, golden fixture — **finished** | +| Phase 4b | Trust Service PRD + hosted reference implementation — **TREV-WP-0006** | +| Phase 5 | Degeneration policy promotion — **TREV-WP-0007** | +| Phase 6 | Federation — design readiness only, not started | +| Phase 7 | Governance + pilot rollout (`coulomb-loop`, `net-kingdom`, `helix-forge`, `railiance-*`) — **TREV-WP-0008** | ### Phase 0 — Concept consolidation (largely complete) @@ -405,30 +407,31 @@ Workplan mapping (see `workplans/`, `SCOPE.md` §4): - Produce `MonetizationExtensionSpecification.md` and `CanonicalMonetizationProfiles.md`. - Working defaults already list Stage 0 extension catalog targets and evidence tiers; research may refine (§14 items 4, 10, 11). -### Phase 4a — Runnable specification foundation (active — WP-0002) +### Phase 4a — Runnable specification foundation (finished — WP-0002) - Machine-readable schemas, pure Outstanding Target fold, offline validators, golden Phase package. - Conversion always recomputable without attestation or network service. -### Phase 4b — Hosted Trust Service (blocked until Phase 1 + 4a Stage 0 signal) +### Phase 4b — Hosted Trust Service (active — WP-0006, unblocked 2026-07-29) - Produce `TrustServiceProductRequirementsDocument.md`. - Implement a centralized reference Trust Service satisfying FR-8–FR-10. -- Must not start under WP-0002; use a successor workplan after SCOPE Stage 0 “done enough” signal. +- Unblocked once Phase 1 (WP-0003) finished and Stage 0 working defaults were published — both true as of 2026-07-29; see `workplans/TREV-WP-0006-trust-service-implementation.md`. -### Phase 5 — Degeneration policy resolution +### Phase 5 — Degeneration policy resolution (active — WP-0007) - Produce `TargetDegenerationPolicyResearch.md`; resolve the Longstop-vs-progress-decay relationship (§13.3, §24.7–24.8). -- Stage 0 pilot: `trsl:policy:linear-longstop-v0` + mandatory Longstop (`OpenQuestions-WorkingDefaults.md` Q7–Q8). +- Stage 0 pilot: `trsl:policy:linear-longstop-v0` + mandatory Longstop (`OpenQuestions-WorkingDefaults.md` Q7–Q8); see `workplans/TREV-WP-0007-degeneration-policy-and-canonical-profiles.md` for promotion to a v1 formula. ### Phase 6 — Federation path - Produce `TrustServiceFederationArchitecture.md`; advance through Stage 1 (public verification) toward Stage 2+ (concept §15). - Out of current SCOPE for delivery; design readiness only. -### Phase 7 — Governance formalization +### Phase 7 — Governance formalization (active — WP-0008) - Produce `TRSL-Governance.md` covering change process, dispute handling, and conflict-of-interest rules (concept §20.3–§20.4). +- Now includes the Licensor-identity question across multiple product lines (`coulomb-loop`, `net-kingdom`, `helix-forge`, `railiance-*`) and pilot-rollout preparation; see `workplans/TREV-WP-0008-governance-and-pilot-rollout.md`. Real Phase declarations remain gated behind that workplan's T05 (legal + governance go-live decision). --- diff --git a/workplans/TREV-WP-0006-trust-service-implementation.md b/workplans/TREV-WP-0006-trust-service-implementation.md new file mode 100644 index 0000000..d3c46fb --- /dev/null +++ b/workplans/TREV-WP-0006-trust-service-implementation.md @@ -0,0 +1,166 @@ +--- +id: TREV-WP-0006 +type: workplan +title: "Trust Service reference implementation (PRD Phase 4b)" +domain: infotech +repo: target-revenue +status: active +owner: claude +topic_slug: infotech +created: "2026-07-29" +updated: "2026-07-29" +--- + +# Trust Service reference implementation (PRD Phase 4b) + +Builds the hosted Trust Service that WP-0002 deliberately deferred: Phase +Registry, Extension Registry, hosted Target Ledger, Metrics, and Conversion +Attestation publication, serving multiple repos rather than the single +offline golden-Phase package. This is the piece explicitly named in +`SCOPE.md` §3 as out of scope until now. + +**Unblocked as of 2026-07-29:** `SCOPE.md` §4 rule 2 required (a) WP-0003's +core extract deliverables to exist, and (b) working defaults for Longstop, +currency, recognition, and minimum evidence to be published, before full +Trust Service implementation could start. Both conditions are now met +(WP-0003 finished 2026-07-29; `specs/OpenQuestions-WorkingDefaults.md` +published since Stage 0). This workplan is the first to actually start +that implementation. + +**Why now:** the midterm goal is to govern and monetize the evolution of +repos across the `coulomb` Forgejo org's product lines (`coulomb-loop`, +`net-kingdom`, `helix-forge`, the `railiance-*` family) — that requires a +real, multi-repo-capable Trust Service, not the single-Phase offline +library WP-0002 produced. + +**Does not include:** accepting real payments or tracking a real Phase for +any production repo — see `workplans/TREV-WP-0008-governance-and-pilot-rollout.md` +for the human-gated go-live step. This workplan builds the infrastructure; +it does not turn it on for anyone's real money. + +## Trust Service Product Requirements Document + +```task +id: TREV-WP-0006-T01 +status: todo +priority: high +``` + +Produce `specs/TrustServiceProductRequirementsDocument.md`: scope, +stakeholders, and requirements for the hosted service, building directly +on `specs/TechnicalSpecificationDocument.md` §4 (component architecture) +and §3's schemas. Must state explicitly which of WP-0002's Stage 0 +guarantees (determinism, offline verifiability, no Trust Service discretion +over conversion) the hosted service inherits unchanged versus which +Stage-0-only constraints (single golden Phase, no auth, no multi-tenancy) +it must now lift. + +## Stack and storage ADR (hosted service — distinct scope from ADR-0001) + +```task +id: TREV-WP-0006-T02 +status: todo +priority: high +human_accept_required: true +``` + +`docs/adr/ADR-0001-stage0-library-stack.md` explicitly scoped out hosting, +storage, and multi-tenancy decisions (its Revisit trigger names this exact +moment). Record a new ADR for: storage engine for the append-only Target +Ledger at multi-repo scale, authentication/authorization model for Phase +Registry writes, and hosting/deployment target — `railiance-infra` and +`railiance-cluster` are the existing platform-infrastructure repos in this +Forgejo org and are the natural first candidates to investigate, not +assumed by default. + +**Human accept gate:** per the same policy as ADR-0001 — agents may draft, +must not treat as accepted without explicit maintainer sign-off. + +## Phase Registry and Extension Registry hosting + +```task +id: TREV-WP-0006-T03 +status: todo +priority: high +``` + +Implement hosted versions of the Phase Registry and Extension Registry +components (`specs/TechnicalSpecificationDocument.md` §4.1), serving +multiple Phase Manifests and extension registrations across repos rather +than one golden fixture. Reject non-conformant manifests/extensions at +registration, exactly as the Stage 0 validators already do — this task +adds multi-tenancy and persistence, not new validation logic. + +## Hosted Target Ledger append API + +```task +id: TREV-WP-0006-T04 +status: todo +priority: high +``` + +Implement an authenticated append API for Target Ledger entries per Phase, +preserving WP-0002's append-only, hash-chained, deterministically-foldable +guarantees exactly. Any party who can compute the fold offline from an +export must get the same Outstanding Target as the hosted service — this +is the property to test most aggressively, since it's the one a hosted +service could most easily and least visibly break. + +## Metrics service + +```task +id: TREV-WP-0006-T05 +status: todo +priority: medium +``` + +Implement the public metrics set from `specs/OpenQuestions-WorkingDefaults.md` +Q9 (Initial Target, cumulative credits, Outstanding Target, conversion +status, last checkpoint, Longstop timestamp as mandatory; velocity/forecast +as recommended, clearly labeled as forecasts per concept §14.6). + +## Conversion Attestation publication + +```task +id: TREV-WP-0006-T06 +status: todo +priority: high +``` + +Implement Conversion Attestation generation and publication as a hosted +service, preserving the non-discretionary rule from +`src/target_revenue/conversion.py`: the service publishes evidence of a +conversion already true from the Manifest + Ledger, never a precondition +for it. Any repo's own tooling must be able to recompute conversion status +without querying this service at all. + +## Multi-repo onboarding flow + +```task +id: TREV-WP-0006-T07 +status: todo +priority: medium +``` + +Define and implement how a repo (e.g. `coulomb-loop`, `net-kingdom`, +`helix-forge`, a `railiance-*` repo) registers a Phase against the hosted +Trust Service: what it commits to its own repo (a Phase Manifest file, +per `specs/PhaseManifestSpecification.md`) versus what it submits to the +Trust Service (the registration call). Coordinate with +`workplans/TREV-WP-0008-governance-and-pilot-rollout.md`, which selects +the actual first repos — this task defines the mechanism, not the pilot +selection. + +## Conformance test suite at hosted scale + +```task +id: TREV-WP-0006-T08 +status: todo +priority: medium +``` + +Extend WP-0002's conformance suite to run against the hosted service: +multiple concurrent Phases across different repos, the golden Phase +example replayed through the hosted API rather than only the offline +library, and a specific regression test that hosted and offline folds of +the same exported ledger always agree. diff --git a/workplans/TREV-WP-0007-degeneration-policy-and-canonical-profiles.md b/workplans/TREV-WP-0007-degeneration-policy-and-canonical-profiles.md new file mode 100644 index 0000000..e87ff03 --- /dev/null +++ b/workplans/TREV-WP-0007-degeneration-policy-and-canonical-profiles.md @@ -0,0 +1,93 @@ +--- +id: TREV-WP-0007 +type: workplan +title: "Degeneration policy research and canonical monetization profiles" +domain: infotech +repo: target-revenue +status: active +owner: claude +topic_slug: infotech +created: "2026-07-29" +updated: "2026-07-29" +--- + +# Degeneration policy research and canonical monetization profiles + +Finalizes two PRD deliverables that pilot Phases (`workplans/TREV-WP-0008-governance-and-pilot-rollout.md`) +cannot responsibly launch without: a degeneration policy beyond the +placeholder `trsl:policy:linear-longstop-v0`, and a full worked canonical +monetization profile catalog beyond the six one-line defaults already in +`specs/MonetizationExtensionSpecification.md` §5. + +**Why this blocks pilot rollout:** every Phase Manifest requires a +`degeneration_policy` reference (`specs/PhaseManifestSpecification.md`, +Required field) and, in practice, at least one Monetization Extension. +Launching real pilot Phases on an admittedly-provisional pilot policy and +one-line profile defaults is a real business decision, not a technical +blocker — but it should be a *chosen* risk, not an accidental one because +this workplan was skipped. + +## Degeneration policy research + +```task +id: TREV-WP-0007-T01 +status: todo +priority: high +``` + +Produce `specs/TargetDegenerationPolicyResearch.md`: survey comparative +models (BSL/FSL-style fixed longstop vs. progress-sensitive decay vs. +hybrid — `history/260729-TRSL-PriorArt-Survey.md` already has partial +groundwork), and resolve concept §13.2's open inputs (progress-sensitive +pause on material Development Credit, contributor diversity factors) that +`trsl:policy:linear-longstop-v0` deliberately left unresolved per +`specs/OpenQuestions-WorkingDefaults.md` Q7. + +## Degeneration formula decision (human gate) + +```task +id: TREV-WP-0007-T02 +status: todo +priority: high +human_accept_required: true +``` + +Using T01, propose either: (a) confirming `linear-longstop-v0` as the +adopted v1 formula (not merely a Stage 0 pilot default), or (b) a +refined/replacement formula. Either way this promotes a working default to +permanent-enough-to-launch-pilots-on status, which per `SCOPE.md` §4 +requires explicit human accept — agents may prepare the recommendation and +leave this `todo`. + +## Canonical monetization profile catalog + +```task +id: TREV-WP-0007-T03 +status: todo +priority: high +``` + +Produce `specs/CanonicalMonetizationProfiles.md`: full worked pricing +narratives and examples for the six canonical-candidate profiles already +named in `specs/MonetizationExtensionSpecification.md` §5 +(`development-license`, `cost-plus-operations`, `phase-sponsorship`, +`service-with-development-allocation`, `product-ideation`, +`general-consulting`), plus fixture files for the two not yet +fixture-backed (`product-ideation`, `general-consulting`), following the +pattern already established in `examples/phase-001/extensions/`. + +## Canonicalization review process (light) + +```task +id: TREV-WP-0007-T04 +status: todo +priority: medium +``` + +Per `specs/MonetizationExtensionSpecification.md` §4, promoting an +extension from `registered` to `canonical` "is a documented human/ +governance action, never automated" — but no document yet describes what +that review actually checks. Produce a short (not a full governance +framework — that's `workplans/TREV-WP-0008-governance-and-pilot-rollout.md` +T01) checklist for canonicalizing the six profiles in this workplan, +sufficient to promote them from `registered` to `canonical` status. diff --git a/workplans/TREV-WP-0008-governance-and-pilot-rollout.md b/workplans/TREV-WP-0008-governance-and-pilot-rollout.md new file mode 100644 index 0000000..0581d30 --- /dev/null +++ b/workplans/TREV-WP-0008-governance-and-pilot-rollout.md @@ -0,0 +1,147 @@ +--- +id: TREV-WP-0008 +type: workplan +title: "Governance formalization and pilot rollout (coulomb / net-kingdom / helix-forge / railiance)" +domain: infotech +repo: target-revenue +status: active +owner: claude +topic_slug: infotech +created: "2026-07-29" +updated: "2026-07-29" +--- + +# Governance formalization and pilot rollout + +The midterm goal: govern and monetize the evolution of repos across the +`coulomb` Forgejo org's product lines — `coulomb-loop`, `net-kingdom`, +`helix-forge`, and the `railiance-*` family (`railiance-apps`, +`railiance-bootstrap`, `railiance-cluster`, `railiance-enablement`, +`railiance-fabric`, `railiance-forge`, `railiance-hosts`, `railiance-infra`, +`railiance-master`, `railiance-platform`). This workplan formalizes the +governance the framework has been designed around but never actually +written down, and prepares (but does not itself execute) the first real +Phase declarations. + +**Hard gate, stated up front:** `SCOPE.md` §3 lists "governing third-party +product Phases in production" as out of scope "after legal + Stage 0 +package ready" — i.e., not yet. This workplan's rollout tasks (T03–T04) +produce **draft, non-binding** Phase Manifests as worked examples, exactly +like `examples/phase-001/` already is. **No real Commercial Entitlement may +be sold, no real Development Credit tracked, and no repo's actual License +header changed to TRSL, until T05 (the go-live gate) is explicitly +accepted** — after TRSL/CUA specialist legal review (`workplans/TREV-WP-0004-global-jurisdiction-research.md` / +`workplans/TREV-WP-0005-enforcement-network-research.md` T10 syntheses +feed this) and T01 (Licensor governance) are both resolved. Moving fast on +T01–T04 must not create pressure to skip T05. + +## Governance document: TRSL-Governance.md + +```task +id: TREV-WP-0008-T01 +status: todo +priority: high +``` + +Produce `specs/TRSL-Governance.md`, per `spec/TargetRevenueLicenseConcept.md` +§20 (complexity budget, versioning, extension governance, operator +governance). Must resolve one question this rollout makes concretely +unavoidable for the first time: **who is "the Licensor"** across four +different product lines under one Forgejo org — a single shared Licensor +entity for all four (simplest, but conflates genuinely different products' +commercial decisions), or a per-product-line Licensor (each of +`coulomb-loop`, `net-kingdom`, `helix-forge`, `railiance` declaring its own +Phases independently under a shared TRSL/CUA template)? This was never +forced while the framework was single-repo-hypothetical; it is now. +Also define: change process for the License/CUA templates themselves once +multiple product lines depend on them, extension canonicalization review +(coordinate with `workplans/TREV-WP-0007-degeneration-policy-and-canonical-profiles.md` +T04's narrower checklist), and dispute/conflict-of-interest handling per +concept §20.3–§20.4. + +## Repo inventory and Phase-candidate survey + +```task +id: TREV-WP-0008-T02 +status: todo +priority: high +``` + +For each of `coulomb-loop`, `net-kingdom`, `helix-forge`, and the +`railiance-*` family: survey current repo goals and status (via the state +hub's `get_domain_summary`/`list_domain_repos`/repo-goal tools, or direct +repo inspection where hub data is thin) to identify one plausible first +Milestone Release candidate per product line — a bounded, recently- or +soon-to-be-completed piece of work with a defensible Target Multiple +classification (`specs/TargetRevenueFrameworkCore.md` §1.4), not an +arbitrary pick. Document why each candidate was chosen and what was +passed over. + +## Draft pilot Phase Manifests (non-binding worked examples) + +```task +id: TREV-WP-0008-T03 +status: todo +priority: high +``` + +Using T02's candidates, draft one Phase Manifest per product line +following `specs/PhaseManifestSpecification.md` and +`schemas/phase_manifest.schema.json` exactly — structurally valid, +conformance-tested the same way `examples/phase-001/` is, but explicitly +marked **draft / not yet declared** (no real Commercial Use restriction +takes effect from these). Choose an applicable Monetization Extension per +Phase from `workplans/TREV-WP-0007-degeneration-policy-and-canonical-profiles.md` +T03's catalog. + +## Contributor rights instrument (CLA) + +```task +id: TREV-WP-0008-T04 +status: todo +priority: medium +``` + +`CONTRIBUTING.md` currently blocks external contributions into any +governed Milestone Release until a contributor-rights instrument exists +(per `history/260729-TRSL-ContributorRights-Research.md`). If any pilot +candidate from T02 has, or expects, external contributors before its +Conversion Event, this is now practically blocking, not theoretical. +Produce `specs/TRSL-ContributorLicenseAgreement-Draft.md`: a CLA scoped +narrowly to the current Phase's TRSL terms plus its already-declared +Future License, per the T04 research's recommendation. Same preliminary- +candidate treatment as the License/CUA V1C1 documents (status banner, +Appendix A-style candidate notes) — this is a new legal document, not +exempt from that pattern. + +## Go-live gate (human decision) + +```task +id: TREV-WP-0008-T05 +status: todo +priority: high +human_accept_required: true +``` + +**Do not mark this task done to authorize real Phase declarations.** It +exists to make the go-live decision a single, explicit, recorded moment +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 + `workplans/TREV-WP-0005-enforcement-network-research.md` T10 syntheses + are complete, or their absence is an explicitly accepted risk; +- 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; +- T01's Licensor-identity question is resolved for whichever product + line goes first; +- `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. + +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 +not blur that line even after everything above is ready.