DECLARATION INDEX

Source inventory

Source paths link to a private repository. Static registration candidates do not prove compilation, feature activation or live invocation.

REVIEWED SOURCE AND CURRENT DRIFT

Status & limits

Each map identifies its own reviewed source revision. Unchanged views can retain an earlier revision. Freshness compares the mapped source content with the implementation at export time; browser evidence applies to the exact generated artifact bytes.

Architecture status record

Planned or pending in the status record

Verification limits

The nine viewers carry artifact-bound Archify receipts with 9/9 showcase checks and all four finalize gates. Each map's receipt identifies its reviewed source and artifact hashes. Exporting a viewer does not create new browser or production acceptance evidence. Installers, model execution, physical pairing, deployments and live Canvas collaboration require separate acceptance evidence.

LOCAL WORKFLOW

Publishing documentation

Sync inventories, check source drift, review changed maps, then export a new static version. GitHub Actions are intentionally disabled.

node scripts/kr8/architecture-sync.mjs sync
node scripts/kr8/architecture-sync.mjs check
node --test scripts/kr8/architecture-test.mjs
node scripts/kr8/architecture-sync.mjs publish site/docs/versions/<version>

An explicit historical export uses --allow-stale and displays the affected maps as requiring semantic review. It does not pass the current architecture gate.

The local watcher is bounded and never deploys or acknowledges semantic changes:

node scripts/kr8/architecture-sync.mjs watch --seconds 300 --interval-ms 2000

After reviewing a new semantic candidate and passing source-backed Archify finalization, record the reviewer, exact source SHA and actual change:

node scripts/kr8/architecture-sync.mjs acknowledge --map agents --source-sha <full-SHA> --reviewer <reviewer> --note "Reviewed source change and verification"

Each version is an immutable directory with a SHA-256 export manifest. The portal selects one version through active.json. Deployment copies the static documentation to the kr8.dev apex host. Existing community and relay subdomains retain their services and routes.

kr8.app hosts the product introduction. The documentation portal is standalone static HTML and has no ChatGPT Sites dependency.