Development record
The spec glossary says a spec is broken into ordered tasks; the build chapter breaks a spec into steps.
issuewontfixminoriss-2610262037031364
The spec glossary says a spec is broken into ordered tasks; the build chapter breaks a spec into steps.
A terminology drift (severity minor) found by the cross-document consistency pass.
- End A:
.abcd/development/brief/glossary/core/spec.md:4— "A specced block of work in abcd's native spec store that implements one or more intents, broken into ordered tasks with acceptance criteria." - End B:
.abcd/development/brief/04-surfaces/34-build.md:84— "the open spec's## Steps, read through the spec store's own reader, parses and leaves at least one step unlanded"
spec.md defines a spec as broken into ordered tasks. 34-build.md reads the spec's ## Steps section and lands the spec step by step. The unit below a spec is named task in one document and step in the other.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 694.
Grounds
- declined: Closed in the 2026-10-27 triage (dcn-2610271112330536) as a duplicate of iss-2610262033556324. Same End A; 34-build.md reads the spec's Steps section as expected.
Frontmatter
| id | iss-2610262037031364 |
|---|---|
| type | issue |
| lifecycle | wontfix |
| severity | minor |
.abcd/work/issues/wontfix/iss-2610262037031364-the-spec-glossary-says-a-spec-is-broken.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.