## Summary - add the Spec 323 Tenantial enterprise UI audit foundation package - add the UI/UX audit registry artifacts, templates, and supporting brand context placeholder - update Spec Kit prompts/templates plus PR fast-feedback guardrails for ongoing UI productization coverage ## Scope - docs-first audit foundation only - no runtime Laravel, Filament, Livewire, route, auth, or database behavior changes intended ## Validation - [x] `git diff --check` - [ ] application test suite run ## Notes - primary spec: `specs/323-tenantial-enterprise-ui-audit-foundation/` - this branch also updates `.gitea/pull_request_template.md`, `.gitea/workflows/test-pr-fast-feedback.yml`, and `scripts/check-ui-productization-coverage` to make the coverage gate durable for future UI work Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de> Reviewed-on: #383
1.9 KiB
1.9 KiB
UI-005 Decision Register
| Field | Value |
|---|---|
| Route | /admin/governance/decisions |
| Source | DecisionRegister |
| Area / scope | Governance / workspace |
| Archetype | Evidence / Audit |
| Design depth | Strategic Surface |
| Repo truth | repo-verified |
| Screenshot | ../screenshots/desktop/ui-005-decision-register.png |
| Browser status | Reached through local workspace route. |
First Five Seconds
The page reads as a governance record surface. It should make historical decision truth, proof links, and review-pack/customer-safe relevance visible without becoming a raw audit table.
Productization Review
- Decision-first: historical rather than queue-first.
- Evidence-first: strong fit for proof/run/evidence linkage.
- Context: workspace hub, environment filtering where explicit.
- Customer/auditor safety: high, because data may feed customer-facing summaries.
- Diagnostics: raw details should be lower than outcome and proof.
Information Inventory
Default content should show decision type, outcome, owner/actor, environment scope where relevant, evidence basis, related operation/run, and review-pack inclusion state.
Dangerous Actions
No immediate destructive action was exercised. Related actions may reopen or link decisions; target review should ensure no unsupported mutation appears primary.
Scores
| IA | Density | User Clarity | Sellability | Disclosure | Hierarchy | DS Fit | A11y | Responsive | Components | UX Writing | Perf |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 4 | 4 | 4 | 4 | 4 | 4 | 4 | 3 | 3 | 4 | 4 | 4 |
Top Issues
- Needs a customer-safe register/reporting variant decision.
- Proof links must stay visible but not overwhelm decision summaries.
- Environment filter state must remain explicit.
Target Direction
P1 strategic target. Treat as the governance ledger pattern for historical proof and customer-safe summaries.