Frontend Implementation Status Matrix

Evalium frontend implementation tracker.

This document is separate from:

docs/product/implementation-status-feature-matrix.md (platform/backend maturity)
docs/ux/UX-COMPONENT-COVERAGE-MATRIX.md (UX-spec coverage quality)

Purpose:

track frontend build state per surface
make dependencies explicit (backend readiness, UX contract, shared primitives)
track accessibility/mobile/readiness gates before feature rollout

Status Definitions

Not Started: no production frontend implementation
In Progress: active implementation work, not yet release-ready
Blocked: implementation cannot proceed due to prerequisite gaps
Partial: implemented in limited scope/feature-flag/prototype only
Implemented: production-ready baseline implemented

Beta planning labels used in the matrix:

Required: must be implemented before frontend beta launch
Required (baseline slice): minimum viable slice required for beta; advanced scope can follow
Required (monitor baseline): read/monitor baseline required for beta; advanced controls can follow
Deferred: intentionally scheduled for post-beta

Matrix

Surface	Frontend Status	Priority	Backend Contract	UX Spec Coverage	Shared Primitives Dependency	Accessibility Gate	Mobile/Task-Tier Gate	Beta Gate	Post-Beta	Notes	Next Gate
Shared App Shell + Primitives (`EntityLink`, Drawer, Hub, Table, StatusChip)	In Progress	P0	Implemented	Full	N/A	In Progress	Not Started	Required	Scale polish and performance tuning	Baseline primitives exist in `frontend/src/lib/components/shared` (`EntityLink`, `DrawerCoordinator` + shell, `StandardHub`, `StandardTable`, `StatusChip`). Production drawer-peek wiring is currently focused on `/questions`; broader surfaces are pending the same shell/drawer rollout. Release-gate component checks are codified in `.github/workflows/frontend-a11y-gate.yml` (`check`, `lint`, `test`, `build`, Playwright CT). Canonical entity routes resolve to `/questions/:id`, `/evaluations/:id`, `/assignments/:id`, `/users/:id`, `/groups/:id`, `/taxonomy/terms/:id`.	Roll drawer-peek/read-model wiring beyond `/questions` and keep release-gate component a11y evidence green in CI
Frontend Contract Layer (API wrapper, CSRF/idempotency/error/status/i18n resolver)	In Progress	P0	Implemented	Full	N/A	Not Started	N/A	Required	Advanced telemetry/error analytics	Shared contract module now includes CSRF token sourcing, OpenAPI idempotency-intent mapping, and targeted wrappers for authoring, support entities, roles governance (`/api/roles`), and auth session administration (`/api/auth/sessions`) used by drawers and admin pages.	Add backend-integrated tests for idempotency/CSRF/error semantics and migrate remaining mutating surfaces to the shared contract path
authoring: Questions	Partial	P0	Implemented	Full	Implemented (baseline shell/link usage)	In Progress	Partial	Required	Advanced authoring assists	Questions is currently the only production surface with the end-to-end inventory + read-only drawer-peek pattern. Canonical detail route and publish actions are live through shared contract wrappers, but full editor + publish-impact/ATAG workflow remains pending.	Implement question editor + publish-impact workflow and then replicate the drawer-peek shell pattern on subsequent authoring surfaces
authoring: Evaluations/Sections/Buckets	Partial	P0	Implemented	Partial	Implemented (baseline shell/link usage)	In Progress	Partial	Required (baseline slice)	Advanced builder ergonomics	Evaluations inventory list/create baseline and canonical detail route are live; detail now exposes version history with create/publish controls, but sections/buckets builder workflow is not started.	Build sections/buckets authoring baseline + validation sidekick and publish-impact controls
authoring: Passages	Not Started	P1	Implemented	Full	Blocked (pending shell primitives)	Not Started	Partial	Deferred	Full passage management rollout	API-ready; should follow question/evaluation patterns	Implement list/detail/editor + linking workflows
Assignments & Schedules	Partial	P0	Implemented (partial workflow nuances)	Partial	Implemented (baseline shell/link usage)	Not Started	Partial	Required	Advanced scheduling workflows	Assignment monitor list/detail baseline is live with canonical monitor status chips and entity links; issue wizard + scheduling mutation flows are still missing.	Build issue wizard + schedule create/edit baseline with contract-layer mutation semantics
Operations Command Centre	Not Started	P1	Implemented (proctor command endpoints pending)	Full	Blocked (pending shell primitives)	Not Started	Partial	Required (monitor baseline)	Live-control and high-scale ops enhancements	Live monitor should be manual-refresh first	Implement monitor read surfaces and capability-gated actions
Runtime Candidate Delivery	Not Started	P0	Implemented	Full	Partial (shared shell not mandatory but shared status/error contract needed)	Not Started	Not Started	Required	Field resilience mode + deeper offline capabilities	Candidate-facing criticality is highest; release-gate accessibility required	Implement launch -> answer -> submit baseline with resilience
Review & Approval Workspace	Not Started	P1	Implemented	Full	Blocked (pending shell primitives)	Not Started	Partial	Required	Richer decision support panels	Defensibility exceptions/triage already backend-live	Build queue + decision drawers + evidence panels
Insights (Readiness, Reporting, Remediation)	Not Started	P1	Implemented (skills parked)	Partial	Blocked (pending shell primitives)	Not Started	Partial	Required (readiness/exceptions slice)	Expanded analytics and explainability surfaces	Must enforce explain links, scope chips, freshness states	Build submission/readiness/reporting baseline
Glass Box (External Read-Only)	Not Started	P1	Implemented	Full	Partial (separate minimal shell)	Not Started	Partial	Deferred	Full external visibility rollout	Link-principal redaction behavior must be explicit in UI	Implement four lens pages with read-only contract
Identity & Access (Users/Groups/Roles/Sessions)	In Progress	P1	Implemented	Full	Implemented (baseline shell/link usage)	Not Started	Partial	Required (targeting baseline)	Complete admin governance features	Users list/detail baseline is architecture-aligned (shared hub/table/link/drawer contract + user status chips); groups list/detail baseline is live on shared primitives; roles and sign-in security administration baselines are now live at `/roles` and `/sign-in-security` with capability grouping, role create/update/clone/assign/unassign/delete, user-role binding lookup, and session revoke/revoke-others actions via contract wrappers.	Add explicit confirmation/reason flow for high-trust actions and stronger mobile task-tier UX for admin actions
Content Packs	Not Started	P1	Implemented	Full	Blocked (pending shell primitives)	Not Started	Partial	Deferred	Full packs authoring/distribution workflow	Lineage endpoint is backend-live and should be surfaced early	Build pack list/detail/publish/install/lineage
Claims & Disputes	Not Started	P2	Implemented (workflow partial)	Full	Blocked (pending shell primitives)	Not Started	Partial	Deferred	Full legal workflow activation	Frontend not yet activated	Implement list/detail/event/ratify workflows
Compliance Centre (Jobs/Ledger + Case target-state)	Not Started	P1	Partial (case orchestration pending)	Partial	Blocked (pending shell primitives)	Not Started	Partial	Deferred	Case orchestration timeline and legal review workflow	Start with jobs/ledger first-class screens; case timeline remains target-state	Implement v1 jobs/ledger UX + clear target-state gating
Audit & Ledger Explorer	Not Started	P2	Partial (federated read, no unified endpoint)	Full	Blocked (pending shell primitives)	Not Started	Partial	Deferred	Unified ledger exploration and advanced filters	Explorer can launch with federated tabs first	Implement tabbed explorer + deep links
Taxonomy Admin and Skills-Adjacent UX	Not Started	P2	Partial (skills inference parked)	Partial	Blocked (pending shell primitives)	Not Started	Partial	Deferred	Skills inference and advanced taxonomy management	Content-domain taxonomy is backend-live; skills/admin surfaces depend on parked capabilities	Implement content taxonomy admin slice

