Make responsible disclosure commitments public safe

CHANGELOG.md

@@ -27,4 +27,4 @@ This lane keeps a visible history of policy changes. Rules may be added as new d
 - Created the initial responsible-disclosure evidence index scaffold.
 - Added the initial dataset policy, schemas, JSONL tables, and manifest.
 
-Generated UTC: `2026-06-15T16:23:00+00:00`
+Generated UTC: `2026-06-15T16:52:39+00:00`

DATASET_POLICY.md

@@ -1,73 +1,22 @@
 # Responsible Disclosure Dataset Policy
 
-This repository is a public index lane for future responsible-disclosure findings, public-safe commitment records, and public-safe source-ledger summaries.
+This dataset is a public-safe lane for responsible-disclosure commitments and later sanitized records.
 
-## Publication Rule
+## Rules
 
-Initial scaffolding and public-safe commitment records are separate from finding rows. Finding rows are only allowed after the disclosure timing rule for findings is satisfied.
+- Try the appropriate private disclosure route first when one is workable.
+- The first disclosure email starts the response clock for a finding.
+- Acknowledgement or good-faith engagement pauses publication.
+- After 14 days with no response, a sanitized public-safe record may be prepared.
+- A grace period may be used before a public commitment becomes visible.
+- Public records must not include reproduction steps, exploit code, affected file names, private correspondence, secrets, tokens, raw logs, local paths, or target-specific mechanics.
+- Limits must be stated plainly when evidence is retained but validation is incomplete.
+- Human review is required before any detailed public disclosure.
 
-The first disclosure email starts the clock. If the recipient acknowledges the report in any way, publication pauses and we work on their timeline while engagement remains good-faith. A simple acknowledgement or request for more time is enough to pause publication.
+## Commitment Records
 
-If there is no reply, no acknowledgement, no receipt confirmation, and no request for more time within two weeks of the first disclosure email, a sanitized public-safe finding row may be published. Unresolved exploit details are still not allowed.
+A commitment record is not a full vulnerability disclosure. It is a short public-safe notice that evidence is retained while technical details remain private for an authorized security responder.
 
-## Public-Safe Commitment Records
+## Full Findings
 
-This lane may also contain non-actionable commitment records when retained evidence exists but a workable private intake route is unavailable or blocked.
-
-Commitment records and full responsible-disclosure findings follow different rules. A commitment record may be published as a public-safe priority and evidence record when a workable private intake route is unavailable or blocked. A full responsible-disclosure finding is different: it may only be published after the notification, acknowledgement, no-response, or clearance rules for findings have been satisfied.
-
-A commitment record is not a vulnerability disclosure and is not a substitute for vendor validation. It exists to preserve priority, authorship, and evidence integrity while the technical packet remains private for a vendor security team or other authorized responder.
-
-For this lane:
-
-- One appropriate private intake attempt is made when available.
-- If no workable private intake route is available or blocked, a public-safe commitment record may be published.
-- The public record must keep reproduction steps, exploit code, affected files, screenshots, raw logs, private correspondence, credentials, secrets, tokens, local paths, and target-specific mechanics out of scope.
-- The public record should describe confidence as meaningful but bounded until product-runtime or vendor-side validation is complete.
-- A commitment record does not start the normal disclosure clock by itself.
-- The two-week no-response rule applies to sanitized finding records, not to non-actionable commitment records.
-
-## Source Ledger Summaries
-
-This lane may record public-safe summaries of ledgers owned by other lanes. Source ledgers remain canonical in their producing lane. The public index only records safe linkage and provenance; detailed rows remain private until individually cleared.
-
-Allowed public source-ledger summaries may include source lane, canonical owner, visibility policy, review date, found-date range, row counts, and ledger hash. They must not include raw bug IDs, target names, local paths, report text, reproduction details, private correspondence, or unresolved technical mechanics.
-
-Private source-ledger mirrors are local-only planning material and are not uploadable.
-
-## Disclosure Receipt Rule Summaries
-
-This lane may record public-safe aggregate timing summaries for responsible-disclosure communication receipts. Allowed public fields include receipt counts, date ranges, rule version, no-response window length, and aggregate clock-state counts. Raw subjects, recipients, message locators, ledger IDs, private correspondence, and technical report details are not allowed in public receipt summaries.
-
-Private disclosure receipt mirrors are local-only planning material and are not uploadable.
-
-## Public Commitment Stage Summaries
-
-Elapsed no-response review first enters a local public-commitment grace-period stage. Allowed public fields include aggregate candidate counts, stage date, grace-period length, grace-period date range, and aggregate stage-state counts. Raw subjects, recipients, message locators, ledger IDs, target names, private correspondence, and technical report details are not allowed in public stage summaries.
-
-Private public-commitment stage mirrors are local-only planning material and are not uploadable. A staged row is not an approval to publish a commitment record.
-
-## Allowed Future Content
-
-- Redacted finding metadata
-- Public-safe validation summaries
-- Hashes of proof packet manifests
-- Public-safe commitment references
-- Public-safe source-ledger linkage summaries
-- Public-safe aggregate disclosure receipt timing summaries
-- Public-safe aggregate public-commitment stage summaries
-- Disclosure timeline receipts
-- Acknowledgement status
-- Public advisory links after embargo or remediation
-
-## Disallowed Content
-
-- Exploit code
-- Undisclosed vulnerability details
-- Private correspondence
-- Secrets, credentials, tokens, raw logs, or local paths
-- Target-identifying details before clearance
-
-## Review Standard
-
-Future updates should pass a public-safety review, a provenance review, and a disclosure-state review before upload.
+Full finding rows are allowed only after disclosure timing and safety review clear them.

