## Summary - introduce a shared operator outcome taxonomy with semantic axes, severity bands, and next-action policy - apply the taxonomy to operations, evidence/review completeness, baseline semantics, and restore semantics - harden badge rendering, tenant-safe filtering/search behavior, and operator-facing summary/notification wording - add the spec kit artifacts, reference documentation, and regression coverage for diagnostic-vs-primary state handling ## Testing - focused Pest coverage for taxonomy registry and badge guardrails - operations presentation and notification tests - evidence, baseline, restore, and tenant-scope regression tests ## Notes - Livewire v4.0+ compliance is preserved in the existing Filament v5 stack - panel provider registration remains unchanged in bootstrap/providers.php - no new globally searchable resource was added; adopted resources remain tenant-safe and out of global search where required - no new destructive action family was introduced; existing actions keep their current authorization and confirmation behavior - no new frontend asset strategy was introduced; existing deploy flow with filament:assets remains unchanged Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de> Reviewed-on: #186
2.2 KiB
2.2 KiB
Product Standards
Canonical, living standards that govern all new and modified Filament UI surfaces. Specs reference these standards; they do not redefine them. Guard tests enforce critical constraints automatically.
Last reviewed: 2026-03-21
Standards Index
| Standard | File | Governs |
|---|---|---|
| Table UX | filament-table-ux.md | Column tiers, sort, search, toggle, pagination, persistence, empty states, timestamps, IDs |
| Filter UX | filament-filter-ux.md | Filter patterns, persistence, soft-delete, date range, enum sourcing, defaults |
| Actions UX | filament-actions-ux.md | Row/bulk/header actions, grouping, destructive safety, inspect affordance |
| Review Checklist | list-surface-review-checklist.md | PR/spec checklist for any new or modified list surface |
How Standards Are Enforced
- Constitution — Principles in
.specify/memory/constitution.mdgovern why we build this way. - Standards (this directory) — Concrete rules for how every surface must behave.
- Guard tests — Automated Pest tests that fail CI when critical standards are violated.
- PR review — The review checklist is checked for every spec or PR that touches a list surface.
When to Update Standards
- When a spec introduces a new surface type or pattern not yet covered.
- When a standard proves too rigid or too loose after real usage.
- When Filament version changes invalidate or enable new native features.
Update the standard first, then adjust implementation to match.
Related Docs
| Document | Location | Purpose |
|---|---|---|
| Constitution | .specify/memory/constitution.md |
Permanent principles (OPSURF-001, UX-001, Action Surface Contract, RBAC-UX) |
| Product Principles | docs/product/principles.md |
High-level product decisions |
| Table Rollout Audit | docs/ui/filament-table-standard.md |
Rollout inventory and implementation state from Spec 125 |
| Action Surface Contract | docs/ui/action-surface-contract.md |
Original action surface reference (now governed by this standard) |