Explicit canonical publication

Decision date: 2026-10-04. Status: accepted for this implementation.

Context

Existing Markdown and evidence already have validation and disclosure boundaries. The owner requested a standalone private documentation repository without copying or pushing platform implementation.

Considered alternatives

Considered: copying all docs, maintaining duplicate site articles, or an explicit route registry with an AST adapter.

Decision

Author website sources once in devSatym/resilience-gate-docs; publish only mapped routes and reviewed assets. Read platform implementation and reviewed evidence from the ignored .source/resilience-gate checkout pinned by site/config/source-repository.json to 2420ff4c2a88b1fa4a19e413cb0752e271480081. Translate logical source links through the Markdown AST and resolve them according to website or upstream ownership.

Consequences

The registry is additional review work, but unmapped/private/audit files stay out of output and search. A fresh clone requires npm run source:prepare before checks/builds. Documentation HEAD and upstream revision remain separate in the publication inventory; private authoring links require repository access. Repository separation preserved the initial 56 mapped routes; subsequent mapped engineering additions undergo the same validation.