Documentation

The in-app Documentation workspace should render the same versioned Markdown used by the public website. This prevents the website and application from developing separate explanations of the same system.

Recommended behavior

• load navigation from documentation/navigation.json;
• render Markdown from documentation/;
• provide full-text search;
• preserve deep links between public and in-app routes;
• display the documentation and engine commit;
• open internal dashboard links without losing the current workspace;
• clearly mark pages that require operator privileges.

Source hierarchy

Public product guidance lives in documentation/. Research papers, detailed engineering standards, and design work orders remain in docs/ and may be linked as advanced material.

Versioning

Documentation should ship with the engine. A public corpus record should link to the documentation version that defined its verdict vocabulary and evidence contract.