The load-check intent defines a stray as a process outside abcd's lanes at near full CPU; the implement chapter defines it by a share of the process's fair share, a 0.4-core loop included, with nothing exempt by name.

The load-check intent defines a stray as a process outside abcd's lanes at near full CPU; the implement chapter defines it by a share of the process's fair share, a 0.4-core loop included, with nothing exempt by name.

A terminology drift (severity minor) found by the cross-document consistency pass.

• End A: .abcd/development/brief/04-surfaces/27-implement.md:240 — "a lifetime CPU share of at least 0.9 of it makes a stray: forty busy loops on 16 cores, each at 0.4 of a core, are all strays"
• End B: .abcd/development/intents/shipped/itd-2609231434459890-abcd-s-own-test-lanes-check-the-machine.md:70 — "a process outside abcd's own lanes at near full CPU for longer than the stray limit"

itd-2609231434459890 defines the stray trigger as a process outside abcd's own lanes at near full CPU for longer than the stray limit. 27-implement.md defines a stray as a process whose lifetime CPU share reaches 0.9 of its fair share of the machine as loaded, so forty loops at 0.4 of a core each on 16 cores are all strays, and it exempts nothing by name: abcd's own lanes are exempt only by time. The word stray names a different set of processes in each document.

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

Grounds

• declined: Closed in the 2026-10-27 triage (dcn-2610271112330536): a later record already settles which end holds. The brief cites the later ruling by id and the issue is resolved with a spec and commit; the intent's looser phrase is the pre-ruling form of the same trigger.