TenantAtlas/docs/ui-ux-enterprise-audit/design-coverage-matrix.md

Design Coverage Matrix

Source of truth: route-inventory.md as of Spec 323. Counts are inventory rows unless explicitly marked as unique files or unique reports.

Summary

Metric	Count	Notes
UI route/page inventory rows	99	Includes dynamic route families and utility/auth endpoints.
Unique page reports	20	page-reports/*.md; some inventory rows intentionally share existing reports where routes resolve to the same surface.
Desktop screenshots	16	Route-inventory-linked desktop evidence, including strategic runtime captures, blocker evidence screenshots, and the Spec 366 rendered-report capture.
Tablet screenshots	0	Deferred to later strategic mockup/implementation specs.
Mobile screenshots	1	Spec 366 adds mobile-ish rendered-report evidence for the customer technical profile; broader mobile coverage remains deferred.
Strategic Surface rows	45	Individual target treatment or explicit product decision required.
Domain Pattern Surface rows	45	Can be handled through grouped pattern specs unless later evidence raises risk.
Design-System Cleanup Surface rows	7	Tables/forms/states/copy cleanup, no individual target mockup expected by default.
Internal / Deprecated / Hidden rows	1	Local-only smoke login routes.
Manual Review Required rows	1	File-discovered break-glass page without confirmed route.
High-priority unresolved/manual-review entries	28	Recorded in unresolved-pages.md.

Spec 325 Target Image Coverage

Spec 325 adds target-image and target-brief coverage for 9 selected P0/P1 strategic surface groups. This is documentation and visual direction only. Runtime implemented remains No.

Metric	Count	Notes
Selected target surface groups	9	Proportional shortlist from 44 strategic rows.
Target experience briefs	9	Stored in target-experience-briefs/.
Target image sidecars	9	Stored in target-images/target/.
Dark target PNGs	9	1600 x 900 PNG files.
Light target PNGs	9	1600 x 900 PNG files for review/customer/auditor/management-safe variants and consistency.
Premium visual reference images	4	User-accepted calibration images stored in target-images/reference/spec-325-premium-reference/.
Runtime UI implemented	0	Spec 325 does not change product runtime surfaces.

Selected surface group	Source row(s)	Target brief	Runtime implemented
Workspace Overview	UI-001, UI-002	target-experience-briefs/workspace-overview.md	No
Environment Dashboard	UI-011	target-experience-briefs/environment-dashboard.md	No
Operations Hub	UI-016	target-experience-briefs/operations-hub.md	No
Governance Inbox	UI-028	target-experience-briefs/governance-inbox.md	No
Customer Review Workspace	UI-038	target-experience-briefs/customer-review-workspace.md	No
Audit Log	UI-025	target-experience-briefs/audit-log.md	No
Restore Safety Workflow	UI-053, UI-054	target-experience-briefs/restore-safety-workflow.md	No
Provider Readiness	UI-072, UI-073	target-experience-briefs/provider-readiness.md	No
Baseline Compare / Drift	UI-061	target-experience-briefs/baseline-compare-drift.md	No

Coverage By Area

Area	Rows	Coverage Notes
Platform/system	14	Route-discovered; not browser-reviewed in Spec 323 because system auth/capability state needs separate fixture.
Governance	12	Strong browser coverage for inbox, decisions, exceptions, baselines; detail/diff routes remain unresolved.
Monitoring	9	Operations hub and alert delivery landing captured; record details and config forms remain pattern/manual review.
Inventory	8	Route-discovered only; coverage, policy version detail, and raw-data exposure need later review.
Evidence / audit	8	Audit log captured; evidence/report detail routes need customer-safe progressive-disclosure review.
Reviews	7	Review register, customer workspace, review pack detail, and the rendered-report route now have bounded browser evidence; Spec 366 adds rendered-report profile, print, and mobile-ish captures while deeper evidence/report surfaces still remain open elsewhere.
Backup / restore	6	High-risk area; Spec 371 adds seeded browser proof for Backup Sets list/detail, while restore runs and create/failure workflow states remain unresolved.
Settings / admin	5	Workspace and environment access are RBAC-sensitive and need later review.
Provider / integration	5	Provider connections and required permissions are captured; create/edit/onboarding remain high-risk unresolved surfaces.
Findings	5	Queue/inbox patterns captured; finding detail needs individual triage target.
Auth/access	4	Mostly flow/guard surfaces; copy and denial states should be pattern-reviewed.
App shell	4	Workspace overview captured; chooser/context routes need domain pattern pass.
Workspace / environment	2	Environment dashboard captured; managed-environments landing now has a runtime report.
Utility	2	Non-product endpoints; design-system cleanup only.
Support	2	Diagnostics/support surfaces should stay secondary to operator workflows.
Provider / onboarding	2	Wizard and draft states require later target treatment.
Directory	2	Provider-bound directory cache pages; likely pattern covered.
Public	1	Welcome route; not a product admin surface.
Customer review	1	Captured; highest customer-safe language priority.

Coverage By Primary Archetype

Primary Archetype	Rows	Design Implication
Settings / Admin	13	RBAC, entitlement, lifecycle, and dangerous setting changes need confirmation and authorization review.
Evidence / Audit	10	Must keep proof, timestamps, source, and raw details clearly separated.
Operations / Monitoring	9	Needs consistent run status, retry/rerun semantics, and diagnostic hierarchy.
Inventory	8	Needs raw provider payload disclosure rules and confidence/status language.
Drift / Diff	8	Needs assignment, comparison, snapshot, and evidence-gap hierarchy.
Provider / Integration	7	Consent, credentials, permissions, and disconnect states require high trust clarity.
Reviews	7	Customer/auditor language, export context, and proof links are central.
Findings / Inbox	6	Needs triage, owner, SLA, exception, and close-state clarity.
Backup / Restore	6	Highest safety burden: dry-run, confirmation, audit, and restore-point truth.
Auth / Access	6	Guard, denial, external auth, and smoke/local flows should stay explicit.
Support / Diagnostics	5	Should not compete with product decision surfaces.
Overview / Dashboard	4	Must prioritize one or two decision paths over raw status.
Exceptions / Accepted Risk	4	Needs accepted-risk language, expiration, approver, and audit continuity.
Workspace / Tenant Context	3	Context must be visible and unambiguous before scoped actions.
Utility / Internal	2	Keep hidden/internal unless deliberately productized.
Customer Workspace	1	Requires customer-safe first-read treatment.

Coverage By Design Depth

Design Depth	Rows	Gate Treatment
Strategic Surface	45	Requires individual target artifact or explicit product decision before substantive UI implementation.
Domain Pattern Surface	45	Can be handled by grouped pattern specs and shared components.
Design-System Cleanup Surface	7	Table/form/action/state cleanup can be folded into implementation waves.
Manual Review Required	1	Must not be treated as product-ready until route/auth state is confirmed.
Internal / Deprecated / Hidden	1	Local-only/testing; keep out of customer-facing design claims.

Missing Or Unclear Coverage

The largest open gaps are strategic detail/workflow surfaces, system-plane routes, and high-risk restore/backup flows that need seeded capability states. unresolved-pages.md records 28 high-priority entries.

Tablet and mobile coverage is intentionally absent from this baseline. Later target specs should add responsive evidence for the app shell, workspace overview, environment dashboard, customer review workspace, governance inbox, operations, evidence, backup/restore, and critical forms.

Recommended Next Specs

1. P0 enterprise shell and workspace/environment decision hierarchy: app shell, workspace overview, environment dashboard, navigation/context.
2. P0 governance and customer review workspace: governance inbox, decision register, exceptions queue, customer review workspace, review register.
3. P0 backup/restore and evidence safety: backup sets, restore runs, backup schedules, review packs, audit/evidence exports.
4. P1 provider/onboarding and access: provider connections, consent/onboarding, environment access scopes, workspace administration.
5. P1 drift/diff and inventory: baseline compare, baseline matrix, policy version detail, inventory coverage.
6. P2 system-plane controls: system dashboard, operational controls, system operation detail, access logs, repair workspace owners.

Update Rule

Future feature work must update this matrix whenever route-inventory.md changes. Add the new row count, adjust area/archetype/depth totals, link any screenshots or reports, and add unresolved entries when browser review is blocked.