## Summary <!-- Kurz: Was ändert sich und warum? --> ## Spec-Driven Development (SDD) - [ ] Es gibt eine Spec unter `specs/<NNN>-<feature>/` - [ ] Enthaltene Dateien: `plan.md`, `tasks.md`, `spec.md` - [ ] Spec beschreibt Verhalten/Acceptance Criteria (nicht nur Implementation) - [ ] Wenn sich Anforderungen während der Umsetzung geändert haben: Spec/Plan/Tasks wurden aktualisiert ## Implementation - [ ] Implementierung entspricht der Spec - [ ] Edge cases / Fehlerfälle berücksichtigt - [ ] Keine unbeabsichtigten Änderungen außerhalb des Scopes ## Tests - [ ] Tests ergänzt/aktualisiert (Pest/PHPUnit) - [ ] Relevante Tests lokal ausgeführt (`./vendor/bin/sail artisan test` oder `php artisan test`) ## Migration / Config / Ops (falls relevant) - [ ] Migration(en) enthalten und getestet - [ ] Rollback bedacht (rückwärts kompatibel, sichere Migration) - [ ] Neue Env Vars dokumentiert (`.env.example` / Doku) - [ ] Queue/cron/storage Auswirkungen geprüft ## UI (Filament/Livewire) (falls relevant) - [ ] UI-Flows geprüft - [ ] Screenshots/Notizen hinzugefügt ## Notes <!-- Links, Screenshots, Follow-ups, offene Punkte --> Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de> Reviewed-on: #223
13 lines
1.1 KiB
Markdown
13 lines
1.1 KiB
Markdown
# Requirements Checklist: Baseline Compare Matrix: High-Density Operator Mode
|
|
|
|
- [x] Spec candidate check is complete and scores the candidate before approval.
|
|
- [x] The spec is explicitly scoped as a follow-up to the existing workspace matrix rather than a new domain truth.
|
|
- [x] Multi-tenant dense mode is defined as the primary operator-density gain.
|
|
- [x] Single-tenant compact mode is defined as a separate adaptive presentation path.
|
|
- [x] Filters, legends, actions, and refresh surfaces are explicitly compressed as supporting context.
|
|
- [x] Visible-set-only semantics and existing RBAC rules are preserved.
|
|
- [x] No new persisted artifact, state family, or generalized UI framework is introduced.
|
|
- [x] Manual presentation override is local to the route and not stored as domain truth.
|
|
- [x] Functional requirements include mode selection, action calming, filter workflow, and last-updated visibility.
|
|
- [x] Definition of done is testable and aligned with operator scanability rather than generic visual polish.
|
|
- [x] Tasks are grouped by user story and include focused verification work. |