Summary

The question this episode answers: Why does the infrastructure component your team trusts most often carry the most hidden recovery risk — and how do you make that gap visible before the incident does?

The answer: Trust displaces testing. The components your team stopped worrying about are the components that stopped getting verified. The gap between a four-hour written RTO and a four-day real RTO is not a planning failure — it is a measurement failure. You measured the wrong thing under the wrong conditions and called it a recovery time objective. The fix is five specific questions, not more tooling.

What you will learn:

• Why the most-trusted parts of your infrastructure are structurally the most dangerous — the MGM 2023 pattern explained
• The three conditions that reliably inflate real RTO above written RTO
• Five questions that make hidden recovery risk visible without requiring a real incident
• The difference between backup-native and recovery-native architecture and why it determines your actual recovery time
• How to evaluate any backup or DR vendor against a single architectural test: does the recovery mechanism share failure modes with the thing it recovers from?

References:

• Dr. David Unwin, Teaspoon of Sugar infographic — open access, 35 languages: https://www.phcuk.org/sugar/
• Dr. David Unwin on The Diary of a CEO (source video): https://www.youtube.com/watch?v=9szCG0PW14c
• MGM Resorts 2023 ransomware incident public timeline: https://www.securityweek.com/mgm-resorts-ransomware-attack/
• Rediacc recovery audit — live restore test, no slides: https://www.rediacc.com/en/professional-services

About this episode: Published by Rediacc — self-hosted infrastructure with sub-60-second recovery. Book a recovery reality check at https://www.rediacc.com/en/professional-services

References

• Dr. David Unwin, Teaspoon of Sugar infographic — food, glycemic index, serving size, and sugar equivalents per serving. Available in 35 languages, open access, not copyrighted. — https://www.phcuk.org/sugar/
• Dr. David Unwin on The Diary of a CEO — the sugar cube demonstration that is the source for this episode's analogy. — https://www.youtube.com/watch?v=9szCG0PW14c
• MGM Resorts 2023 ransomware incident — public timeline of the attack and ten-day recovery period. SecurityWeek coverage. — https://www.securityweek.com/mgm-resorts-ransomware-attack/
• Rediacc recovery reality check — live restore test against your real environment, no slides. Book at rediacc.com/rto-audit. Code AUDIT30 for extended trial. — https://www.rediacc.com/en/professional-services

What This Episode Answers If technology has always enriched the owners and impoverished the renters, which side of that divide does your infrastructure put you on?

The Answer Ownership is the only durable answer to the K-shaped economy — and that principle scales from national energy policy all the way down to who controls your disaster recovery.

What You'll Learn

• Why the Engels Pause of 1790-1840 is the most instructive historical model for understanding AI disruption in 2026, and what the fifty-to-seventy-five-year pain window actually looked like
• How the theory of marginal productivity was commissioned by JP Morgan specifically to prevent workers from concluding they were underpaid — and how the same logic runs in cloud pricing today
• The Norway vs. UK North Sea oil decision as the direct structural precedent for infrastructure ownership choices being made this quarter
• Why AI's instant global deployment eliminates the adaptation window that allowed previous technology transitions to self-correct before social breakdown reached crisis levels
• What the active DOJ antitrust cases against Google and Amazon mean for recovery plans that depend entirely on the continued corporate integrity of one cloud provider
• The specific threat environment — ransomware spikes during economic transition, AI model weights as high-value extortion targets — that makes infrastructure resilience non-optional rather than best-practice

About This Episode Sourced from a two-and-a-half-hour debate between Nick Hanauer (venture capitalist, first major external investor in Amazon) and Daniel Priestley (entrepreneur, 5,500 businesses coached) on The Diary of a CEO, published June 8, 2026. Extended sovereignty assessment at https://www.rediacc.com/en/solutions/data-sovereignty

References

