Design implementation

The normative contract is the repository-root DESIGN.md.

Production boundary

Production uses stock Zensical runtime chrome from zensical.toml. The technical repository graph uses assets/graph.css and assets/wiki.js; the secondary Ask tool uses the .wiki-ask-scoped assets/ask-wiki.css and assets/ask-wiki.js. These assets must not style navigation, evidence tables, findings, Defence registers or the page shell. Ask output is navigational synthesis and has no evidence authority.

The former customised interface is isolated as the frozen, non-production zensical.sunset.toml plus assets/theme.css profile. It shares content and navigation with production but is not served by the always-on service.

Reader model

The navigation is organised as Evidence base, Findings, Defence application, Methods and assurance, Outputs, and About and tools. This sequence mirrors the authority and use path from source material to bounded synthesis and then analytical application. Repository operations and graphs are secondary because they explain how the wiki works rather than what the evidence shows.

The complete report corpus is browsed through generated catalogue and map pages. Individual generated report records are linked and searchable but are not all placed in the left navigation. Representative case narratives remain available as readable anchors.

Traceability model

primary source → report → claim → mechanism → candidate requirement → assurance test

The report catalogue, report records and case–mechanism/evidence map are generated views of the canonical included-case dataset. The repository graph is a separate technical Graphify view and has no evidence authority.