# Context map | Task | Required target context | Add when needed | |---|---|---| | Explain the subject | [Home](https://healthcare-data-management-wiki.pages.dev/index.md), [applicability map](https://healthcare-data-management-wiki.pages.dev/applicability/index.md), and [legal framework](https://healthcare-data-management-wiki.pages.dev/legal-framework/index.md) | [DSPT](https://healthcare-data-management-wiki.pages.dev/dspt/index.md) when NHS information or systems are involved; sources and limitations | | Explain or check DSPT responsibilities | [DSPT](https://healthcare-data-management-wiki.pages.dev/dspt/index.md), [source register](https://healthcare-data-management-wiki.pages.dev/sources/index.md), and [operating model](https://healthcare-data-management-wiki.pages.dev/operating-model/index.md) | Organisation processing NHS patient information completes and publishes annually under NHS policy; purchaser checks supplier status before contract award under NHS guidance. Match legal entity, year, status, service coverage and required audit evidence. Actual terms govern access or receipt deadlines | | Set the DSPT condition for direct GP recruitment records | [Worked decision](https://healthcare-data-management-wiki.pages.dev/recruitment-assurance/index.md), [authority table](https://healthcare-data-management-wiki.pages.dev/dspt/index.md#what-makes-dspt-mandatory), and [contract condition](https://healthcare-data-management-wiki.pages.dev/dspt/index.md#recommended-contract-condition) | Commissioner should require Standards Met or Standards Exceeded before the contractor's first receipt, maintained throughout processing. Keep this proposal separate from NHS policy, section 250 scope, GC21.2 and the actual contract | | Maintain requester framing across new and existing content | Mapped authoring policy, [requester chapter](https://healthcare-data-management-wiki.pages.dev/requester-assurance/index.md), relevant subject page and portable concept | Preserve request/information direction, actual roles, responsible actor, authority, timing, evidence and legal qualifications; strengthen clarity rather than inventing duties | | Prepare or assess a request for identifiable records | [Requester readiness](https://healthcare-data-management-wiki.pages.dev/requester-assurance/index.md), [recruitment decision](https://healthcare-data-management-wiki.pages.dev/recruitment-assurance/index.md), and [data lifecycle](https://healthcare-data-management-wiki.pages.dev/data-lifecycle/index.md) | GP/provider receives the request and sends information; requester receives data. Keep mandatory DPIA, role-specific agreements and recommended evidence distinct | | Research a claim | Source register and relevant concept | Validation queue and Graphify | | Write new original English prose | Manifest `roles.authoring_policy` path, or `AUTHORING.md` fallback; the relevant source and intended reader task | Name the actor, action, exact authority, evidence and deadline. Apply the DenchCo ASD-STE100-inspired 80% house style, protected text and material exceptions; no computed score or compliance claim | | Maintain the Wiki | Manifest, agent guide, and change log | Design and runtime contracts | | 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 and project status | Failed or unrun checks and unparked validation items | | Propose a reusable Standard change | [Tracked proposal workflow](https://healthcare-data-management-wiki.pages.dev/llm-wiki/standard-proposals/index.md), verified originating commit/JJ phase, and immutable Standard pin | Marker matches, affected contract, licence/browser evidence, fixture, migration impact, payload/form digest, upstream registry, and adoption authority |