README.md

@@ -15,168 +15,45 @@ size_categories:
 
 # Responsible Disclosure Evidence Index
 
-This Hugging Face dataset is a public-safe evidence index for responsible-disclosure findings, non-actionable commitment records, and source-ledger linkage summaries.
+This is a public-safe responsible-disclosure lane. It records our rules and links to non-actionable commitment notes. It does not publish exploit steps, private emails, source paths, proof-of-concept code, raw logs, or unresolved technical packets.
 
-The lane is intentionally live before full findings are published. The goal is to give future validated findings, public-safe commitments, and cross-lane provenance summaries a stable home with clear safety rules, provenance expectations, and disclosure gates.
+## Public Commitments
 
-This lane is backed by source ledgers owned by other lanes. The cyber bug ledger is canonical in the cyber lane. The public index only records safe linkage and provenance; detailed bug rows remain private until individually cleared.
+- [ChromeOS: authentication-boundary research](commitments/chromeos-authentication-boundary-commitment-20260606.md)
+- [Linux kernel: virtualization and networking-boundary research](commitments/linux-kernel-virtualization-boundary-commitment-20260615.md)
+- [Werkzeug: Windows path-handling boundary research](commitments/werkzeug-windows-path-boundary-commitment-20260615.md)
 
-## Current Status
+These are not full vulnerability disclosures. They are public-safe notices that evidence is retained and that technical details are withheld for an authorized security responder.
 
-No full responsible-disclosure findings are published here yet.
+## Rules We Follow
 
-This generated package currently includes 0 public-safe commitment records. A commitment record is not the same thing as a full responsible-disclosure finding.
+- We try the appropriate private disclosure route first when one is workable.
+- The first disclosure email starts the response clock for a finding.
+- Any acknowledgement or good-faith engagement pauses publication.
+- If there is no response after 14 days, we may prepare a sanitized public-safe record.
+- We may add a grace period before making a public commitment visible.
+- Public notes stay non-actionable: no reproduction steps, exploit code, private correspondence, secrets, tokens, raw logs, local paths, or target-specific mechanics.
+- Unvalidated or partly validated work is labelled with its limits.
+- Human review is required before anything more detailed than a public-safe commitment is published.
 
-The source-ledger index currently contains 1 public-safe source-ledger summary row. Private source-ledger mirrors, when generated for local planning, are not uploadable and are currently: no local-only source-ledger mirror rows.
+## What Is Visible Here
 
-The disclosure receipt rule index currently contains 1 public-safe disclosure receipt timing summary. Private disclosure receipt mirrors, when generated for local planning, are not uploadable and are currently: no local-only disclosure receipt rows.
+- Public-safe commitment markdown files.
+- Public-safe ledger and timing summaries.
+- Hashes and manifests for provenance.
+- Empty placeholders for future finding records.
 
-The public-commitment stage index currently contains 1 public-safe public-commitment stage summary. It records aggregate grace-period staging only. Private public-commitment stage mirrors, when generated for local planning, are not uploadable and are currently: no local-only public-commitment stage rows.
+## Current Machine-Readable State
 
