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

Add public breach/termination record to TRSL V1C1 §7 (Trust Service)

Browse source 
Per maintainer request after reviewing V1C1: breaches and their resolution
are transparently published via the Trust Service, giving the ecosystem a
conformity signal and creating reputational pressure toward compliance
alongside the existing commercial remedies.

- V1C1 §7.4 (new): Trust Service publishes the Licensor's breach notices,
  cure status, and termination determinations per Phase, distinguishing
  "alleged" from "determined" — a ministerial recording act, not a new
  discretionary authority (consistent with §5.4's evidence-not-cause
  principle). Named-by-default disclosure is the intended mechanism (the
  deterrent only works if the party is identifiable), flagged in Appendix A
  item 10 as the single most legally sensitive addition in this candidate:
  it touches Commercial Use Agreement confidentiality, defamation law, and
  data-protection law where the affected party is an individual.
- TSD §4.1: new Breach/Compliance Record Trust Service component, noted as
  license-driven and deferred to a future Trust Service PRD rather than
  retrofitted into WP-0002's already-finished Stage 0 scope.
- OpenQuestions-WorkingDefaults.md Q12: records the adopted default (publish
  alleged/determined breach status) and the still-open naming-policy question.
- PRD FR-10: cross-references the new public record without resolving the
  naming question.

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

1
specs/ProductRequirementsDocument.md
View file

@ -253,6 +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.
### FR-11 — Successive Phases