TenantAtlas/specs/362-sync-capture-backup-operation-semantics/checklists/requirements.md

Requirements Checklist: Spec 362 - Sync, Capture, and Backup Operation Semantics

Purpose: Preparation analysis for Spec 362 readiness
Created: 2026-06-07
Feature: /Users/ahmeddarrazi/Documents/projects/wt-plattform/specs/362-sync-capture-backup-operation-semantics/spec.md

Candidate Selection And Guardrails

• CHK001 The candidate source is explicit: the direct user-provided Spec 362 draft from /Users/ahmeddarrazi/.codex/attachments/c6e1919f-3e04-4f47-b6a8-58c0fdc2ab82/pasted-text.txt.
• CHK002 No specs/362-* package existed before Spec Kit branch creation.
• CHK003 The active candidate queue's empty-state note is respected; this package is an intentional manual promotion, not an auto-selected queue item.
• CHK004 Related specs were checked and treated correctly: Specs 358, 359, and 361 are implementation context, and Spec 360 remains canonical-cutover context only.
• CHK005 Repo-truth deviations from the user draft are recorded in spec.md, especially the narrowed safe scope around inventory.sync, baseline.capture, and backup.schedule.execute plus the explicit defer/fail-closed treatment for policy.sync and backup_set.update.

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 scores above the approval threshold.
• CHK011 The spec keeps OperationRun, InventoryItem, BaselineSnapshot, BackupSet, and BackupItem persistence unchanged.
• CHK012 The spec explains why bounded adapter extension is justified now under ABSTR-001: the repo already has real registry-backed reconciliation consumers and current proof seams for the selected families.
• CHK013 The spec keeps scope bounded to inventory-sync reconciliation, baseline-capture reconciliation, backup-schedule reconciliation, and honest unsupported-family handling.
• CHK014 The proportionality review rejects a generic sync/backup engine, new operation types, new persistence, and weak "latest artifact exists" heuristics.

Plan / Task Alignment

• CHK015 The plan identifies the actual repo surfaces likely to change, including the current registry, write seam, proof models, proof presenters, and operations/detail pages.
• CHK016 The plan keeps Filament v5 / Livewire v4 posture and provider-registration location visible.
• CHK017 The plan explicitly states that no migration, no new panel/provider, no new global search change, and no new asset strategy are expected.
• 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 queue families, generic sync/backup heuristics, and unsupported-family widening.
• CHK020 The tasks keep the current OperationRun lifecycle owner, current presenter/link surfaces, and current workspace-first RBAC model authoritative.

UI / Monitoring / Proof Coverage

• CHK021 UI Surface Impact is completed and does not claim a new page family.
• CHK022 The changed surfaces are correctly classified as existing operations monitoring/detail plus existing inventory, baseline, and backup detail follow-through, not a new strategic customer-facing page.
• CHK023 No new page-report identity or route-inventory expansion is required unless implementation proves a materially new visible hierarchy.
• CHK024 Audience-aware disclosure and no-overclaim wording boundaries are explicit for operations, run detail, and current proof/detail surfaces.

Test Governance

• CHK025 The declared test families are the narrowest honest proof: Unit + Feature + one bounded Browser smoke.
• CHK026 No heavy-governance family or PGSQL-only schema lane is introduced by default.
• CHK027 Planned validation commands are explicit, partitioned into the primary Spec 362 gate and bounded contextual regressions, and remain scoped to selected-family fallout only.

Readiness Gate Outcome

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

Review Outcome

• CHK032 Outcome class: acceptable-special-case
• CHK033 Workflow outcome: keep
• CHK034 Final note location: active feature PR close-out entry Guardrail / Smoke Coverage
• CHK035 Preparation analyze result: pass via repo-based cross-artifact review; no standalone local speckit.analyze command was exposed in this repo surface beyond prompts and agent instructions
• CHK036 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