Field assignment 10 · Weaponizing Bureaucracy

Pre-build the binder before you're asked. Inherit one compliance control instead of re-earning it.

Boss you'll face with this work: The Innovation Lead · practice the pitch →

Brief 10 — use it at work

GHOST reviews the answer in-character (“that's a vitamin, not a tourniquet — find the bleeding neck”). Your text is sent to the Claude API for the reply only; it is never stored server-side.

The math for this assignment

Audit Defense Score

D_audit · Ch 11

(Certifications × scope) ÷ auditor fear. Make saying NO riskier than saying YES.

Worked example — Security review, and a nervous auditor

You carry SOC 2 Type II and a current pen test, and you inherit your cloud provider's FedRAMP controls — three real, independent attestations. They cover about 6 of 10 of what's in scope. The auditor has been burned before and it shows.

It came out at 6.0. Green — rubber-stamp territory.

Leave that auditor's fear at 8 instead of working it down and the identical paperwork reads 2.25 — yellow, and a quarter in review. By then the certifications are fixed and the fear isn't. Bring the comparison matrix; make saying no the riskier option.

Your turn — change one number

Real independent attestations you carry (count — inherited controls count)3

Scope coverage (1–10)6

Auditor fear (1–10)3

Result6.00

Green. Rubber stamp. Bring the comparison matrix anyway.

Book's benchmark: 🟢 ≥ 4 (rubber stamp) · 🟡 1.5–3.9 · 🔴 < 1.5 (rejection).

From the module

REAPER flags ZERO as "anomalous vendor behavior"; an audit opens. She walks in with a 3-inch compliance binder and a matrix showing she beats the legacy vendor. 45 minutes. The flag is downgraded. BISHOP adjusts his crooked badge and walks away.

Re-read Weaponizing Bureaucracy →

← assignment 9 assignment 11 →