• The Diary of a CEO: 'EMERGENCY DEBATE: The Death Of The Middle Class! Only The Top 1% Will Survive!' — Nick Hanauer and Daniel Priestley, June 8 2026 — https://www.youtube.com/watch?v=uLBsHXNEwAU
• Henry George, Progress and Poverty (1879) — the best-selling book in US history at the time; foundational text on land rent as wealth extraction — https://openlibrary.org/works/OL60753W
• John Bates Clark, The Distribution of Wealth (1899) — introduced the theory of marginal productivity at JP Morgan's commission to counter Henry George — https://openlibrary.org/works/OL1117620W
• Adam Smith, The Wealth of Nations (1776) — Chapter 8 on wages: employer-worker power asymmetry recognized by capitalism's founding theorist — https://openlibrary.org/works/OL76827W
• Daron Acemoglu and James Robinson, The Narrow Corridor: States, Societies, and the Fate of Liberty — the 'narrow corridor' between laissez-faire capitalism and socialism as the optimal growth zone — https://en.wikipedia.org/wiki/The_Narrow_Corridor
• Friedrich Engels and the Engels Pause (1790-1840) — the period of stagnant real wages during early British industrialization despite surging aggregate output — https://en.wikipedia.org/wiki/Friedrich_Engels
• Charles Dickens, Oliver Twist and A Tale of Two Cities — cited as literary products of the Jevons Paradox / Industrial Revolution displacement era — https://en.wikipedia.org/wiki/Charles_Dickens
• William Stanley Jevons and the Jevons Paradox — agricultural mechanization as the structural model for AI-driven labor displacement — https://en.wikipedia.org/wiki/Jevons_paradox
• Nick Hanauer, 21st Century Economics — free download at marketsbuiltforhumans.org; the alternative economic paradigm for human flourishing over capital efficiency — https://marketsbuiltforhumans.org
• Anthropic economic impact report on AI and entry-level employment (DOI: 10.2139/ssrn.5453694) — https://doi.org/10.2139/ssrn.5453694
• DOJ v. Google LLC — search monopoly liability finding; remedy phase ongoing as of 2026 — https://en.wikipedia.org/wiki/United_States_v.Google_LLC(2023)
• Lloyds Banking Group / Citra Living — 70,000 UK homes purchased for permanent rental income strategy — https://en.wikipedia.org/wiki/Lloyds_Banking_Group

Summary

The question: When a political system loses control of its military — when there is no center capable of making and honoring an agreement — what infrastructure survives?

The answer: Distributed, isolated cells. Iran's Mosaic Defense operates as 31 independent provincial units with no centralized command. Even if Iran's political leadership signs a ceasefire, the IRGC cells in the field do not have to honor it. The center cannot compel the cells. This is not a diplomacy failure — it is architecture. And it is the same architecture principle that determines which infrastructure survives a determined attacker.

What you'll learn:

• Why Iran's 31-cell Mosaic Defense makes a ceasefire structurally impossible — and what that means for your workload isolation strategy
• How the vassal-state pattern (GCC as externally constructed prosperity vs. Iran as internally cohesive isolation) maps directly to cloud-dependent vs. self-hosted infrastructure
• Why no nation will replace the US as the global trade enforcer — the system fractures, not transitions — and what that means for every cloud contract built on that assumption
• Why technology-only defense strategies fail against determined distributed attackers, and why architecture contains what tools can only detect
• The concrete audit to run this week: count how many production workloads share a control plane, a snapshot target, and a geographic cluster with their backup

References: See below.

Chapters: See timestamps below.

About this episode: The Mosaic Architecture Assessment discussed in this episode is available at rediacc.com/mosaic through July 2026.

About the show: Discontinuity is a weekly briefing on infrastructure resilience, published by Rediacc. This show is published by Rediacc OÜ. The narrator is an AI library voice rendering research the team writes. Sponsor reads are for Rediacc's own products.

References

