Chapter summary
Chapter 9 is the implementation manual. The entire essay distills into ten interlocking gears: build the targeting system, pay for results, pre-commit compute in escrow, build action networks (robotic labs and micro-factories), pool data through trusts, demand immutable decision logs, enforce the two-source rule for critical decisions, co-locate power and intelligence, design fairness into targets, and teach civic intelligence literacy. The chapter then delivers role-specific playbooks for seven stakeholder classes. National leaders charter Capability Accounts and launch Compute-for-Outcomes Auctions within 90 days. Mayors publish City Outcome Ledgers with weekly dashboards on water, power, education, and health. Health system operators automate evaluation before action, tying AI authority to live safety scores. Infrastructure operators define reliability targets measured in outage-minutes avoided. Industrial leaders enforce 24-hour design-to-part delivery and two-source verification. Investors shift from venture capital (betting on apps) to infrastructure capital (betting on rails — targeting platforms, auditing tools, data trusts, action networks). Citizens join data trusts and demand benchmark transparency from every institution that holds power over them. The chapter then names what must stop: innovation theater, vanity scorecards, effort-based procurement, single-provider dependence, secret model changes, and data systems without safety throttles. Funding requires no new money — 1% national budget reallocation to outcome procurement, 10% city capital budgets tied to results, and philanthropic conversion to payment-for-clear prizes. Success metrics shift from effort to impact: student retention over seat-hours, healthspan over treatment volume, outage-minutes avoided, cost per ton of carbon removed, and safety-brake trigger frequency.
Key frameworks or claims
- Ten gears of the abundance engine: Targeting, outcome payment, compute escrow, action networks, data pooling, decision logs, two-source rule, power-compute co-location, fairness-by-design, civic literacy. All ten must mesh simultaneously.
- Stakeholder playbooks with 90-day/6-month/1-year cadences: Concrete first moves for each role, not abstract principles.
- Innovation theater as the enemy: Meetings, proposals, and press releases that feel like progress but solve nothing. The explicit anti-pattern.
- Before Monday Noon: Pick one outcome metric and publish it. Draft a Target Charter. Propose one outcome-based contract. Open a Compute Escrow line item. Write the first Decision Log template.
- Funding by reallocation: The capital exists but is trapped in low-efficiency systems. No new money required.
RDCO strategic mapping
The ten-gear framework is the most operationally useful artifact in the entire essay for RDCO. It maps directly to how the autonomous agent stack should be evaluated: does each tool we adopt have a targeting system, outcome-based success criteria, and a decision log? The “innovation theater” concept is a sharp editorial weapon for Sanity Check — many AI launches are exactly this pattern. The investor playbook (own primitives, not applications) reinforces the strategic logic behind RDCO focusing on evaluation and frameworks rather than building commodity AI apps. The “Before Monday Noon” section is a template for closing Sanity Check issues: give the reader one concrete action they can take immediately, not a vague call to “stay curious.”
Related
- book-solve-everything-ch8-muddle-vs-machine-2026-04-13
- book-solve-everything-ch7-the-moonshots-2026-04-13
- book-solve-everything-epilogue-quiet-hum-2026-04-13
- book-solve-everything-ch2-the-thesis-2026-04-13
- 2026-04-12-harrison-chase-harness-blog
- synthesis-harness-thesis-dissent-2026-04-12