Skip to main content

Production Ownership Boundary

Handoff transfers production operations responsibility, not universal ownership of the system.

Transfers to Anchor After Acceptance​

  • production monitoring
  • production logging access and response
  • production alerting and escalation
  • production backups and restore operations
  • production secrets operations
  • production security visibility and operational controls
  • production incident response coordination
  • production runbook stewardship
  • production runtime administration within the documented ownership model

Stays With the Development Company​

  • application roadmap and feature decisions
  • code authoring and engineering implementation
  • CI pipeline ownership
  • development workflow and branch policy
  • dev and staging environment ownership unless separately agreed
  • development-era tooling such as dev and staging Cloudflare or PostHog when retained during active development

Shared Boundary Areas​

Some areas require explicit coordination:

  • production deployments
  • rollback decisions during code regressions
  • schema or migration changes
  • DNS or edge changes with customer impact
  • changes that alter observability, backup scope, or secrets handling

Runtime Truth​

Production runtime truth belongs to the operational systems used by Anchor, not to a development tracking registry. The handoff package and production runbook must identify where runtime health, alerts, logs, backups, and security signals are actually observed.