Findings with outcome 2/3 (67%)
For custom progress bars, fixed inline height MAY be used when Tailwind height utilities are not reliably present in the loaded Filament theme.
12. Context Chip Pattern
Context chips provide lightweight environment context.
Examples:
Workspace
Provider / Tenant type
Latest activity
Billing state
Scope
Rules:
chips SHOULD appear below the page header and above the KPI row
chips are not primary actions
chips MUST NOT collapse to 0px
long values SHOULD truncate
mobile MAY wrap
desktop SHOULD remain horizontal where possible
no fake provider labels
provider labels MUST be repo-real or neutral fallback
Allowed provider fallback:
Provider-VerbindungProvider connection
Do not invent:
Microsoft Graph
unless the repo-real provider identity supports it.
13. Dashboard Main / Aside Pattern
TenantPilot dashboards use a decision-first main/aside layout.
Desktop:
Main content: col-span-8
Aside: col-span-4
Mobile:
stacked layout
Main content SHOULD contain:
recommended actions
governance status
primary decision surfaces
recent operational context where appropriate
Aside SHOULD contain:
current review
risk exceptions
provider health
customer-safe output
readiness context
Rules:
aside cards are compact
no long tables in aside
no raw logs/json in aside
each aside card has at most one action
actions inside aside cards are secondary/gray
aside cards must not imply unavailable product maturity
14. Empty State Pattern
Empty states must be honest and action-aware.
Every empty state SHOULD include:
clear title
short explanation
optional next action only if repo-real route and capability exist
Good:
Kein aktives ReviewFür diesen Tenant ist aktuell kein Review in Bearbeitung.
Good:
Keine kundensichere Ausgabe verfügbarErzeuge ein Review-Paket, sobald Evidence und Review bereit sind.
Bad:
Kunden-Workspace öffnen
when no customer-safe workspace is repo-verified.
Rules:
no fake CTA
no implied product maturity
no placeholder/demo content
no customer-safe claim without repo verification
no action without route and capability
15. Loading, Stale and Error States
15.1 Loading
Loading states SHOULD use:
skeleton
quiet placeholder
short loading text when needed
Avoid:
spinner spam
layout shifting
blocking entire dashboard unless necessary
15.2 Stale
Stale states SHOULD show:
badge or label
reason if available
last refreshed/checked timestamp when repo-real
Stale states MUST NOT use alarming surfaces unless operator action is required.
15.3 Error
Error states SHOULD show:
reason
impact
next action if available
Technical details MUST remain behind progressive disclosure.
Never default to:
raw exception
JSON payload
stack trace
logs
raw API response
16. Table and List Pattern
Tables should remain Filament-native unless there is a strong product reason.
Rules:
row hover only if row click is enabled
otherwise use explicit row action
status columns use badges
raw IDs hidden by default
technical columns behind toggle or detail view
destructive actions are never primary
no button flood in each row
no raw technical fields as default operator experience
TenantPilot tables SHOULD support decision-first scanning:
status
reason
impact
owner/scope
next action
details only on demand
Anti-pattern:
Operator must inspect raw IDs, payloads and logs to understand what matters.
17. Form and Detail Page Pattern
17.1 Forms
Forms SHOULD:
group fields into sections
use clear section titles
keep primary save/submit action consistent
separate destructive actions
hide advanced/technical fields behind collapsible sections where appropriate
Forms MUST NOT:
expose raw internal fields as primary inputs unless needed
mix destructive and primary actions at equal visual weight
rely on placeholder text as the only explanation
17.2 Detail Pages
Detail pages SHOULD:
be read-first
show status/reason/impact before technical details
use progressive disclosure for diagnostics
avoid looking like edit forms when read-only
Technical details SHOULD be grouped under:
Technical DetailsDiagnosticsRaw Details
and collapsed or secondary by default.
18. Customer-safe Surface Rules
Customer-safe surfaces must be read-only, calm and evidence-first.
Rules:
no raw technical logs by default
no internal operation noise by default
no admin-only actions
no unsupported maturity claims
no Open customer workspace unless Customer Review Workspace is repo-verified
use Export-Artefakte anzeigen or Review-Paket öffnen when only artifacts/packs exist
customer-safe copy must be especially precise
customer-safe output must distinguish between:
Review Pack
Evidence Snapshot
Export Artifact
Customer Workspace
Do not label the whole customer-safe output as failed if only the latest export/review-pack generation failed.
Prefer precise copy:
Review-Paket fehlgeschlagenExport fehlgeschlagenKeine kundensichere Ausgabe verfügbar
19. Component Ownership Rules
Business logic belongs in:
SummaryBuilder
ViewModel
Presenter
Link service
Policy/capability layer
domain service
Blade may:
render fields
branch on explicit view model flags
render provided URLs/icons/badges/progress values
Blade MUST NOT:
invent routes
infer capabilities
calculate business status
hardcode provider maturity
calculate fake progress
infer customer-safe maturity
parse raw payloads for product decisions
duplicate business logic from services/builders
Preferred flow:
Domain model/service→ SummaryBuilder/ViewModel/Presenter→ Blade render
Not allowed:
Blade template→ queries database→ invents status→ decides capability→ renders action
20. Localization Rules
Visible UI copy MUST use localization keys.
Rules:
no new hardcoded user-facing copy in Blade
DE/EN mixture is accepted only as explicit Localization v1 debt
customer-facing copy must be especially careful
labels must not overclaim product maturity
status labels should use shared badge/status language where possible
Until Localization v1 is complete:
mixed language may exist in operator-only surfaces
new copy should still be added through localization files
PR/close-out notes SHOULD mention known localization debt when relevant
21. Accessibility and Keyboard Rules
Custom interactive UI MUST be accessible.
Rules:
clickable navigation uses