<!-- Derived Markdown alternate of llm-wiki/context-map.md; canonical repository sources and registered evidence retain authority. -->


# Context map

| Task | Required target context | Add when needed |
|---|---|---|
| Introduce the concepts | [Foundations overview](https://copper-tiger.pages.dev/foundations/index.md), [records](https://copper-tiger.pages.dev/foundations/records-and-purposes/index.md), [systems](https://copper-tiger.pages.dev/foundations/systems-and-capabilities/index.md), [information and work](https://copper-tiger.pages.dev/foundations/information-and-work/index.md), [governance, assurance and procurement](https://copper-tiger.pages.dev/foundations/governance-assurance-procurement/index.md), then [digital health landscape](https://copper-tiger.pages.dev/foundations/digital-health-landscape/index.md) | Assume no shared clinical/digital terminology; build definitions in order, then apply them to capabilities and assurance. Use the generic GP patient before the Defence application |
| Define the programme | [Programme scope](https://copper-tiger.pages.dev/programme-definition/index.md), [operating model](https://copper-tiger.pages.dev/operating-model/index.md), [architecture](https://copper-tiger.pages.dev/architecture/index.md), [national interfaces](https://copper-tiger.pages.dev/national-regional-integration/index.md) | Supplier agnostic; public evidence, proposal and discovery separate |
| Prepare a programme decision | [Decision brief](https://copper-tiger.pages.dev/programme-decision-brief/index.md), [project status](https://copper-tiger.pages.dev/project/status/index.md) and [discovery register](https://copper-tiger.pages.dev/validation-queue/index.md) | Focus on the wider case for change, outcomes and strategic direction. Keep public findings, proposals and open questions distinct. The owner rejected detailed referral development as the next priority; do not reintroduce it without new direction |
| Explain the subject | [Foundations](https://copper-tiger.pages.dev/foundations/index.md), [Defence context](https://copper-tiger.pages.dev/defence-context/index.md), [primary record](https://copper-tiger.pages.dev/primary-record/index.md), [model](https://copper-tiger.pages.dev/architecture/index.md), [flows](https://copper-tiger.pages.dev/information-flows/index.md), [governance](https://copper-tiger.pages.dev/governance/index.md) and [project status](https://copper-tiger.pages.dev/project/status/index.md) | Follow the [overview reading path](https://copper-tiger.pages.dev/index.md#read-the-argument-in-order); use detailed references for the question being answered |
| Check record-role consistency | [Foundation definitions](https://copper-tiger.pages.dev/foundations/records-and-purposes/index.md), [information and work](https://copper-tiger.pages.dev/foundations/information-and-work/index.md), [terms](https://copper-tiger.pages.dev/terms/index.md) and the relevant Human and portable concept pages | GP source role plus PRC role; community/hospital source accounts; contributions under applicable NHS conventions; primarily read-only DShCR separate from clinical authoring, PRC filing and responsibility |
| Develop shared-record capabilities | [Architecture](https://copper-tiger.pages.dev/architecture/index.md), [system concepts](https://copper-tiger.pages.dev/foundations/systems-and-capabilities/index.md), [flows](https://copper-tiger.pages.dev/information-flows/index.md), [governance](https://copper-tiger.pages.dev/governance/index.md) and [terms](https://copper-tiger.pages.dev/terms/index.md) | Connected, longitudinal overview with fuller source-record access; coverage/currency/permissions remain explicit. IntP two-way exchange and core clinical information for source-system CDSS; source authority/reconciliation remain TBC. HPD profiles and EMPI matching/shared demographics stay distinct from clinical records and patient administration. Continuity, forms and patient-facing options remain TBC. [SRC-212](https://copper-tiger.pages.dev/sources/index.md#src-212) [SRC-220](https://copper-tiger.pages.dev/sources/index.md#src-220) |
| Explain Defence healthcare and military medicine | [Programme terminology](https://copper-tiger.pages.dev/programme-definition/index.md#scope-and-initial-emphasis), [primary record](https://copper-tiger.pages.dev/primary-record/index.md), [Defence context](https://copper-tiger.pages.dev/defence-context/index.md) and [governance](https://copper-tiger.pages.dev/governance/index.md) | Wider Armed Forces/civilian scope; occupational health-led qualifies military medicine. Preserve public-source scope, occupational/command boundaries and dated history. [SRC-221](https://copper-tiger.pages.dev/sources/index.md#src-221) |
| Develop the broad concept | [NHS reference model](https://copper-tiger.pages.dev/nhs-reference-model/index.md), [terms](https://copper-tiger.pages.dev/terms/index.md), [legal framework](https://copper-tiger.pages.dev/legal-framework/index.md) | NHS England baseline, material devolved differences, public primary sources only |
| Specify information exchange | [Correspondence](https://copper-tiger.pages.dev/clinical-correspondence/index.md), [mechanisms](https://copper-tiger.pages.dev/exchange-mechanisms/index.md), [ADT](https://copper-tiger.pages.dev/messaging-and-events/index.md) | Exact profiles, versions, identity, acknowledgements and clinical tasks |
| Explain Defence mechanisms | [Public mechanism map](https://copper-tiger.pages.dev/defence-mechanisms/index.md) | Dated local evidence, announcement versus delivery, explicit unknowns |
| Assess GP IT procurement | [Framework](https://copper-tiger.pages.dev/gp-it-framework/index.md), [Lot 1](https://copper-tiger.pages.dev/gp-it-lot-1/index.md), [Lot 2](https://copper-tiger.pages.dev/gp-it-lot-2/index.md), [Lot 3](https://copper-tiger.pages.dev/gp-it-lot-3/index.md), [DSIC](https://copper-tiger.pages.dev/dsic/index.md), [TIF](https://copper-tiger.pages.dev/tech-innovation-framework/index.md) and [terms](https://copper-tiger.pages.dev/terms/index.md#gp-it-framework-and-assurance-terms); portable concept in `knowledge/concepts/gp-it-procurement.md` | Notice stage, lot scope, buyer eligibility, effective requirement versions, MUST/MAY epics and capability-specific evidence |
| 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](https://copper-tiger.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 |