Requirements Checklist: Weekly Cycle Flow

Specification Quality Gates

Completeness

  • Full cycle flow defined from scheduling to closeout
  • Timing parameters configurable
  • Exception paths documented
  • Integration with State Authority specified

Testability

  • All acceptance scenarios use Given/When/Then format
  • Success criteria are measurable
  • Independent tests defined per user story
  • Timing thresholds are explicit and configurable

Constitution Alignment

§1 Weekly Cadence Invariant

  • FR-101: Auto-scheduling ensures every Active user has cycles
  • FR-102: Configurable timing supports different anchors
  • FR-108: Auto-progression maintains cadence without user action
  • Delays are explicit state changes (DeliveryUncertain event)

§2 Circular Inventory Invariant

  • FR-106: Scan-based packing ensures accurate tracking
  • FR-107: Garments locked at commitment (Reserved state)
  • FR-112, FR-113: Inspection required before return to Available
  • FR-113: Auto-routing respects lifecycle bounds

§3 State Truth Discipline

  • All operations use State Authority for entity transitions
  • New entities (SchedulingJob, CommitmentBatch, etc.) support audit
  • Variance events documented (CompensatingAllocation, MissingGarment)

§4 Explicit Failure Handling

  • US8 covers exception workflows
  • Late return escalation path defined (reminder → hold → loss)
  • Missing item handling specified
  • Carrier loss handling specified

§5 Probabilistic Fit

  • Fit intelligence receives actual (not planned) garment data
  • Damage reports inform fit learning
  • No fit decisions made in this layer (deferred to FitIntelligenceSubsystem)

§6 Cognitive Load Minimization

  • Auto-scheduling requires no user action
  • Auto-progression through windows requires no user action
  • Return reminders are progressive, not demanding
  • Default behaviors handle normal cases

Functional Requirements Traceability

Requirement User Story Constitution Reference
FR-101 US1 §1 (cadence), §6 (no user action)
FR-102 US1 §1 (timing control)
FR-103 US2 §1 (commitment binding)
FR-104 US2 §2 (inventory management)
FR-105 US3 §2 (operational accuracy)
FR-106 US3 §2 (tracking accuracy)
FR-107 US4 §1 (batch efficiency)
FR-108 US5 §1 (auto-progression), §6 (no user action)
FR-109 US6 §6 (progressive reminders)
FR-110 US6 §6 (flexibility)
FR-111 US6 §4 (explicit hold)
FR-112 US7 §2 (inspection required)
FR-113 US7 §2 (lifecycle routing)
FR-114 US7 §3 (accounting accuracy)
FR-115 US8 §4 (exception paths)

Dependencies

Depends On (must exist before this feature)

  • State Authority Subsystem (entity state management)
  • User, Garment, Box, Cycle tables in Airtable
  • Transition automations for all entities

Provides To (downstream dependencies)

  • Fit Intelligence Subsystem (garment/cycle data for learning)
  • User Contract Enforcement (settlement data)
  • Observability/Audit (event stream)

Risk Assessment

Critical Risks Addressed

  1. Cadence collapse → Auto-scheduling + auto-progression + escalation holds
  2. Inventory drift → Scan-based packing + variance detection
  3. Late return cascade → Progressive escalation + HoldLogistics

Risks NOT in Scope

  • Fit prediction accuracy (FitIntelligenceSubsystem)
  • Payment processing details (UserContractEnforcementSubsystem)
  • User communication content (ExperienceMinimizationSubsystem)
  • Carrier integration details (external API—manual for pilot)

Approval

  • Spec reviewed against constitution
  • Timing parameters validated with operations
  • State Authority integration verified
  • Ready for /speckit.plan