Skip to content

Project conformance

Selected level

Full / Level 7 (operational) under the evidence-linked knowledge standard.

Control Implementation
Human wiki Zensical navigation, decision guide, requirement model, legal and standards synthesis
LLM wiki Routing, response contract, maintenance and Graphify instructions
Evidence Source register, evidence matrix, validation queue and research log
Concepts Machine-checked canonical concept-link registry
Discovery/export Generated llms.txt, llms-full.txt, llms.json and OKF output
Graph Graphify raw update plus published/checked 2D and 3D views
Standards Structured CSV source and generated, checkable register
Design Binding tokens/components contract and visual-shape check
Renderer Zensical full, strict build, Regulation 28-style production shell
Service Per-user LaunchAgent, shared registry, stable port 8015 and HTTP-200 health
Deployment Live Cloudflare Pages Direct Upload with gated exact-commit workflow and canonical HTTP-200 health

Verification record

Initialization verified on 27 July 2026:

  • canonical content: 40 registered primary sources and 16 structured standards entries;
  • evidence controls: source IDs unique; claims through CLM-019; citations and 39-document local-link set clean;
  • concepts: five substantive canonical concepts and required inbound routes passed;
  • discovery/export: LLM and OKF outputs generated and current;
  • Graphify: deterministic refresh produced 552 nodes and 1,234 relationships with source, citation, navigation, filesystem, Markdown-link and file-reference layers; the default build and verification gate both refresh and check the 2D/3D publication assets;
  • renderer: Zensical 0.0.51 strict build completed with no issues; executable design checks cover governed Mermaid parts, bounded rectangular radii, pill exclusivity, tokenised rails/borders and single graph framing;
  • service: registered and installed as local.codex-dev.nhs-data-sharing-wiki; canonical URL returned HTTP 200 and service status reported healthy; terminating only listener PID 26860 caused launchd to restore service under PID 35057 with HTTP 200;
  • deployment: Direct Upload controls check private/protected-repository readiness, secret boundaries, exact-commit release records, canonical HTTP-200 health evidence and rollback procedure;
  • portfolio: source-controlled and live eight-service port audits passed;
  • browser: desktop and 390px-wide navigation, source deep link, and both graph views loaded in Chromium with no console warnings.
  • provenance: a child-root Git-backed Jujutsu repository was initialized; wiki initialization and verified runtime were committed as local phases 653401c1 and c2b9f25a.

10 Year Plan and digital-first expansion

Expansion verified on 27 July 2026:

  • canonical content: 64 registered sources and 20 structured standards entries;
  • evidence controls: claims through CLM-037, 19 maintained validation items and the 40-document local-link set passed;
  • concepts: six substantive canonical concepts and all required inbound routes passed;
  • policy boundary: the 2019 digital-first lineage, current 2026/27 primary-care contractual floor, NHS App, SPR, FDP, HDRS, NHS Online, inclusion, accessibility and assurance were separated by authority, status, purpose and delivery state;
  • Graphify: the enriched publication refresh produced 596 nodes and 1,364 relationships across 2D and 3D views;
  • renderer: strict Zensical build and executable design/visual-shape controls passed;
  • browser: desktop and 390px policy-page navigation, responsive content, SRC-041 deep-link targeting and source-row highlight passed with no console warnings or errors;
  • service: the canonical home and policy page returned HTTP 200 under the healthy LaunchAgent service, and the parent live port audit passed all eight registered services.

Chapter 3 analogue-to-digital commitment map

Expansion verified on 27 July 2026:

  • canonical content: 75 registered sources, 21 structured standards entries and 41 Markdown documents;
  • evidence controls: claims through CLM-052, 27 maintained validation items, linked citations and the 41-document local-link set passed;
  • concepts: seven substantive canonical concepts and all required inbound routes passed;
  • policy/delivery boundary: every named Chapter 3 App tool, the SPR propositions, HealthStore, patient-generated data, proxy access, AI/ambient documentation, accessibility, workforce sign-on and the unnamed planned-care platform were separated by current floor, live capability, limited rollout, roadmap, policy and legislation-dependent state;
  • current-status additions: limited AI-triage rollout, the summer-2027 HealthStore target, DAPB3051 v3.1 and its 31 December 2026 conformance date, National Proxy Service private beta, current NHS App accessibility defects and partial CIS2 versus future NHS-wide single sign-on were reconciled against primary sources;
  • Graphify: the required refresh produced 626 nodes and 1,457 relationships across the published 2D and 3D views;
  • renderer: strict Zensical build, content, standards, citation, discovery, local-link, canonical-concept, visual-shape, deployment-readiness and graph checks passed;
  • browser: desktop and 390px Chapter 3 navigation and responsive content rendered correctly; the SRC-069 deep link targeted the registered source row; no console warnings or errors were reported;
  • service: the canonical home, Chapter 3 page and source deep link returned HTTP 200 under the healthy LaunchAgent, and the parent live port audit passed all eight registered services.

