Runtime and deployment boundaries

The web application owns Astro server output and Wrangler Worker preview/deploy commands. The backoffice owns Laravel and the registry editor; its export writes a local R2-compatible tree before any separate publication step. Rust services read a validated versioned export, not Laravel tables. The CLI consumes local metadata and snapshots, while Docusaurus emits a static build/ directory.

sibyl sync is a separate, explicit boundary: it needs a payload, an HTTPS endpoint, environment authorization, and a confirmed successful response. Local documentation commands never invoke it.

No local build, test, or docs command creates Cloudflare resources, changes DNS, writes a production database, publishes a registry, contacts a remote registry, or calls synchronization services. A passing local build is evidence about the checkout and generated static artifact only.