Responsibilities Matrix

Responsibility	Development Company	Anchor	Notes / Boundary
Code changes	Owns	Informed	Engineering changes originate with the development company unless separately staffed.
Release contents	Owns	Reviews operational impact	The development company defines what ships; Anchor reviews production readiness.
Production deployment execution	Supports	Owns after handoff	Anchor governs production rollout procedure for accepted systems.
Dev and staging pipelines	Owns	Not default owner	Anchor does not automatically take over non-production pipelines.
Production monitoring	Provides requirements during handoff	Owns after handoff	Anchor owns production visibility and alert coverage.
Production logging	Ensures logs are usable	Owns operational access and response	Structured logs are required before handoff.
Alert routing	Provides signal expectations	Owns routing and escalation	Anchor owns production alert delivery and escalation logic.
Backups	Documents requirements	Owns production backup operations	Applies to stateful systems after acceptance.
Secrets operations	Documents application needs	Owns production secrets operations	Production secrets governance shifts to Anchor after handoff.
Security visibility	Discloses system risks and controls	Owns production security visibility	Anchor owns operational monitoring and response posture.
Incident response	Supports engineering diagnosis and fixes	Owns production incident process	Anchor coordinates production response; the development company supports code-level remediation.
Runbooks	Must produce initial runbook	Owns operational stewardship after acceptance	Runbook must exist before handoff.
DNS and Cloudflare placement	Documents required model	Owns or administers production according to documented model	Client-owned zones with delegated access are acceptable if documented.
Ownership and escalation mapping	Must provide	Owns production escalation path after acceptance	Handoff package must identify both sides.