tegwick
236ebc2509
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>
9 lines
78 B
Text
9 lines
78 B
Text
__pycache__/
|
|
*.pyc
|
|
.pytest_cache/
|
|
*.egg-info/
|
|
build/
|
|
dist/
|
|
.venv/
|
|
*.swp
|
|
*.swo
|