-The repository currently contains:
-
-- this dataset card
-- safety and inclusion policy
-- schemas for future redacted records
-- `data/finding_index.jsonl`, currently empty
-- `data/commitment_index.jsonl`, currently empty; reserved for public-safe commitment records
-- `data/source_ledger_index.jsonl`, currently contains 1 public-safe source-ledger summary row
-- `data/disclosure_receipt_rule_index.jsonl`, currently contains 1 public-safe disclosure receipt timing summary
-- `data/public_commitment_stage_index.jsonl`, currently contains 1 public-safe public-commitment stage summary
-- a manifest describing the package and row counts
-
-## Commitments vs Responsible-Disclosure Findings
-
-A responsible-disclosure finding is a public-safe record for a vulnerability after the notification, review, and disclosure-clearance rules for this lane have been satisfied.
-
-A commitment record is a timestamped, hash-backed public-safe notice that retained evidence exists while the technical packet remains private for a vendor security team or other authorized responder. It does not include reproduction steps, exploit code, affected files, raw logs, private correspondence, credentials, secrets, tokens, local paths, or target-specific mechanics.
-
-Commitment records and full responsible-disclosure findings follow different rules. A commitment record may be published as a public-safe priority and evidence record when a workable private intake route is unavailable or blocked. A full responsible-disclosure finding is different: it may only be published after the notification, acknowledgement, no-response, or clearance rules for findings have been satisfied.
-
-For this lane, commitment records preserve priority and evidence integrity. They are not vulnerability disclosures, are not substitutes for vendor validation, and do not start the normal disclosure clock by themselves. The two-week no-response rule applies to sanitized finding records, not to non-actionable commitment records.
-
-## What Will Go Here Later
-
-Future rows may include public-safe, redacted records for findings after responsible-disclosure gates clear:
-
-- finding index metadata
-- validation summary references
-- proof packet manifest hashes
-- public-safe commitment references when a private intake route is not workable
-- disclosure timeline receipts
-- maintainer or security-contact acknowledgement status
-- post-embargo advisory links or summaries
-
-Rows are intended to be provenance-first. Future entries should point to hash-backed artifacts or public advisories rather than exposing raw exploit material.
-
-## What Will Not Go Here
-
-This dataset must not contain:
-
-- undisclosed vulnerability details
-- exploit code
-- proof-of-concept code for unresolved issues
-- target-identifying evidence before disclosure clearance
-- private emails or private maintainer correspondence
-- tokens, credentials, secrets, raw logs, or local machine paths
-- material that would help weaponize an unresolved issue
-
-## Why This Exists
-
-This lane exists so responsible-disclosure work does not need to invent a public record format at the moment a record is ready. The boundary is explicit:
-
-- full findings and commitment records are separate states
-- safety policy comes first
-- public rows require review and disclosure clearance
-- every public record should be understandable without exposing unsafe details
-
-## Disclosure Timing Rule
-
-This lane uses a simple rule for future findings:
-
-- The first disclosure email starts the clock.
-- If the project, maintainer, security contact, or authorized representative acknowledges the report in any way, publication pauses. A simple "we received this, please give us time" is enough.
-- While there is good-faith engagement, we work on their timeline and do not publish a finding here.
-- If there is no reply, no acknowledgement, no receipt confirmation, and no request for more time within two weeks of the first disclosure email, a sanitized public-safe record may be published here.
-- If later engagement appears to be only delay without substantive progress, that is handled as a separate review rather than by automatic publication.
-
-## Public-Safe Commitment Records
-
-This lane may also contain non-actionable commitment records when retained evidence exists but a workable private intake route is unavailable or blocked.
-
-A commitment record is not a vulnerability disclosure and is not a substitute for vendor validation. It exists to preserve priority, authorship, and evidence integrity while the technical packet remains private for a vendor security team or other authorized responder.
-
-For this lane:
-
-- one appropriate private intake attempt is made when available
-- if no workable private intake route is available or blocked, a public-safe commitment record may be published
-- the public record must keep reproduction steps, exploit code, affected files, screenshots, raw logs, private correspondence, credentials, secrets, tokens, local paths, and target-specific mechanics out of scope
-- the public record should describe confidence as meaningful but bounded until product-runtime or vendor-side validation is complete
-- a commitment record does not start the normal disclosure clock by itself
-- the two-week no-response rule applies to sanitized finding records, not to non-actionable commitment records
-
-## Source Ledger Bridge
-
-This lane can consume public-safe summaries from ledgers owned by other lanes. Source ledgers remain canonical in their producing lane; bridge outputs are views, not replacements.
-
-The public source-ledger index records only safe linkage and provenance such as source lane, canonical owner, row counts, review date, found-date range, visibility policy, and ledger hash. It must not include raw bug IDs, target names, local paths, report text, reproduction details, or unresolved technical mechanics.
-
-When a private source-ledger mirror is generated, it is local-only planning material. It exists so this lane can follow through on disclosure evidence work without copying ownership away from the producing lane. It must remain out of uploads and public releases until a future safe publication schema explicitly clears individual rows.
-
-## Disclosure Receipt Rule Bridge
-
-This lane can also consume metadata-only communication receipts for responsible-disclosure timing review. The public receipt rule index records aggregate timing and rule state only. It must not include raw subjects, recipients, message URLs, ledger IDs, report text, reproduction details, or unresolved technical mechanics.
-
-Private disclosure receipt mirrors are local-only planning material. They connect sent-email receipt metadata back to canonical source-ledger rows so the 14-day no-response rule can be followed without copying private details into a public index.
-
-## Public Commitment Stage Bridge
-
-Elapsed no-response review does not directly create a public commitment. This lane can first stage elapsed receipt groups into a public-commitment grace-period queue. The public stage index records only aggregate counts, stage dates, grace-window dates, and rule state. It must not include raw subjects, recipients, message URLs, ledger IDs, target names, report text, reproduction details, or unresolved technical mechanics.
-
-Private public-commitment stage mirrors are local-only planning material. They connect elapsed disclosure receipts back to canonical source-ledger rows while the grace period runs and before any public-safe commitment record is individually reviewed.
-
-## Future Inclusion Gates
-
-A future full responsible-disclosure finding should only be added after all applicable conditions are met:
-
-- the affected maintainer or security contact has been notified through an appropriate route
-- either an acknowledgement/engagement path has resolved to public clearance, or the two-week no-response rule above has elapsed
-- unsafe reproduction detail has been removed or summarized safely
-- artifact hashes and validation receipts are available
-- a human review confirms the row is public-safe
-
-Public-safe commitment records follow the separate commitment-record rule above.
-
-## Files
-
-- `DATASET_POLICY.md`: safety and inclusion policy for future rows
-- `schemas/finding_index.schema.json`: schema for future finding metadata
-- `schemas/commitment_index.schema.json`: schema for public-safe commitment records
-- `schemas/source_ledger_index.schema.json`: schema for public-safe source-ledger summaries
-- `schemas/disclosure_receipt_rule_index.schema.json`: schema for public-safe disclosure receipt timing summaries
-- `schemas/public_commitment_stage_index.schema.json`: schema for public-safe public-commitment stage summaries
-- `schemas/contact_receipt.schema.json`: schema for future contact receipts
-- `schemas/timeline_receipt.schema.json`: schema for future disclosure timeline receipts
-- `data/finding_index.jsonl`: currently empty
-- `data/commitment_index.jsonl`: currently empty; reserved for public-safe commitment records
-- `data/source_ledger_index.jsonl`: currently contains 1 public-safe source-ledger summary row
-- `data/disclosure_receipt_rule_index.jsonl`: currently contains 1 public-safe disclosure receipt timing summary
-- `data/public_commitment_stage_index.jsonl`: currently contains 1 public-safe public-commitment stage summary
-- `data/contact_receipts.jsonl`: currently empty
-- `data/timeline_receipts.jsonl`: currently empty
-- `commitments/`: reserved for public-safe commitment markdown files
-- `private/source_ledgers/`: local-only source-ledger mirrors when explicitly generated
-- `private/disclosure_receipts/`: local-only disclosure receipt mirrors when explicitly generated
-- `private/public_commitment_stage/`: local-only public-commitment stage mirrors when explicitly generated
-- `CHANGELOG.md`: visible policy change history
-- `manifest.json`: scaffold manifest and row counts
-
-## AI Assistance
-
-This dataset lane and its initial documentation were prepared with AI assistance. Future entries require human review before publication.
+- `data/commitment_index.jsonl` contains 3 public-safe commitment records.
+- `data/source_ledger_index.jsonl` contains 1 public-safe ledger summary row.
+- `data/disclosure_receipt_rule_index.jsonl` contains 1 public-safe timing summary.
+- `data/public_commitment_stage_index.jsonl` contains 1 public-safe grace-period summary.
+- `data/finding_index.jsonl` is empty.
+- No private mirrors are included in this upload.
 
 ## Repository
 
 Dataset page: https://huggingface.co/datasets/cjc0013/responsible-disclosure-evidence-index
 
