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.

workplans/TREV-WP-0004-global-jurisdiction-research.md

@@ -4,7 +4,7 @@ type: workplan
 title: "Global jurisdictional research for TRSL and Commercial Use Agreement"
 domain: infotech
 repo: target-revenue
-status: active
+status: finished
 owner: claude
 topic_slug: infotech
 created: "2026-07-29"
@@ -339,12 +339,29 @@ should ordinarily share a governing law).
 
 ```task
 id: TREV-WP-0004-T10
-status: todo
+status: done
 priority: high
 human_accept_required: true
+human_accepted_by: Bernd
+human_accepted_at: "2026-07-29"
 state_hub_task_id: "b6a81a88-a9a2-4012-ba69-9f650381b003"
 ```
 
+**Result:** Synthesis produced at `history/260729-TRSL-Jurisdiction-Synthesis.md`.
+Human acceptance (Bernd, 2026-07-29): the maintainer decided full specialist
+legal review is postponed until the framework moves out of beta, given
+limited legal/commercial exposure during build/alpha and the expectation
+that the License/CUA will be revised on stakeholder/customer feedback before
+the legal framework settles. On that basis, the synthesis's proposed
+alpha/beta working defaults are adopted and applied to both V1C1 documents'
+Appendix A tables and status banners: License Appendix A item 6 and CUA
+Appendix A item 1 (governing law → arbitration at a neutral seat), CUA item 3
+(liability cap → kept, drafted prominently/proportionately), and CUA item 5
+(data protection → minimal-collection practice, no DPA drafted yet). CUA item
+4 (indemnification) is deliberately left unresolved, per the synthesis's own
+reasoning that this is the correct default, not a gap. This closes this
+workplan without claiming the legal framework is final.
+
 Using T01–T09, produce a consolidated jurisdictional risk matrix (one row
 per jurisdiction/family, columns for: standard-terms clarity regime,
 liability-cap enforceability, indemnification norms, data-protection

workplans/TREV-WP-0005-enforcement-network-research.md

@@ -4,7 +4,7 @@ type: workplan
 title: "Enforcement Network — legal feasibility and design research"
 domain: infotech
 repo: target-revenue
-status: active
+status: finished
 owner: claude
 topic_slug: infotech
 created: "2026-07-29"
@@ -318,12 +318,28 @@ legal decisions (concept §3.2, §10).
 
 ```task
 id: TREV-WP-0005-T10
-status: todo
+status: done
 priority: high
 human_accept_required: true
+human_accepted_by: Bernd
+human_accepted_at: "2026-07-29"
 state_hub_task_id: "cdd3ca93-2ec0-4326-959b-2c88de11b41b"
 ```
 
+**Result:** Synthesis produced at `history/260729-TREN-Synthesis.md`.
+Human acceptance (Bernd, 2026-07-29): same alpha/beta risk-acceptance basis
+as `TREV-WP-0004-T10` (see that task's Result). The synthesis's five
+proposed resolutions to `specs/EnforcementNetworkConcept.md` §13.5 are
+adopted and applied: funding source (Licensor direct), FX methodology
+(announcement-date rate), reimbursement of advanced financing from Recovery
+before Development Credit, the 18-month trailing look-back window, and
+tier-3 split-role collapse to a single non-contingent Local Counsel
+engagement by default. §13.2's Jurisdiction Percentage Cap table (12
+jurisdictions/families) is applied as the authoritative reference. Japan's
+Article 12 fee-splitting risk is explicitly **not** resolved by this
+acceptance and remains flagged — no Enforcement Action should be pursued in
+Japan without specific counsel review, even during alpha/beta.
+
 Using T01–T09, produce a consolidated feasibility matrix (one row per
 jurisdiction/family: direct lawyer contingency permitted? statutory cap?
 litigation funding regulatory status? recommended structural variant) and

workplans/TREV-WP-0008-governance-and-pilot-rollout.md

@@ -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