TenantAtlas/specs/057-filament-v5-upgrade/data-model.md

Data Model: Admin UI Stack Upgrade (Filament v5 + Livewire v4)

This feature is a framework/UI dependency upgrade. No new domain entities are introduced.

Existing Entities (Referenced)

Tenant

• Purpose: tenant-scopes all UI data access.
• Key fields (existing): id, tenant identity metadata.
• Relationships: Tenant → many OperationRun.

OperationRun

• Purpose: canonical Monitoring → Operations record per constitution.
• Key fields (existing, inferred from usage):
  • tenant_id
  • type, status, outcome
  • initiator_name
  • created_at, started_at, completed_at
  • JSONB: run context/failures/summary (per repo context)
• Relationships:
  • belongsTo Tenant.

Schema / Migration Expectations

Decision: No database schema changes intended

• Rationale:
  • Filament/Livewire upgrade does not require domain schema changes.
  • Spec allows migrations only if strictly required by dependencies; current plan avoids introducing such requirements.

Guardrails (if a migration becomes necessary)

• Must be reversible with a safe down().
• Must be non-destructive (no data loss; avoid drops unless explicitly planned).
• Must be called out in release notes.

Validation Rules / State Transitions

• No new validation rules.
• No new state machines.
• Existing OperationRun status/outcome conventions remain unchanged.