-Generated UTC: `2026-06-15T16:23:00+00:00`
+Generated UTC: `2026-06-15T16:52:39+00:00`

commitments/chromeos-authentication-boundary-commitment-20260606.md

@@ -0,0 +1,32 @@
+# ChromeOS Public-Safe Commitment
+
+Date: 2026-06-06
+
+Status: public_safe_commitment
+
+This is a non-actionable commitment note for privately retained ChromeOS authentication-boundary research.
+
+We are not publishing a vulnerability report here. We are recording that retained evidence exists, that the evidence is not being ignored, and that technical details remain withheld for an authorized security responder.
+
+## Current Position
+
+- The retained packet is meaningful but bounded.
+- A complete ChromeOS product-runtime validation pass is not claimed.
+- Final severity, exploitability, affected-version scope, and reward eligibility are not claimed.
+- Technical details remain private.
+
+## Explicit Limitations
+
+We are not claiming attacker control, current-version exploitability, reproducible public vulnerable behavior, security effect, remediation status, or vendor validation. The evidence level is stronger than source-only suspicion and weaker than completed product-runtime validation.
+
+## Public-Safety Boundary
+
+This note does not include reproduction steps, exploit code, affected files, source paths, screenshots, raw logs, private correspondence, credentials, secrets, tokens, or target-specific mechanics.
+
+## Responsible-Disclosure Position
+
+If Google, Chromium, or an authorized responder provides a workable private handling path, technical handling should happen there. Until then, this public note preserves priority and evidence integrity without publishing actionable detail.
+
+## Retained Evidence
+
+Locally retained evidence is hash-backed. Hashes may be shared with an authorized responder to establish provenance without exposing the technical packet publicly.

commitments/linux-kernel-virtualization-boundary-commitment-20260615.md

@@ -0,0 +1,28 @@
+# Linux Kernel Public-Safe Commitment
+
+Date: 2026-06-15
+
+Status: public_safe_commitment
+
+This is a non-actionable commitment note for privately retained Linux kernel virtualization and networking-boundary research.
+
+A responsible-disclosure email was sent on 2026-05-27. The 14-day no-response review date was 2026-06-10. We are applying an additional grace period before any fuller public-safe record is considered.
+
+## Current Position
+
+- A private technical packet is retained.
+- No full public finding is published here.
+- Final severity, exploitability, affected-version scope, and remediation status are not claimed.
+- Technical details remain private for an authorized security responder.
+
+## Explicit Limitations
+
+We are not claiming attacker control, current-version exploitability, reproducible public vulnerable behavior, security effect, remediation status, or maintainer validation. The evidence level is meaningful but bounded.
+
+## Public-Safety Boundary
+
+This note does not include reproduction steps, exploit code, affected files, source paths, raw logs, private correspondence, credentials, secrets, tokens, or target-specific mechanics.
+
+## Responsible-Disclosure Position
+
+If the Linux kernel security team, maintainers, or an authorized responder engages, public technical disclosure pauses while good-faith handling continues.

commitments/werkzeug-windows-path-boundary-commitment-20260615.md

