Checklists

requirements.md

Specification Quality Checklist: Mission-Surface Resolver Strangler-Finish

Purpose: Validate specification completeness and quality before proceeding to planning Created: 2026-06-21 (re-scoped to strangler-finish same day) Feature: spec.md

Content Quality

  • ✅ No implementation details beyond the code-surface anchors a maintainer audience needs
  • ✅ Focused on the outcome (the three resolution legs agree; coord-empty resolves loudly; coord-deleted hard-fails uniformly)
  • ✅ Written for the relevant stakeholder (internal developer tooling; primary stakeholder is a maintainer)
  • ✅ All mandatory sections completed

Requirement Completeness

  • ✅ No [NEEDS CLARIFICATION] markers remain
  • ✅ Requirements are testable and unambiguous
  • ✅ Requirement types are separated (Functional / Non-Functional / Constraints)
  • ✅ IDs are unique across FR-### (001-008), NFR-### (001-005), C-### (001-005), SC-### (001-008)
  • ✅ All requirement rows include a non-empty Status value
  • ✅ Non-functional requirements include measurable thresholds (gate-green-each-step; type+code assertion not weakened; warning test-asserted; byte-identical; zero external callers)
  • ✅ Success criteria are measurable (31/0 gate; zero callers; mutation flips; zero reach-ins)
  • ✅ Success criteria are technology-agnostic outcomes
  • ✅ All acceptance scenarios are defined
  • ✅ Edge cases are identified (create-window; no-coord; dangling caller; net-new warning)
  • ✅ Scope is clearly bounded (collapse-convergence + 2 tidies IN; CoordAuthorityUnavailable deletion / acceptance-lane reroute / mission_runtime taxonomy / #2046-redo OUT)
  • ✅ Dependencies and assumptions identified

Feature Readiness

  • ✅ All functional requirements have clear acceptance criteria (mapped to SC-001..008)
  • ✅ User scenarios cover primary flows
  • ✅ Feature meets measurable outcomes defined in Success Criteria
  • ✅ No implementation details leak beyond the necessary code-surface anchors

Notes

(audit/guard/differential) + FR-004 typed-error already BUILT + GREEN (mission 01KVGCE8). The operator chose to pull the collapse forward. Basis: research/collapse-reduction-map-randy.md + research/collapse-boundary-analysis-alphonso.md.

equivalence gate is the deletion-safety net and stays green at every WP boundary (27/6 → 29/4 → 31/0).

coord-empty drains for free under Option B; coord-deleted converges its exception spelling to CoordinationBranchDeleted (hard-fail preserved, C-001), keeping CoordAuthorityUnavailable exported (C-003), migrating the agent status public contract in the same slice (FR-005).

  • Re-scoped 2026-06-21 to the #2040 strangler-FINISH after a brownfield check found the R1 safety net
  • The collapse is a convergence (route 3 legs through one body), not a large deletion. The differential
  • Central decision (operator: converge fully): the aggregate CoordAuthorityUnavailable boundary —