The step intent says `implement step` and the spec's Steps section share one word; the step glossary entry says `implement step` performs a stage, not a step.

The step intent says implement step and the spec's Steps section share one word; the step glossary entry says implement step performs a stage, not a step.

A naming conflict (severity minor) found by the cross-document consistency pass.

• End A: .abcd/development/brief/glossary/core/step.md:18 — "abcd implement step performs one stage, not one step"
• End B: .abcd/development/intents/shipped/itd-2609212103565953-a-spec-lists-its-steps-and-the-build.md:43 — "implement step (the loop's step interface) and this section share the word, and the command page says so."

The shipped intent rules that the loop's implement step interface and the spec's ## Steps section share the word 'step', and that the command page says so. The glossary entry rules the opposite. In the build loop the word names only the spec's piece, and abcd implement step performs one stage of a lane. The two documents give the word one shared sense and two separate senses, so a reader of the intent will take implement step to land a spec step.

Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 1018.

Grounds

• declined: Closed in the 2026-10-27 triage (dcn-2610271112330536): a later record already settles which end holds. The resolved issue says which holds and why; the glossary was rewritten to match and the code and payloads use performed_stage and stage.