@@ -0,0 +1,28 @@
+# Werkzeug Public-Safe Commitment
+
+Date: 2026-06-15
+
+Status: public_safe_commitment
+
+This is a non-actionable commitment note for privately retained Werkzeug Windows path-handling boundary research.
+
+A responsible-disclosure email was sent on 2026-05-25. The 14-day no-response review date was 2026-06-08. We are applying an additional grace period before any fuller public-safe record is considered.
+
+## Current Position
+
+- A private technical packet is retained.
+- No full public finding is published here.
+- Final severity, exploitability, affected-version scope, and remediation status are not claimed.
+- Technical details remain private for an authorized security responder.
+
+## Explicit Limitations
+
+We are not claiming attacker control, current-version exploitability, reproducible public vulnerable behavior, security effect, remediation status, or maintainer validation. The evidence level is meaningful but bounded.
+
+## Public-Safety Boundary
+
+This note does not include reproduction steps, exploit code, affected files, source paths, raw logs, private correspondence, credentials, secrets, tokens, or target-specific mechanics.
+
+## Responsible-Disclosure Position
+
+If the Werkzeug maintainers, Pallets maintainers, or an authorized responder engages, public technical disclosure pauses while good-faith handling continues.

data/commitment_index.jsonl

@@ -0,0 +1,3 @@
+{"affected_area": "authentication-boundary research", "commitment_path": "commitments/chromeos-authentication-boundary-commitment-20260606.md", "commitment_sha256": "3aab5666be75f1d73a717b9c2c294414ba60066dedf294a14747469d3297f35f", "disclosure_clock_state": "commitment_record_does_not_start_normal_disclosure_clock", "disclosure_state": "public_safe_commitment_visible_technical_details_withheld", "private_intake_state": "workable_private_route_not_available_for_current_evidence_level", "project": "ChromeOS", "proof_manifest_sha256": "3aab5666be75f1d73a717b9c2c294414ba60066dedf294a14747469d3297f35f", "public_action_state": "public_hf_visible_non_actionable_commitment", "public_safe_summary": "Public-safe commitment for privately retained ChromeOS authentication-boundary research. Technical details are withheld.", "published_utc": "2026-06-06T00:00:00+00:00", "record_id": "chromeos-authentication-boundary-commitment-20260606", "record_type": "public_safe_commitment", "staged_utc": "2026-06-06T00:00:00+00:00", "technical_packet_state": "private_retained_for_authorized_responder", "validation_summary": "Retained evidence is meaningful but bounded; attacker control, current-version exploitability, security effect, and full ChromeOS product-runtime validation are not claimed."}
+{"affected_area": "virtualization and networking-boundary research", "commitment_path": "commitments/linux-kernel-virtualization-boundary-commitment-20260615.md", "commitment_sha256": "fb837a4c92fc423322d22112313086773f86bdba94739ccb6c76660a575ba932", "disclosure_clock_state": "commitment_record_does_not_start_normal_disclosure_clock", "disclosure_state": "public_safe_commitment_visible_technical_details_withheld", "private_intake_state": "workable_private_route_not_available_for_current_evidence_level", "project": "Linux kernel", "proof_manifest_sha256": "fb837a4c92fc423322d22112313086773f86bdba94739ccb6c76660a575ba932", "public_action_state": "public_hf_visible_non_actionable_commitment", "public_safe_summary": "Public-safe commitment for privately retained Linux kernel research after the no-response review date. Technical details are withheld.", "published_utc": "2026-06-15T00:00:00+00:00", "record_id": "linux-kernel-virtualization-boundary-commitment-20260615", "record_type": "public_safe_commitment", "staged_utc": "2026-06-15T00:00:00+00:00", "technical_packet_state": "private_retained_for_authorized_responder", "validation_summary": "Private evidence is retained; attacker control, current-version exploitability, security effect, final severity, affected-version scope, and remediation status are not claimed."}
+{"affected_area": "Windows path-handling boundary research", "commitment_path": "commitments/werkzeug-windows-path-boundary-commitment-20260615.md", "commitment_sha256": "41257b5dfc7605e11c6ffad7f13408dac427bd2964a5ae211fef5b7f692f99dc", "disclosure_clock_state": "commitment_record_does_not_start_normal_disclosure_clock", "disclosure_state": "public_safe_commitment_visible_technical_details_withheld", "private_intake_state": "workable_private_route_not_available_for_current_evidence_level", "project": "Werkzeug", "proof_manifest_sha256": "41257b5dfc7605e11c6ffad7f13408dac427bd2964a5ae211fef5b7f692f99dc", "public_action_state": "public_hf_visible_non_actionable_commitment", "public_safe_summary": "Public-safe commitment for privately retained Werkzeug research after the no-response review date. Technical details are withheld.", "published_utc": "2026-06-15T00:00:00+00:00", "record_id": "werkzeug-windows-path-boundary-commitment-20260615", "record_type": "public_safe_commitment", "staged_utc": "2026-06-15T00:00:00+00:00", "technical_packet_state": "private_retained_for_authorized_responder", "validation_summary": "Private evidence is retained; attacker control, current-version exploitability, security effect, final severity, affected-version scope, and remediation status are not claimed."}

data/disclosure_receipt_rule_index.jsonl

