cesnimda
6.3 KiB
Phase 3 — UX architecture checkpoint
Based on d6d3dd9, on codex/ui-redesign-phase3, 2026-09-10. This package defines the target architecture; it does not implement it. No application code, routes, styling, APIs, schema, dependencies or CI configuration change in this phase. Phase 4 and B07 have not started. B06 implementation complete; F04 remains open.
Authority and reading order
The product brief, original design direction, Phase 1 full functionality ledger and Phase 2 preservation matrix remain authoritative. This package resolves presentation choices using current source. It never replaces a PRES contract with its shorter summary. Later user instructions govern any conflict with the original illustrative brief.
| Document | Decision it supplies |
|---|---|
| Information architecture | Grouped navigation and where every less-visible capability lives |
| Route plan | All 31 existing patterns, aliases, query/state contracts and staged additions |
| Application shell | Existing shell reuse, account boundaries, headers and navigation behavior |
| Dashboards | Personal layouts, data-qualified widget catalogue and separate aggregate admin |
| Jobs workspace | One table/board workspace, filters, statuses, bulk operations and preview |
| Job workspace | Section ownership and optional guided application journey |
| Career Profile | Canonical editing, extraction review and source propagation |
| CV workspace | Editor/preview, source overrides, advanced controls and history |
| Documents | Federated discovery of existing artifacts and frozen relationships |
| AI interaction | Grounding, explicit review, destination scope and provider failures |
| Commands, notifications and tasks | Contextual commands and distinct task/event/message lifecycles |
| Responsive strategy | Mobile task behavior and density |
| Design system | MUI tokens, states and bounded visual proposals |
| Component architecture | Retain/refactor/consolidate/add map |
| Accessibility | Loaded-state and manual gates before repeating shared defects |
| Preservation impact | All 57 contracts, recommendations and implementation evidence chain |
| Open decisions | Genuine product choices, contradictions and unavailable data |
| Phase 4 plan | Small foundation tickets, dependencies and first slice |
Scope classification
- Existing / preserve: all 57 PRES groups, including advanced CV controls, NAV alerts, correspondence delivery safeguards, owner-bound artifacts, Google/Outlook calendar actions, public CVs, account security and admin operations.
- Existing / improve UX: grouped navigation, one Jobs view switch, clear job sections, source/override labels, coherent document entry, discoverable settings, shared error/focus presentation.
- New: explicitly numbered NEW requirements in Open decisions, such as dashboard layout order/size, broader commands, density, aggregate admin analytics and due-dated tasks. Availability and implementation phases differ; a candidate metric is not an available feature.
- Baseline defects / debt: P2-D01 SQLite package/tailoring failure; F14 loaded accessibility; separate concurrency, idempotency, calendar and paid-lifecycle queues; failed remote CI browser runner; F04 runtime ingress evidence. Do not fix these incidentally or preserve their defective results as desired behavior.
Selected architecture
Retain React Router inside the Next static SPA, MUI/Emotion, the existing auth/private-tree lifecycle and shared Axios client. Reorganize navigation without changing most paths. Keep a full job page and a focused optional read-only preview. Career Profile remains canonical; CV settings override one derived document; job drafts and frozen packages remain separate resources.
Use one main brand hue through semantic light/dark tokens; final identity is undecided. Prefer the current mobile drawer over adding a second navigation system. Personal dashboard customization starts with owner-scoped layout metadata; cross-device persistence needs an explicit choice before implementation. New aggregate admin metrics must be server-computed and privacy-bounded.
Evidence and limits
Source validation includes App/AppShell, route helpers, Jobs/table/board, workspace/asset models, Career/CV owners, analytics controller/service/DTOs, account/provider/notification owners and the Phase 1/2 test evidence. Open decisions records corrections to illustrative requirements and source-backed metric limitations. No user study, fresh visual prototype, provider evaluation or production inspection is claimed.
The unchanged Phase 2 executed baseline is 916 backend and 313 frontend tests passing (Phase 1: 916 / 298). General browser results are 23 actual passes + 1 expected failure, not 24 successful workflows. B04 HTTP 9, B06 native HTTP 6, PDF admission 1 and Compose validation 3 passed. Standalone TypeScript, lint and Release builds passed there. Those are reused results for unchanged application code, not freshly executed Phase 3 suites. Historical TS2571 is corrected; remote CI/production certification remains outstanding.
Completion checks and exact commands are recorded in Phase 4 plan. These check document completeness, source/route/PRES references and documentation-only scope. No visual implementation is approved by a document passing validation.
Next boundary
Recommended first implementation slice: P4-01 semantic state and focus foundation in the existing theme, with loaded regression fixtures. Keep existing brand identity, routes and page composition. Follow the bounded plan and stop for review before expanding to the shell or representative pages. Production release remains separately gated by CI and F04 evidence.