Adapt specs and workplans to SWOT Stage 0 sequencing

Introduce SCOPE, expanded README, CONTRIBUTING, and provisional open-question
defaults. Rescope Trust Service work to offline schemas/fold/fixtures, add
normative core extraction workplan, and split PRD roadmap Phase 4 into
foundation vs hosted service. Sync workplans with State Hub.
This commit is contained in:
tegwick 2026-07-28 18:34:10 +02:00
parent 7286b52f07
commit 4496244bb8
16 changed files with 1252 additions and 227 deletions

View file

@ -29,6 +29,16 @@ This workplan does **not** produce final legal text. It produces the research
basis and an initial non-binding draft skeleton for specialist review, per
`specs/TechnicalSpecificationDocument.md` §8 (out-of-scope reinforcement).
**Sequencing:** Runs in parallel with WP-0003 (normative core extract) and
WP-0002 (schemas / pure fold). Does not depend on a hosted Trust Service.
Stage 0 terminology and Future License enum defaults are in
`specs/OpenQuestions-WorkingDefaults.md` (Q1–Q3, Q15); refine or challenge
them with research evidence rather than silently inventing alternatives.
**Human gate:** Task T06 (TRSL draft skeleton) MUST NOT be marked `done`
without explicit human accept (SCOPE §4, CONTRIBUTING.md). Agents may
prepare the draft and leave status `todo` or note “ready for human accept.”
## Survey delayed-open-source and source-available license models
```task
@ -48,6 +58,8 @@ wording, and known criticisms or disputes. Record findings so they can be
diffed directly against TRSL's Phase/Target/Conversion model in
`spec/TargetRevenueLicenseConcept.md` §7, §10, §18.
**Deliverable path (suggested):** `history/` or `specs/research/TRSL-PriorArt-Survey.md`.
## Survey OSI Open Source Definition and Fair Source boundary framing
```task
@ -65,6 +77,10 @@ OSI-approved license" framing applies or should be adapted. Produce
recommended terminology guardrails (source-available vs. open source vs.
commercially licensed) for use consistently across all TRF documents.
Align with README terminology guardrail and
`specs/OpenQuestions-WorkingDefaults.md` Q1–Q2; update those if research
improves the wording (human accept if changing published working defaults).
## Survey patent-grant and Future License precedent (MIT vs Apache-2.0)
```task
@ -83,6 +99,9 @@ parallel canonical options (per PRD open question 3 /
whether the TRSL pre-conversion phase itself needs an express patent license
independent of the eventual Future License choice.
Working default already allows both Future Licenses in schemas
(`OpenQuestions-WorkingDefaults.md` Q3); this task confirms or revises that.
## Survey contributor-rights instruments for dual-future licensing
```task
@ -101,6 +120,10 @@ whether a DCO alone is sufficient or whether TRSL requires a broader inbound
grant (per `history/260728-InitialExploration.md` §8 and
`spec/TargetRevenueLicenseConcept.md` §21.4).
Update `CONTRIBUTING.md` if the recommendation changes interim policy
(external contributions still blocked for governed Milestone Releases until
instrument exists).
## Survey jurisdiction-specific standard-terms constraints
```task
@ -119,6 +142,9 @@ constraints in other jurisdictions relevant to likely early commercial users
"commercial use," "captured," "Development Credit," and "Conversion Event."
Flag terms that most urgently need objective, litigation-safe definitions.
Feed clarity-critical terms into T06 skeleton as `[LEGAL]` markers and into
working defaults Q2 if definitions improve.
## Synthesize findings into an initial TRSL draft skeleton
```task
@ -126,6 +152,7 @@ id: TREV-WP-0001-T06
status: todo
priority: high
state_hub_task_id: "9e29b76f-37c0-4204-8cdc-e8d75e8412b4"
human_accept_required: true
```
Using T01–T05, produce `specs/TargetRevenueSourceLicense-Draft.md`: a
@ -136,3 +163,7 @@ commercial-use restriction, automatic Future License conversion, patent
treatment, termination and cure, warranty/liability exclusions). Explicitly
mark every clause requiring specialist legal review before use, per
`spec/TargetRevenueLicenseConcept.md` §21.5.
**Human accept gate:** Do not set this task to `done` until a human maintainer
explicitly accepts the skeleton as adequate briefing material for counsel.
Agent completion of the file is “ready for review,” not done.