@@ -1 +1 @@
-{"as_of_date": "2026-06-15", "clock_state_counts": {"no_response_window_elapsed_review_required": 3, "paused_or_review_needed_acknowledgement_present": 2}, "details_state": "detailed_receipts_and_ledger_links_remain_private_until_individually_cleared", "generated_utc": "2026-06-15T16:23:00+00:00", "ledger_link_count": 6, "no_response_days": 14, "no_response_review_date_max": "2026-06-20", "no_response_review_date_min": "2026-06-08", "no_response_window_elapsed_review_required_count": 3, "paused_or_review_needed_acknowledgement_present_count": 2, "pending_no_response_window_count": 0, "public_safe_note": "This row summarizes responsible-disclosure email timing only. Subjects, recipients, message locators, ledger IDs, and technical details remain private.", "receipt_count": 5, "record_id": "disclosure-receipt-rule-summary", "record_type": "disclosure_receipt_rule_summary", "responsible_disclosure_rule": "responsible_disclosure_clock_v1", "sent_date_max": "2026-06-06", "sent_date_min": "2026-05-25", "source_receipt_kind": "gmail_sent_metadata", "source_sha256": "059c2676fb828ec3388033369db2b8cdffda19b58604df90006ba722601013d4", "source_state": "gmail_sent_visible_list_metadata_seed_pending_message_url_export", "visibility_policy": "aggregate_public_safe_summary_only", "visibility_profile": "public_safe_summary"}
+{"as_of_date": "2026-06-15", "clock_state_counts": {"no_response_window_elapsed_review_required": 3, "paused_or_review_needed_acknowledgement_present": 2}, "details_state": "detailed_receipts_and_ledger_links_remain_private_until_individually_cleared", "generated_utc": "2026-06-15T16:52:39+00:00", "ledger_link_count": 6, "no_response_days": 14, "no_response_review_date_max": "2026-06-20", "no_response_review_date_min": "2026-06-08", "no_response_window_elapsed_review_required_count": 3, "paused_or_review_needed_acknowledgement_present_count": 2, "pending_no_response_window_count": 0, "public_safe_note": "This row summarizes responsible-disclosure email timing only. Subjects, recipients, message locators, ledger IDs, and technical details remain private.", "receipt_count": 5, "record_id": "disclosure-receipt-rule-summary", "record_type": "disclosure_receipt_rule_summary", "responsible_disclosure_rule": "responsible_disclosure_clock_v1", "sent_date_max": "2026-06-06", "sent_date_min": "2026-05-25", "source_receipt_kind": "gmail_sent_metadata", "source_sha256": "059c2676fb828ec3388033369db2b8cdffda19b58604df90006ba722601013d4", "source_state": "gmail_sent_visible_list_metadata_seed_pending_message_url_export", "visibility_policy": "aggregate_public_safe_summary_only", "visibility_profile": "public_safe_summary"}

data/public_commitment_stage_index.jsonl

@@ -1 +1 @@
-{"as_of_date": "2026-06-15", "details_state": "candidate_receipts_and_ledger_links_remain_private_until_individually_cleared", "generated_utc": "2026-06-15T16:23:00+00:00", "grace_days": 7, "grace_period_active_count": 3, "grace_period_elapsed_human_review_required_count": 0, "grace_period_end_date_max": "2026-06-22", "grace_period_end_date_min": "2026-06-22", "no_response_review_date_max": "2026-06-15", "no_response_review_date_min": "2026-06-08", "public_action_state": "local_stage_only_no_public_commitment_approved", "public_commitment_stage_rule": "public_commitment_grace_stage_v1", "public_safe_note": "This aggregate row stages elapsed no-response disclosure receipts into a grace-period public-commitment review queue. It does not name targets, expose receipt IDs, publish technical details, or approve a public commitment.", "record_id": "public-commitment-stage-summary", "record_type": "public_commitment_stage_summary", "source_clock_state": "no_response_window_elapsed_review_required", "source_receipt_count": 5, "stage_date": "2026-06-15", "stage_state_counts": {"public_commitment_grace_period_active": 3}, "staged_candidate_count": 3, "visibility_policy": "aggregate_public_safe_stage_summary_only", "visibility_profile": "public_safe_summary"}
+{"as_of_date": "2026-06-15", "details_state": "candidate_receipts_and_ledger_links_remain_private_until_individually_cleared", "generated_utc": "2026-06-15T16:52:39+00:00", "grace_days": 7, "grace_period_active_count": 2, "grace_period_elapsed_human_review_required_count": 0, "grace_period_end_date_max": "2026-06-22", "grace_period_end_date_min": "2026-06-22", "no_response_review_date_max": "2026-06-10", "no_response_review_date_min": "2026-06-08", "public_action_state": "local_stage_only_no_public_commitment_approved", "public_commitment_stage_rule": "public_commitment_grace_stage_v1", "public_safe_note": "This aggregate row stages elapsed no-response disclosure receipts into a grace-period public-commitment review queue. It does not name targets, expose receipt IDs, publish technical details, or approve a public commitment.", "record_id": "public-commitment-stage-summary", "record_type": "public_commitment_stage_summary", "source_clock_state": "no_response_window_elapsed_review_required", "source_receipt_count": 5, "stage_date": "2026-06-15", "stage_state_counts": {"public_commitment_grace_period_active": 2}, "staged_candidate_count": 2, "visibility_policy": "aggregate_public_safe_stage_summary_only", "visibility_profile": "public_safe_summary"}

data/source_ledger_index.jsonl