DAPB4101 implementation reconciliation

Reconciliation verified on 27 July 2026:

  • canonical content: 75 registered sources, 21 structured standards entries and 41 Markdown documents;
  • evidence controls: claims through CLM-053, 28 maintained validation items and the linked citation/local-link set passed;
  • standards boundary: DAPB4101 v1.0.0 is recorded as a scoped section-250 laboratory-to-GP direct-care standard, distinct from general shared-record, App, AI, planning or research authority;
  • date boundary: the current ISN’s 30 April 2025 full-conformance date is preserved alongside NHS England’s later extension announcement; April 2027 is classified only as the intended pilot testing/assurance milestone because no replacement date or amended ISN is published;
  • implementation boundary: the FHIR/SNOMED pilot, gradual PaLM adoption, interim PBCL, EDIFACT coexistence, sender/receiver roles, specialty limits and clinical-safety checks are explicit;
  • Graphify: the required refresh produced 629 nodes and 1,463 relationships across the published 2D and 3D views;
  • verification: strict Zensical build, content, standards, citation, discovery, local-link, canonical-concept, visual-shape, deployment-readiness and graph checks passed;
  • service: the canonical home, pathology synthesis and SRC-028 deep link returned HTTP 200 under the healthy LaunchAgent, and the parent live port audit passed all eight registered services.

NHS Notify and App-first messaging reconciliation

Reconciliation verified on 27 July 2026:

  • canonical content: 76 registered sources, 21 structured standards entries and 41 Markdown documents;
  • evidence controls: claims through CLM-054, 29 maintained validation items and the linked citation/local-link set passed;
  • authority boundary: the current Medium Term Planning Framework’s addressee-specific migration requirements are separated from the 2025 Directions that require NHS England to operate Notify and from each sender’s own purpose, data-protection and confidentiality authority;
  • service boundary: the live API/MESH and PDS flow, configurable App-first routing, email/SMS/letter fallback, onboarding, status semantics, staged features and NHS App API distinction are explicit;
  • safety and inclusion boundary: sender-owned time-critical alternatives, reply routes, preferences, objections, accessible/language templates, transparency, retention, national data opt-out assessment and DCB0129/DCB0160 scope are validation gates;
  • Graphify: the required refresh produced 633 nodes and 1,472 relationships across the published 2D and 3D views;
  • verification: strict Zensical build, content, standards, citation, discovery, local-link, canonical-concept, visual-shape, deployment-readiness and graph checks passed;
  • service: the canonical home, NHS Notify synthesis and SRC-076 deep link returned HTTP 200 under the healthy LaunchAgent, and the parent live port audit passed all eight registered services.

Production publication

Production publication was established on 27 July 2026:

  • repository: private GitHub origin at https://github.com/ajdench/nhs-data-sharing-wiki with the reviewed content history on main;
  • deployment: authenticated Cloudflare Pages Direct Upload to https://nhs-data-sharing-wiki.pages.dev/;
  • release gate: the working tree must be clean and HEAD, local main and origin/main must identify the same commit before verification and upload;
  • health: the canonical production URL, not merely a loaded deployment or listener, must return HTTP 200;
  • record: the GitHub production release records the exact deployed commit and Cloudflare deployment identifier after final browser and HTTP validation.

A loaded LaunchAgent or open listener is insufficient: health requires the canonical URL http://127.0.0.1:8015/ to return HTTP 200.

Known limitations:

  • GitHub declined branch protection for the private repository on the current account plan; pull-request review, force-push/deletion protection and a required verification check therefore cannot yet be enforced server-side;
  • the checked-in GitHub Actions deployment path requires separately provisioned least-privilege Cloudflare repository secrets; current production publication uses authenticated local Direct Upload;
  • time-sensitive law, standards consultations and flow-specific applicability remain in the validation queue.