Skip to main content

Operations

Cross-repo shipping and configuration. Two residents, two jobs:

  • Release policy — the rules every package follows when it ships: semver clock ownership, compatibility lines, what must sync where.
  • Environment variables — the cross-repo env-var matrix: which vars exist, which must pair across repos (e.g. Clerk instance keys).

Per-repo release mechanics (the walkable checklists) live in each repo's docs/release.md. When a production deploy story exists beyond the test stack, its runbooks land here too.