@@ -1 +1 @@
-{"bug_lane_count": 20, "canonical_owner": "cyber_lane", "canonical_owner_label": "Cyber lane", "details_state": "detailed_rows_remain_private_until_individually_cleared", "found_date_max": "2026-06-15", "found_date_min": "2026-05-25", "generated_utc": "2026-06-15T16:23:00+00:00", "ledger_sha256": "31df0f5ca45214c57d15774ca60fe55f04d4af85aa1893bce7df82225942de0e", "public_commitment_lane_stage_count": 4, "public_safe_note": "This lane is backed by a source ledger owned by the cyber lane. The public index records linkage and provenance only; detailed rows remain private until individually cleared.", "record_id": "source-ledger-cyber-bug-ledger", "record_type": "source_ledger_bridge", "research_lead_count": 4, "responsible_disclosure_email_receipt_count": 5, "responsible_disclosure_ledger_link_count": 6, "review_date": "2026-06-15", "row_count": 24, "row_counts_by_kind": {"bug_lane": 20, "research_lead": 4}, "source_lane": "cyber", "source_ledger_kind": "cyber_bug_ledger", "total_private_row_count": 24, "visibility_policy": "public_safe_summary_only", "visibility_profile": "public_safe_summary"}
+{"bug_lane_count": 20, "canonical_owner": "cyber_lane", "canonical_owner_label": "Cyber lane", "details_state": "detailed_rows_remain_private_until_individually_cleared", "found_date_max": "2026-06-15", "found_date_min": "2026-05-25", "generated_utc": "2026-06-15T16:52:39+00:00", "ledger_sha256": "50313129a5be1a11720d72693bcf210fd1b2af41a7ce782a22c28a3298f7508b", "public_commitment_lane_stage_count": 2, "public_safe_note": "This lane is backed by a source ledger owned by the cyber lane. The public index records linkage and provenance only; detailed rows remain private until individually cleared.", "record_id": "source-ledger-cyber-bug-ledger", "record_type": "source_ledger_bridge", "research_lead_count": 4, "responsible_disclosure_email_receipt_count": 5, "responsible_disclosure_ledger_link_count": 6, "review_date": "2026-06-15", "row_count": 24, "row_counts_by_kind": {"bug_lane": 20, "research_lead": 4}, "source_lane": "cyber", "source_ledger_kind": "cyber_bug_ledger", "total_private_row_count": 24, "visibility_policy": "public_safe_summary_only", "visibility_profile": "public_safe_summary"}

data/timeline_receipts.jsonl

@@ -0,0 +1,3 @@
+{"artifact_sha256": "3aab5666be75f1d73a717b9c2c294414ba60066dedf294a14747469d3297f35f", "event_type": "public_safe_commitment_public_hf_visible", "event_utc": "2026-06-06T00:00:00+00:00", "public_safe_note": "Public-safe commitment is visible. Technical details remain withheld.", "record_id": "chromeos-authentication-boundary-commitment-20260606"}
+{"artifact_sha256": "fb837a4c92fc423322d22112313086773f86bdba94739ccb6c76660a575ba932", "event_type": "public_safe_commitment_public_hf_visible", "event_utc": "2026-06-15T00:00:00+00:00", "public_safe_note": "Public-safe commitment is visible. Technical details remain withheld.", "record_id": "linux-kernel-virtualization-boundary-commitment-20260615"}
+{"artifact_sha256": "41257b5dfc7605e11c6ffad7f13408dac427bd2964a5ae211fef5b7f692f99dc", "event_type": "public_safe_commitment_public_hf_visible", "event_utc": "2026-06-15T00:00:00+00:00", "public_safe_note": "Public-safe commitment is visible. Technical details remain withheld.", "record_id": "werkzeug-windows-path-boundary-commitment-20260615"}

manifest.json

