runbook

A practical guide for operating, troubleshooting, escalating, and recovering a deployed system — written so the support team can use it without the FDE in the room.
The runbook told support how to disable write-back if the CRM API failed.

override signal

A signal generated when users correct, reject, or bypass system output — one of the most valuable inputs for improving evals and workflow design.
The override signal revealed that the model misunderstood one policy clause.

implementation strategy

The plan for sequencing technical work, customer decisions, risks, rollout, and handoff so implementation reaches production efficiently.
The implementation strategy shipped read-only retrieval first and deferred automation.

operator

A technical operator. A person who interfaces with a business to figure out what needs to be automated how, then creates that automation (typically using some custom software and some existing software) and sees it through to successful production that improves the business' efficiency, profitability, or capabilities. This may be an engineer with business and communication skills and initiative.
That org moved its rote work from office tools to agents, so its people could focus on the things they do best as humans, as proof that the operator who made it happen really succeeded.

cutover

The switch from the old process or system path to the new deployed one.
The cutover happened after the last batch job completed.