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

3
specs/TechnicalSpecificationDocument.md
View file

@ -206,6 +206,9 @@ Per `specs/TargetRevenueLicenseConcept.md` §14.2, every Trust Service component
| Target Ledger | Append entries; serve the entry chain per Phase | Editing, deleting, or reordering settled entries |
| Metrics | Calculate and label facts/calculations/forecasts/recommendations distinctly | Presenting a forecast as if it were a ledger fact |
| Attestation | Publish a signed statement once the ledger fold reaches zero | Requiring its own publication as a condition of conversion |
| Breach/Compliance Record | Publish the Licensor's breach notices, cure status, and termination determinations for a Phase, distinguishing `alleged` from `determined` (`specs/TargetRevenueSourceLicense-V1C1.md` §7.4) | Independently deciding whether a breach occurred — that determination is the Licensor's, or a dispute process's, never the Trust Service's own judgment |
**New in V1C1 (2026-07-29):** the Breach/Compliance Record component is a license-driven addition, not yet reflected in a Stage 0 schema — WP-0002 shipped before this clause existed. Schema and pure-fold treatment (if any is needed; this is a record-publication concern, not a Target-Ledger fold input) are deferred to the Trust Service PRD (`specs/ProductRequirementsDocument.md` §11.1 item 8), not added retroactively to WP-0002's scope. The naming-policy question in V1C1 Appendix A item 10 must be resolved before this component's public/confidential evidence tiering (§14.5) can be finalized.
---