tegwick
4496244bb8
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.
169 lines
7.2 KiB
Markdown
169 lines
7.2 KiB
Markdown
---
|
||
id: TREV-WP-0001
|
||
type: workplan
|
||
title: "TargetRevenueSourceLicense prior-art and adjacent-concept research"
|
||
domain: infotech
|
||
repo: target-revenue
|
||
status: active
|
||
owner: claude
|
||
topic_slug: infotech
|
||
created: "2026-07-28"
|
||
updated: "2026-07-28"
|
||
state_hub_workstream_id: "6f91cef8-c75c-4955-aaba-0b240390fbe9"
|
||
---
|
||
|
||
# TargetRevenueSourceLicense prior-art and adjacent-concept research
|
||
|
||
Research prior art and adjacent licensing/monetization concepts to ground an
|
||
initial draft of the Target Revenue Source License (TRSL). The concept is
|
||
already established in `spec/TargetRevenueLicenseConcept.md` and
|
||
`specs/ProductRequirementsDocument.md`; `history/260728-InitialExploration.md`
|
||
already surfaces several reference points (Fair Source, PolyForm
|
||
NonCommercial, Business Source License 1.1, FSL, OSI Open Source Definition,
|
||
SPDX `LicenseRef-` conventions, German §31/§307/§32 considerations). This
|
||
workplan deepens and formalizes that groundwork into a research artifact
|
||
sufficient to brief specialist legal drafting (PRD Roadmap Phase 2, MVP
|
||
deliverable `TargetRevenueSourceLicense-Draft.md`).
|
||
|
||
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
|
||
id: TREV-WP-0001-T01
|
||
status: todo
|
||
priority: high
|
||
state_hub_task_id: "d2953e5a-7831-4593-93fd-3bd8faaec48d"
|
||
```
|
||
|
||
Survey and compare structurally similar models: Business Source License 1.1
|
||
(MariaDB), Functional Source License (FSL), PolyForm Noncommercial /
|
||
PolyForm Shield, Fair Source (fair.io), Elastic License 2.0, Sentry's SSPL-
|
||
adjacent choices, and any other revenue- or time-triggered conversion
|
||
licenses. For each, capture: the trigger mechanism (fixed date vs. revenue vs.
|
||
hybrid), the pre-conversion restriction scope, the automatic-conversion legal
|
||
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
|
||
id: TREV-WP-0001-T02
|
||
status: todo
|
||
priority: high
|
||
state_hub_task_id: "3f6166cd-d8a3-4f2e-a52e-28ecd08a8cf1"
|
||
```
|
||
|
||
Confirm and document precisely why TRSL's pre-conversion state cannot be
|
||
described as "Open Source" under the OSI Open Source Definition
|
||
(field-of-endeavour non-discrimination), and how Fair Source's "source
|
||
available with limited business-protection restriction, later converts to
|
||
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
|
||
id: TREV-WP-0001-T03
|
||
status: todo
|
||
priority: medium
|
||
state_hub_task_id: "0df9125d-0bbb-4e21-8b04-8a5dda02d140"
|
||
```
|
||
|
||
Research the practical and legal tradeoffs between MIT and Apache-2.0 as
|
||
canonical Future Licenses, focusing on: the extent and legal certainty of any
|
||
implied patent grant under MIT, Apache-2.0's explicit patent grant and
|
||
patent-litigation termination clause, and precedent for offering both as
|
||
parallel canonical options (per PRD open question 3 /
|
||
`spec/TargetRevenueLicenseConcept.md` §24.3). Produce a recommendation on
|
||
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
|
||
id: TREV-WP-0001-T04
|
||
status: todo
|
||
priority: medium
|
||
state_hub_task_id: "25fbf15c-60c4-4284-af84-49d109b74cf8"
|
||
```
|
||
|
||
Research contributor license agreement (CLA) and copyright assignment
|
||
patterns used by projects that must promise two future states (a restricted
|
||
phase license plus an eventual permissive license) — e.g. how BSL/FSL-based
|
||
projects and other dual/relicensing projects handle contributor rights.
|
||
Compare against the Developer Certificate of Origin (DCO), and determine
|
||
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
|
||
id: TREV-WP-0001-T05
|
||
status: todo
|
||
priority: medium
|
||
state_hub_task_id: "1fe4b444-90b0-49d0-8d2a-9e3a99d2822a"
|
||
```
|
||
|
||
Deepen the German-law groundwork already sketched in
|
||
`history/260728-InitialExploration.md` §10 (§31 UrhG scoped rights of use,
|
||
§307 BGB standard-terms clarity requirement, §32 UrhG author remuneration)
|
||
and identify whether comparable standard-terms / consumer-protection
|
||
constraints in other jurisdictions relevant to likely early commercial users
|
||
(e.g. US, EU generally) impose similar clarity requirements on terms such as
|
||
"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
|
||
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
|
||
non-binding initial drafting basis (not final legal text) structuring the
|
||
license around the components already identified in
|
||
`spec/TargetRevenueLicenseConcept.md` §21 (permitted noncommercial use,
|
||
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.
|