Archive WP-0001 research to history/; add TRSL V1C1 license candidate
Persists the five prior-art/legal research artifacts and the original draft skeleton as dated history/ records (260729- prefix, git mv to preserve history), consistent with this repo's convention that history/ holds dated non-normative artifacts rather than living working documents: - history/260729-TRSL-PriorArt-Survey.md - history/260729-TRSL-Terminology-Guardrails.md - history/260729-TRSL-FutureLicense-PatentPrecedent.md - history/260729-TRSL-ContributorRights-Research.md - history/260729-TRSL-Jurisdiction-StandardTerms.md - history/260729-TargetRevenueSourceLicense-Draft.md (superseded) Adds specs/TargetRevenueSourceLicense-V1C1.md: the first candidate written as actual operative license text (11 sections: definitions, noncommercial grant, commercial-use restriction, patent license, automatic conversion, successive phases, termination/cure, warranty/liability, trademarks, general provisions) rather than a bracket-annotated skeleton. Carries a prominent preliminary-status notice near the top and a non-normative Appendix A tracking the nine items still needing legal resolution before any candidate can become official Version 1.0. Updates all cross-references (README, PRD, TSD, SCOPE, workplan) to the new paths; the workplan's T06 human-accept gate now points at V1C1. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
parent
55a1756f7c
commit
f37f79192d
12 changed files with 223 additions and 44 deletions
|
|
@ -41,6 +41,10 @@ Extracted and stabilized from the concept draft under `workplans/TREV-WP-0003-no
|
|||
|
||||
**Forbidden synonyms:** do not treat undifferentiated "revenue captured" as equivalent to Development Credit (see `CONTRIBUTING.md` § Terminology); do not call pre-conversion software "Open Source" (see the guardrail table above).
|
||||
|
||||
## TRSL license candidate
|
||||
|
||||
[`specs/TargetRevenueSourceLicense-V1C1.md`](specs/TargetRevenueSourceLicense-V1C1.md) is the first candidate written as actual operative license text (Version 1, Candidate 1) rather than a bracket-annotated skeleton — **preliminary, not final, not for production use** (see the notice at the top of that file). It is grounded in the prior-art and jurisdiction research archived under `history/260729-TRSL-*.md`, and supersedes the earlier skeleton now archived at `history/260729-TargetRevenueSourceLicense-Draft.md`.
|
||||
|
||||
## Repository layout
|
||||
|
||||
| Path | Role |
|
||||
|
|
@ -54,7 +58,6 @@ Extracted and stabilized from the concept draft under `workplans/TREV-WP-0003-no
|
|||
| `schemas/` | Machine-readable JSON Schemas (WP-0002) |
|
||||
| `src/target_revenue/` | Pure Python validators, hash chain, Outstanding Target fold, conversion detection (WP-0002) |
|
||||
| `docs/adr/` | Architecture decisions; ADR-0001 (Stage 0 library stack) **accepted** 2026-07-29 |
|
||||
| `specs/research/` | TRSL prior-art and legal-adjacent research (WP-0001) briefing `specs/TargetRevenueSourceLicense-Draft.md` |
|
||||
|
||||
**`spec/` vs `specs/` (resolved 2026-07-29):** the concept document originally lived under a separate singular `spec/` directory, which `history/260728-SWOT-Assessment.md` flagged as a "perpetual footgun." It has been merged into `specs/` alongside the product/tech specs and normative extracts — there is now one specs directory for the whole repository. The historical split, and the decision to merge it, remain visible in `history/260728-SWOT-Assessment.md` (unedited, as a dated record) rather than rewritten here.
|
||||
|
||||
|
|
@ -62,7 +65,7 @@ Extracted and stabilized from the concept draft under `workplans/TREV-WP-0003-no
|
|||
|
||||
| Workplan | Focus |
|
||||
| --- | --- |
|
||||
| [TREV-WP-0001](workplans/TREV-WP-0001-license-prior-art-research.md) | Prior-art research (T01–T05 done) → non-binding TRSL draft skeleton (T06 ready for human review) |
|
||||
| [TREV-WP-0001](workplans/TREV-WP-0001-license-prior-art-research.md) | Prior-art research (T01–T05 done, archived to `history/`) → TRSL V1C1 license candidate (T06 ready for human review) |
|
||||
| [TREV-WP-0002](workplans/TREV-WP-0002-trust-service-foundation.md) | Schemas, pure Outstanding Target fold, golden fixture — **finished** |
|
||||
| [TREV-WP-0003](workplans/TREV-WP-0003-normative-core-extraction.md) | Extract stable normative core docs — T01–T05 done, T06 human review open |
|
||||
|
||||
|
|
|
|||
2
SCOPE.md
2
SCOPE.md
|
|
@ -28,7 +28,7 @@
|
|||
- `specs/TargetRevenueFrameworkCore.md`
|
||||
- `specs/PhaseManifestSpecification.md`
|
||||
- `specs/TargetLedgerSpecification.md`
|
||||
- Prior-art research and non-binding `TargetRevenueSourceLicense-Draft.md` skeleton (WP-0001).
|
||||
- Prior-art research (archived under `history/260729-TRSL-*.md`) and non-binding `TargetRevenueSourceLicense-V1C1.md` candidate (WP-0001).
|
||||
- Provisional answers to conversion-critical open questions (`specs/OpenQuestions-WorkingDefaults.md`).
|
||||
- Degeneration policy research artifact (recommended default for Stage 0 pilots).
|
||||
- Canonical monetization profiles as documentation (defaults + examples).
|
||||
|
|
|
|||
|
|
@ -28,8 +28,8 @@ This is a real, meaningful difference: Apache-2.0 gives downstream users an expl
|
|||
## 2. Practical implications for TRSL's Future License choice
|
||||
|
||||
1. **MIT is legally simpler but leaves patent questions open** for whatever the Milestone Release becomes after conversion. For a Phase where patentable technique is plausible (novel algorithms, hardware-adjacent work), Apache-2.0's explicit grant plus litigation-termination deterrent is the safer default.
|
||||
2. **Apache-2.0's grant is contribution-scoped, not project-scoped** — it does not retroactively patent-license anything beyond what each contributor added. This matters for TRSL because a converted Milestone Release could carry contributions from multiple parties (licensor + external contributors, if/when a contributor-rights instrument exists — see `specs/research/TRSL-ContributorRights-Research.md`); Apache-2.0's per-contributor scoping is actually a good fit for that multi-party structure.
|
||||
3. **Neither license's patent posture depends on which is chosen as *only* the Future License** — the pre-conversion Phase itself has no patent grant either way in the models surveyed (`specs/research/TRSL-PriorArt-Survey.md` §3.4: BSL, FSL, PolyForm all omit one pre-conversion).
|
||||
2. **Apache-2.0's grant is contribution-scoped, not project-scoped** — it does not retroactively patent-license anything beyond what each contributor added. This matters for TRSL because a converted Milestone Release could carry contributions from multiple parties (licensor + external contributors, if/when a contributor-rights instrument exists — see `history/260729-TRSL-ContributorRights-Research.md`); Apache-2.0's per-contributor scoping is actually a good fit for that multi-party structure.
|
||||
3. **Neither license's patent posture depends on which is chosen as *only* the Future License** — the pre-conversion Phase itself has no patent grant either way in the models surveyed (`history/260729-TRSL-PriorArt-Survey.md` §3.4: BSL, FSL, PolyForm all omit one pre-conversion).
|
||||
|
||||
## 3. Recommendation
|
||||
|
||||
|
|
@ -23,7 +23,7 @@ Not retrievable verbatim via automated fetch this session (the English translati
|
|||
|
||||
### §32 UrhG — Equitable remuneration
|
||||
|
||||
Confirmed (gesetze-im-internet.de, fetched 2026-07-29): absent explicit contractual remuneration terms, "equitable remuneration is deemed to have been agreed," judged against "what is customary and fair in business relations... duration, frequency, extent and time of use," and an author may compel modification of a proven-inequitable agreement. This is chiefly relevant to **contributor** compensation (`specs/research/TRSL-ContributorRights-Research.md`), not to the commercial-entitlement pricing paid by TRSL's commercial users — but any employee/contractor arrangement behind a Phase's own development work should account for it.
|
||||
Confirmed (gesetze-im-internet.de, fetched 2026-07-29): absent explicit contractual remuneration terms, "equitable remuneration is deemed to have been agreed," judged against "what is customary and fair in business relations... duration, frequency, extent and time of use," and an author may compel modification of a proven-inequitable agreement. This is chiefly relevant to **contributor** compensation (`history/260729-TRSL-ContributorRights-Research.md`), not to the commercial-entitlement pricing paid by TRSL's commercial users — but any employee/contractor arrangement behind a Phase's own development work should account for it.
|
||||
|
||||
## 2. EU-level constraint (scoping correction to prior research)
|
||||
|
||||
|
|
@ -24,7 +24,7 @@ Compare TRSL's Phase/Initial Target/Development Credit/Conversion Event model (`
|
|||
1. **Follow FSL's simplification over BSL's flexibility.** BSL's per-licensor Additional Use Grant text is the single most-criticized design choice in this family (by BSL's own successor). TRSL's working default of a closed `{MIT, Apache-2.0}` Future License enum and no per-Phase custom Change License text is the right call — confirmed against real precedent, not just internal preference.
|
||||
2. **FSL's per-version fixed trigger is a useful contrast to TRSL's revenue-plus-remission model.** FSL treats every version identically (2 years, always). TRSL's Target Multiple + Development Credit + Remission Credit model is more expressive (lets commercial validation *shorten* the effective protection period) but also more novel — meaning TRSL carries more of the definitional burden itself; it cannot lean on FSL's or BSL's established case law or community familiarity for its trigger mechanism, only for its *conversion clause structure* (automatic, self-executing, no discretionary declaration).
|
||||
3. **PolyForm Noncommercial's use-case taxonomy is a solid drafting reference for TRSL's noncommercial permitted-use clause** (working default Q1), but contributes nothing to TRSL's conversion mechanism, which must be original.
|
||||
4. **None of BSL, FSL, or PolyForm include a patent grant in the pre-conversion license text.** This is worth flagging for T03/T06: TRSL is not deviating from norm by omitting one, but concept §21.1 already lists "patent treatment" as a required license component — worth deciding deliberately rather than by silent omission (see `specs/research/TRSL-FutureLicense-PatentPrecedent.md`).
|
||||
4. **None of BSL, FSL, or PolyForm include a patent grant in the pre-conversion license text.** This is worth flagging for T03/T06: TRSL is not deviating from norm by omitting one, but concept §21.1 already lists "patent treatment" as a required license component — worth deciding deliberately rather than by silent omission (see `history/260729-TRSL-FutureLicense-PatentPrecedent.md`).
|
||||
5. **Elastic License 2.0 confirms the category boundary**: a "source-available with commercial restriction" license is not automatically a delayed-open-source license. TRSL's identity is specifically the *automatic, self-executing conversion* — this should be emphasized in any explainer material (README, T06 draft) as the feature that distinguishes TRSL from the larger and more common "just restrict commercial use forever" category that ELv2 represents.
|
||||
|
||||
## 4. Open items for T06
|
||||
|
|
@ -29,7 +29,7 @@ TRSL's pre-conversion Phase satisfies all three:
|
|||
2. Modification/redistribution permitted subject to the commercial-use restriction (a "minimal restriction to protect the producer's business model" in Fair Source's own words).
|
||||
3. TRSL's Conversion Event **is** a DOSP mechanism — a mandatory, eventual transition to an OSI-approved license (MIT/Apache-2.0).
|
||||
|
||||
Fair Source is explicitly a **category label and definition, not a specific enforceable license text** — it does not itself specify a trigger mechanism. TRSL's revenue/Target-based trigger is therefore a *novel instance* within the Fair Source category, not something Fair Source's own material provides precedent for at the mechanism level (see `specs/research/TRSL-PriorArt-Survey.md` §3.2 for the closer per-version time-trigger precedent from FSL).
|
||||
Fair Source is explicitly a **category label and definition, not a specific enforceable license text** — it does not itself specify a trigger mechanism. TRSL's revenue/Target-based trigger is therefore a *novel instance* within the Fair Source category, not something Fair Source's own material provides precedent for at the mechanism level (see `history/260729-TRSL-PriorArt-Survey.md` §3.2 for the closer per-version time-trigger precedent from FSL).
|
||||
|
||||
## 3. Recommended terminology guardrail (confirms and slightly sharpens README's existing table)
|
||||
|
||||
|
|
@ -1,7 +1,9 @@
|
|||
# Target Revenue Source License — Draft Skeleton (Non-Binding)
|
||||
|
||||
**Archived 2026-07-29:** this file was originally `specs/TargetRevenueSourceLicense-Draft.md` (WP-0001-T06's first-pass synthesis). It has been moved into `history/` as a dated research artifact and superseded by `specs/TargetRevenueSourceLicense-V1C1.md` — the first candidate written as actual operative license text rather than a bracket-annotated skeleton. This file remains useful as the record of *why* each V1C1 clause reads the way it does (its `[CONFIRMED BY RESEARCH]` / `[LEGAL]` / `[WORKING DEFAULT]` / `[OPEN]` tagging maps directly to V1C1's appendix of candidate notes).
|
||||
|
||||
**Document version:** TRSL-Draft-0.1
|
||||
**Status:** DRAFT SKELETON — NOT FINAL LEGAL TEXT — NOT FOR PRODUCTION USE
|
||||
**Status:** DRAFT SKELETON — NOT FINAL LEGAL TEXT — NOT FOR PRODUCTION USE — SUPERSEDED BY `specs/TargetRevenueSourceLicense-V1C1.md`
|
||||
**Prepared by:** Agent synthesis of `workplans/TREV-WP-0001-license-prior-art-research.md` T01–T05, for specialist legal review
|
||||
**Human accept gate:** This document is "ready for review," not "done." `workplans/TREV-WP-0001-license-prior-art-research.md` T06 must not be marked `done` until a human maintainer accepts it as adequate briefing material for counsel (`SCOPE.md` §4, `CONTRIBUTING.md`).
|
||||
|
||||
|
|
@ -16,13 +18,13 @@ Every clause below is one of:
|
|||
- **[WORKING DEFAULT]** — reflects a Stage 0 provisional answer from `specs/OpenQuestions-WorkingDefaults.md`; not yet promoted to permanent norm.
|
||||
- **[OPEN]** — genuinely undecided; concept §24 or PRD §14 question not yet resolved by any research task.
|
||||
|
||||
This skeleton follows the component list already identified in `specs/TargetRevenueLicenseConcept.md` §21.1, and incorporates the research findings in `specs/research/`.
|
||||
This skeleton follows the component list already identified in `specs/TargetRevenueLicenseConcept.md` §21.1, and incorporates the research findings in the `history/260729-TRSL-*.md` files listed in the summary table at the end of this document.
|
||||
|
||||
---
|
||||
|
||||
## 1. Definitions [LEGAL, structural recommendation CONFIRMED BY RESEARCH]
|
||||
|
||||
Per `specs/research/TRSL-Jurisdiction-StandardTerms.md` §5, German AGB law's Transparenzgebot can void a clause for ambiguity alone, independent of substantive fairness. The final license **should** include a dedicated Definitions section, not scattered inline first-use definitions. At minimum, define objectively (priority order per `specs/research/TRSL-Jurisdiction-StandardTerms.md` §4):
|
||||
Per `history/260729-TRSL-Jurisdiction-StandardTerms.md` §5, German AGB law's Transparenzgebot can void a clause for ambiguity alone, independent of substantive fairness. The final license **should** include a dedicated Definitions section, not scattered inline first-use definitions. At minimum, define objectively (priority order per `history/260729-TRSL-Jurisdiction-StandardTerms.md` §4):
|
||||
|
||||
1. **Settled Payment** [LEGAL] — exact settlement mechanics (processor clearance, chargeback window, business-day count).
|
||||
2. **Commercial Use** [LEGAL, working default scope in Q2] — objective test distinguishing personal/research/nonprofit/educational use (`specs/OpenQuestions-WorkingDefaults.md` Q1–Q2) from commercial use, including treatment of affiliates, contractors, mixed-purpose, and public-sector use.
|
||||
|
|
@ -31,51 +33,51 @@ Per `specs/research/TRSL-Jurisdiction-StandardTerms.md` §5, German AGB law's Tr
|
|||
|
||||
## 2. Permitted noncommercial use [WORKING DEFAULT / LEGAL]
|
||||
|
||||
**[WORKING DEFAULT, Q1]** During a protected Phase, noncommercial users may view source, evaluate, test, and use the software for personal, research, educational, and recognized non-profit purposes, in a scope similar to PolyForm Noncommercial 1.0.0's use-case taxonomy (`specs/research/TRSL-PriorArt-Survey.md` §3.3; confirmed structurally applicable, not a license text to copy verbatim).
|
||||
**[WORKING DEFAULT, Q1]** During a protected Phase, noncommercial users may view source, evaluate, test, and use the software for personal, research, educational, and recognized non-profit purposes, in a scope similar to PolyForm Noncommercial 1.0.0's use-case taxonomy (`history/260729-TRSL-PriorArt-Survey.md` §3.3; confirmed structurally applicable, not a license text to copy verbatim).
|
||||
|
||||
**[LEGAL]** Exact clause text, including modification and redistribution rights during the protected Phase, requires specialist drafting.
|
||||
|
||||
## 3. Commercial-use restriction and entitlement requirement [CONFIRMED BY RESEARCH / LEGAL]
|
||||
|
||||
**[CONFIRMED BY RESEARCH]** Restricting commercial use for a protected period, while permitting broader noncommercial use, is a well-established license category (Fair Source's "minimal restrictions to protect the producer's business model," `specs/research/TRSL-Terminology-Guardrails.md` §2) with direct precedent in BSL 1.1's production-use gate and FSL's narrower "do not undermine the producer" restriction (`specs/research/TRSL-PriorArt-Survey.md` §2).
|
||||
**[CONFIRMED BY RESEARCH]** Restricting commercial use for a protected period, while permitting broader noncommercial use, is a well-established license category (Fair Source's "minimal restrictions to protect the producer's business model," `history/260729-TRSL-Terminology-Guardrails.md` §2) with direct precedent in BSL 1.1's production-use gate and FSL's narrower "do not undermine the producer" restriction (`history/260729-TRSL-PriorArt-Survey.md` §2).
|
||||
|
||||
**[LEGAL]** The commercial-use gate itself (requiring a Commercial Use Agreement per `specs/TargetRevenueLicenseConcept.md` §21.2) needs drafted text; the **definition** of "commercial use" that triggers it is the single highest Transparenzgebot-exposure term in the framework (`specs/research/TRSL-Jurisdiction-StandardTerms.md` §4 item 2) and is explicitly **[OPEN]** pending legal input.
|
||||
**[LEGAL]** The commercial-use gate itself (requiring a Commercial Use Agreement per `specs/TargetRevenueLicenseConcept.md` §21.2) needs drafted text; the **definition** of "commercial use" that triggers it is the single highest Transparenzgebot-exposure term in the framework (`history/260729-TRSL-Jurisdiction-StandardTerms.md` §4 item 2) and is explicitly **[OPEN]** pending legal input.
|
||||
|
||||
## 4. Modification and redistribution during the protected Phase [LEGAL]
|
||||
|
||||
Not resolved by this research pass. Recommend drafting from the BSL 1.1 baseline ("copy, modify, create derivative works, redistribute, and make non-production use") since it is the closest confirmed precedent (`specs/research/TRSL-PriorArt-Survey.md` §2), adapted to TRSL's commercial-use gate rather than BSL's production-use gate. **[LEGAL]** for final wording.
|
||||
Not resolved by this research pass. Recommend drafting from the BSL 1.1 baseline ("copy, modify, create derivative works, redistribute, and make non-production use") since it is the closest confirmed precedent (`history/260729-TRSL-PriorArt-Survey.md` §2), adapted to TRSL's commercial-use gate rather than BSL's production-use gate. **[LEGAL]** for final wording.
|
||||
|
||||
## 5. Patent treatment [CONFIRMED BY RESEARCH, recommendation given / LEGAL for text]
|
||||
|
||||
**[CONFIRMED BY RESEARCH]** Neither BSL, FSL, nor PolyForm Noncommercial include a pre-conversion patent grant (`specs/research/TRSL-PriorArt-Survey.md` §3.4) — omitting one would not be unusual. However, `specs/research/TRSL-FutureLicense-PatentPrecedent.md` §4 recommends TRSL **include** a minimal express patent license for the pre-conversion Phase, scoped like Apache-2.0 Section 3 (contribution-scoped, litigation-terminable), because TRSL's commercial-entitlement model is closer to a paid commercial license than a permissive OSS grant, and commercial licenses conventionally address patent scope explicitly.
|
||||
**[CONFIRMED BY RESEARCH]** Neither BSL, FSL, nor PolyForm Noncommercial include a pre-conversion patent grant (`history/260729-TRSL-PriorArt-Survey.md` §3.4) — omitting one would not be unusual. However, `history/260729-TRSL-FutureLicense-PatentPrecedent.md` §4 recommends TRSL **include** a minimal express patent license for the pre-conversion Phase, scoped like Apache-2.0 Section 3 (contribution-scoped, litigation-terminable), because TRSL's commercial-entitlement model is closer to a paid commercial license than a permissive OSS grant, and commercial licenses conventionally address patent scope explicitly.
|
||||
|
||||
**[LEGAL]** Exact clause text for the pre-conversion patent grant.
|
||||
|
||||
## 6. Future License and automatic conversion [CONFIRMED BY RESEARCH]
|
||||
|
||||
**[WORKING DEFAULT, Q3]** `future_license` ∈ {MIT, Apache-2.0}, chosen per Phase at declaration time. See `specs/research/TRSL-FutureLicense-PatentPrecedent.md` §3 for a project-level recommendation (Apache-2.0 default where patentable technique is plausible; MIT where simplicity is prioritized and patent risk is judged negligible) — this is Phase-author guidance, not a framework-level forced default.
|
||||
**[WORKING DEFAULT, Q3]** `future_license` ∈ {MIT, Apache-2.0}, chosen per Phase at declaration time. See `history/260729-TRSL-FutureLicense-PatentPrecedent.md` §3 for a project-level recommendation (Apache-2.0 default where patentable technique is plausible; MIT where simplicity is prioritized and patent risk is judged negligible) — this is Phase-author guidance, not a framework-level forced default.
|
||||
|
||||
**[CONFIRMED BY RESEARCH]** The conversion mechanism should follow the established two-step structure confirmed across both BSL 1.1 and FSL (`specs/research/TRSL-PriorArt-Survey.md` §2, §4): the restricted rights **terminate**, and rights under the Future License are granted **in their place**, automatically, at the Conversion Event — not a discretionary re-licensing act. This matches `specs/TargetRevenueLicenseConcept.md` Rule 6 and Rule 9 exactly and requires no structural invention; only legal wording.
|
||||
**[CONFIRMED BY RESEARCH]** The conversion mechanism should follow the established two-step structure confirmed across both BSL 1.1 and FSL (`history/260729-TRSL-PriorArt-Survey.md` §2, §4): the restricted rights **terminate**, and rights under the Future License are granted **in their place**, automatically, at the Conversion Event — not a discretionary re-licensing act. This matches `specs/TargetRevenueLicenseConcept.md` Rule 6 and Rule 9 exactly and requires no structural invention; only legal wording.
|
||||
|
||||
**[LEGAL]** Final clause text. Recommend phrasing anchored on: "The Conversion Event occurs automatically when [Outstanding Target, as defined in §1, equals zero]. Upon the Conversion Event, the rights granted under §3 of this License terminate, and the Future License identified in the applicable Phase Manifest is granted in their place, without further act by either party." Precise legal phrasing per counsel.
|
||||
|
||||
## 7. Termination and cure [OPEN]
|
||||
|
||||
Not researched in this pass beyond confirming that BSL/FSL/ELv2 all include violation-cure mechanisms (typically a 30-day-scale remediation window before permanent termination, per `specs/research/TRSL-PriorArt-Survey.md` §2 Elastic License 2.0 entry). **[LEGAL]** for TRSL-specific text; **[OPEN]** whether TRSL's cure period should differ from this norm given its credit/ledger model (e.g., whether a cured violation should generate a compensating ledger entry rather than simply restoring rights).
|
||||
Not researched in this pass beyond confirming that BSL/FSL/ELv2 all include violation-cure mechanisms (typically a 30-day-scale remediation window before permanent termination, per `history/260729-TRSL-PriorArt-Survey.md` §2 Elastic License 2.0 entry). **[LEGAL]** for TRSL-specific text; **[OPEN]** whether TRSL's cure period should differ from this norm given its credit/ledger model (e.g., whether a cured violation should generate a compensating ledger entry rather than simply restoring rights).
|
||||
|
||||
## 8. Warranty and liability exclusions [LEGAL]
|
||||
|
||||
Standard boilerplate across all surveyed licenses (MIT's "AS IS... WITHOUT WARRANTY" language, confirmed verbatim in `specs/research/TRSL-FutureLicense-PatentPrecedent.md` §1, is the baseline pattern). **[LEGAL]** for TRSL-specific text; no structural research finding beyond confirming this is universal practice worth following, not deviating from.
|
||||
Standard boilerplate across all surveyed licenses (MIT's "AS IS... WITHOUT WARRANTY" language, confirmed verbatim in `history/260729-TRSL-FutureLicense-PatentPrecedent.md` §1, is the baseline pattern). **[LEGAL]** for TRSL-specific text; no structural research finding beyond confirming this is universal practice worth following, not deviating from.
|
||||
|
||||
## 9. Contributor rights [CONFIRMED BY RESEARCH — separate deliverable]
|
||||
|
||||
**[CONFIRMED BY RESEARCH]** A Developer Certificate of Origin alone is **not** sufficient for TRSL, because its certification is scoped to "the open source license indicated in the file" at time of contribution and does not extend to a future, different Future License (`specs/research/TRSL-ContributorRights-Research.md` §2). TRSL requires a **Contributor License Agreement** (not copyright assignment — assignment is a heavier ask and depresses contribution volume) scoped narrowly to: (a) the current Phase's TRSL terms, and (b) the Phase's **already-declared** Future License at the Conversion Event (`specs/research/TRSL-ContributorRights-Research.md` §4).
|
||||
**[CONFIRMED BY RESEARCH]** A Developer Certificate of Origin alone is **not** sufficient for TRSL, because its certification is scoped to "the open source license indicated in the file" at time of contribution and does not extend to a future, different Future License (`history/260729-TRSL-ContributorRights-Research.md` §2). TRSL requires a **Contributor License Agreement** (not copyright assignment — assignment is a heavier ask and depresses contribution volume) scoped narrowly to: (a) the current Phase's TRSL terms, and (b) the Phase's **already-declared** Future License at the Conversion Event (`history/260729-TRSL-ContributorRights-Research.md` §4).
|
||||
|
||||
**[LEGAL, separate deliverable]** The CLA text itself is out of scope for this license draft — recommend a dedicated `TRSL-ContributorLicenseAgreement-Draft.md` once external contributions become an active near-term need. Until then, `CONTRIBUTING.md`'s current block on external contributions to governed Milestone Releases remains in effect.
|
||||
|
||||
## 10. Terminology guardrail (non-clause, drafting instruction)
|
||||
|
||||
Per `specs/research/TRSL-Terminology-Guardrails.md` §3: pre-conversion software under this license must never be described as "Open Source," "free software," or "open core" in any recital, preamble, or accompanying documentation — it is **source-available** (noncommercial use) or **commercially licensed** (commercial use). Post-conversion, the Milestone Release may be described as Open Source under its declared Future License without qualification. This guardrail applies to marketing and documentation copy as much as to the license text itself.
|
||||
Per `history/260729-TRSL-Terminology-Guardrails.md` §3: pre-conversion software under this license must never be described as "Open Source," "free software," or "open core" in any recital, preamble, or accompanying documentation — it is **source-available** (noncommercial use) or **commercially licensed** (commercial use). Post-conversion, the Milestone Release may be described as Open Source under its declared Future License without qualification. This guardrail applies to marketing and documentation copy as much as to the license text itself.
|
||||
|
||||
## 11. What this draft does not attempt
|
||||
|
||||
|
|
@ -83,7 +85,7 @@ Per `specs/TargetRevenueLicenseConcept.md` §21.3 and `SCOPE.md` §3: this draft
|
|||
|
||||
## 12. Legal review requirement
|
||||
|
||||
This document is a product/engineering research synthesis, not legal advice or final license text. Per `specs/TargetRevenueLicenseConcept.md` §21.5, final drafting requires specialist review covering (at minimum): automatic conditional license grants, standard-terms law (Transparenzgebot and equivalents — `specs/research/TRSL-Jurisdiction-StandardTerms.md`), copyright and patent rights, contributor rights (`specs/research/TRSL-ContributorRights-Research.md`), audit and evidence provisions, international enforceability, consumer/business distinctions (`specs/research/TRSL-Jurisdiction-StandardTerms.md` §2's EU consumer-law scoping), and insolvency/service-discontinuity scenarios.
|
||||
This document is a product/engineering research synthesis, not legal advice or final license text. Per `specs/TargetRevenueLicenseConcept.md` §21.5, final drafting requires specialist review covering (at minimum): automatic conditional license grants, standard-terms law (Transparenzgebot and equivalents — `history/260729-TRSL-Jurisdiction-StandardTerms.md`), copyright and patent rights, contributor rights (`history/260729-TRSL-ContributorRights-Research.md`), audit and evidence provisions, international enforceability, consumer/business distinctions (`history/260729-TRSL-Jurisdiction-StandardTerms.md` §2's EU consumer-law scoping), and insolvency/service-discontinuity scenarios.
|
||||
|
||||
---
|
||||
|
||||
|
|
@ -91,10 +93,10 @@ This document is a product/engineering research synthesis, not legal advice or f
|
|||
|
||||
| Source | Contribution to this draft |
|
||||
|---|---|
|
||||
| `specs/research/TRSL-PriorArt-Survey.md` | §3–§4, §6 (conversion structure, restriction scope precedent) |
|
||||
| `specs/research/TRSL-Terminology-Guardrails.md` | §10 (terminology guardrail) |
|
||||
| `specs/research/TRSL-FutureLicense-PatentPrecedent.md` | §5, §6 (patent treatment, Future License guidance) |
|
||||
| `specs/research/TRSL-ContributorRights-Research.md` | §9 (contributor rights, CLA recommendation) |
|
||||
| `specs/research/TRSL-Jurisdiction-StandardTerms.md` | §1, §3 (definitions structure, priority terms) |
|
||||
| `history/260729-TRSL-PriorArt-Survey.md` | §3–§4, §6 (conversion structure, restriction scope precedent) |
|
||||
| `history/260729-TRSL-Terminology-Guardrails.md` | §10 (terminology guardrail) |
|
||||
| `history/260729-TRSL-FutureLicense-PatentPrecedent.md` | §5, §6 (patent treatment, Future License guidance) |
|
||||
| `history/260729-TRSL-ContributorRights-Research.md` | §9 (contributor rights, CLA recommendation) |
|
||||
| `history/260729-TRSL-Jurisdiction-StandardTerms.md` | §1, §3 (definitions structure, priority terms) |
|
||||
|
||||
**Next step:** human review and accept per the T06 gate, then route to specialist counsel with this document and its five research inputs as the briefing package.
|
||||
|
|
@ -337,7 +337,7 @@ The MVP corresponds to the "Proposed Initial Deliverables" already identified in
|
|||
2. `PhaseManifestSpecification.md` / `TargetLedgerSpecification.md` — field tiers and fold rules — **WP-0003**.
|
||||
3. Machine-readable schemas + pure Outstanding Target fold + golden Phase package under `examples/` — **WP-0002**.
|
||||
4. `OpenQuestions-WorkingDefaults.md` — provisional defaults for conversion-critical open questions — **done (provisional)**.
|
||||
5. `TargetRevenueSourceLicense-Draft.md` — non-binding legal drafting basis — **WP-0001** (human accept gate).
|
||||
5. `TargetRevenueSourceLicense-V1C1.md` — first candidate operative license text (Version 1, Candidate 1), non-binding — **WP-0001** (human accept gate). Supersedes the earlier draft skeleton, archived at `history/260729-TargetRevenueSourceLicense-Draft.md`.
|
||||
6. `MonetizationExtensionSpecification.md` (or Stage 0 stub) + path to `CanonicalMonetizationProfiles.md`.
|
||||
|
||||
**Tier B — After Stage 0 package:**
|
||||
|
|
@ -394,8 +394,8 @@ Workplan mapping (see `workplans/`, `SCOPE.md` §4):
|
|||
|
||||
### Phase 2 — Legal drafting basis (active — WP-0001)
|
||||
|
||||
- Produce `TargetRevenueSourceLicense-Draft.md` for specialist legal review (automatic conditional grants, standard-terms law, contributor rights, cross-border enforceability — concept §21.5).
|
||||
- Human accept required before marking draft skeleton complete.
|
||||
- Produce `TargetRevenueSourceLicense-V1C1.md` for specialist legal review (automatic conditional grants, standard-terms law, contributor rights, cross-border enforceability — concept §21.5).
|
||||
- Human accept required before a future candidate can become official V1.0.
|
||||
|
||||
### Phase 3 — Extension and profile catalog
|
||||
|
||||
|
|
|
|||
159
specs/TargetRevenueSourceLicense-V1C1.md
Normal file
159
specs/TargetRevenueSourceLicense-V1C1.md
Normal file
|
|
@ -0,0 +1,159 @@
|
|||
# Target Revenue Source License
|
||||
|
||||
**Version 1.0, Candidate 1 (V1C1)**
|
||||
|
||||
---
|
||||
|
||||
> **PRELIMINARY CANDIDATE — SUBJECT TO CHANGE — NOT FINAL — DO NOT USE FOR PRODUCTION SOFTWARE OR REAL COMMERCIAL TRANSACTIONS**
|
||||
>
|
||||
> This is the first working candidate of the Target Revenue Source License, written as operative license text rather than a research outline. It is offered so that the license can be read, tested against real scenarios, and reviewed as a whole — **not** as a final, legally binding, or production-ready document.
|
||||
>
|
||||
> Before any candidate of this license can become the official **Version 1.0** release:
|
||||
>
|
||||
> 1. it must pass specialist legal review in every jurisdiction where it will be used (see `history/260729-TRSL-Jurisdiction-StandardTerms.md` for known exposure, particularly German AGB/Transparenzgebot clarity requirements);
|
||||
> 2. every item listed in **Appendix A — Candidate Notes** below must be resolved or explicitly and knowingly accepted by the Licensor;
|
||||
> 3. a human maintainer must explicitly accept it, per `workplans/TREV-WP-0001-license-prior-art-research.md` T06 and `CONTRIBUTING.md`'s human-decision-gate policy.
|
||||
>
|
||||
> Until all three conditions are met, this document is a **drafting candidate**, not a license anyone should rely on. Bracketed placeholders (e.g. `[Licensor Legal Name]`) must be filled in per deployment; they are normal template blanks, not indicators of incompleteness — the substantive incompleteness is tracked separately in Appendix A.
|
||||
|
||||
---
|
||||
|
||||
## Preamble
|
||||
|
||||
This Target Revenue Source License ("**License**") governs the Software identified in the applicable Phase Manifest. It implements the Target Revenue Framework: a defined development Phase accumulates Development Credit and Remission Credit against an immutable Initial Target until the Milestone Release automatically and irrevocably converts to a declared permissive Future License.
|
||||
|
||||
Commercial beneficiaries fund the creation and early availability of a software improvement; once the declared target is satisfied, the governed release becomes permissively open source.
|
||||
|
||||
## 1. Definitions
|
||||
|
||||
Capitalized terms used in this License have the meanings given below. Where a term is also defined in the Phase Manifest or Target Ledger for a specific Phase, the Phase Manifest and Target Ledger govern the *values* (amounts, dates, identifiers) and this License governs the *legal effect* of those values — the two must not be read as conflicting definitions of the same concept.
|
||||
|
||||
**"Commercial Entitlement"** means a right, purchased or otherwise granted under a Commercial Use Agreement, to make Commercial Use of the Software during a Phase.
|
||||
|
||||
**"Commercial Use"** means use of the Software by or for any person or organization other than in Noncommercial Use as defined below. [Candidate note: this is a working definition per `specs/OpenQuestions-WorkingDefaults.md` Q2 and is flagged in Appendix A as needing objective refinement for affiliates, contractors, mixed-purpose, and public-sector use before V1.0.]
|
||||
|
||||
**"Commercial Use Agreement"** means the separate agreement, referenced by the applicable Phase Manifest, under which a Commercial Entitlement is purchased or granted. This License does not itself set pricing, metering, or payment terms — those are governed by the Commercial Use Agreement.
|
||||
|
||||
**"Conversion Event"** means the moment the Outstanding Target for a Phase reaches zero, as computed from the Phase Manifest and Target Ledger per the Target Ledger Specification. The Conversion Event occurs automatically and is not conditioned on any declaration, attestation, or other act by the Licensor or any Trust Service.
|
||||
|
||||
**"Development Credit"** means the portion of a collected and settled payment explicitly allocated toward satisfying the Initial Target of a specific Phase, as recorded in that Phase's Target Ledger.
|
||||
|
||||
**"Future License"** means the permissive license identified in the applicable Phase Manifest, being either the MIT License or the Apache License, Version 2.0, which applies to the Milestone Release upon the Conversion Event.
|
||||
|
||||
**"Initial Target"** means the immutable monetary target declared for a Phase in its Phase Manifest.
|
||||
|
||||
**"Licensor"** means **[Licensor Legal Name]**, the party that publishes the Phase Manifest and holds the rights necessary to grant this License and the Future License for the Milestone Release.
|
||||
|
||||
**"Milestone Release"** means the precisely identified software release designated in the applicable Phase Manifest, identified by an immutable source revision, release artifact, or cryptographic digest.
|
||||
|
||||
**"Noncommercial Use"** means use of the Software for personal purposes, private study, hobby or amateur projects; use by any charitable organization, educational institution, public research organization, or government institution acting in a non-revenue-generating capacity; or other use of a materially similar character. [Candidate note: modeled on PolyForm Noncommercial 1.0.0's use-case taxonomy per `history/260729-TRSL-PriorArt-Survey.md` §3.3; exact scope flagged in Appendix A.]
|
||||
|
||||
**"Outstanding Target"** means, at any time, `max(0, Initial Target − cumulative Development Credit − cumulative Remission Credit)` for a Phase, as computed from that Phase's Target Ledger.
|
||||
|
||||
**"Phase"** means a bounded development undertaking governed by one Initial Target, one Milestone Release, one degeneration policy, and one Future License declaration, as declared in a Phase Manifest.
|
||||
|
||||
**"Phase Manifest"** means the published, immutable declaration identifying a Phase, its Milestone Release, Initial Target, Future License, degeneration policy, and Target Ledger location, as specified in the Phase Manifest Specification.
|
||||
|
||||
**"Remission Credit"** means a transparent, non-revenue reduction of a Phase's Outstanding Target, generated under that Phase's published degeneration policy and recorded in the Target Ledger.
|
||||
|
||||
**"Settled Payment"** means a payment that has cleared through its payment processor and is no longer subject to reversal in the ordinary course (chargeback, dispute, or equivalent), as further specified by the applicable Commercial Use Agreement or monetization extension. [Candidate note: exact settlement mechanics flagged in Appendix A as the highest-priority definition needing objective refinement.]
|
||||
|
||||
**"Software"** means the source code, object code, and associated documentation of the Milestone Release identified in the applicable Phase Manifest.
|
||||
|
||||
**"Target Ledger"** means the append-only record of Development Credit, Remission Credit, and correction entries for a Phase, as specified in the Target Ledger Specification.
|
||||
|
||||
**"You"** or **"Licensee"** means the individual or entity exercising rights under this License.
|
||||
|
||||
## 2. Grant of Rights for Noncommercial Use
|
||||
|
||||
Subject to the terms of this License, the Licensor grants You a worldwide, royalty-free, non-exclusive license, during the applicable Phase, to:
|
||||
|
||||
(a) use, reproduce, and study the Software for any Noncommercial Use;
|
||||
|
||||
(b) modify the Software and create derivative works of it for any Noncommercial Use; and
|
||||
|
||||
(c) redistribute the Software and Your modifications, in source or object form, for any Noncommercial Use, provided that You include this License, unmodified, with any such redistribution, and that You do not remove or alter any copyright, patent, trademark, or attribution notices contained in the Software.
|
||||
|
||||
This grant does not extend to Commercial Use. Commercial Use requires a Commercial Entitlement under Section 3.
|
||||
|
||||
## 3. Commercial Use
|
||||
|
||||
You may not make Commercial Use of the Software during the applicable Phase unless You hold a valid, current Commercial Entitlement under a Commercial Use Agreement with the Licensor covering the applicable Phase. A Commercial Entitlement granted under one Phase's Commercial Use Agreement does not extend to a later Phase's Milestone Release unless the Commercial Use Agreement expressly says so.
|
||||
|
||||
This Section 3 states the existence and boundary of the commercial-use restriction. It does not itself set pricing, invoicing, metering, audit rights, or payment terms — those are governed exclusively by the applicable Commercial Use Agreement.
|
||||
|
||||
## 4. Patent License
|
||||
|
||||
Subject to the terms of this License, each contributor to the Software grants You, during the applicable Phase and solely to the extent of rights granted under Sections 2 and 3, a perpetual (subject to the termination below), worldwide, non-exclusive, no-charge, royalty-free patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Software, limited to those patent claims licensable by that contributor that are necessarily infringed by their contribution(s) alone or by combination of their contribution(s) with the Software.
|
||||
|
||||
If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Software or a contribution incorporated within it constitutes direct or contributory patent infringement, then any patent licenses granted to You under this Section 4 for the Software shall terminate as of the date such litigation is filed.
|
||||
|
||||
[Candidate note: modeled on Apache License 2.0 §3, adapted to this License's Phase structure, per `history/260729-TRSL-FutureLicense-PatentPrecedent.md` §4. Flagged in Appendix A pending legal review.]
|
||||
|
||||
## 5. Automatic Conversion to the Future License
|
||||
|
||||
**5.1 Automatic effect.** Upon the Conversion Event for a Phase, the rights and restrictions in Sections 3 (Commercial Use) of this License, as they apply to that Phase's Milestone Release, terminate automatically. In their place, the Milestone Release is licensed under the Future License identified in that Phase's Phase Manifest, effective as of the Conversion Event, without any further act, declaration, or attestation required by the Licensor, any Trust Service, or any other party.
|
||||
|
||||
**5.2 Irrevocability.** Once a valid Conversion Event has occurred for a Phase, no subsequent refund, chargeback, accounting correction, dispute, or termination of this License for an unrelated breach shall revoke, suspend, or otherwise impair the Future License grant for that Phase's Milestone Release. Any shortfall or dispute arising after a Conversion Event is a commercial or accounting matter between the relevant parties and does not reinstate a commercial-use restriction over already-converted Software.
|
||||
|
||||
**5.3 Prior freedom preserved.** A later Phase covering subsequent improvements to the Software does not restrict, withdraw, or otherwise affect the rights granted under the Future License for an earlier Phase's already-converted Milestone Release.
|
||||
|
||||
**5.4 Evidence, not cause.** A Trust Service may publish a Conversion Attestation documenting a Conversion Event. Such an attestation is evidence that the Conversion Event occurred; it is not a condition of, and its absence or delay does not postpone, the automatic effect described in Section 5.1. Any person may independently verify whether a Conversion Event has occurred directly from the Phase Manifest and Target Ledger.
|
||||
|
||||
## 6. Successive Phases
|
||||
|
||||
The Licensor may declare a new Phase covering subsequent improvements to the Software following a Milestone Release's Conversion Event. Each Phase is independently governed by its own Phase Manifest, Initial Target, degeneration policy, and Target Ledger. Nothing in a later Phase's Phase Manifest may be construed to reduce or withdraw rights already granted under Section 5 for an earlier Phase's Milestone Release.
|
||||
|
||||
## 7. Term and Termination
|
||||
|
||||
**7.1 Term.** This License applies to the Software for the duration of the applicable Phase, and, for the Milestone Release, indefinitely following that Phase's Conversion Event under the Future License.
|
||||
|
||||
**7.2 Termination for breach.** If You breach Section 3 (Commercial Use) or Section 2(c) (redistribution notice requirement), the Licensor may terminate this License as to You. Before such termination becomes effective, the Licensor shall provide You written notice of the breach; if You cure the breach within thirty (30) days of that notice, this License continues in effect. A second breach of the same provision within twelve (12) months may be terminated immediately without a further cure opportunity.
|
||||
|
||||
**7.3 Effect of termination.** Termination under this Section 7 affects only Your rights under Sections 2 and 3 for the Phase in which the breach occurred. It does not affect any rights already vested under Section 5 (Automatic Conversion) for a Milestone Release whose Conversion Event has already occurred, per Section 5.2.
|
||||
|
||||
[Candidate note: cure-period length and structure modeled on the norm observed across BSL 1.1, FSL, and Elastic License 2.0 in `history/260729-TRSL-PriorArt-Survey.md` §2; whether a cured violation should also generate a Target Ledger entry is flagged **[OPEN]** in Appendix A.]
|
||||
|
||||
## 8. Disclaimer of Warranty
|
||||
|
||||
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NONINFRINGEMENT. THE LICENSOR DOES NOT WARRANT THAT THE SOFTWARE WILL BE ERROR-FREE OR THAT ANY PHASE WILL REACH ITS CONVERSION EVENT.
|
||||
|
||||
## 9. Limitation of Liability
|
||||
|
||||
IN NO EVENT SHALL THE LICENSOR OR ANY CONTRIBUTOR BE LIABLE FOR ANY CLAIM, DAMAGES, OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT, OR OTHERWISE, ARISING FROM, OUT OF, OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE, EXCEPT TO THE EXTENT SUCH LIMITATION IS PROHIBITED BY APPLICABLE LAW.
|
||||
|
||||
## 10. Trademarks
|
||||
|
||||
This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary attribution.
|
||||
|
||||
## 11. General Provisions
|
||||
|
||||
**11.1 Governing law and venue.** [To be specified per deployment; see Appendix A — jurisdiction selection affects Section 1's "Commercial Use" and "Settled Payment" definitions and is not resolved by this candidate.]
|
||||
|
||||
**11.2 Severability.** If any provision of this License is held unenforceable, the remaining provisions remain in full force, and the unenforceable provision shall be reformed to the minimum extent necessary to make it enforceable.
|
||||
|
||||
**11.3 No waiver.** Failure to enforce any provision of this License is not a waiver of future enforcement of that or any other provision.
|
||||
|
||||
**11.4 Entire agreement (as to licensing).** This License, together with the applicable Phase Manifest and, where applicable, the Commercial Use Agreement, constitutes the entire agreement between You and the Licensor regarding the Software's licensing terms. Operations, service, and consulting arrangements are governed by separate agreements, if any, and are not part of this License.
|
||||
|
||||
**11.5 Definitions control.** Marketing materials, documentation, or other non-normative communications about the Software must not describe pre-Conversion-Event Software as "Open Source," "free software," or "open core." Pre-conversion Noncommercial Use is **source-available**; pre-conversion Commercial Use requires a **Commercial Entitlement**; only post-conversion Software may be described as Open Source, under the Future License.
|
||||
|
||||
---
|
||||
|
||||
## Appendix A — Candidate Notes (Non-Normative)
|
||||
|
||||
This appendix is not part of the operative license text. It tracks what must be resolved before this candidate can become official Version 1.0, and links each item to its research basis. Removing this appendix without resolving its items would not make the license more final — it would just make the gaps invisible.
|
||||
|
||||
| # | Section | Item | Status | Research basis |
|
||||
|---|---|---|---|---|
|
||||
| 1 | §1, §3 | Objective definition of "Commercial Use" (affiliates, contractors, mixed-purpose, public-sector edge cases) | **[LEGAL, OPEN]** | `history/260729-TRSL-Jurisdiction-StandardTerms.md` §4 item 2 |
|
||||
| 2 | §1 | Exact mechanics of "Settled Payment" (processor clearance, chargeback window, business-day count) | **[LEGAL, OPEN]** — highest priority | `history/260729-TRSL-Jurisdiction-StandardTerms.md` §4 item 1 |
|
||||
| 3 | §1, §2 | Exact scope of "Noncommercial Use" | **[LEGAL]** | `history/260729-TRSL-PriorArt-Survey.md` §3.3 |
|
||||
| 4 | §4 | Patent license clause text, review against local patent law | **[LEGAL]** | `history/260729-TRSL-FutureLicense-PatentPrecedent.md` §4 |
|
||||
| 5 | §7 | Whether a cured breach should generate a compensating Target Ledger entry | **[OPEN]** | — |
|
||||
| 6 | §11.1 | Governing law and venue selection | **[LEGAL, OPEN]** | `history/260729-TRSL-Jurisdiction-StandardTerms.md` §2–§3 |
|
||||
| 7 | (all) | Full review under German AGB law (Transparenzgebot) and, where applicable, EU consumer-protection law | **[LEGAL]** | `history/260729-TRSL-Jurisdiction-StandardTerms.md` §1–§2 |
|
||||
| 8 | (all) | Contributor rights sufficient to grant this License and the Future License (CLA) | **[LEGAL]**, separate deliverable | `history/260729-TRSL-ContributorRights-Research.md` §4 |
|
||||
| 9 | (all) | Full specialist legal review in every jurisdiction of intended use | **[LEGAL]** | `specs/TargetRevenueLicenseConcept.md` §21.5 |
|
||||
|
||||
**Promotion path:** per `SCOPE.md` §4 and `workplans/TREV-WP-0001-license-prior-art-research.md` T06, this candidate requires explicit human acceptance before being treated as adequate briefing material for counsel, and specialist legal sign-off on every item above before any candidate may be published as official Version 1.0.
|
||||
|
|
@ -250,7 +250,13 @@ target-revenue/
|
|||
├── history/
|
||||
│ ├── 260728-InitialExploration.md
|
||||
│ ├── 260728-SWOT-Assessment.md
|
||||
│ └── 260728-SWOT-Followup-Spec-Workplan-Adaptations.md
|
||||
│ ├── 260728-SWOT-Followup-Spec-Workplan-Adaptations.md
|
||||
│ ├── 260729-TRSL-PriorArt-Survey.md # WP-0001 research, archived
|
||||
│ ├── 260729-TRSL-Terminology-Guardrails.md # WP-0001 research, archived
|
||||
│ ├── 260729-TRSL-FutureLicense-PatentPrecedent.md # WP-0001 research, archived
|
||||
│ ├── 260729-TRSL-ContributorRights-Research.md # WP-0001 research, archived
|
||||
│ ├── 260729-TRSL-Jurisdiction-StandardTerms.md # WP-0001 research, archived
|
||||
│ └── 260729-TargetRevenueSourceLicense-Draft.md # superseded by V1C1, archived
|
||||
├── docs/adr/
|
||||
│ └── ADR-0001-stage0-library-stack.md # accepted
|
||||
├── specs/
|
||||
|
|
@ -262,8 +268,7 @@ target-revenue/
|
|||
│ ├── PhaseManifestSpecification.md # WP-0003
|
||||
│ ├── TargetLedgerSpecification.md # WP-0003
|
||||
│ ├── MonetizationExtensionSpecification.md # WP-0003
|
||||
│ ├── TargetRevenueSourceLicense-Draft.md # WP-0001, ready for human review
|
||||
│ ├── research/ # WP-0001 prior-art / legal research
|
||||
│ ├── TargetRevenueSourceLicense-V1C1.md # WP-0001, ready for human review
|
||||
│ └── (not yet started:)
|
||||
│ ├── CanonicalMonetizationProfiles.md
|
||||
│ ├── TargetDegenerationPolicyResearch.md
|
||||
|
|
|
|||
|
|
@ -48,7 +48,7 @@ priority: high
|
|||
state_hub_task_id: "d2953e5a-7831-4593-93fd-3bd8faaec48d"
|
||||
```
|
||||
|
||||
Result 2026-07-29: `specs/research/TRSL-PriorArt-Survey.md` produced,
|
||||
Result 2026-07-29: `history/260729-TRSL-PriorArt-Survey.md` produced,
|
||||
grounded in primary-source license text fetched live (BSL 1.1, FSL,
|
||||
PolyForm Noncommercial, Fair Source, Elastic License 2.0, OSI OSD). Key
|
||||
finding: FSL's fixed two-license, single-trigger design was created
|
||||
|
|
@ -66,7 +66,7 @@ wording, and known criticisms or disputes. Record findings so they can be
|
|||
diffed directly against TRSL's Phase/Target/Conversion model in
|
||||
`specs/TargetRevenueLicenseConcept.md` §7, §10, §18.
|
||||
|
||||
**Deliverable path (suggested):** `history/` or `specs/research/TRSL-PriorArt-Survey.md`.
|
||||
**Deliverable path:** `history/260729-TRSL-PriorArt-Survey.md` (research artifacts are archived to `history/` with a date prefix once produced, per 2026-07-29 maintainer instruction).
|
||||
|
||||
## Survey OSI Open Source Definition and Fair Source boundary framing
|
||||
|
||||
|
|
@ -77,7 +77,7 @@ priority: high
|
|||
state_hub_task_id: "3f6166cd-d8a3-4f2e-a52e-28ecd08a8cf1"
|
||||
```
|
||||
|
||||
Result 2026-07-29: `specs/research/TRSL-Terminology-Guardrails.md` produced.
|
||||
Result 2026-07-29: `history/260729-TRSL-Terminology-Guardrails.md` produced.
|
||||
Confirmed via primary OSD text (Clause 6, field-of-endeavor
|
||||
non-discrimination) that pre-conversion TRSL cannot be Open Source, no
|
||||
ambiguity. Confirmed Fair Source's three-part DOSP definition applies
|
||||
|
|
@ -106,7 +106,7 @@ priority: medium
|
|||
state_hub_task_id: "0df9125d-0bbb-4e21-8b04-8a5dda02d140"
|
||||
```
|
||||
|
||||
Result 2026-07-29: `specs/research/TRSL-FutureLicense-PatentPrecedent.md`
|
||||
Result 2026-07-29: `history/260729-TRSL-FutureLicense-PatentPrecedent.md`
|
||||
produced. Confirmed via primary text: MIT has zero patent language (implied
|
||||
grant legally unsettled); Apache-2.0 has an explicit, contribution-scoped
|
||||
patent grant plus litigation-termination clause. No change to working
|
||||
|
|
@ -136,7 +136,7 @@ priority: medium
|
|||
state_hub_task_id: "25fbf15c-60c4-4284-af84-49d109b74cf8"
|
||||
```
|
||||
|
||||
Result 2026-07-29: `specs/research/TRSL-ContributorRights-Research.md`
|
||||
Result 2026-07-29: `history/260729-TRSL-ContributorRights-Research.md`
|
||||
produced. Confirmed via primary DCO 1.1 text that its certification is
|
||||
scoped to "the open source license indicated in the file" at time of
|
||||
contribution — it does not extend to a future, different Future License,
|
||||
|
|
@ -171,7 +171,7 @@ priority: medium
|
|||
state_hub_task_id: "1fe4b444-90b0-49d0-8d2a-9e3a99d2822a"
|
||||
```
|
||||
|
||||
Result 2026-07-29: `specs/research/TRSL-Jurisdiction-StandardTerms.md`
|
||||
Result 2026-07-29: `history/260729-TRSL-Jurisdiction-StandardTerms.md`
|
||||
produced. Confirmed §31/§32 UrhG text via primary source; §307 BGB
|
||||
Transparenzgebot confirmed via secondary legal sources (not primary-text-
|
||||
verified this session — flagged for counsel verification). Important
|
||||
|
|
@ -220,7 +220,17 @@ Agent completion of the file is “ready for review,” not done.
|
|||
|
||||
Result 2026-07-29: `specs/TargetRevenueSourceLicense-Draft.md` produced,
|
||||
synthesizing T01–T05. Every clause tagged `[CONFIRMED BY RESEARCH]`,
|
||||
`[LEGAL]`, `[WORKING DEFAULT]`, or `[OPEN]` per §0's reading key. **Status
|
||||
remains `todo` — ready for human review, not accepted.** Task should be
|
||||
marked `done` only after a maintainer confirms the skeleton is adequate
|
||||
briefing material for counsel.
|
||||
`[LEGAL]`, `[WORKING DEFAULT]`, or `[OPEN]` per §0's reading key.
|
||||
|
||||
Result 2026-07-29 (same day, maintainer instruction): the draft skeleton
|
||||
was archived to `history/260729-TargetRevenueSourceLicense-Draft.md`
|
||||
(dated research artifact) and superseded by
|
||||
`specs/TargetRevenueSourceLicense-V1C1.md` — Version 1, Candidate 1,
|
||||
written as actual operative license text rather than a bracket-annotated
|
||||
skeleton, per maintainer request. V1C1 carries its own preliminary-status
|
||||
notice near the top and a non-normative "Candidate Notes" appendix mapping
|
||||
back to this task's `[LEGAL]`/`[OPEN]` items. **Status remains `todo` —
|
||||
ready for human review, not accepted.** Task should be marked `done` only
|
||||
after a maintainer confirms V1C1 is adequate briefing material for counsel
|
||||
(the deliverable this task now points to; the archived skeleton is
|
||||
superseded, not the current target of the human-accept gate).
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue