Infrastructure

In one line: Docusaurus renders the reference site; controlled publication and source identity keep its claims accountable.

The reference implementation uses Docusaurus with Mermaid and the existing Cloudflare Pages deployment. Consuming organizations may retain approved equivalents. A same-repository layout simplifies version association but does not prove deployed code and published documentation share a revision.

Keep a build/release receipt linking source revision, admitted corpus and served bundle. Verify the configured deployment path and actual served result; local build success is not remote publication success.

Docusaurus pages, HTML, search indexes, attachments and other assets are derived outputs. Public source admission and final-output classification apply to all of them. Labels and pattern scanners support review; they do not authorize disclosure or guarantee detection of every secret.

The future workspace keeps interactive questions, contributions, decisions and approvals in its authoritative store. Docusaurus renders permitted revisioned views. An MCP knowledge assistant retrieves with the same access/revision policy and cites sources; it does not approve changes or silently reconstruct inaccessible history. See Governed Factory and Business Intent Lifecycle.