TenantAtlas/specs/360-operationrun-canonical-cutover-cleanup/checklists/requirements.md

Requirements Checklist: Spec 360 - OperationRun Canonical Cutover Cleanup

Purpose: Preparation analysis for Spec 360 readiness
Created: 2026-06-06
Feature: specs/360-operationrun-canonical-cutover-cleanup/spec.md

Candidate Selection And Guardrails

• CHK001 The candidate source is explicit: direct user-provided draft plus repo-verified post-merge current code truth.
• CHK002 No specs/360-* package existed before this prep.
• CHK003 Related existing specs were checked for completed or contextual signals and are treated correctly: 358 is baseline context, 359 is merged functional baseline, and historical Spec-355 references to another 360 are context only.
• CHK004 The active candidate queue's no safe automatic next-best-prep target note is respected; this package is an intentional manual promotion rather than an auto-selected queue item.
• CHK005 Repo-truth deviations from the user draft are recorded in spec.md, especially the already-merged Spec 359 baseline, the existing restore adapter consumer, the missing canonical context.dispatch seam, and the historical Spec-355 numbering reference.

Required Prep Artifacts

• CHK006 spec.md exists and contains no template placeholders.
• CHK007 plan.md exists and is repo-aware.
• CHK008 tasks.md exists and is ordered, small, and verifiable.
• CHK009 This checklist exists.

Spec Quality

• CHK010 Spec Candidate Check is completed and scored above the approval threshold.
• CHK011 The spec keeps OperationRun persistence unchanged and explicitly forbids new lifecycle columns or tables.
• CHK012 The spec explains why one bounded adapter extension seam is justified now under ABSTR-001: the repo already has two real adapter consumers.
• CHK013 The spec keeps scope bounded to canonical reconciliation, dispatch/correlation, operation-type canonicalization, reader cutover, and Spec 359 close-out only.
• CHK014 The proportionality review rejects universal business reconciliation engines, schema expansion, and legacy compatibility for pre-production history.

Plan / Task Alignment

• CHK015 The plan identifies the actual repo surfaces likely to change, including current adapter, job, service, reader, and type-catalog seams.
• CHK016 The plan keeps Filament v5 / Livewire v4 posture and provider-registration location visible.
• CHK017 The plan explicitly requires PGSQL proof for duplicate-index or lock-sensitive behavior and one bounded Browser smoke for existing operations surfaces.
• CHK018 The tasks start with repo truth and failing tests before runtime edits.
• CHK019 The tasks include explicit anti-creep guardrails against new persistence, new adapter families, new UI families, and legacy compatibility shims.

UI / Monitoring / Reader Coverage

• CHK020 UI Surface Impact is completed and does not claim a new page family.
• CHK021 The changed surfaces are correctly classified as existing operations monitoring/detail plus existing review-start feedback follow-through, not a new strategic or customer-facing page.
• CHK022 No new page-report identity or route-inventory expansion is required unless implementation proves a materially new visible hierarchy.
• CHK023 Audience-aware disclosure and canonical related-artifact linkage boundaries are explicit.

Test Governance

• CHK024 The declared test families are the narrowest honest proof: Unit + Feature + one bounded Browser smoke, with PGSQL lane coverage for duplicate-index and correlation-sensitive truth.
• CHK025 No heavy-governance family is introduced.
• CHK026 Planned validation commands are explicit, partitioned into primary merge gate vs contextual regressions vs separate external probes, and include Spec 358 plus Spec 359 plus the bounded Spec 360 browser or PGSQL proof.

Readiness Gate Outcome

• CHK027 Candidate Selection Gate passes.
• CHK028 Spec Readiness Gate passes.
• CHK029 Runtime implementation has not started in this preparation step.
• CHK030 Recommended next step is implementation, not more prep.

Review Outcome

• Outcome class: acceptable-special-case
• Workflow outcome: keep
• Final note location: active feature PR close-out entry Guardrail / Smoke Coverage
• Preparation analyze result: pass via repo-based cross-artifact review; no standalone local speckit.tasks or speckit.analyze generator command was exposed in this repo surface beyond prompts and agent instructions
• Tooling note: Spec Kit branch/spec creation succeeded via create-new-feature.sh, setup-plan.sh generated the plan file, and tasks.md plus this checklist were authored manually to match the repo's Spec Kit templates and agent instructions