DCP READ-ONLY: CONNECTED DEVELOPMENT / UI PREVIEW DCP BATCH 5/6 SOAK IN PROGRESS TELEMETRY: UNKNOWN COMMAND EXECUTION LOCKED
Internal Backup Dashboard
Product data source: MOCK STATIC UNKNOWN· MOCK = example fixture · STATIC = documented/committed template · UNKNOWN = no evidence. UNKNOWN is never shown as PASS.
MOCK EXAMPLE · development-only product-planning data. No production project, no live backend, no execution, no mutation endpoint. Genuine local artifacts are marked STATIC; example fixtures are marked MOCK.
- Slug
- internal-backup-dashboard
- Stage
- OWNER_DECISION
- PRD gate
- NEEDS_OWNER_DECISION
- Build readiness
- 5/13 VERIFIED
Idea Brief — IDEA-002
- Title
- Internal Backup Dashboard
- Status
- DISCOVERY
- Owner intent
- Ari wants a dashboard to see backup status at a glance.
- Problem
- Backup status is spread across files and not visible in one place.
- Who is affected
- Ari (Owner), DevOps
- Desired outcome
- One page showing backup freshness and last restore test.
- Why now
- Backups will become more important once the timer is enabled.
- Existing solution
- The AI Company Portal already shows a DR Scoreboard and Backup Freshness widgets.
- Initial scope
- Show backup status
- Show last restore test
- Potential MVP
- Extend the existing portal DR Scoreboard
Constraints
- No production deploy from planning
- Read-only display
Assumptions
- The existing portal can be extended.
Open questions
- Does the existing portal lack any dashboard field?
Kill criteria
| ID | Criterion | Outcome | Evidence | Owner decision |
|---|---|---|---|---|
| K-001 | existing system solves >= 80% of the need | TRIGGERED | Portal already has a DR Scoreboard + Backup Freshness widgets. | OWNER DECISION REQUIRED |
| K-010 | idea duplicates existing capability | TRIGGERED | Backup Dashboard duplicates Portal capability. | OWNER DECISION REQUIRED |
PRD — PRD-002
- Title
- Internal Backup Dashboard
- Status
- CRITIC_REVIEW
- Executive summary
- A dashboard to show backup status.
- Problem statement
- Backup status is not visible in one place.
- Business objective
- Make backup freshness visible.
Users / Personas
- Ari (Owner) — Check backup freshness
- DevOps — Check restore readiness
Scope
- Show backup status
- Show last restore test
Non-scope (must not leak into tasks)
- Mutations
- Backup execution
MVP
- Extend the portal DR Scoreboard
Later phases
noneFunctional Requirements
| ID | Class | Statement | Status | Source |
|---|---|---|---|---|
| no items recorded — UNKNOWN, not PASS | ||||
Non-Functional Requirements
| ID | Class | Statement | Status | Source |
|---|---|---|---|---|
| no items recorded — UNKNOWN, not PASS | ||||
Security Requirements
| ID | Class | Statement | Status | Source |
|---|---|---|---|---|
| no items recorded — UNKNOWN, not PASS | ||||
Data Requirements
| ID | Class | Statement | Status | Source |
|---|---|---|---|---|
| no items recorded — UNKNOWN, not PASS | ||||
API / Integration Requirements
| ID | Class | Statement | Status | Source |
|---|---|---|---|---|
| no items recorded — UNKNOWN, not PASS | ||||
Dependencies
| ID | Class | Statement | Status | Source |
|---|---|---|---|---|
| no items recorded — UNKNOWN, not PASS | ||||
Risks
| ID | Class | Statement | Status | Source |
|---|---|---|---|---|
| no items recorded — UNKNOWN, not PASS | ||||
Assumptions (never auto-requirements)
| ID | Class | Statement | Status | Source |
|---|---|---|---|---|
| A-001 | ASSUMPTION | The existing portal can be extended. | PROPOSED | MOCK |
Open Questions (stay open until answered)
| ID | Class | Statement | Status | Source |
|---|---|---|---|---|
| Q-001 | OPEN_QUESTION | Does the existing portal lack any required field? | OPEN | MOCK |
User stories
- As a owner, I want see backup status, so that I know backups are fresh.
Acceptance criteria
- AC-001: Backup freshness is visible on the portal [testable]
Definition of Done
- Backup freshness visible in the portal
Milestones
- M1: Extend portal — Add any missing field
Initial test scenarios
- Portal shows backup freshness
Kill criteria
| ID | Criterion | Outcome | Evidence | Owner decision |
|---|---|---|---|---|
| K-001 | existing system solves >= 80% of the need | TRIGGERED | Portal already shows a DR Scoreboard. | OWNER DECISION REQUIRED |
| K-010 | idea duplicates existing capability | TRIGGERED | Duplicate of portal capability. | OWNER DECISION REQUIRED |
Product Critic Review — CR-002
Product data source: MOCK STATIC UNKNOWN· MOCK = example fixture · STATIC = documented/committed template · UNKNOWN = no evidence. UNKNOWN is never shown as PASS.
MOCK EXAMPLE · development-only product-planning data. No production project, no live backend, no execution, no mutation endpoint. Genuine local artifacts are marked STATIC; example fixtures are marked MOCK.
- Recommendation
- NEEDS_OWNER_DECISION
- Summary
- The existing AI Company Portal already provides a DR Scoreboard and Backup Freshness. Prefer extending the portal over creating another application.
- Value challenge
- Value is low if the portal already shows this.
- Scope challenge
- A whole new app is unnecessary for a display need.
- Architecture challenge
- No new service or database.
- Operations challenge
- A second app adds operational burden.
- Security challenge
- Reuse the portal's existing read-only boundary.
- Dependency review
- Depends on portal telemetry, already present.
- Acceptance-criteria review
- Criteria testable.
- MVP review
- Smallest MVP = extend the portal; no new app.
Blocking issues
- possible duplicate capability — Plan may duplicate an existing capability. Recommend reuse before build; owner decision required.
Non-blocking issues
- hidden operational burden — Plan implies ongoing operations (availability/backup/restore). Ensure backup/restore and rollback are in scope.
Reuse opportunities
- Extend the existing AI Company Portal.
- Reuse the DR Scoreboard + Backup Freshness widgets.
Missing owner decisions
- OD-001
Proposed changes (traceable; never overwrite the original)
no proposed changesPRD Gate
| Gate | Result | Detail |
|---|---|---|
| G1 PROBLEM_CLEAR | PASS | problem statement present |
| G2 USER_CLEAR | PASS | users identified |
| G3 OBJECTIVE_CLEAR | PASS | objective present |
| G4 SCOPE_CLEAR | PASS | scope defined |
| G5 NON_SCOPE_CLEAR | PASS | non-scope defined |
| G6 OWNER_DECISIONS_COMPLETE | FAIL | 1 owner decision(s) unresolved; 0 blocking item(s) |
| G7 ACCEPTANCE_CRITERIA_TESTABLE | PASS | all acceptance criteria testable |
| G8 MVP_SMALL_ENOUGH | PASS | MVP judged small enough |
| G9 DEPENDENCIES_IDENTIFIED | WARNING | no dependencies documented |
| G10 RISKS_IDENTIFIED | WARNING | no risks documented |
| G11 SECURITY_CONSIDERED | WARNING | no security requirements documented |
| G12 KILL_CRITERIA_CLEAR | FAIL | 2 kill criterion triggered |
| G13 CRITIC_REVIEW_COMPLETE | FAIL | critic review has blocking issues |
| G14 TECHNICAL_HANDOFF_READY | UNKNOWN | technical handoff readiness UNKNOWN |
Build Readiness
Build Readiness
5/13 VERIFIED
VERIFIED only · UNKNOWN is never a pass
Problem
VERIFIED
Users
VERIFIED
Scope
VERIFIED
Requirements
WARNING · 0 confirmed requirement(s)
Acceptance Criteria
VERIFIED · all testable
Dependencies
WARNING
Risks
WARNING
Security
WARNING
MVP
VERIFIED
Owner Decisions
BLOCKED · unresolved owner decision
Critic Review
BLOCKED · blocking issue
Kill Criteria
BLOCKED · criterion triggered
Technical Handoff
UNKNOWN
Blockers
- Owner Decisions — unresolved owner decision
- Critic Review — blocking issue
- Kill Criteria — criterion triggered
Warnings
- Requirements — 0 confirmed requirement(s)
- Dependencies — warning
- Risks — warning
- Security — warning
Unknown
- Technical Handoff — unknown
Owner Decisions
OD-001 · UNANSWERED
- Question
- Extend the existing AI Company Portal or build a new application?
- Why it matters
- Building a new application duplicates an existing capability.
- Options
- Extend the portal — Reuse existing UI, no duplicate app.
- New application — Duplicated effort and operations.
- Product Architect recommendation
- Extend the existing portal.
- Product Critic view
- Extend the portal — the need is largely solved.
No technical handoff. A handoff is only created after PRD approval.