DCP READ-ONLY: CONNECTED DEVELOPMENT / UI PREVIEW DCP BATCH 5/6 SOAK IN PROGRESS TELEMETRY: UNKNOWN COMMAND EXECUTION LOCKED
Service · PostgreSQL
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
DCP task/policy/audit state and n8n data become unavailable; no published ports, private network only.
Depends on: — · blast radius
Runbook completeness · PostgreSQL
| Dimension | State | Evidence |
|---|---|---|
| health check documented | YES | Reported via DCP /health database field (read-only). |
| backup documented | NO | First real dump not run; evidence UNKNOWN. |
| restore documented | UNKNOWN | Disposable restore drill designed but never executed. |
| rollback documented | YES | Restore from verified backup and/or revert DCP image; additive-only. |
| monitoring documented | NO | Only the DCP /health database check documented; no dedicated probe. |
| owner documented | YES | service-owners.json: Developer/DevOps/Ari/Security roles assigned. |
| dependencies documented | YES | Dependency map documents PostgreSQL as a hard DATABASE dependency. |
| incident guidance documented | YES | Recovery Wizard scenario for PostgreSQL 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.