fix template, remove okr, use casan.*
This commit is contained in:
@@ -1,11 +1,14 @@
|
||||
# BD-MOD-01 OKR Management
|
||||
# Business Design — OKR Web Application
|
||||
|
||||
## Screen Layout
|
||||
- SCR-00 Login: centered sign-in form without sidebar.
|
||||
- SCR-01 Dashboard: fixed sidebar, fixed header, filter bar, OKR list.
|
||||
- SCR-02 Detail: objective overview, tabs, key result list.
|
||||
- SCR-03 Create Objective: title, description, owner, quarter, save.
|
||||
- SCR-04 Key Result Detail: current progress, progress input, comment, save.
|
||||
- SCR-00: Login Screen
|
||||
- SCR-01: Dashboard / OKR List (Left Navigation + List)
|
||||
- SCR-02: OKR Detail Screen
|
||||
- SCR-03: Create / Edit Objective
|
||||
- SCR-04: Key Result Detail / Update
|
||||
|
||||
## User Journeys
|
||||
Each functional requirement must have a normal flow, validation failure, authorization failure where applicable, and observable completion state.
|
||||
|
||||
## API Boundary
|
||||
Frontend calls backend only through src/lib/api.ts and uses cookie/JWT auth.
|
||||
Network and data boundaries must follow docs/technical_architecture.md. UI components may not bypass the approved API client boundary.
|
||||
|
||||
Reference in New Issue
Block a user