TenantAtlas/specs/399-dashboard-inbox-table-contract/checklists/requirements.md

Requirements Checklist: Spec 399 - Dashboard / Inbox / Table Contract Migration v1

Purpose: Validate that the Spec 399 preparation package is complete, bounded, testable, and ready for implementation review. Created: 2026-06-22 Feature: specs/399-dashboard-inbox-table-contract/spec.md

Content Quality

• CHK001 Feature value is stated from an operator/admin perspective, not as implementation-only cleanup.
• CHK002 Selected candidate, source, close alternatives, and deferral rationale are recorded.
• CHK003 Completed related specs are treated as read-only context and are not reopened.
• CHK004 Scope is limited to existing dashboard, inbox, and table-heavy /admin surfaces.
• CHK005 Explicit non-goals forbid runtime framework, presenter family, status enum family, persisted taxonomy, and compatibility-mode work.
• CHK006 No application implementation or runtime-code edit is included in this preparation package.

Requirement Completeness

• CHK007 No [NEEDS CLARIFICATION] markers remain.
• CHK008 User stories are independently testable and prioritized.
• CHK009 Functional requirements are observable and testable.
• CHK010 Acceptance criteria map to the named dashboard, inbox, table, Operations Hub, and technical-proof behavior.
• CHK011 Success criteria are measurable and include browser proof, table budgets, visible complexity, and no new runtime truth.
• CHK012 Edge cases cover calm states, native pagination limitations, technical-annex tables, OperationRun proof, RBAC-hidden actions, and unrelated browser failures.
• CHK013 Assumptions and open questions are non-blocking.

Product Surface Contract

• CHK014 docs/product/standards/product-surface-contract.md is referenced as an active gate.
• CHK015 No-legacy posture is explicit: canonical replacement, no hidden old layouts, aliases, old labels, fallback readers, or legacy fixtures.
• CHK016 Product Surface Impact records page archetypes, primary questions, primary actions, surface budgets, Technical Annex/deep-link demotion, status vocabulary, and exceptions.
• CHK017 Product Surface exceptions are none planned; any future exception is a stop condition requiring spec/plan update.
• CHK018 Browser proof is required for rendered UI changes.
• CHK019 Human Product Sanity is required and has reviewer questions.
• CHK020 Implementation report close-out fields are named in spec, plan, and tasks.

UI And Filament Readiness

• CHK021 UI Surface Impact is explicitly checked and is consistent with Productization Coverage.
• CHK022 Route inventory and design coverage matrix update expectations are recorded.
• CHK023 Page reports are proportional and not required by default.
• CHK024 Filament/Livewire posture records Livewire v4.1.4 compliance and no Livewire v3 usage.
• CHK025 Provider registration posture records no panel provider changes and current Laravel 12 provider location.
• CHK026 Global search posture is unchanged unless implementation explicitly updates spec/plan first.
• CHK027 Destructive/high-impact action requirements include confirmation, authorization, audit safety, and test coverage.
• CHK028 Asset strategy records no new assets expected and filament:assets only if assets are registered later.
• CHK028A List/table surface work references docs/product/standards/list-surface-review-checklist.md.
• CHK028B Dark mode, accessibility, and Filament-native/shared-primitive proof is required for touched custom Blade surfaces.

Task Readiness

• CHK029 spec.md, plan.md, and tasks.md exist for specs/399-dashboard-inbox-table-contract/.
• CHK030 Tasks are ordered by discovery, tests-first expectations, user-story implementation, proof continuity, browser/coverage close-out, and non-goals.
• CHK031 Tasks name concrete likely files and preserve implementation discovery before runtime edits.
• CHK032 Tasks include Product Surface browser proof, Human Product Sanity, implementation report, Pint, and diff checks.
• CHK033 Tasks explicitly forbid completed-spec rewrites and broad framework/persistence/status-family expansion.

Review Outcome

• CHK034 Review outcome class: acceptable-special-case.
• CHK035 Workflow outcome: keep.
• CHK036 Final note location: active implementation report and PR close-out under Guardrail / Exception / Smoke Coverage.