## 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
1.9 KiB
1.9 KiB
Audit Log Target Image Sidecar
Not Implementation Truth
This target image is visual direction only. It is not runtime implementation truth, not a product capability claim, and not a substitute for later repo, RBAC, data, audit, and browser verification.
Links
| Item | Link |
|---|---|
| Source route | /admin/audit-log |
| Source screenshot | ../../screenshots/desktop/ui-008-audit-log.png |
| Source page report | ../../page-reports/ui-008-audit-log.md |
| Target brief | ../../target-experience-briefs/audit-log.md |
| Dark target image | audit-log-target-dark.png |
| Light target image | audit-log-target-light.png |
Transformation Table
| Current state | Target direction |
|---|---|
| Audit page can read as raw event history. | Event proof, scope, and selected detail become first-read. |
| Raw metadata can overpower evidence. | Human-readable proof precedes raw metadata. |
| Export/share copy needs review. | Export is scope-aware and marked for later authorization/audit verification. |
Repo-Truth Classification
| Element in target image | Classification | Implementation note |
|---|---|---|
| Audit route and screenshot | repo-verified | Existing route/screenshot anchor. |
| AuditLog event fields | repo-verified | Existing page/model concepts. |
| Selected proof panel | plausible-existing | New hierarchy over current data. |
| Export readiness | foundation-only | Requires runtime/export verification. |
| Compliance claims | unknown | Must not be asserted without proof. |
Conceptual Elements Requiring Verification
- Export scope and redaction
- Selected event entitlement behavior
- Evidence links from audit records
- Customer/auditor wording
Implementation Notes
Later implementation should keep scope filters visible and raw metadata behind progressive disclosure.
Do Not Implement Blindly
Do not add compliance-ready language or audit export behavior without a separate verified implementation spec.