Readiness Rollup

Use this matrix with:

docs/ux/UX-FRONTEND-READINESS-CHECKLIST.md (P0/P1/P2 readiness gates)
docs/ux/UX-ACCESSIBILITY-STANDARDS-AND-GUARDRAILS.md (WCAG 2.2 AA + ATAG responsibilities)
docs/ux/UX-MOBILE-AND-TASK-TIER-POLICY.md (mobile/desktop task policy)

Rollup guidance:

Do not mark a surface Implemented unless the corresponding readiness and accessibility gates are PASS.
Candidate delivery requires stricter release-gate evidence than admin-only surfaces.

Recommended Build Order

Frontend contract layer (API wrapper, CSRF, idempotency, error/status/i18n mapping).
Shared app primitives (EntityLink, drawer coordinator, hub/table shells, canonical status chips).
Minimal end-to-end authoring path (Questions + basic Evaluations publish flow).
Identity core required for operations targeting (Users/Groups basics).
Assignments and monitor baseline (issue + canonical status buckets).
Runtime candidate delivery baseline (start -> answer -> submit) with strict accessibility/resilience gates.
Review and approval workspace (decisions, evidence panels, defensibility triage).
Insights baseline (readiness, exceptions, reporting blocks + explain links).
Glass Box and Content Packs (external read-only visibility + lineage/install workflows).
Claims/Disputes, Compliance case orchestration UX, Audit Explorer, and advanced taxonomy/skills-adjacent UX.

Rule:

If a step depends on unresolved P0 gate items, it remains blocked regardless of feature urgency.

Strategic Differentiator Backlog (Post-Baseline)

Use these as deliberate "UX advantage" tracks once baseline surfaces are stable.

Differentiator	Value	Dependencies	Suggested Start
Field Resilience Mode (candidate + field operator)	Reduces failure risk in low-connectivity environments with explicit sync/retry/recovery UX	Runtime baseline, autosave contracts, deterministic submit states	After runtime baseline is `Implemented`
Defensibility Copilot Panels (reason -> action guidance)	Converts readiness/KOE reason codes into immediate, unambiguous next actions for operators	Review workspace + insights baseline + reason-code dictionaries	After review workspace is `Partial`
Progressive Complexity UI (Quick vs Advanced flows)	Keeps mobile/simple tasks fast while preserving expert controls for complex workflows	Shared shell primitives + task-tier policy + role/capability checks	After authoring + assignments are `Partial`
Translation Override Workspace (org > tenant > product)	Makes language customisation operational without code deployments; aligns with i18n-first architecture	Frontend contract layer + i18n resolver + capability controls + audit events	After shared shell + identity surfaces are `Implemented`
Exception Noise Controls (digest, suppression hygiene, SLA views)	Prevents command centres from becoming high-volume noise streams and improves actionability	Defensibility queue surfaces + triage state + telemetry	After operations and insights baselines are `Partial`

Execution rule:

Do not start these tracks before all P0 readiness gates are PASS.

Maintenance Rule

Update this file whenever:

a frontend surface status changes
a dependency unblocks/blocks implementation
readiness/a11y/mobile gate outcomes change
a surface moves from target-state to active implementation

Status Definitions​

Matrix​

Readiness Rollup​

Recommended Build Order​

Strategic Differentiator Backlog (Post-Baseline)​

Maintenance Rule​