# Changelog

This lane keeps a visible history of policy changes. Rules may be added as new disclosure shapes are encountered. The goal is not to hide past choices; the goal is to make the safety boundary clearer over time.

## 2026-06-10

- Added source-ledger bridge support for public-safe cross-lane provenance summaries.
- Clarified that source ledgers remain canonical in their producing lanes.
- Clarified that private source-ledger mirrors are local-only planning material and are not uploadable.
- Added disclosure receipt rule summary support for public-safe aggregate timing review.
- Added public-commitment grace-period staging for elapsed no-response disclosure receipts.

## 2026-06-06

- Clarified that commitment records and full responsible-disclosure findings follow different publication rules.
- Clarified that the two-week no-response rule applies to sanitized finding records, not to non-actionable commitment records.
- Clarified the top-level README distinction between full responsible-disclosure findings and public-safe commitment records.
- Clarified that a package may contain commitment records while `data/finding_index.jsonl` remains empty.
- Clarified current file status for staged private-review packages.
- Added a public-safe commitment record policy for cases where retained evidence exists but no workable private intake route is available.
- Clarified that technical packets remain private for a vendor security team or other authorized responder.
- Clarified that commitment records are not vulnerability disclosures and do not start the normal disclosure clock by themselves.
- Clarified that public records must omit reproduction steps, exploit code, affected files, screenshots, raw logs, private correspondence, credentials, secrets, tokens, local paths, and target-specific mechanics.

## 2026-06-03

- Created the initial responsible-disclosure evidence index scaffold.
- Added the initial dataset policy, schemas, JSONL tables, and manifest.

Generated UTC: `2026-06-15T17:07:18+00:00`