| Explain the subject |
Home, applicability map, and legal framework |
DSPT when NHS information or systems are involved; sources and limitations |
| Assess an NHS-data assurance claim |
DSPT, source register, and operating model |
Actual entity, assessment period, coverage, status, audit and governing terms; DSPT does not authorise processing |
| Decide on DSPT for direct GP recruitment records |
Worked decision, authority table, and contract condition |
Recommend an explicit mandatory term; distinguish NHS policy, section 250 scope, GC21.2 and the actual contract; preserve separate legal permissions |
| Maintain requester framing across new and existing content |
Mapped authoring policy, requester chapter, 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, recruitment decision, and data lifecycle |
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 |
DenchCo ASD-STE100-inspired 80% house style, protected text, stricter local policy, 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, 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 |