Tutorial · Published 26 August 2026
Deploying a cerilo publishing workspace safely
A production checklist for Name ownership, roles, channels, approvals, budgets, scheduler tests, receipts, and handback.
Establish the Name and roles
Verify domain ownership, name the registrant, set owner/editor/guest roles, and record who may approve external publishing and deal actions.
Start with a disposable or low-impact channel while the workflow is proven.
Connect one channel
Store provider tokens in the governed vault, request the minimum scopes, create a test draft, and approve the exact revision.
Revoke the token after the test and prove the adapter fails visibly without losing the scheduled job.
Exercise scheduler failure
Race two workers, inject a timeout, return a rate limit, crash after provider acceptance, and retry. Confirm one logical publication and a durable receipt or reconciliation state.
Inspect workspace isolation throughout.
Prove export and handback
Export Nameplate, site content, posts, deals, receipts, and channel configuration without raw secrets. Rehearse domain transfer and account closure as far as current capability permits.
Any pre-launch or externally blocked step remains an explicit action, not a checked box.
Production checklist
- Verify Domain-first ownership against the deployed environment, not a screenshot.
- Verify Receipts for effects against the deployed environment, not a screenshot.
- Verify Transactional AI budget against the deployed environment, not a screenshot.
- Verify Truthful capability state against the deployed environment, not a screenshot.