# Research and change log ## 23 October 2026 — homepage layout restored - Restored the gold tiger explanation directly beneath the green architecture explanation, with the reading path before the continuity example and evidence guidance after it. - Restored the earlier two-column evidence-table format using the current public evidence, proposed direction and discovery wording. Kept the revised text, both approved questions, architectural detail, diagram, image treatment and section anchors. - Preserved the preceding layout review as dated history. This restoration changes presentation, not programme direction or evidence status. - Updated the browser check’s representative bullet-list route to the existing Foundations governance page, because the homepage definitions are now a table. Kept all list-layout assertions. ## 23 October 2026 — homepage flow and duplication - Kept both approved governing questions unchanged and preserved the substance of the green architectural explanation. Grouped its coverage and access qualifications beside the shared-view description. - Moved the continuity example before the onward reading path and placed evidence-reading guidance before the links. Consolidated programme scope in the introduction, retaining all healthcare purposes. The shorter caption retains concurrent care, source records and distinct sharing patterns. - Moved the unchanged gold tiger explanation to the end of the page. Preserved its image treatment, the continuity diagram, existing section anchors and earlier dated history. ## 23 October 2026 — Defence healthcare and military medicine consistency - Reviewed current Human Wiki pages, portable concepts and agent guidance against the revised question. Corrected the remaining broad “occupational health-led Defence healthcare” paraphrase and aligned military-only access summaries with the wider scope. - Clarified the owner’s terminology in programme scope and terms: occupational health-led qualifies military medicine; Defence healthcare remains inclusive of Armed Forces and civilian patients. Registered the direction as [SRC-221](https://copper-tiger.pages.dev/sources/index.md#src-221). - Preserved dated wording, source records, public findings and specific occupational-care examples. Kept treatment, occupational assessment and command disclosure distinct; the clarification does not change access authority or care entitlements. ## 23 October 2026 — linked questions and fuller shared-record explanation - Subsequent wording refinement: the second question now ends “across Defence healthcare and occupational health-led military medicine?” Both canonical copies match; earlier wording is retained in the revision history. - Replaced the single long governing question with the two approved linked questions on the overview and architecture. The first concerns lifelong GP-record continuity, explicitly including transfer from and to NHS general practice when Defence care arrangements begin and end. The second concerns the complementary internal DShCR. - Preserved the existing green architectural-principle paragraph and added the fuller explanation beneath it within the same callout. Removed only the Care Hub/Cortisone clause from the homepage introduction. - Defined contiguous presentation across sources and longitudinal continuity over time. Added authorised complete-source access, business continuity options and two-way IntP exchange, including core clinical information for CDSS in independent specialist source systems. Preserved source-record, EMPI, HPD and workflow boundaries. - Aligned Foundations, reference pages, programme summaries, portable concepts and discovery. Registered the clarification as owner direction in [SRC-220](https://copper-tiger.pages.dev/sources/index.md#src-220), separately from public evidence. Full wording revisions and the publication decision remain in internal context; the [project update](https://copper-tiger.pages.dev/project/updates/index.md#23-october-2026-linked-questions-and-shared-information) summarises them. - Extended the local governing-callout checks to support the approved two-paragraph format while retaining exact text and paragraph-order checks. The pinned Wiki Standard revision is unchanged. - The verification audit identified a dependency issue. Updated the bundled DOMPurify sanitizer from 3.4.16 to 3.4.17 and aligned its runtime checks; the Mermaid version and Wiki Standard pin remain unchanged. ## 22 October 2026 — governing question and inclusive continuity - Applied the owner-approved governing question identically to the overview and architecture. It centres on maintaining patients’ lifelong GP records to applicable NHS conventions and standards, continuity and transfer to NHS general practice, alongside a complementary DShCR. - Made Armed Forces and civilian patients explicit in the programme scope and related record explanations. Retained service-specific public guidance as bounded examples. “When care arrangements change” replaces a universal service-leaving condition. - Registered the wording decision as owner direction, with no change to public evidence states or organisational approval. Recorded the successive revisions and rationale in internal context and published their [summary](https://copper-tiger.pages.dev/project/updates/index.md#22-october-2026-governing-question-and-inclusive-continuity). Earlier wording remains in historical records. ## 22 October 2026 — shared record and platform clarification - Revised Foundations and the internal architecture from the completed owner clarification. The DShCR is a comprehensive, primarily read-only overview; source accounts and PRC contributions retain their distinct purposes. - Separated the IntP broker from workflow processing, the HPD from access enforcement, and the EMPI's identity/shared-demographic functions from patient administration. Kept forms, continuity design and patient-facing features open. - Updated the architecture diagram, glossary, knowledge summaries and discovery queue. Registered owner direction separately from public PHR, continuity, identifier, provenance and hash references. Raw deliberations remain outside the reader corpus. ## 22 October 2026 — supplier-agnostic Foundations signposts - Removed the remaining named product example and obsolete promises of product profiles, adoption comparisons and purchasing-route maps from Foundations. Updated the reading path to describe the capability landscape. ## 21 October 2026 — brighter tiger gold - Brightened the tiger explanation's text, citation and rail towards the image's warm gold tones. Both appearances retain readable text contrast. ## 21 October 2026 — tiger sizing during zoom - Made the explanatory tiger's height, width and text indent adapt together to zoom and text wrapping. The image uses the active font's visible letter height and its original aspect ratio. A width limit preserves reading space on narrow screens. ## 21 October 2026 — tiger callout spacing - Moved the explanatory tiger image closer to the gold rail and narrowed its column to keep a small gap before the text. Reduced its height to align with the visible lettering rather than the full line boxes. ## 21 October 2026 — homepage callout labels and image - Changed the overview labels to “Leading architectural principle:” and “The Copper Tiger:”. Repeated the existing tiger image inside its explanation, between the left rail and the indented text. Sized it against the text height, with a width limit on narrow screens. Applied darker muted gold to the explanatory text, citation and rail. Kept the title image and source citation. ## 21 October 2026 — strategic focus of the decision brief - Revised the [decision brief](https://copper-tiger.pages.dev/programme-decision-brief/index.md) around the wider Defence healthcare case for change, desired outcomes and strategic direction. Removed the detailed referral scenario, pathway-selection decision and scenario-based completion condition at the owner's request. - Broadened the problem–evidence–outcome map to care and readiness, continuity, governed purposes, resilience, experience, learning and value. Rechecked the existing public DMS, Medical Operating Concept, transition and professional-confidentiality sources. Preserved dates, limits and the distinction between public findings, proposed direction and open questions. - Aligned current programme, status and agent summaries with the strategic focus. Earlier log entries retain the history of the superseded brief. Existing evidence states and source identities are unchanged. ## 21 October 2026 — programme-definition decision brief - Added the draft [decision brief](https://copper-tiger.pages.dev/programme-decision-brief/index.md), with a problem–evidence–outcome table, proposed referral pathway, open questions and decisions requested. The scenario includes a pending result and connectivity interruption; it is not an approved workflow. - Rechecked the bounded records, referral, imaging, shared-care governance and CQC sources used in the brief. Imaging guidance and local CQC findings remained available through official indexed text after blocked direct retrieval. Preserved source identities, earlier retrieval records and evidence states; no new measured benefit or Defence-wide failure is claimed. - Linked the brief from programme definition, operating model, project status, agent context and the knowledge index. Kept the three programme priorities and parked implementation dependencies unchanged. The internal Defence shared care record retains capabilities beyond viewing. ## 21 October 2026 — Defence operating environments - Clarified the proposed programme scope in the overview and programme definition: the whole Defence healthcare operating model across Firmbase, Overseas and Operational (MARITIME, LAND and AIR) environments. External partner interfaces remain in scope. This records owner direction, not a new public evidence claim. ## 20 October 2026 — record terminology across the wiki - Reviewed the clinical model, flows, governance, product and procurement references, glossary and agent material against the Foundations definitions. Reframed the architecture and portable concept around source records, the GP record's additional PRC role and shared care access. Kept existing page addresses. - Corrected wording that treated PRC contributions and retained source records as alternatives, equated software with a record, or implied that only the PRC can be longitudinal. Updated the architecture diagram to identify the GP source and PRC roles. - Distinguished shared viewing, stored or retrieved information, filing into the PRC and accepting clinical work. Kept product-specific access and direct-entry capabilities explicit. - Aligned the glossary, concept summaries and maintenance guidance. Preserved original source wording, evidence identities and states, dated product/procurement evidence, and the distinction between the proposed model and implemented services. ## 19 October 2026 — simpler navigation - Removed the draft pen icons and tooltips from navigation at the owner's request, along with their unused asset and styling. Kept ordinary section chevrons and all source lifecycle metadata. - Replaced marker-presence checks with checks that draft markers and tooltips are absent and navigation remains usable. Recorded the pinned Standard's conditional `DKBWS-HUMAN-003` rule as not applicable; the Standard pin and catalogue are unchanged. ## 19 October 2026 — record roles and sharing diagram - Added a three-record diagram to [Records and their purposes](https://copper-tiger.pages.dev/foundations/records-and-purposes/index.md#how-source-records-contribute-to-continuing-care). It labels the GP record's additional PRC role and the referral, report, care-update, letter, result and summary flows. - Kept the diagram focused on selected communications. The caption distinguishes shared viewing, PRC updates and responsibility for follow-up, and recognises direct community–hospital communication. - Retained the shared Mermaid style, added an accessible title and description, and included the page in the discovered browser-verification inventory. Existing evidence states are unchanged. ## 17 October 2026 — source records and the GP record's continuing role - Clarified that the GP record is both a service-specific source record and the primary record of care (PRC). Community, intermediate-care and hospital records preserve their own originating accounts and contribute relevant information to the PRC. - Explained the wiki's specialist-source terminology without treating it as an exclusive record class, a consultant-only record or a separate application. Distinguished longitudinal history from the PRC role. - Connected the records through referral, correspondence, care updates, diagnostic reports and discharge summaries. Preserved the differences between updating the PRC, shared viewing, full GP-record transfer and accepting clinical work. - Aligned the glossary, applied landscape, information-flow example, primary-record reference and portable concept. Rechecked the existing NHS records, referral, outpatient and acute discharge sources; evidence states are unchanged. ## 17 October 2026 — vendor solutions and adoption evidence - Split the landscape table into clinical role, system category, example vendor solutions, and purchasing relationships. Separated RIS from PACS so product counts match their functions. - Added 25 dedicated solution profiles and a separate adoption reference. Kept the six-page Foundations sequence intact. Included the acute EPR third-place tie and retained HealthShare and IRIS as additional examples. - Used the existing InterSystems Codex project as a source-discovery lead, then cited original public evidence here. Its selected estate observations were not reused as a market census. - Recorded compiler counts only as evidence of that compilation. Distinguished practice/patient, filtered trust and historical ICS measures. Withheld a current GP ranking because cached and live register counts conflicted; preserved the CMA's 2022 patient-volume bands separately. - Registered 51 new public sources and 15 bounded claims covering product scope, NHS deployment, public awards, exact catalogue entries and adoption evidence. Retained the differences between supplier scope, clinical source-record role, assurance, buying and implementation. The Rio profile is a reference page, not a worked scenario. - Completed the machine-readable metadata for the fourteen previously registered landscape sources without changing their evidence states. Added the new public-source metadata, claim traces and a bounded market-evidence gap. ## 17 October 2026 — Foundations narrative consolidation - Reviewed the six pages as one introduction for clinical and digital readers. The sequence now moves from overview to records, systems, information and work, governance, then the applied digital health landscape before Defence context. - Gave record definitions, software capabilities, workflow terms, assurance and purchasing terms distinct teaching locations. Removed repeated primers and moved dated framework detail into the final product map. - Introduced one generic GP and specialist patient scenario, with each page developing a different aspect. Kept proposed workflow states and Defence implementation limits explicit. - Clarified the distinction between an epic requirement and the Epic product. Retained all six foundation functions, product examples, dated purchasing qualifications and existing evidence states; Rio remains a brief example. - Updated navigation, page handoffs and reader/agent guidance. Kept the six page addresses and existing relationship diagram unchanged. ## 17 October 2026 — digital health concepts, products and purchasing - Added a sixth Foundations page mapping clinical purpose and record roles to system categories, named products, assurance and purchasing evidence. Covered general practice, acute hospitals, mental-health/community care, laboratories, imaging, shared records and integration. - Explained what primary and specialist source records share and where their scope differs. A specialist source record can sit within a broad EPR or departmental system; it is not a purchasing category. - Included concise examples for Medicus, EMIS Web GP, Epic, Rio, WinPath, Sectra, HealthShare and IRIS. Rio remains a product example without a separate worked scenario, following the owner's direction. - Repaired blank-line breaks in the source and evidence tables so linked rows render as table entries. - Registered fourteen primary sources and eight bounded claims. Distinguished supplier descriptions, catalogue assessments, exact service listings, framework categories and historical contract awards. Preserved existing evidence states. - Recorded G-Cloud transition wording and product-scope gaps in the validation queue. Kept expired GP IT Futures, current TIF and planned Digital Primary Care procurement distinct. - Linked the page from Foundations, architecture, the homepage, glossary and agent/concept guidance; updated the six-page reading sequence. ## 17 October 2026 — five-page Foundations introduction - Added the agreed introduction for mixed clinical and digital readers with no shared terminology assumed. The five pages cover the relationship map, record purposes, systems and capabilities, information movement and clinical work, then governance, assurance and procurement. - Explained how the primary record of care relates to Foundation EPR Solutions, supporting capabilities and shared-record platforms. Linked record roles, technical delivery, clinical tasks, permitted purposes and purchasing categories throughout. - Used one hypothetical Defence GP and specialist journey to connect the explanations. Kept the scenario distinct from implemented Defence services and retained the planned procurement and rollout qualifications. - Reused registered evidence and checked relevant primary sources. No source or claim states changed. Added contextual links to the detailed references, concept index and LLM guidance. - Placed Foundations before Defence context in the navigation and homepage reading path. Extended the ordinary diagram inventory to include the new relationship map, with the same browser verification requirements. ## 17 October 2026 — narrative structure and reading paths - Reviewed the navigation against the governing question. The previous order placed the NHS reference and six procurement pages before the clinical model. Several page endings sent readers back to earlier explanations without a clear continuation. - Reordered the wiki around clinical need and model, information flows, governance and access, delivery and procurement, then evidence and decisions. Kept the existing page addresses, source claims and evidence states. - Added an ordered homepage route and a shorter first reading path. Clarified the separate roles of the architecture, NHS reference model, flow, governance and Defence-mechanism pages. Added purposeful handoffs into supporting detail and the final implementation limits. - Aligned the portable concept index and LLM guidance. Preserved parked evidence gaps and the qualified Defence timetable. The research boundary now identifies the separate 17 October procurement and assurance addition. ## 17 October 2026 — lighter grey explanation - Lightened the copper-tiger explanation from `#444444` to `#666666` at the owner's request. Its text, source superscript and rail share the softer grey. ## 17 October 2026 — charcoal explanation and source superscripts - Changed the copper-tiger explanation's text, citation and rail from black to charcoal. Retained the readable light-neutral treatment in dark mode. - Checked the published Standard revision and its local Codex citation branch. Applied that branch's numeric superscript pattern without changing this wiki's Standard pin. - Preserved full source identities in canonical Markdown, accessible labels and tooltips. Grouped adjacent citations with commas while keeping each number independently linked to its exact source row. - Preserved explanatory links, notes and code examples. Added renderer and browser checks for the presentation in both appearances and at desktop and mobile widths. ## 17 October 2026 — wiki-wide Mermaid coverage - Confirmed that the shared Safari correction loads throughout the wiki. The current corpus contains two Mermaid diagrams, on the homepage and architecture page. - Replaced fixed verification routes with automatic discovery across all canonical pages. Reconciled diagram content and counts with the built site, and required the shared adapter on every diagram page. - Added checks for palette and page-width changes at reduced zoom, followed by enlargement. Both browser engines now inspect every discovered page; newly added pages enter the same matrix automatically. - Added discovery fixtures for nested pages, multiple diagrams, missing output, stale content and missing adapters. Retained the distinction between automated CSS scaling and native Safari observations. ## 17 October 2026 — lot pages, DSIC, TIF and framework terminology - Applied the five browser comments: added an attributed scope blockquote, linked each lot to a researched page, created DSIC and TIF pages, and expanded the glossary. - Started with local Graphify and content in InterSystems, Care Hub and DMICP InterOp. Used their taxonomy, assurance and roadmap coverage as leads, then checked the original public sources. Scoped searches also found narrower DA-OPIP integration references and adjacent UK Digital Health material. - Qualified a local TIF description against its official six-core-function scope. Preserved the distinction between foundation records, supporting capabilities and shared views. - Registered twelve primary sources and ten traced claims. Examined C13, Digital Diagnostics and Task Management, including MUST/MAY requirements and effective versus future-published versions. - Recorded migration-guide scope, TIF clinical release and one attributed practice case. Distinguished Lot 3 lifecycle context from contractual deliverables and flagged UK3 call-off wording for final-document clarification. - Kept the inaccessible attachment and future tender conditions parked. Updated navigation, source-table placement, knowledge and LLM discovery. Earlier Defence rollout qualifications remain unchanged. ## 17 October 2026 — Safari zoom transitions and single-line clinical label - Reproduced label drift after native Safari zoom changes and overlapping text when a two-line label was enlarged. The earlier mount-only correction was insufficient. - Updated label positioning after resize and font loading. Converted line offsets to SVG units and increased the wrapping threshold so “Defence primary healthcare” stays on one line in a wider box. - Inspected the homepage in Safari 27.0.1 at 50%, 75%, 100%, 125%, 150% and 200%, including reloads and a 50% to 200% transition. Inspected the architecture at 50%. - Extended the Chromium and WebKit checks to preserve the same mounted diagram during CSS zoom and viewport changes. Added a single-line assertion that still identifies the label if it wraps. These automated checks supplement the native Safari observations. ## 17 October 2026 — Digital Primary Care Open Framework research - Followed the HTN lead to the official UK3 notice, its OCDS API, earlier engagement and current NHS guidance. Registered eight sources with dates, access limits and rights metadata. - Added [framework research](https://copper-tiger.pages.dev/gp-it-framework/index.md), seven traced claims and one portable concept. Recorded value/VAT, lot scope, indicative timing, anticipated MOD buyer scope and TIF continuity. - Separated procurement from service approval and implementation. Added current NHS HealthShare structured-consumer evidence with capability/version limits. - Parked final tender, attachment and participation questions until new public evidence appears. Preserved the Defence timetable correction and existing source states. - Reviewed the separate InterSystems wiki to prepare a specific research prompt. The handoff artifact is not COPPER TIGER topic evidence or a message sent to another chat. ## 17 October 2026 — Safari diagram label positioning - Reproduced low-positioned Mermaid labels in Safari 27.0.1 at the existing 50% page zoom. - Centred ordinary SVG labels after mounting, using their measured geometry. Preserved the node boxes, connectors, wording, colours and reader's zoom setting. - Added actual-page label containment and centring checks in Chromium and WebKit. The matrix covers both diagrams, appearances, page widths and reloads. Native Safari zoom remains a separate visual check; CSS scaling is only supplementary coverage. ## 16 October 2026 — broad NHS technical and legal reference - Confirmed NHS England as baseline, with material devolved differences. The requested expansion covers both concepts and implementation detail, using public primary sources only. Undocumented Defence mechanisms remain unknown. - Added the [reference model](https://copper-tiger.pages.dev/nhs-reference-model/index.md), [legal framework](https://copper-tiger.pages.dev/legal-framework/index.md), [correspondence catalogue](https://copper-tiger.pages.dev/clinical-correspondence/index.md), [exchange mechanisms](https://copper-tiger.pages.dev/exchange-mechanisms/index.md), [ADT reference](https://copper-tiger.pages.dev/messaging-and-events/index.md) and [Defence mechanism map](https://copper-tiger.pages.dev/defence-mechanisms/index.md). Expanded terminology and connected the architecture to proposed interface contracts and legal decision records. - Registered 59 public sources and 25 traced claims. Recorded current versions, source dates, retrieval limitations and the distinction between content standards, technical specifications, transport and clinical responsibility. - Identified public Defence e-RS participation and bounded local workflow evidence. Distinguished those findings from estate-wide protocol claims. Preserved the existing attributed timetable correction without treating it as new public evidence. - Recorded commenced 2026 legal changes, NEMS deprecation/migration notices, live STU3 Transfer of Care profiles and developing pathology interfaces. Worked message sequences and recovery rules remain labelled proposals. - Added four portable concepts, source-linked navigation and broader public-evidence questions. Updated Human and LLM discovery while preserving the governing question, image and original seed bytes. - Completion uses the full applicable verification, graph/site regeneration, maintainer provenance check and Jujutsu commit. Generated receipts remain derived evidence. ## 16 October 2026 — header colours and Defence clinical services - Added a short explanation of the Chinese tiger tally below the homepage purposes summary, using a black compact callout. Registered the museum source and bounded the claim to historical function, without identifying the pictured specimen. - Refined the header to pale sage after the owner's request for less intensity. Muted the dark-mode header and retained readable text and controls. - Applied the owner's green-header direction and softened copper colours across both appearances, diagrams and graph views. Kept the original brand values and image intact. - Clarified the governing question to say “across Defence clinical services and specialties” at the owner's request. - Applied the exact wording to the homepage and architecture callouts. Preserved the historical scope record and its original quotation. ## 14 October 2026 — civilian history and military clinical scope - Expanded the governing question at the owner's request. Made civilian history explicit within the lifelong primary record and added information access, sharing, clinical specialties and military healthcare requirements. - Added five public sources and one project scope record. Researched care during service, full-record requests, aviation and diving medicine, and the forward concept for deployed care. - Propagated the distinction through the architecture, topic pages, glossary, six-concept bundle context, LLM guidance and discovery. Added six traced claims and two bounded validation items. - Kept treatment, occupational assessment, command disclosure and secondary purposes distinct. Preserved the original transcripts and the rollout-timetable correction. ## 14 October 2026 — homepage project image - Added the COPPER TIGER image beside the homepage title, with a smaller size on narrow screens. - Retained its original colours, transparent background and bytes. Moved the single canonical PNG to `docs/assets/brand/copper-tiger.png` so the wiki build serves it directly. - Updated the asset record to reflect the owner's request to display it on the local homepage. - Corrected a diagram verification false failure exposed by the title layout. Diagram screenshots now inspect every pixel; the colour, opacity and topology requirements are unchanged. ## 14 October 2026 — shared callout style - Made the governing question's slim rail, compact inset and transparent background the default authored callout style. - Applied the shared treatment to the home summary, retaining green text and rail in both colour modes. The same geometry applies to all current callouts and the reusable `.callout` component. ## 14 October 2026 — COPPER TIGER image retained - Preserved the owner-provided COPPER TIGER PNG at `assets/brand/copper-tiger.png` for later project use. - Kept the original bytes and alpha channel. The adjacent JSON record holds provenance, dimensions and a SHA-256 checksum. - The image is a project visual asset and has not been placed on wiki pages. ## 14 October 2026 — initial research edition - Ingested the three user-provided Markdown transcripts without changing their original bytes. Registered their roles as design intent and unverified research leads. [SRC-001](https://copper-tiger.pages.dev/sources/index.md#src-001) [SRC-002](https://copper-tiger.pages.dev/sources/index.md#src-002) [SRC-003](https://copper-tiger.pages.dev/sources/index.md#src-003) - Verified and expanded the subject against official NHS England, MOD, parliamentary, legislation, ICO, GMC, CQC and NDG sources. Kept source dates, scope and retrieval limitations distinct. - Qualified the single-GP assumption, identified GP2GP and GP Connect boundaries, and separated source records, correspondence, shared viewing and clinical responsibility. - Registered the owner’s update that the announced 2027 timetable remains under review and it is not yet confirmed that rollout will proceed as announced. Applied the owner’s latest clarification in place of the earlier, stronger wording. The published announcement remains historical formal evidence. [SRC-011](https://copper-tiger.pages.dev/sources/index.md#src-011) [SRC-030](https://copper-tiger.pages.dev/sources/index.md#src-030) - Selected an independent Standard Production consumer at immutable Standard revision `d339a0e30de41c4a3260f22c00c96898299a1834`. External deployment remains off. - Applied the chosen main `#966e2c`, secondary `#658a6e` and third `#684b34` colours, with accessible scheme variants recorded in the design contract. - Built the Human and LLM views, six linked concepts, source register, evidence matrix and bounded validation queue. Both graph views open on research and evidence, with the complete repository available through the scope control. - Passed the browser checks for search, source-row navigation, diagrams, width controls, mobile tables, both colour modes and graph scope changes. The completion workflow reruns all applicable checks and records the result before its Jujutsu commit. - Registered the local service on port 8028 in the parent portfolio and user-local registry. Confirmed exact service identity and automatic recovery after interruption. The parent reservation changes are outside this independent wiki repository. - Recorded the audit baseline: no known Python vulnerabilities; Node audit meets the moderate threshold with two low-severity package findings for `GHSA-238p-pmpm-9mq7` in the qualified KaTeX/Mermaid dependency chain. The [evidence matrix](https://copper-tiger.pages.dev/evidence-matrix/index.md) records claim states. The [validation queue](https://copper-tiger.pages.dev/validation-queue/index.md) preserves unresolved issues without promoting them to facts. Current implementation status is in [project status](https://copper-tiger.pages.dev/project/status/index.md). ## 20 October 2026 — programme-wide supplier-agnostic definition Preserved the prior clean wiki at v1.0.0 before publication changes. Added the programme scope, operating model, internal Defence architecture and national/regional interface map. Registered the national research and owner direction separately. Updated record definitions, discovery, navigation and agent context. Retired product profiles/comparisons from the current corpus; their source provenance and release history remain. Original seed bytes and the pinned Wiki Standard revision are unchanged. See [programme definition](https://copper-tiger.pages.dev/programme-definition/index.md) and [release history](https://copper-tiger.pages.dev/project/releases/index.md).