tegwick
5de52c87d0
Bernd reviewed the License candidate and accepted it, conditioned on one
refinement to §1's "Commercial Use" definition: replaces the prior
circular definition ("use other than Noncommercial Use") with an
objective, billing-based trigger. Commercial Use now means billing a
customer for pre-conversion Software use, full stop - regardless of
whether the resulting payment is registered with the Trust Service.
Billing without recording the payment in the Target Ledger is Commercial
Use without a valid Commercial Entitlement, a Section 3 violation
addressed under Section 7 and, where applicable, the Enforcement Network.
This substantially resolves the affiliate/contractor/mixed-purpose/
public-sector ambiguity Appendix A item 1 flagged, since classification
no longer depends on who the customer is, only on whether they are
billed. A narrower residual item remains open: whether consumer-
protection law overrides this classification for an individual/sole-
proprietor customer in a given jurisdiction (the same recurring pattern
found across WP-0004's jurisdiction research).
Updates the document's status banner: condition 3 (human acceptance) is
now met; conditions 1 (specialist legal review) and 2 (full Appendix A
resolution) remain open - V1C1 is accepted as adequate briefing material
for counsel, not yet official Version 1.0. Marks WP-0001-T06 done and the
WP-0001 workplan finished (all 6 tasks complete). Updates
OpenQuestions-WorkingDefaults.md Q2, README, and CONTRIBUTING.md to match.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
47 lines
2.8 KiB
Markdown
47 lines
2.8 KiB
Markdown
# Contributing to target-revenue
|
|
|
|
## Repository status
|
|
|
|
This repository defines a **framework concept and specifications**. It does not yet provide a production-ready Target Revenue Source License (TRSL) or a production Trust Service.
|
|
|
|
**Do not** use draft TRSL language to govern production software or accept customer commercial entitlements under TRF until specialist legal review is complete and SCOPE says otherwise.
|
|
|
|
## What contributions are welcome now
|
|
|
|
| Kind | Guidance |
|
|
| --- | --- |
|
|
| Spec and doc improvements | Preferred: clarity, consistency with core terms, open-question research, examples |
|
|
| Schemas, pure fold, validators, golden fixtures | Preferred once workplans WP-0002 / WP-0003 are active |
|
|
| Prior-art research notes | Prefer updating or linking from WP-0001 deliverables |
|
|
| Implementation of a full hosted Trust Service | Out of scope until SCOPE sequencing rules are met |
|
|
|
|
## Terminology
|
|
|
|
Use the normative terms from `specs/TargetRevenueLicenseConcept.md` §7 (day-to-day reference: `specs/TargetRevenueFrameworkCore.md` §1). Do **not** reintroduce ambiguous synonyms for conversion metrics (e.g. treating total project “revenue captured” as equivalent to Development Credit).
|
|
|
|
Pre-conversion software is **source-available**, not OSI Open Source.
|
|
|
|
## External contributions and governed code
|
|
|
|
**External contributions are not accepted into any governed Milestone Release** until a contributor-rights instrument (CLA, assignment, or equivalent inbound grant covering both TRSL phase and Future License) is adopted.
|
|
|
|
Documentation-only and schema-only contributions to *this* framework repository may be accepted under the repository LICENSE without that instrument, at maintainer discretion.
|
|
|
|
A Developer Certificate of Origin (DCO) alone is **not** assumed sufficient for dual-phase relicensing of product code; see open questions and WP-0001-T04.
|
|
|
|
## Human decision gates
|
|
|
|
The following must not be marked complete by agents alone without explicit human accept (comment, decision record, or maintainer message):
|
|
|
|
- TRSL V1C1 license candidate (WP-0001-T06 — **accepted 2026-07-29** as adequate briefing material for counsel; still requires specialist legal review and full Appendix A resolution before official V1.0)
|
|
- Library/stack ADR that locks implementation technology (WP-0002-T01 — **accepted 2026-07-29**, see ADR-0001)
|
|
- Promotion of working defaults into normative core wording (WP-0003-T06, open)
|
|
- WP-0004/WP-0005 jurisdiction-synthesis tasks (T10 in each, open)
|
|
|
|
## Workplans
|
|
|
|
Prefer small, hub-linked workplan tasks. Do not register workplans only in the State Hub; write the workplan file under `workplans/` and run consistency sync so local files remain source of truth.
|
|
|
|
## Questions
|
|
|
|
Start from `README.md` reading order and `SCOPE.md`. Unresolved product questions live in the PRD §14 and `specs/OpenQuestions-WorkingDefaults.md`.
|