| Both sides previous revisionPrevious revision | |
| provenance:privacy:browser_storage [2026/09/17 07:23] – Markup rendering sweep: wrap escapes, CLI flag typography, and heading quotes. Authored by Claude. karel.kubicek.claude | provenance:privacy:browser_storage [2026/09/17 10:45] (current) – Record consentAction schema clarification; Authored by Claude karel.kubicek.claude |
|---|
| | assessed a law | ''legal.length > 0'' | 402 | | | assessed a law | ''legal.length > 0'' | 402 | |
| | assessed the GDPR or ePrivacy | of those, ''legal[].law'' matches GDPR or ePrivacy | 283 | | | assessed the GDPR or ePrivacy | of those, ''legal[].law'' matches GDPR or ePrivacy | 283 | |
| | crawled and stated a consent action | crawled AND ''crawlConfig.consentAction'' is not a sentinel | 349 | | | crawled with ''consentAction'' field populated (schema; not an audited paper claim) | crawled AND ''crawlConfig.consentAction'' is not a sentinel | 349 | |
| |
| **A sentinel bug that survived the first draft.** The consent population was originally written as ''consentAction !== "not-stated"'', which gave **585**. ''not-applicable'' is a sentinel too and 236 crawled papers carry it, so that filter counted a sentinel as an answer — exactly the failure the site's own rules warn about. The corrected filter uses ''isSentinel()'' from ''lib.mjs'' and gives **349**, which is the figure ''OVERVIEW.md'' publishes for ''crawlConfig.consentAction''. The mention share moved from 13.8% to **18.9%**. Caught by the figures-versus-script reviewer, not by me; see §14. | **A sentinel bug that survived the first draft.** The consent population was originally written as ''consentAction !== "not-stated"'', which gave **585**. ''not-applicable'' is a sentinel too and 236 crawled papers carry it, so that filter counted a sentinel as an answer — exactly the failure the site's own rules warn about. The corrected filter uses ''isSentinel()'' from ''lib.mjs'' and gives **349** raw schema-populated fields, which is the figure ''OVERVIEW.md'' publishes for ''crawlConfig.consentAction''. The separate 2026-09-05 full-text audit found **55 of 1,120 crawling papers (4.9%)** stating an action; the 66/349 storage overlap below remains conditioned on the raw field filter. The mention share moved from 13.8% to **18.9%**. Caught by the figures-versus-script reviewer, not by me; see §14. |
| |
| **4 of 5,859 papers have no ''paper.cols.txt''** and are excluded from every full-text figure. They are not excluded from the extraction-field figures, which is a small inconsistency and is stated here rather than papered over. | **4 of 5,859 papers have no ''paper.cols.txt''** and are excluded from every full-text figure. They are not excluded from the extraction-field figures, which is a small inconsistency and is stated here rather than papered over. |
| ## Overlap with the compliance literature | ## Overlap with the compliance literature |
| |
| Population N names >=1 core store share Tier A | Population N names >=1 core store share Tier A |
| ------------------------------------------- --- -------------------- ----- ------ | --------------------------------------------------- --- -------------------- ----- ------ |
| assessed a law 402 35 8.7% 4 | assessed a law 402 35 8.7% 4 |
| assessed the GDPR or the ePrivacy Directive 283 27 9.5% 3 | assessed the GDPR or the ePrivacy Directive 283 27 9.5% 3 |
| crawled and stated a consent action 349 66 18.9% 22 | crawled with consentAction field populated (schema) 349 66 18.9% 22 |
| |
| Again a MENTION test. It does not say those papers measured only cookies, only that the | Again a MENTION test. It does not say those papers measured only cookies, only that the |
| |
| Mechanical rendering repair only: a fresh live raw/XHTML export of 188 pages was checked with ''check_wrap.mjs'' and ''check_typography.mjs''. Affected plugin tags, CLI flags and heading markup were repaired; no figures or substantive prose were changed. The resulting source and rendered DOM were re-checked after saving. | Mechanical rendering repair only: a fresh live raw/XHTML export of 188 pages was checked with ''check_wrap.mjs'' and ''check_typography.mjs''. Affected plugin tags, CLI flags and heading markup were repaired; no figures or substantive prose were changed. The resulting source and rendered DOM were re-checked after saving. |
| | |
| | ===== ConsentAction audit propagation, 2026-09-17 ===== |
| | |
| | **What was wrong.** The browser-storage overlap table called the 349-paper raw ''consentAction'' filter ''crawled and stated a consent action''. That filter only establishes a non-sentinel schema value, not a paper claim; the downstream 66/349 storage overlap was therefore also easy to misread. |
| | |
| | **Command and real output.** ''node scripts/report_browser_storage.mjs'' → ''crawled with consentAction field populated (schema) | 349 | 66 | 18.9% | 22''. ''node scripts/consent_action_noninteraction_audit.mjs'' → **55/1,120 = 4.9%** audited paper claims and **279/313 = 89.1%** unsupported ''no-interaction'' labels. |
| | |
| | **What changed.** The report output, population table and explanatory paragraph now label the 349 filter as schema population and say that the storage overlap remains conditioned on that raw field filter; the audited claim count is separate. |
| | |
| | **Review.** One **model: 'sonnet'** figures-vs-script pass re-ran ''report_browser_storage.mjs'' and checked the edited overlap row, both legal rows around it, and the 66/349 calculation. No mismatch was found. No citation pass was needed: no citekey or quoted claim changed. |
| | |
| | **Rejected finding.** The 349 filter was not silently changed to 55: doing so would change the denominator of the browser-storage overlap question. It is now labelled and bounded correctly. |
| |