• Professor Jiang, Game Theory #20: Mid-Term Examination, Predictive History (YouTube) — https://www.youtube.com/watch?v=ue8y5e3HnHE
• Quran, Surah Al-Anfal (8), verse 60 — 'And prepare against them whatever you are able of power' — https://quran.com/8/60
• Quran, Surah Ar-Ra'd (13), verse 11 — 'Indeed, Allah will not change the condition of a people until they change what is in themselves' — https://quran.com/13/11
• AWS me-south-1 (Bahrain), Azure UAE North (Dubai), Azure UAE South (Abu Dhabi), GCP me-central1 (Doha) — 250,000+ workloads at geopolitical risk per 2100 business impact analysis — https://aws.amazon.com/about-aws/global-infrastructure/regions_az/
• GDP impact modeling: Strait of Hormuz disruption -0.5% to -2.0% of global GDP within 90 days (duration-dependent); 21 million barrels per day throughput at risk — https://www.eia.gov/todayinenergy/detail.php?id=56920
• JD Vance, quoted on Israel-Lebanon strikes after US-Iran ceasefire: 'a legitimate misunderstanding' — CBS News, 2026 — https://www.cbsnews.com

The Question When the same structural force that hollowed out the middle class hits your infrastructure budget, which architectural decisions survive the squeeze?

The Answer The disintermediation mechanism — technology closing information asymmetries until a middleman's revenue position collapses — has moved from labor markets into corporate IT infrastructure. Cloud hyperscalers, legacy backup vendors, and per-seat SaaS layers are now in the lag phase: still extracting rent, but doing so via switching cost rather than technical necessity. The ownership exit — self-hosted, verifiable, recoverable infrastructure — changes the compounding arithmetic in your favor.

What You'll Learn

• Why the economic mechanism that eliminated middle-class jobs and the current cloud cost crisis are the same structural event, one decade apart
• How the rent-trap arithmetic works in legacy backup contracts — and why switching cost feels higher than it actually is
• Why AI production velocity has made the weekly staging environment the next middleman to be eliminated
• What the clone-on-demand model looks like architecturally and why the sixty-second threshold is the key variable
• Why verifiability — the ability to run a real recovery test on a Tuesday afternoon — is the compliance property you can't get from rented infrastructure
• The three-number audit: renewal date, cloud bill growth rate, and last tested recovery date

References

• Diary of a CEO: "Will the Middle-Class Be Wiped Out?" — Daniel Priestley vs. Nick Hanauer, hosted by Steven Bartlett (June 10, 2026): https://www.youtube.com/watch?v=4sN_zR8Vf94
• Rediacc product documentation: https://rediacc.com
• Infrastructure cost comparison tool: https://rediacc.com/own-your-stack

About This Episode This episode connects the macroeconomic disintermediation pattern to infrastructure architecture decisions — specifically backup and recovery. Use code OWNIT30 at rediacc.com/own-your-stack for the infrastructure cost comparison tool.

The question this episode answers: When an AI agent has write access to your production system and it's wrong — what survives?

The answer: The teams that survive machine-speed engineering are the ones who never gave AI agents access to the original — only to a tested copy they can walk away from in under sixty seconds.

What you'll learn:

• Why 'capability without judgment' is an infrastructure risk category, not just a philosophical observation
• The three specific failure modes AI agents create in production: schema events, data modification, and secret leakage
• Why the blast radius of an AI mistake is velocity-shaped, not magnitude-shaped
• What zero-trust applied to non-human actors actually requires architecturally
• The three tests an isolated AI-agent environment must pass to be genuinely useful
• How recovery speed determines whether containment is sustainable as a daily practice — not just a policy on paper

References:

• John Lennox interview, 'Does This Prove That God Is Real?', Diary of a CEO with Steven Bartlett (June 2026): https://www.youtube.com/watch?v=dBb_Xxj37VQ
• John Lennox, '2084: Artificial Intelligence and the Future of Humanity', Zondervan (2020): https://www.zondervan.com/9780310109761/2084/
• Jesus Christ — first-century historical figure referenced in Lennox's personal testimony on forgiveness: https://en.wikipedia.org/wiki/Jesus

About this episode: Built for the CTO, CISO, or founder running AI agents in production-adjacent environments who hasn't yet done a formal audit of what those agents can touch and modify. The AI-agent containment assessment is at rediacc.com/ai-safety.

About this show: Discontinuity is a weekly briefing on infrastructure resilience, published by Rediacc. The narrator is an AI library voice rendering research the team writes. Sponsor reads are for Rediacc's own products.