Methods and assurance
This section explains how the corpus was assembled, how evidence is coded and synthesised, and how a reader can audit the route from primary source to interpretation.
Review conduct
- Review design and audits routes through method, protocol, selection flow, historical and supplied-document audits, counts and update policy.
- Analytical lenses routes through the coding framework, information lifecycle and literature context.
- Evidence controls routes through provenance, claims, counter-positions, uncertainty, validation and change.
Traceability and assurance
- Source register: stable source identifiers, provenance and reliability limits.
- Source types and reliability: how primary reports, responses, context and analytical records differ.
- Claims register, with a generated human-readable view: stable cross-case, project and translation claims with source, report and mechanism mappings.
- Validation queue: unsupported claims, rechecks and release gates.
- Research change record: evidential and methodological changes.
- Evidence assurance and uncertainty: generated disclosure of qualified rows, coverage gaps and downstream status.
- Living update and release policy: update triggers and distinction between evidence releases and editorial corrections.
The included-report dataset is the row-level authority for the current corpus. Generated catalogues, graphs and discovery files are routes into that evidence; they do not add authority.
The review method also records where AI-assisted tools supported discovery, extraction, drafting and checking, and why automation does not replace source verification or an independent human second review.
Assurance boundary
The current work is a targeted evidence map and thematic case synthesis. It is not an exhaustive systematic review, prevalence study, causal comparison of products, or finding about current Defence systems. Candidate requirements remain analytical translations until validated against DPHC workflows and Programme CORTISONE specifications.