docs(spec): approve dashboard planning gate
This commit is contained in:
@@ -1,10 +1,10 @@
|
||||
# Merchant Dashboard Capability Spec
|
||||
|
||||
- Status: Draft — not approved for implementation
|
||||
- Status: Approved product specification — implementation planning authorized; implementation not yet authorized
|
||||
- Capability: Merchant dashboard
|
||||
- Last updated: 2026-08-20
|
||||
|
||||
Detailed screen-level behavior, representative layouts, content, accessibility, partial-delivery states, and export workflows are specified in [`DASHBOARD-UX-SPEC.md`](DASHBOARD-UX-SPEC.md). Both documents require explicit approval before implementation planning.
|
||||
Detailed screen-level behavior, representative layouts, content, accessibility, partial-delivery states, and export workflows are specified in [`DASHBOARD-UX-SPEC.md`](DASHBOARD-UX-SPEC.md). Both specifications are approved for implementation planning; implementation still requires approval of the plan, task list, and applicable interface contracts.
|
||||
|
||||
## Objective
|
||||
|
||||
@@ -103,4 +103,4 @@ Still required before implementation:
|
||||
- Approved machine-readable analytics, identity, detail, SSE, error, and CSV export interface contracts.
|
||||
- Product/interface approval for the exact CSV schema, encoding, filename, row cap, delivery, retention, and audit behavior.
|
||||
- Static adapter fallback/routing behavior under the final Nginx configuration.
|
||||
- Explicit approval of this capability spec and `DASHBOARD-UX-SPEC.md`.
|
||||
- Approved Phase 2 implementation plan and Phase 3 task list.
|
||||
|
||||
Reference in New Issue
Block a user