Conformance record
| Field | Value |
|---|---|
| Applicable profile | Evidence-linked topic wiki using a targeted evidence map and thematic case synthesis |
| Highest implemented level | Level 4 Graph-Linked; no Level 5 or Level 6 claim |
| Renderer | Zensical 0.0.50 runtime-default UI, production |
| Adapter | No production chrome adapter; repository-graph and Ask Wiki component assets are content-scoped |
| Sunset UI | Frozen non-production profile (zensical.sunset.toml, assets/theme.css) |
| Material | Omitted by explicit user choice |
| Authority chain | Primary source → report → claim → mechanism → candidate requirement → assurance test; statement type and transferability limits remain explicit |
| Evidence status | Current pass: 87 retained candidates, 71 fully extracted included reports, 16 exclusions; complete 379-row 2018 publication-cohort enumeration/extraction with 36 retained cohort decisions and 343 rows lacking contextual dispositions; targeted 2019–2026 discovery and limited later-migration check; official source URL retained for every included row; not exhaustive interval-wide and not a prevalence estimate |
| Generated evidence views | Complete 71-report catalogue, individual report pages and case–mechanism/evidence map generated from docs/icmm/included_cases.csv, with freshness and row/page-count checks |
| Defence traceability | Stable candidate REQ- and designed AST- registers; Defence validation and test execution are not claimed |
| Repository graph | Graphify source workflow plus same-data 2D and 3D publication, demoted to a technical view under About and tools; not study evidence |
| Generated discovery | Content-aware llms.txt, llms-full.txt, and llms.json with authority metadata and freshness check |
| OKF sidecar | Not implemented; no Level 6 claim |
| Browser evidence | Current stock-profile pass covered the home route, complete report catalogue, a 2018 generated report, findings, Defence requirements/tests, the 2018 method audit, search, two-level nested navigation, mobile drawer, narrow tables, visible keyboard focus, Mermaid rendering and both repository graphs. The 20 July Ask Wiki pass additionally covered desktop and narrow form layout, correct /search.json retrieval, one-result-per-page diversity, missing-key validation, fail-closed endpoint behaviour, six retrieved links and console errors. No page-level horizontal overflow or console errors were observed; broader screen-reader testing remains open. No Level 5 claim. |
| Full runtime/release discipline | Not claimed |
| Local runtime | LaunchAgent-backed regulation-28-wiki service at http://127.0.0.1:8000/; registered, loaded, HTTP 200, restart tested |
| Last verification | 2026-07-20 Ask Wiki pass: canonical regeneration; content, endpoint, access-control, bounded-input, link, semantic trace, abstract, profile-isolation and discovery-freshness checks; Pages Function compilation; Graphify refresh/publication; strict stock and sunset builds; desktop/narrow Ask Wiki browser pass. Production secret, inference and deployment checks remain pending until the protected release. Pages rejects the Workers ratelimits binding, so no per-user or WAF rate limit is claimed. |
Production intentionally exposes the native Zensical baseline. The reader model now separates evidence, findings, Defence application, methods and outputs from operational tooling. The repository graph remains a Graph-Linked implementation contribution, but the generated case–mechanism/evidence map is the reader-facing analytical map. The sunset UI is retained for comparison, not as a supported adapter.