Skip to main content

Release And Deployment

Purpose​

  • This page summarizes the maintainer workflow for releasing and deploying Origo-facing changes.

Required reading​

  • docs/Developer/Tests-And-Gates.md
  • docs/deployment-reference.md
  • control-plane/README.md
  • docs-site/CLOUDFLARE.md

Process​

  1. Confirm the touched runtime or docs surface is documented accurately.
  2. Confirm the relevant gates pass.
  3. Confirm any deployment env or schedule contract changes are explicit.
  4. Ship the change through the normal branch, review, and deploy path.

Checklist​

  • Runtime documentation is up to date.
  • Proof or observability obligations are visible where required.
  • Deployment-sensitive environment variables are documented.
  • Control-plane entrypoints and schedules remain aligned with current runtime truth.
  • Docs-site route and Cloudflare Worker settings are aligned with the deployed path.

Failure cases and review notes​

  • Do not treat historical slice closeout notes as release documentation.
  • Do not ship a deployment-affecting change with stale env or schedule docs.
  • docs/Developer/Local-Environment-And-Stack.md
  • docs/Developer/SQL-Migrations.md
  • control-plane/README.md
  • docs-site/CLOUDFLARE.md