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.
The runbook told support how to disable write-back if the CRM API failed.
The forward deployed engineering manager moved an engineer onto the account when the rollout became production-critical.
The FDE wrote an MCP connector for the internal knowledge base.
The override signal revealed that the model misunderstood one policy clause.
The implementation strategy shipped read-only retrieval first and deferred automation.
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.
The escalation path sent tool failures to the platform owner, not the business sponsor.
The cutover happened after the last batch job completed.