Checklists

requirements.md

Specification Quality Checklist: Built-In Doctrine Seam Consolidation

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

Content Quality

  • ✅ No implementation details (languages, frameworks, APIs) — module/symbol names appear only where they are the domain boundary (the seam) being specified
  • ✅ Focused on user value and business needs (fail-loud correctness, provable completion, one source)
  • ✅ Written for the affected stakeholders (runtime, developers, operators, CI)
  • ✅ 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 (outcomes: one authority, fail-loud, zero dead readers, unchanged graph identity)
  • ✅ All acceptance scenarios are defined
  • ✅ Edge cases are identified (carve-out, synthetic-tier override, forbidden-pattern guards)
  • ✅ Scope is clearly bounded (C-002 out-of-scope list; SC-006 no-touch assertion)
  • ✅ Dependencies and assumptions identified (C-004 cross-mission order; Assumptions section)

Feature Readiness

  • ✅ All functional requirements have clear acceptance criteria (User Stories 1–3 + Success Criteria)
  • ✅ User scenarios cover primary flows (resolve → fail-closed; finish relocation; unify vocabulary)
  • ✅ Feature meets measurable outcomes defined in Success Criteria
  • ✅ No implementation details leak into specification beyond the specified seam boundary

Notes

occurrence_map.yaml is authored during /spec-kitty.plan.

ownership split at notes/pr3117-ci-failures.txt; source issues at notes/source-issues.txt.

scoped out (C-002) and sequenced after FR-010 lands (C-004).

  • This is a research-led structural mission; the "users" are the runtime, developers, and operators.
  • change_mode: bulk_edit is set (FR-008/009/012 are same-string cross-file repoints); the
  • Full research + design synthesis seeded at notes/research-synthesis.md; PR #3117 CI-failure
  • This is Mission 1 of 2; the sibling charter-pack-usage-journey mission (#3104/#3105/#3118) is