What's new in Readiness Engineering, Volume 4: Running the Workforce

The second half of The Build is now Volume 4: 17 chapters in three parts on operating a readiness workforce every day from dated records in Git, with every consequential decision left to a person. It follows Quarry Lane Health through a March simulation, hiring its site development representative through a paid work sample, and running the workforce until it reaches Run in September. You learn to run observation, enrichment, probes and the second research pass as jobs that read and write records, check every state change against its gate, and turn an operator’s correction into a rule and a test in the same commit. It ends with a second workforce and the automation line, moved only on evidence from your own records.

Run a readiness workforce every day from dated records in Git, and leave every decision that belongs to a person with a person. This volume follows Quarry Lane Health through a March simulation, the hire of its site development representative through a paid work sample, and the months until the workforce reaches Run in September, when it starts a partner workforce on shared rules. Each scheduled job, check and audit appears first as a prompt and then as the skill, MCP server or script that runs it, with the labeled cases it must pass before it runs unattended. You learn to run observation, enrichment, probes and the second research pass as jobs on records, check every state change against its gate and every contact against the suppression list, turn an operator’s correction into a rule and a test in the same commit, and build the Actionboard and audits from the records. It is for the operator running the workforce and the engineer supporting it.