# Spec 336 Requirements Checklist - Purpose: Preparation-quality validation for Spec 336 before runtime implementation. - Created: 2026-05-29 - Feature: [spec.md](../spec.md) ## Content Quality - [x] Spec Candidate Check is filled and justifies why this is Core Enterprise alignment work. - [x] Scope is bounded to Baseline Compare Landing UX alignment; explicit non-goals exclude backend compare/evidence rewrites. - [x] Acceptance criteria are testable (Feature + Browser smoke + screenshots). - [x] Spec includes truthful-copy constraints (no healthy/compliant/customer-safe claim). ## Repo Truth - [x] Spec number/branch reconciled to repo numbering: - `335-restore-run-detail-post-execution-proof-productization` already exists. - This package is correctly created as `336-baseline-compare-product-process-flow-alignment`. - [x] Confirmed scope paths exist: - `apps/platform/app/Filament/Pages/BaselineCompareLanding.php` - `apps/platform/resources/views/filament/pages/baseline-compare-landing.blade.php` - `apps/platform/app/Support/Baselines/BaselineCompareStats.php` - `apps/platform/app/Services/Baselines/BaselineSnapshotTruthResolver.php` - `apps/platform/app/Services/Baselines/BaselineCompareService.php` - `apps/platform/app/Jobs/CompareBaselineToTenantJob.php` - [x] Repo-truth artifacts exist and constrain state invention: - [repo-truth-map.md](../repo-truth-map.md) - [baseline-compare-state-contract.md](../baseline-compare-state-contract.md) ## Security / Isolation / RBAC - [x] Capability-first RBAC is explicitly required for all actions and deep links. - [x] Cross-workspace/environment leakage is explicitly tested and forbidden. - [x] No `/admin/t` routes, no legacy tenant query aliases, and no remembered environment as authority are introduced. ## UI Guardrail / Disclosure - [x] Decision-first ordering is explicit (decision card → flow → proof → diagnostics collapsed). - [x] Exactly one dominant primary next action per state is required. - [x] Diagnostics are collapsed by default; raw diff/payload is never default-visible. ## Test And Smoke Readiness - [x] Plan includes the intended lane mix (Feature + Browser). - [x] Tasks are ordered, small, and verifiable with explicit file targets. - [x] Minimal validation commands are listed in spec/tasks. - [x] Screenshot list is explicit and scoped to this spec directory. ## Preparation Analysis Outcome - [x] Preparation artifacts are internally consistent (spec ↔ plan ↔ tasks ↔ truth map ↔ state contract). - [x] Every requirement in the spec maps to one or more tasks. - [x] No preparation issue requires application implementation to resolve. - [x] Candidate Selection Gate result: PASS (user-provided candidate + referenced as follow-up in Spec 333; not a completed spec package). - [x] Spec Readiness Gate result: PASS for later implementation.