Close WP-0004/WP-0005 with alpha/beta legal-review deferral

Maintainer decision (2026-07-29): full specialist legal review of the
TRSL/CUA is postponed until the framework moves out of beta, given
limited legal/commercial exposure during build/alpha. WP-0004-T10 and
WP-0005-T10 synthesize their jurisdiction research into adopted alpha/beta
working defaults (governing law -> arbitration at a neutral seat,
liability cap, data protection minimal-collection practice, and the
Enforcement Network's fee mechanics) rather than full resolution, and are
accepted on that basis. Propagates the decision to the License/CUA V1C1
Appendix A tables and status banners, SCOPE.md, CONTRIBUTING.md, the
WP-0008-T05 go-live gate, and README.md.
This commit is contained in:
tegwick 2026-07-29 20:46:49 +02:00
parent 4d2e1e5153
commit d07c77f40a
11 changed files with 190 additions and 30 deletions

View file

@ -136,11 +136,19 @@ 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;
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;
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