Name What Broke

India Today reported in July 2026 that this job can pay up to a million dollars a year, and The Economic Times reported the same role at $200,000 two months before that, neither outlet saying whether its figure means base or package. Nobody agrees what a forward deployed engineer is, so nobody agrees what one is worth.

The Wall Street Journal, on 19 July 2026, headlined it "The hottest job in tech isn't very glamorous." That part is fair. You fly to somebody else's office, log into a network you do not control, and make their mess produce something. Demand is not the question. AWS has put a billion dollars into embedding engineers like this inside its customers, TCS is building a team of 8,900, and Google is hiring hundreds.

Here is the part no job ad mentions. What ends the engagement is almost never a model that failed. It is an ordinary afternoon when the thing you built returns a wrong number in front of the customer, and five parties can each make a defensible case that it was not them. The model. The runtime wrapped around it, which shipped twenty-six releases in the thirty days to 26 July 2026. The deterministic tool layer. The data going in. Your own code, which is the suspect nobody checks first. Everybody argues from memory. Nobody has a receipt.

This book builds the receipt. One command-line tool, fdectl, seven subcommands, twenty-one chapters, built against a corpus of authored inputs that disagree with each other four ways. Here is what got built, and what the laptop it was written on could not run.

Five sandbox probes state their expected verdict before running, and the boundary report's verdict column takes four values, so EXCLUDED and COULD NOT VERIFY reach the page. On the capture machine that report printed met 0, not met 2, unobtained 3, and one unobtained row had predicted a different failure from the one it hit. An MCP server on protocol revision 2025-11-25, written ahead of three documented removals and shipping one it cannot avoid as a declared exception; the only client that ever reached it is the book's own conformance runner. A deterministic Python layer where every result declares the inputs it read and the code path behind it, which is the code describing itself rather than anything observing it. A hook that decides six recorded PreToolUse payloads and writes a receipt an eval row can read; Claude Code never ran here, so the receipt records that a deny was returned, not that a command did not run. An eval suite that puts an owner on every failing row or writes UNATTRIBUTED and publishes the rate, over rows written by hand, because no session, container or live server could start here. A last chapter that installs the method into a repository in one line as seven rows, which over its own fixture tree print three READY, one UNATTRIBUTED, three NOT PROVEN.

Nothing in this book booted inside a customer's network. Appendix F is a register of thirty-two rows naming every gap, what stopped it, and the one piece of evidence that would close each one, and a program in the build refuses a row that names no such evidence. Ten of the nineteen host-blocked rows close on a laptop with docker and a route out. Two printed blocks, in this front matter and the preface, were captured by a person and diffed by no program.

The checkable pay numbers are stranger. Anthropic posts no title called Forward Deployed Engineer; the phrase appears once inside a requirements bullet on a posting that states $315,000 to $380,000, read 25 July 2026. Chapter 2 is about that gap between the phrase everybody uses and the titles anybody posts.