DC-345 · Service responsibility

Service Ownership Map

Know who owns the major platform surfaces, who backs them up, where the runbook lives, which dashboard to open, and how escalation should move if the first operator is unavailable.

Incident Center Jump to map
Ownership posture

Primary owner, fallback owner, escalation path

Directory live

This surface is meant for active command and clean handoffs. If a service is involved in the incident, the card tells you who should own it, who can step in, and which operational surface is the fastest route to evidence.

Service lanes—Core operator-owned services represented
Primary owners—Named first-call owners across the map
Fallback coverage—Every listed service has an explicit backup owner
Dashboards linked—Fast evidence surfaces linked directly from the map
Filters

Find an owner by service or domain

0 matches
Customer path owners—

Auth, edge, and API lanes that directly alter user-facing posture.

Platform data owners—

State, recovery, and persistence lanes with heavier blast radius during failure.

Comms + fleet owners—

Operator paging, delivery posture, and fleet freshness ownership.

Duck Control · service ownership map · owners, backups, runbooks, dashboards, escalation DC-345 local build