Development record
The glossary says a spec is broken into ordered tasks with acceptance criteria; the intent chapter's spec stub carries Summary, Footprint and Steps sections and no criteria.
The glossary says a spec is broken into ordered tasks with acceptance criteria; the intent chapter's spec stub carries Summary, Footprint and Steps sections and no criteria.
A terminology drift (severity minor) found by the cross-document consistency pass.
- End A:
.abcd/development/brief/glossary/core/spec.md:4— "broken into ordered tasks with acceptance criteria" - End B:
.abcd/development/brief/04-surfaces/05-intent.md:203— "an empty## Stepssection (a spec listing no step is built as one step)"
glossary/core/spec.md defines a spec as 'broken into ordered tasks with acceptance criteria', decomposed into numbered tasks. 05-intent says planning mints a stub with a Summary placeholder, a Footprint section and 'an empty ## Steps section (a spec listing no step is built as one step)'. One page calls the unit below a spec a task and the other a step, which the glossary's own step entry forbids calling a task, and the stub carries no acceptance criteria.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 451.
Frontmatter
| id | iss-2610262033556324 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610262033556324-the-glossary-says-a-spec-is-broken-into.md
open on GitHub ↗ · commit history ↗
mentions3
- iss-2610262037031364The spec glossary says a spec is broken into ordered tasks; the build chapter breaks a spec into steps.
- iss-2610262040292997The spec glossary defines a spec as broken into tasks; the step glossary forbids 'task' for the unit below a spec.
- iss-2610262041427822The spec glossary entry says a spec breaks down into numbered tasks; the vocabulary intent made the step the unit below a spec.