The record uses several of its own words in more than one sense, and a product thinker cannot tell them apart from the brief alone. 'Phase' names a roadmap phase (an ordered stretch of work ending in a milestone, phases/phase-N-slug.md) and also the brief's plumbing phases that a roadmap phase bundles (phases/README.md, 'which intents and which brief plumbing-phases this phase bundles'); tonight two different documents both claimed the number 7 and two more the number 8. 'Plan' names the intent verb (abcd intent plan, the maintainer's sign-off that mints a spec) and also the roadmap as a build plan, and a session's own plan. 'Roadmap' holds phases and rfcs but the dashboard reads the spec store. 'Record' means the whole development record and also one file in a family. 'Surface' means a verb's front door and also the brief's surface chapters. 'Closed loop', 'ledger', 'construal' and 'reading position' appear with no first-use definition outside the chapter that coins them. Ask: one glossary entry per term in the brief's glossary (or a glossary chapter if none exists), each with the senses it carries and the one spelling used for each sense, referenced from phases/README.md and the intent surface page; the site export links terms to it. Surfaced at the 2026-09-01 interview when the maintainer could not follow questions that used these words unexplained.

The record uses several of its own words in more than one sense, and a product thinker cannot tell them apart from the brief alone. 'Phase' names a roadmap phase (an ordered stretch of work ending in a milestone, phases/phase-N-slug.md) and also the brief's plumbing phases that a roadmap phase bundles (phases/README.md, 'which intents and which brief plumbing-phases this phase bundles'); tonight two different documents both claimed the number 7 and two more the number 8. 'Plan' names the intent verb (abcd intent plan, the maintainer's sign-off that mints a spec) and also the roadmap as a build plan, and a session's own plan. 'Roadmap' holds phases and rfcs but the dashboard reads the spec store. 'Record' means the whole development record and also one file in a family. 'Surface' means a verb's front door and also the brief's surface chapters. 'Closed loop', 'ledger', 'construal' and 'reading position' appear with no first-use definition outside the chapter that coins them. Ask: one glossary entry per term in the brief's glossary (or a glossary chapter if none exists), each with the senses it carries and the one spelling used for each sense, referenced from phases/README.md and the intent surface page; the site export links terms to it. Surfaced at the 2026-09-01 interview when the maintainer could not follow questions that used these words unexplained.

Grounds

• pursued: we expect a product thinker to follow a question that uses these words once the glossary fixes one spelling per sense; it is wrong if a reader still has to ask which phase or which plan is meant, or if the record keeps minting new senses the entries do not catch.