@@ -1,6 +1,6 @@
 {
   "change_log_present": true,
-  "commitment_record_count": 0,
+  "commitment_record_count": 3,
   "contact_receipt_row_count": 0,
   "contains_exploit_code": false,
   "contains_findings": false,
@@ -19,13 +19,28 @@
   "files": [
     {
       "path": "CHANGELOG.md",
-      "sha256": "4af1b8b99c545390cf8021e6b16c3639ba6ca99ebc5f73ff774c5286facca436",
+      "sha256": "94adba4ed4a5ef19cb7a74b700e7d9337b123db8494501f806c5ebd5bdd54e20",
       "size_bytes": 2035
     },
+    {
+      "path": "commitments/chromeos-authentication-boundary-commitment-20260606.md",
+      "sha256": "3aab5666be75f1d73a717b9c2c294414ba60066dedf294a14747469d3297f35f",
+      "size_bytes": 1686
+    },
+    {
+      "path": "commitments/linux-kernel-virtualization-boundary-commitment-20260615.md",
+      "sha256": "fb837a4c92fc423322d22112313086773f86bdba94739ccb6c76660a575ba932",
+      "size_bytes": 1348
+    },
+    {
+      "path": "commitments/werkzeug-windows-path-boundary-commitment-20260615.md",
+      "sha256": "41257b5dfc7605e11c6ffad7f13408dac427bd2964a5ae211fef5b7f692f99dc",
+      "size_bytes": 1334
+    },
     {
       "path": "data/commitment_index.jsonl",
-      "sha256": "e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855",
-      "size_bytes": 0
+      "sha256": "5c9554f83985800005c6510bf4cfd6378094e6ab4d6a66b14423a8e3b94f57b3",
+      "size_bytes": 3939
     },
     {
       "path": "data/contact_receipts.jsonl",
@@ -34,7 +49,7 @@
     },
     {
       "path": "data/disclosure_receipt_rule_index.jsonl",
-      "sha256": "53931219ef7a2440e784c8a079e7e2bf6a52536ab505464a7b236ab104bf83d9",
+      "sha256": "7e247d3d88bea67278105ebb9277152d02c644f1e7ac8d40b463ea64e345960b",
       "size_bytes": 1331
     },
     {
@@ -44,28 +59,28 @@
     },
     {
       "path": "data/public_commitment_stage_index.jsonl",
-      "sha256": "687dee2860407e052a85e9db384892da7120de62bca0357df1535fb048ad2e15",
+      "sha256": "c12bff86a6fa10e9bb3b42296214c6aa115cd30fe6d97a9129cd2e8a2a26b4e9",
       "size_bytes": 1268
     },
     {
       "path": "data/source_ledger_index.jsonl",
-      "sha256": "914359c4a299a2bb24f366048675cfad549f68ce9a58c541b333bb3b9f9f5906",
+      "sha256": "576af96a07afb654cf25bc1822f5d69f320c52fdc89d81cdc0934ae79af17eea",
       "size_bytes": 1110
     },
     {
       "path": "data/timeline_receipts.jsonl",
-      "sha256": "e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855",
-      "size_bytes": 0
+      "sha256": "2736ca7038593c93bb756eb704d187903e30101463afb9d7aed93b50cb568919",
+      "size_bytes": 1052
     },
     {
       "path": "DATASET_POLICY.md",
-      "sha256": "a9b2231c36a11ca31bcc9758fb8dde07ee40de8703d06b1854a56ebfc284c9df",
-      "size_bytes": 5112
+      "sha256": "fb20fe988dc3d042d3c2f9eb40a65c621e3bb78a568d003c411ec67490b96684",
+      "size_bytes": 1183
     },
     {
       "path": "README.md",
-      "sha256": "2e4354690a94ba0f876c60781effe6a4986480d8cd813bed7e74e0f3d702d6f0",
-      "size_bytes": 12127
+      "sha256": "f62c7f31f0d2a1f468adc576cfc05daaba285ac5497edc86fe7b43bee9cbe442",
+      "size_bytes": 2622
     },
     {
       "path": "schemas/commitment_index.schema.json",
@@ -104,13 +119,13 @@
     },
     {
       "path": "manifest.json",
-      "sha256": "70497fc0c1d5721e54165b4b3661293bf9386034cc73f8c383e0feaa5bc229d6",
-      "size_bytes": 6013
+      "sha256": "d627e14f2935118471b7a61386b677dbb84450598677ff88a5e92f7cfec5f6bd",
+      "size_bytes": 6701
     }
   ],
   "finding_row_count": 0,
   "future_findings_require_disclosure_clearance": true,
-  "generated_utc": "2026-06-15T16:23:00+00:00",
+  "generated_utc": "2026-06-15T16:52:39+00:00",
   "hf_repo_id": "cjc0013/responsible-disclosure-evidence-index",
   "manifest_version": "responsible_disclosure_hf_dataset_lane_v1",
   "private_disclosure_ledger_link_row_count": 0,
@@ -125,11 +140,11 @@
   "private_public_commitment_stage_row_count": 0,
   "public_actions_allowed_for_this_empty_scaffold": false,
   "public_actions_allowed_for_this_local_bundle": false,
-  "public_commitment_stage_candidate_count": 3,
+  "public_commitment_stage_candidate_count": 2,
   "public_commitment_stage_grace_days": 7,
   "public_commitment_stage_safety_boundary": "Public stage rows contain aggregate grace-period timing only. Detailed commitment-stage receipt mappings remain private until individually cleared.",
   "public_commitment_stage_summary_count": 1,
-  "public_release_review_state": "not_applicable",
+  "public_release_review_state": "public_safe_commitments_visible_technical_details_withheld",
   "public_safe_commitment_records_allowed": true,
   "public_safe_disclosure_receipt_rule_summaries_allowed": true,
   "public_safe_public_commitment_stage_summaries_allowed": true,
@@ -148,11 +163,11 @@
   },
   "source_ledger_safety_boundary": "Public source-ledger rows contain safe linkage and provenance only. Detailed rows remain private until individually cleared.",
   "source_ledger_sha256s": [
-    "31df0f5ca45214c57d15774ca60fe55f04d4af85aa1893bce7df82225942de0e"
+    "50313129a5be1a11720d72693bcf210fd1b2af41a7ce782a22c28a3298f7508b"
   ],
-  "status": "public_commitment_stage_summary_local_only",
-  "timeline_receipt_row_count": 0,
+  "status": "public_visible_public_safe_commitments_technical_details_withheld",
+  "timeline_receipt_row_count": 3,
   "title": "Responsible Disclosure Evidence Index",
-  "upload_performed": false,
-  "upload_visibility": "not_uploaded"
+  "upload_performed": true,
+  "upload_visibility": "public"
 }