ahmido
bd26e209de
Some checks failed
Main Confidence / confidence (push) Failing after 57s
## Summary - add the provider boundary catalog, boundary support types, and guardrails for platform-core versus provider-owned seams - harden provider gateway, identity resolution, operation registry, and start-gate behavior to require explicit provider bindings - add unit and feature coverage for boundary classification, runtime preservation, unsupported paths, and platform-core leakage guards - add the full Spec Kit artifact set for spec 237 and update roadmap/spec-candidate tracking ## Validation - `cd apps/platform && ./vendor/bin/sail artisan test --compact tests/Unit/Providers/ProviderBoundaryClassificationTest.php tests/Unit/Providers/ProviderBoundaryGuardrailTest.php tests/Feature/Providers/ProviderBoundaryHardeningTest.php tests/Feature/Providers/UnsupportedProviderBoundaryPathTest.php tests/Feature/Guards/ProviderBoundaryPlatformCoreGuardTest.php` - `cd apps/platform && ./vendor/bin/sail artisan test --compact tests/Unit/Providers/ProviderGatewayTest.php tests/Unit/Providers/ProviderIdentityResolverTest.php tests/Unit/Providers/ProviderOperationStartGateTest.php` - `cd apps/platform && ./vendor/bin/sail bin pint --dirty --format agent` - browser smoke: `http://localhost/admin/provider-connections?tenant_id=18000000-0000-4000-8000-000000000180` loaded with the local smoke user, the empty-state CTA reached the canonical create route, and cancel returned to the scoped list Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de> Reviewed-on: #273 |
||
|---|---|---|
| .. | ||
| filament-actions-ux.md | ||
| filament-filter-ux.md | ||
| filament-table-ux.md | ||
| list-surface-review-checklist.md | ||
| README.md | ||
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-04-24
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 and whether new persistence, abstractions, or semantic frameworks are justified at all. - 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 (PROP-001, BLOAT-001, OPS-UX-START-001, UI-CONST-001, DECIDE-001, UI-SURF-001, ACTSURF-001, UI-HARD-001, UI-EX-001, HDR-001, OPSURF-001, UI-FIL-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) |