Data, citation and reuse
This page provides direct access to the canonical structured records behind the Wiki. The current evidence-search cut-off is 2026-07-22. Generated pages, discovery files, the repository graph and Ask-the-Wiki answers are not source evidence and should not replace these records or the linked primary Judiciary publications.
The distribution, checksum, temporal and rights disclosures adopt selected data-catalogue practices from W3C DCAT 3, SRC-284; the project does not claim a conformant DCAT catalogue.
Canonical data downloads
| Dataset | Rows | Authority role | SHA-256 |
|---|---|---|---|
| Source register | 286 | Stable source provenance, role and reliability limits | 9075f8bc93f3a3eae5943e2789df4dfc31014b7a54a7688e4ea1903681f87033 |
| Screening log | 165 | Retained candidate discovery and dispositions | 5663ddb1474acc0ad9345762a22b690beed594af010d08f3de61ea09cacbeed6 |
| 2018 publication-cohort manifest | 379 | Archive enumeration, attachment identity, extraction route and available screening linkage | 05df998c880e1f22148af80c9e7ffc8ef449dfb0ca68360fe94fc663e3f3a47a |
| Included-report dataset | 112 | Canonical report extractions, controlled facets and source mappings | 73e280b750650684cf6e82104cbf09c1a430dcfe33c819369aeacdbfcbc950c2 |
| Claims register | 28 | Stable selective claims and source/report/code trace | 4169327c0e6c35993c256ef6b4ced560d7527d1f8cb0150861fa3102a7c3229a |
| Counter-position register | 10 | Bounded clarifications, disagreements, counter-risks and anomalies | 5574366f9f0b135f5e4494f11f286085a4a2b1133e00d9bebb75aa00456bb1ca |
| Candidate requirements | 13 | Defence-unvalidated analytical translations | b4f95550cc80e986a3a52ca02ae604365f979ad20de8d1e38f1804f3c20f0350 |
| Designed assurance tests | 13 | Unexecuted assurance-scenario designs | 0488674bd3fa28ef62da07e8da599e69c155cf09fcc96cf05ba2bf470c6844dc |
Checksums identify the exact bytes in this release. A later checksum indicates a changed file; inspect the research and evidence change log and Git history to determine whether the change is evidential, analytical or editorial.
Schema and controlled vocabularies
- Search protocol defines the candidate and screening boundary.
- Sociotechnical coding framework defines report fields, mechanisms and care-pathway classifications.
- Source types and authority separates reports, recipient responses, context and analytical records.
- Glossary and evidence labels defines stable IDs and downstream status labels.
- Evidence assurance and uncertainty exposes qualifications, coverage limits and open gates.
Suggested citation
Regulation 28 Digital Safety: targeted evidence map and thematic case synthesis. Evidence search cut-off 2026-07-22. Regulation 28 Digital Safety Wiki. Cite the page or dataset title, access date and, where available, the repository commit used.
For a report-specific proposition, cite the official PFD report and its registered SRC- record first. Cite this project only for its extraction, coding or synthesis. For a candidate Defence requirement or assurance scenario, include its stable REQ- or AST- identifier and state that it is unvalidated or unexecuted as applicable.
Rights and reuse boundary
No open-data or content licence is asserted by this project for Judiciary reports, response attachments, third-party publications or supplied material. Public availability is not permission to relicense. Reusers should check the originating publisher's terms, preserve source attribution and public redactions, avoid reconstructing redacted or private information, and distinguish verbatim source content from project extraction and analysis.
The structured project records are provided for audit and reuse subject to those source rights and the stated methodological limitations. No DOI, archived release package or formal citation metadata is currently claimed.