Publishing contract

The workbench is built for https://www.christianmlange.com/gme-1d/. The Contabo-side route and destination directory already exist — see CONTABO_ROUTE.md at the repo root for exactly what is deployed there and when it changed. Repository setup itself still never touches Contabo.

Local authoring

make site
.venv/bin/python -m mkdocs serve

The built site contains the main, supplementary, and combined PDFs; workbench pages; figure/evidence pages; and the complete rendered derivation archive. All pages carry noindex, nofollow, noarchive metadata.

qluster01 deployment

tools/publish_online.sh runs the build audit and publishes in one step — there is no separate gate to satisfy, so it can run whenever there is something worth publishing:

tools/publish_online.sh
# equivalent to:
#   make check
#   ~/bin/publish-docs.sh gme-1d ./site

Continuous publishing is provided by tools/gme-1d-online-publisher.service as a qluster user systemd unit. It runs tools/supervise_online_publisher.sh, which calls publish_online.sh in a loop (~60s). Installation and enablement are qluster01-side deployment steps, not repository setup steps.

Contabo remains a static target only: there must be no repo clone or build there.

Shared infrastructure

Changing the Caddy route or authentication policy changes shared Contabo infrastructure and requires explicit user approval — that has already happened for the current route (see CONTABO_ROUTE.md). Any further change to it (e.g. adding auth back) needs approval again.

Release transition

The drafting site is publicly accessible but deliberately carries noindex metadata while it remains a working document. At preprint release, the same surface can become the polished, indexable site and PDF release. Implementation, reviewer, and archival data packages remain private until separately scoped after the paper and final evidence panel are complete.