Development record
The spec glossary defines a spec as broken into tasks; the step glossary forbids 'task' for the unit below a spec.
issuewontfixminoriss-2610262040292997
The spec glossary defines a spec as broken into tasks; the step glossary forbids 'task' for the unit below a spec.
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/glossary/core/step.md:6— "forbidden_synonyms: ["task", "sub-task", "scope"]"
The spec entry's definition breaks a spec into ordered tasks, and its body says numbered tasks. The step entry makes the step the unit below a spec and lists 'task' and 'sub-task' as forbidden synonyms. So the glossary's own definition of spec uses a word the glossary forbids.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 934.
Grounds
- declined: Closed in the 2026-10-27 triage (dcn-2610271112330536) as a duplicate of iss-2610262033556324. Same End A and cause, seen from step.md's forbidden synonyms.
Frontmatter
| id | iss-2610262040292997 |
|---|---|
| type | issue |
| lifecycle | wontfix |
| severity | minor |
.abcd/work/issues/wontfix/iss-2610262040292997-the-spec-glossary-defines-a-spec-as.md
open on GitHub ↗ · commit history ↗
mentions2
- dcn-26102711123305362026-10-27 — The product thinker accepted on 2026-10-27 the triage of the 1301 records the 2026-10-26 consistency pass filed. The duplicates, the records a later record already settles, the ones that are no contradiction and the one already fixed are closed with each reader's reason. Every other record gets its fix as its remedy, the rulings' accepted answers included, so a drain can take it. The 45 major records left open are deferred past v0.15.1, because the brief's single-home rewrite rewrites or removes most of the passages they quote. The person ruled the major rulings one at a time; the minor rulings take their recommended answers.
- iss-2610262033556324The 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.