feat: normalize operator outcome taxonomy #186

Merged
ahmido merged 1 commits from 156-operator-outcome-taxonomy into dev 2026-03-22 12:13:36 +00:00
Owner

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
## 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
ahmido added 1 commit 2026-03-22 10:24:32 +00:00
ahmido merged commit 3c3daae405 into dev 2026-03-22 12:13:36 +00:00
Sign in to join this conversation.
No reviewers
No Label
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: ahmido/TenantAtlas#186
No description provided.