ahmido
3eff4d8579
## 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
4.1 KiB
4.1 KiB
Spec 325 Strategic Target Image Implementation Candidates
Spec 325 creates target artifacts only. These candidates group later runtime implementation work proportionally so the project does not create one implementation spec per small page.
Recommended Order
| Order | Candidate lane | Source target artifacts | Why this group is proportional |
|---|---|---|---|
| 1 | Customer Review Workspace productization | ../target-experience-briefs/customer-review-workspace.md, ../target-images/target/customer-review-workspace-target.md |
Highest sellability and customer-safe review impact. |
| 2 | Governance Inbox decision experience | ../target-experience-briefs/governance-inbox.md, ../target-images/target/governance-inbox-target.md |
Central operator human-in-the-loop workflow; can absorb decision register and exception detail patterns later. |
| 3 | Operations Hub productization | ../target-experience-briefs/operations-hub.md, ../target-images/target/operations-hub-target.md |
Establishes execution truth and OperationRun outcome grammar before related alert/run detail work. |
| 4 | Evidence and review pack consumption productization | ../target-experience-briefs/audit-log.md, ../target-experience-briefs/customer-review-workspace.md |
Provides customer-safe proof and audit/export language without overloading runtime pages with raw diagnostics. |
| 5 | Restore safety UX productization | ../target-experience-briefs/restore-safety-workflow.md, ../target-images/target/restore-safety-workflow-target.md |
Highest destructive-action risk; needs seeded capability/browser fixture and strict audit/OperationRun tests. |
| 6 | Provider onboarding/readiness UX cleanup | ../target-experience-briefs/provider-readiness.md, ../target-images/target/provider-readiness-target.md |
Trust-critical setup and recovery surface; can later extend to create/detail/onboarding wizard states. |
| 7 | Drift/Baseline decision experience | ../target-experience-briefs/baseline-compare-drift.md, ../target-images/target/baseline-compare-drift-target.md |
Requires seeded baseline/compare data; target first defines assignment, evidence gaps, and decision hierarchy. |
| 8 | Workspace and Environment dashboard productization | ../target-experience-briefs/workspace-overview.md, ../target-experience-briefs/environment-dashboard.md |
High first-read value; can be implemented after decision/action hierarchy is agreed. |
Shared Pattern Dependencies
Spec 326 Tenantial Pattern Library & State System should be prepared before broad implementation if multiple lanes begin to repeat:
- status/trust badges
- evidence summary strips
- OperationRun outcome strips
- dangerous-action confirmation grammar
- customer-safe review cards
- detail drawer disclosure levels
- empty/loading/error state grammar
- workspace/environment context headers
Do not turn these into a runtime framework inside a single page implementation. Extract only after real repeated cases prove the need.
Conceptual Elements Requiring Repo Verification
| Element | Why verification is required |
|---|---|
| Recommended next action copy | Must come from real policy/capability/operation state, not target-image prose. |
| Evidence completeness and freshness labels | Must map to existing evidence snapshots, review packs, reports, or explicit new spec scope. |
| Restore safety gate steps | Must map to actual restore dry-run, validation, confirmation, audit, and OperationRun behavior. |
| Provider permission readiness | Must map to provider connection state, required permissions, and safe diagnostic disclosure. |
| Drift impact summaries | Must map to assigned baseline, latest compare result, evidence gaps, and tenant/environment scope. |
| Customer-safe export/share actions | Must be authorized, audited, scoped, and redacted before becoming runtime UI. |
Do Not Implement Yet
Do not implement every visual tile, label, drawer, or action shown in target PNGs as a literal UI requirement. Later specs must first confirm data availability, RBAC, workspace/environment entitlement, audit logging, OperationRun semantics, customer-safe disclosure, and dangerous-action confirmation behavior.