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
166
workplans/TREV-WP-0006-trust-service-implementation.md
Normal file
166
workplans/TREV-WP-0006-trust-service-implementation.md
Normal file
|
|
@ -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.
|
||||
Loading…
Add table
Add a link
Reference in a new issue