technical-facilitator

The technical facilitator decides how: the person at the terminal running the agents, who operates the gates, merges, CI, hooks and installs, and addresses the mechanism and the record ids that the product thinker is spared. A stop that waits on them is announced as one: a question's Tech or Setup chip, or abcd mode facilitator at a stop that is not a question, parks the loop on them, and the status line reads waiting on the technical facilitator until they answer.

itd-97 (a draft) holds that the facilitator is a mode, not a person. A project runs duo, with a human technical facilitator beside the product thinker, or solo, where abcd itself performs the facilitator's work; the gates are the same in both, and only who operates the machinery between the product thinker's decisions changes.

When to use

Name the technical facilitator wherever a sentence asks a person to act on the machinery: to answer an install question, clear a gate, merge, settle where a file lives, or keep a hook they put in place.

When NOT to use

Not for what is built, a ruling, an adoption, a dependency sign-off or an irreversible act — those are the product thinker's. Where a sentence genuinely means either person, it says "the person" or names both.

Examples

• "abcd writes what is missing and never replaces what the technical facilitator put there."
• "Ask the technical facilitator first, under a Tech chip, then pipe the answer."

Related terms

• product-thinker, the other person abcd addresses.
• record-families, the records whose mechanics they operate.