Checklists

requirements.md

Specification Quality Checklist: LOC-insensitive census freshness gate

Purpose: Validate specification completeness and quality before proceeding to planning Created: 2026-07-06 Feature: spec.md

Content Quality

  • ✅ No implementation details (languages, frameworks, APIs) — census/worklist/routing are domain terms, not tech stack
  • ✅ Focused on user value and business needs (contributor + CI maintenance tax)
  • ✅ Written for non-technical stakeholders (purpose + primary scenario are plain-language)
  • ✅ 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-###, NFR-###, and C-### entries
  • ✅ All requirement rows include a non-empty Status value
  • ✅ Non-functional requirements include measurable thresholds
  • ✅ Success criteria are measurable
  • ✅ Success criteria are technology-agnostic
  • ✅ All acceptance scenarios are defined (primary + 4 anti-tamper + edge cases)
  • ✅ Edge cases are identified (rank-swap, exactly-at-floor, arch_blind_groups)
  • ✅ Scope is clearly bounded (Out of Scope section)
  • ✅ Dependencies and assumptions identified

Feature Readiness

  • ✅ All functional requirements have clear acceptance criteria (SC-001..SC-006 map to FRs)
  • ✅ User scenarios cover primary flows
  • ✅ Feature meets measurable outcomes defined in Success Criteria
  • ✅ No implementation details leak into specification

Notes

live reproduction already captured (see mission tracer / plan phase).

recorded as C-001; the how is deferred to the plan phase per specify discipline.

red-first reproduction (C-003) is required to use a rank-altering churn, so FR-007 cannot ship vacuously.

empty, structurally-pinned-empty surface); recorded in Out of Scope.

names the shared live_derived_worklist derivation so both surfaces are fixed by construction. Every FR now maps to at least one binding success criterion.

  • Validation passed. The mission is a narrowly-scoped enforcement-gate change with a
  • The exact fix mechanism (drop loc at the shared derivation, live floor check) is
  • Post-spec adversarial gate (verdict: minor) folded:
  • FR-007 order-insensitivity now has a binding success criterion (SC-007) and the
  • arch_blind_groups LOC-insensitivity removed from scope (unfalsifiable on the
  • Refuted finding (--verify-census) confirmed the derivation-level fix; C-001 now