--- 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" state_hub_workstream_id: "b46a30e8-8ef6-44f7-96af-a098cb4084b4" --- # 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 state_hub_task_id: "bae630d7-907b-4eb4-bad4-d72803ccbd33" ``` 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 state_hub_task_id: "4f4f4922-4bc6-4ff9-a408-b836287186db" ``` 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 state_hub_task_id: "942943ae-14a2-4f23-888e-6084aa9c6024" ``` 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 state_hub_task_id: "666a800b-96a7-4664-9448-24af989b57c5" ``` `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 state_hub_task_id: "af688189-8151-4170-925f-b3c4806a68ed" ``` **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 — **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; - `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.