User Tools

Site Tools


provenance:privacy:data_subject_rights

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
provenance:privacy:data_subject_rights [2026/09/16 11:21] – Log the citations re-review: all fixes confirmed, new material verified, and the two sources the reviewer could not fetch recorded against their dated snapshots. Authored by Claude karel.kubicek.claudeprovenance:privacy:data_subject_rights [2026/09/16 11:22] (current) – Close the two open verification items: chromestatus confirmed independently, all 8 citekeys and the six extraction-quote rows re-verified. Authored by Claude karel.kubicek.claude
Line 944: Line 944:
  
   * **Accepted:** the EDPB CEF 2026 URL 301-redirects to a slightly different slug. It resolves 200 with ''-L''; a future check that omits ''-L'' will see the redirect and should follow it rather than record a failure.   * **Accepted:** the EDPB CEF 2026 URL 301-redirects to a slightly different slug. It resolves 200 with ''-L''; a future check that omits ''-L'' will see the redirect and should follow it rather than record a failure.
-  * **Rejected as a finding, recorded as a limitation:** it could not verify the ''chromestatus'' feature entry or the Colorado ''coag.gov/uoom/'' page, because ''api.chromestatus.com'' refused its TLS connection and both pages render client-side for ''WebFetch''. Both **were** fetched successfully during the run — chromestatus through its JSON API (HTTP 200, 11,059 bytes) and ''coag.gov/uoom/'' with ''curl'' and a browser User-Agent (HTTP 200, 81,392 bytes) — and both are stored as dated byte snapshots under ''dsr/external/'', which is what ''dsr_quotecheck.py'' checks the published quotes against. This is the case the snapshot design exists for: a source that one tool can read and another cannot is not a source that has gone away.+  * **Rejected as a finding, recorded as a limitation:** it could not verify the ''chromestatus'' feature entry or the Colorado ''coag.gov/uoom/'' page, because ''api.chromestatus.com'' refused its TLS connection and both pages render client-side for ''WebFetch''. Both **were** fetched successfully during the run — chromestatus through its JSON API (HTTP 200, 11,059 bytes) and ''coag.gov/uoom/'' with ''curl'' and a browser User-Agent (HTTP 200, 81,392 bytes) — and both are stored as dated byte snapshots under ''dsr/external/'', which is what ''dsr_quotecheck.py'' checks the published quotes against. This is the case the snapshot design exists for: a source that one tool can read and another cannot is not a source that has gone away. **Closed after publication:** the reviewer's own delegated check later reached the chromestatus JSON and confirmed every claim independently — the feature name, the motivation string as an exact substring, the //Proposed// stage, the absence of a milestone on all four stages, the 2026-01-02 update timestamp, and the non-Google creator address. The same pass re-verified all 8 citekeys on this page and all six rows of the extraction-quote table in §6, including the two awkward ones: {[farooqi2020_canarytrap]}'s table paraphrase and {[rupp2022_leave]}'s column splice. ''coag.gov/uoom/'' remains unreadable to that toolchain and readable to ''curl''; the snapshot stands.
  
 ==== 11.3 Figures against the script (model: sonnet) ==== ==== 11.3 Figures against the script (model: sonnet) ====
provenance/privacy/data_subject_rights.txt · Last modified: by karel.kubicek.claude