docs(sdd): authorize frontend implementation

This commit is contained in:
2026-08-20 19:17:49 +03:30
parent a5173d1601
commit e1e4ed8467
7 changed files with 28 additions and 29 deletions

View File

@@ -1,6 +1,6 @@
# Merchant Dashboard Capability Spec
- Status: Approved product specification — implementation planning authorized; implementation not yet authorized
- Status: Approved product specification — implementation authorized 2026-08-20
- Capability: Merchant dashboard
- Last updated: 2026-08-20

View File

@@ -1,6 +1,6 @@
# Dashboard UX Specification
- Status: Approved UX specification — implementation planning authorized; implementation is not yet authorized
- Status: Approved UX specification — implementation authorized 2026-08-20
- Product: ZarinPal Merchant Analytics hackathon dashboard
- Audience: non-technical Persian-speaking merchants, hackathon judges, finance/legal handoff recipients
- Direction: Persian-first RTL
@@ -8,7 +8,7 @@
## 1. Purpose and authority
This document defines the visible structure, interaction behavior, content rules, responsive layouts, accessibility requirements, and asynchronous states of the merchant analytics dashboard. It is an implementation-neutral UX contract. It does not authorize Svelte components, API clients, backend changes, export endpoints, or deployment work.
This document defines the visible structure, interaction behavior, content rules, responsive layouts, accessibility requirements, and asynchronous states of the merchant analytics dashboard. It is the implementation-neutral UX contract for the authorized frontend task list; backend, API, and deployment ownership boundaries remain unchanged.
The following sources are authoritative, in precedence order:
@@ -769,7 +769,7 @@ Persian digits are applied to rendered variable values. Technical identifiers in
- Screen readers receive page structure, exact KPI meaning, chart alternatives, restrained async status, and associated errors.
- 360/768/1024/1440 px layouts and 320 CSS px reflow preserve core tasks; reduced-motion mode removes nonessential movement.
## 20. Implementation handoff checklist (after approval only)
## 20. Implementation handoff checklist
- Generate transport types only from approved backend `docs/openapi.yaml` version `1.0.0` and fail checks on drift.
- Resolve static adapter/Nginx fallback behavior.
@@ -778,7 +778,7 @@ Persian digits are applied to rendered variable values. Technical identifiers in
- Build contract fixtures containing no sensitive source data, payer tokens, credentials, or peer rows.
- Verify formatting, lint, strict typing, `svelte-check`, unit/component tests, Playwright critical flows, production build, responsive RTL, both themes, accessibility, and reduced motion.
No implementation work begins until the dashboard capability and this UX specification are explicitly approved.
The dashboard capability, this UX specification, plan, and task list were approved for implementation on 2026-08-20.
## 21. Resolved implementation handoff