coulomb/target-revenue
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Route breach-record naming policy through Commercial Use Agreement, not License

Browse source 
Revises V1C1 §7.4 per maintainer instruction: the License no longer sets a
named-by-default disclosure rule for published breach/termination records.
Instead, whether a Commercial Entitlement holder is named is governed
exclusively by the applicable Commercial Use Agreement — a bilaterally
negotiated contract where informed consent can actually be obtained. The
License itself only guarantees an anonymized Phase-and-category fallback
where no Commercial Use Agreement addresses it or none exists (e.g. a
noncommercial Section 2(c) breach).

This meaningfully reduces the License text's own legal exposure: the open
item is no longer "should the License name parties by default" but
"the not-yet-drafted Commercial Use Agreement template needs its own
naming/consent/data-protection clause" — recommended as a future
TRSL-CommercialUseAgreement-Draft.md deliverable, analogous to the CLA
recommendation already on record.

Updates Appendix A item 10, OpenQuestions-WorkingDefaults.md Q12 item 5,
PRD FR-10, and TSD §4.1 to match.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
tegwick 2026-07-29 11:03:39 +02:00
parent 236ebc2509
commit c12a4043c4
5 changed files with 24 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

2
specs/ProductRequirementsDocument.md
View file

@ -253,7 +253,7 @@ The Trust Service's five core responsibilities — Phase Registry, Extension Reg
- Public records expose aggregate Development/Remission Credit, Outstanding Target, applicable extensions, and conversion status without customer-identifying detail.
- Confidential evidence (contracts, invoices, receipts) is accessible only to authorized audit/dispute parties.
- Private commercial data is never required to be uploaded to the Trust Service.
- **(Added 2026-07-29)** Breach and termination determinations under `specs/TargetRevenueSourceLicense-V1C1.md` §7.4 are published as a distinct public conformity signal; whether the affected party is named by default is an open, legally sensitive question (`specs/OpenQuestions-WorkingDefaults.md` Q12 item 5) and is not resolved by this requirement.
- **(Revised 2026-07-29)** Breach and termination determinations under `specs/TargetRevenueSourceLicense-V1C1.md` §7.4 are published as a distinct public conformity signal, with an anonymized Phase-and-category fallback by default; whether a Commercial Entitlement holder is named is governed by the applicable Commercial Use Agreement, a separate deliverable not yet drafted (`specs/OpenQuestions-WorkingDefaults.md` Q12 item 5).
### FR-11 — Successive Phases