Set up practical implementation workplans (WP-0006/0007/0008)
With WP-0001/0002/0003 finished, PRD Phase 4b (hosted Trust Service) is unblocked per SCOPE.md's own sequencing rule, and the midterm goal shifts from framework design to practical application: governing and monetizing repos across the coulomb Forgejo org's product lines (coulomb-loop, net-kingdom, helix-forge, the railiance-* family). - TREV-WP-0006: Trust Service reference implementation (PRD Phase 4b). Eight tasks from PRD to conformance-tested hosted service, explicit that it builds infrastructure only - no real payments or Phase tracking. - TREV-WP-0007: Degeneration policy finalization (PRD Phase 5) and the full canonical monetization profile catalog (remainder of Phase 3) - pilot Phases can't responsibly launch on the placeholder pilot policy and one-line profile defaults alone. - TREV-WP-0008: Governance formalization (PRD Phase 7) and pilot rollout preparation. Forces a real design decision the framework never had to answer while single-repo-hypothetical: who is "the Licensor" across four independent product lines. Produces draft, non-binding Phase Manifests as worked examples for one repo per product line, and a CLA draft. All three explicitly preserve SCOPE.md's existing "no production Phases until legal review" guardrail rather than overriding it under pressure to monetize real repos: WP-0008-T05 is a dedicated, human-gated go-live decision, and no other task in any of the three workplans is permitted to authorize a real Phase, real Commercial Entitlement sale, or real Development Credit tracking. Updates SCOPE.md (new Stage 0/Stage 1 maturity table, revised out-of-scope table distinguishing "infrastructure in scope" from "going live still gated"), PRD roadmap (Phase 4b/5/7 now active, pointing at the new workplans), and README's active-work table accordingly. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
parent
cdfdd7f6b3
commit
dd7f7d2181
6 changed files with 442 additions and 27 deletions
|
|
@ -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).
|
||||
|
||||
---
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue