DCP READ-ONLY: CONNECTED DEVELOPMENT / UI PREVIEW DCP BATCH 5/6 SOAK IN PROGRESS TELEMETRY: UNKNOWN COMMAND EXECUTION LOCKED
Service · DCP
Data provenance: REAL MOCK STATIC CONFIG UNKNOWN· REAL = live read-only DCP · MOCK = demo, never production truth · STATIC CONFIG = documented defaults · UNKNOWN = not safely queryable
Read-only service detail. Ownership is a STATIC role model; dependencies come from the documented map; the runbook score is documentation completeness, NOT service health.
Ownership (roles, not people)
- Technical owner
- Developer
- Operational owner
- DevOps
- Approval owner
- Ari
- Recovery owner
- DevOps
- Review owner
- Security
- Sensitive
- yes
- Source
- STATIC CONFIG
Dependencies
The task/policy/audit control plane and its dashboard stop; dependent automation loses its control plane.
Depends on: postgres, tailscale · blast radius
Runbook completeness · DCP
Batch 5/6 production; soak pending.
| Dimension | State | Evidence |
|---|---|---|
| health check documented | YES | Compose healthcheck + read-only /health documented. |
| backup documented | NO | No real backup run; timer disabled. Documented intent only. |
| restore documented | UNKNOWN | Restore drill designed (AUTOMATED-RESTORE-DRILL.md) but not run. |
| rollback documented | YES | Revert DCP_IMAGE_TAG to the prior SHA (docs/PRODUCTION-DEPLOYMENT.md). |
| monitoring documented | NO | Monitoring design present; no verified alert delivery. |
| owner documented | YES | service-owners.json: auth/operational/recovery roles assigned. |
| dependencies documented | YES | SERVICE-DEPENDENCY-MAP.md documents DCP -> PostgreSQL and edges. |
| incident guidance documented | YES | INCIDENT-MODEL.md + Recovery Wizard scenario for DCP unhealthy. |
Only YES counts in the numerator; NOT_APPLICABLE is excluded from the denominator; UNKNOWN is never counted as YES. This is documentation completeness, separate from the Reliability score.