| Where is the one-page précis of the whole Wiki? |
Home → Executive summary → linked canonical evidence, findings, Defence application and assurance records |
| What reports are included? |
Evidence base → all included reports → generated report record → primary Judiciary link |
| Why was a report included or excluded? |
Screening log → included-case dataset or exclusion record → review protocol |
| What did the coroner state? |
Generated report record or representative case → primary source; use the claims register where a stable CLM- trace exists |
| What did a recipient say? |
Official response evidence → registered SRC- response → explicitly labelled respondent account; do not merge it with the coronial concern or implementation evidence |
| What mechanisms recur? |
Findings overview → mechanism page → named report records and coding framework |
| How are reports distributed across mechanisms? |
Case–mechanism/evidence map → individual generated report pages; do not interpret an em dash as an evidence gap |
| Is a claim ready to cite? |
Claims register → source/verification → applicability and residual gap → validation queue |
| What matters to DPHC/CORTISONE? |
Transferability assessment → DPHC/CORTISONE view → finding–requirement–test crosswalk → REQ- register → AST- catalogue → Defence evidence gaps |
| Is a Defence control accepted or tested? |
Requirements CSV validation status → assurance-tests CSV execution status; the current registers contain candidates and designed tests |
| What research is next? |
Validation queue → search protocol → research log |
| What is publication-ready? |
Outputs overview → relevant ICMM derivative → canonical evidence trace and current submission checks |
| How is the wiki maintained? |
Maintenance guide → repository AGENTS.md → project conformance record |
| What does the 2D/3D graph show? |
About and tools → repository graph → Graphify maintenance; both projections share one complete enriched technical dataset, not study evidence |