TenantAtlas/docs/ui-ux-enterprise-audit/target-images/reference/spec-325-premium-reference/README.md
ahmido 3eff4d8579 Spec 325: add screenshot-anchored strategic target images (#385)
## Summary
- add the Spec 325 artifacts for screenshot-anchored strategic target images
- update the UI/UX enterprise audit documents to capture strategic surfaces and grouped follow-up candidates
- add supporting follow-up specs, target experience briefs, and target image assets for the audit workflow

## Testing
- not run (documentation/spec artifact changes only)

Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de>
Reviewed-on: #385
2026-05-18 07:18:13 +00:00

41 lines
2.1 KiB
Markdown

# Spec 325 Premium Visual Reference Set
These four images are user-accepted premium visual references for the Spec 325 target-image direction.
They are visual calibration references only. They are not repo-real product screenshots, not implementation truth, and not evidence that the shown metrics, actions, labels, dates, entities, or workflow states exist in the application.
## Reference Images
| Reference | File | Intended calibration use |
| --- | --- | --- |
| Platform Overview | `platform-overview-premium-reference.png` | Premium shell, dense dashboard composition, sidebar/topbar rhythm, overview cards. |
| Governance Inbox | `governance-inbox-premium-reference.png` | Decision workbench, table/detail split, severity filters, right-side drawer. |
| Backup & Restore | `backup-restore-premium-reference.png` | Backup/restore domain density, service-health tables, restore-plan detail panel. |
| Evidence & Audit | `evidence-audit-premium-reference.png` | Evidence/audit proof surfaces, tabs, audit timeline, proof card, export/report affordances. |
## Accepted Direction
Use these references for:
- dark premium enterprise shell
- calm high-density panel system
- left navigation plus top context bar
- right-side decision/detail panels
- evidence/audit/proof pathways
- dense but scanable tables
- operational/product context visible above diagnostics
## Required Corrections Before Runtime Implementation
Later implementation specs must still correct or verify:
- no green/success state unless backed by repo-verified evidence
- dangerous restore actions need stronger friction than a normal green execute button
- concrete metrics, dates, users, and entities are conceptual unless repo-verified
- customer-safe and auditor-safe surfaces must hide raw diagnostics by default
- every action requires RBAC, audit, workspace/environment scope, and OperationRun verification where relevant
## Relationship To Generated Target Images
The first generated Spec 325 PNGs are treated as IA/content scaffolds. The accepted premium direction is this reference set plus the regenerated premium target PNGs under `../../target/`.