Context map
| Task | Required target context | Add when needed |
|---|---|---|
| Answer what must be digital | Home, digital requirements register and how to read a requirement. Keep the information, responsible organisation, recipient, method, timing and authority together. | Relevant national chapter, source record and unresolved limits |
| Explain national reporting | National service reports; register rows ENG-015, WAL-003, SCT-D04 and NI-P01 | A return means a report. SMR01 is operational; exact digital legal linkage/claim/extraction conditions remain visible |
| Establish legal force | Legal framework, exact instrument and registered source. Separate statute, prescribed contract, adopted contract, saved have-regard regime, administrative mandate, guidance and operation. | Commencement, notice/version, service category, current contract and local schedule; an unseen term remains unknown |
| Compare public and private providers | Provider comparison, four-nation comparison and the row's provider/funding scope | Actual commissioning route, national participation and contract; ownership alone does not determine applicability |
| Apply the summary-record case | SCR and equivalent records and its linked register rows | Upload, retrieval, viewing and permitted users are separate roles |
| Apply the blood-results case | Blood tests and results and the national chapter | Ordering, lab reporting, clinical receipt, patient access and public-health notification; writing is not automatically digital-only |
| Apply the discharge case | Hospital discharge and its actual national/contractual scope | Capacity and representation, continuing-care recipients, method, deadline and local protocol |
| Apply child/adult protection | Protection explanation, worked examples, exact protection catalogue | Concerns can arise at any point in care. Separate reporting duty, digital route, any continuing-care handover and controlled access; police/education and private scope are actor-specific. Discharge is one worked setting. |
| Assess planning, research or public health | Purpose distinctions, relevant digital requirement and exact collection/notification/research authority | Secondary-use status, confidentiality, opt-outs and recipient permissions; these purposes remain in scope |
| Research a claim | Source register, relevant concept and primary official publication | Validation queue, local research leads and Graphify navigation; local synthesis is not independent authority |
| Write new original English prose | Manifest roles.authoring_policy path, or AUTHORING.md fallback; relevant source and reader task |
DenchCo ASD-STE100-inspired 80% house style, protected text and material exceptions; no computed compliance claim |
| Maintain the Wiki | Manifest, agent guide, project status and change log | Design and runtime contracts; derived outputs do not substitute for canonical source |
| Prepare a development response | Manifest capability, canonical Human Wiki URL and captured response draft | Markdown/HTML/plain-GFM link forms; --managed-live exact service identity and route HTTP; host pre-send hook for an uncaptured response |
| Select follow-up work | Current goal, project status and applicable verification | Failed or unrun checks and unparked validation items; do not reopen completed work without its recorded trigger |
| Propose a reusable Standard change | Tracked proposal workflow, verified originating commit/JJ phase and immutable Standard pin | Marker matches, affected contract, rights/evidence, fixture, migration impact, payload/form digest, upstream registry and adoption authority |
Subject routes
Digital requirements · How to read a requirement · Legal framework · Comparison · England · Wales · Scotland · Northern Ireland