RESHUFFLE An interactive companion to the book
Cascade ▸ from d-o3-decision-rights-evolution

How do decision rights evolve continuously?

D-layer dynamics: continuous redistribution of decision rights as AI capability evolves.

visited
63
edges
74
hops
3
chains
4 / 4
failure modes
2
counters
1
gates
27
d-o3-decision-rights-evolution state-evolution-mechanism

Decision-Rights State Evolution (O3)

Jobs D Org D
The continuously-evolving distribution of the five Coordination Powers and the Unified Action Scaffold across humans, teams, and AI. Decision rights are not redistributed once - they continuously shift driven by D2 (worker agency demanding new authority), D4 (new dependencies create new rights questions), D5 (governance at finer granularity), and D6 (external valuation shifts which rights matter). The node-shaped home for O3's continuous evolution.
lineage principal-agent-theory:jensen-meckling + coase + management-control-theory

Reading the cascade

Decision rights don't move in a single redistribution event - they evolve continuously as AI capability shifts, as humans recontribute, and as competitive valuation reshuffles. D-O3 Decision-Rights State Evolution is the D-layer dynamic that models this continuous movement. This cascade is small but structurally important - it shows how the dynamics layer interacts with the org chain.

Figure. Where the cascade fires. Cells colored by activity intensity (none / light / medium / heavy). Status flags mark cells containing failure modes (🔴), counter-strategies (🟢), gates (), or dimension shifts (). The arrow shows the reading direction.
outside-in
hop 1 immediate
hop 2 2nd hop
hop 3 3rd hop
1st-order Competitive Ecosystem
1
8
10 🔴 🟢
2nd-order Organizations
2
12
12 🔴 🟢
3rd-order Workflows
2
11
15 🔴 🟢
4th-order Jobs (workers)
1
9
15 🔴
inside-out
hop 1 immediate
hop 2 2nd hop
hop 3 3rd hop
1st-order Jobs (workers)
1
9
15 🔴
2nd-order Workflows
2
11
15 🔴 🟢
3rd-order Organizations
2
12
12 🔴 🟢
4th-order Competitive Ecosystem
1
8
10 🔴 🟢

How it plays out, mechanism by mechanism

The cascade's load-bearing causal links, in order of how they fire. Each link names the actual mechanism - the carrier, the channel, the why - not just the relationship.

Hop 3 3rd hop · 2 mechanisms
  • Vertical-Specificity Gating Condition vertical-specificity-gate cross layer driver Workflow Modularity Degree workflow-modularity-degree 🔀 industry→workflow

    The book's Earth AI mining case suggests that highly vertical industries support deeper workflow modularity - Earth AI bundles AI prediction with drilling and verification because the vertical specifics permit and reward integration. In contrast, horizontal industries with weak vertical specifics struggle to modularize workflows beyond shallow layers. Industry-level vertical specificity gates how deeply workflows can be unbundled.

  • Coordination coordination cross layer driver Cost-Collapse Mechanism (propagation of coord cost drop) cost-collapse-mechanism 🔀 workflow→workflow

    The book treats org-level coordination architecture as the precondition for workflow-level cost collapse. Without internal coordination - knowledge management, shared representation, agentic execution within teams - the workflow-level cost collapse has nowhere to land. Ramp restructured its own teams around agentic execution before the workflows it ran could collapse coordination cost for customers. Internal coordination is the substrate.

Where this fires in the wild

Real-world cases where the cascade has played out (or where it's currently playing out). The abstract primitives become concrete when you can see the mechanism firing at a named entity in a specific year.

From the book 2022-2025

Ramp redistributes expense decision rights to agents

Ramp

Ramp's expense routing doesn't ask managers to approve every receipt - agentic-execution evaluates policy compliance, vendor history, and budget context, then auto-approves or escalates. Decision-power redistributed from line manager to agent; unified-decision (the AI's verdict) feeds unified-execution (the auto-payment). The cascade fires through the D-layer: decision-rights state evolves continuously as the agent's confidence envelope widens, driven by D2 (worker demanding less approval friction) and D5 (governance moving to finer per-expense granularity).

  • d-o3-decision-rights-evolution
  • unified-decision
  • unified-execution-seamless
  • scope-expansion
Validation walkthrough 2022-2025

Mastercard centralizes fraud decision rights to the network

Mastercard

Mastercard's Decision Intelligence Pro (Feb 2024, gen-AI scanning ~1T data points) shifted fraud-scoring decision rights from individual issuing banks to the network operator. Issuers now accept/reject against Mastercard's score rather than running independent decisions. The D-layer dynamic is explicit: as Mastercard's model improved, decision-rights state evolved - unified-decision migrated network-ward, then scope-expansion kicked in as Account Intelligence sold the same decision substrate to non-bank customers. Decision rights compound when one party holds the coordination substrate.

From the book 2017-2024

Uber Freight pulls dispatch decision rights to the algorithm

Uber Freight

Pre-platform truckers held meaningful decision rights - which load, which broker, which lane, which price. Uber Freight pulled those rights into the algorithm: load assignment, pricing, routing, and acceptance-rate gating all became platform decisions. The cascade fires through workflow-governance-locus-shift - governance moved from trucker to whoever holds the algorithm - and gate-evolution-mechanism: the gates to participate stopped being skill, reliability, and relationships and became algorithmic metrics. D-layer rate-mismatch in plain sight.

  • d-o3-decision-rights-evolution
  • workflow-governance-locus-shift
  • gate-evolution-mechanism
  • algorithmic-management

Reading from your position

Pick where you sit in this cascade. Same primitives, completely different read - what you cause, what's coming for you, and what counter-moves you can wield.

+3 absent actors

These actors don't appear in this cascade: Solution Provider, Complementor, Worker (Below the Algorithm).

As Worker (Above the Algorithm) ⚖ mixed

As Worker (Above the Algorithm), the cascade is mixed for you - 0 capabilities and 1 threat both fire.

You direct or govern AI - strategy, judgment, design, taste, exception-handling, system-of-work ownership.

You are here

  • above-the-algorithm-vs-below-the-algorithm
  • rebundled-role

What you cause

Your position doesn't cause downstream effects in this cascade - you're at the receiving end.

What's coming for you

  • 🔴 AI Commoditization hop 3 · Jobs (workers)

What's available to you

No specific counter-strategies for your position appear in this cascade.

As Tool Provider ⚖ mixed

As Tool Provider, the cascade is mixed for you - 1 capability and 1 threat both fire.

Foundation-model providers, infrastructure layers, AI primitives - you sell capability that others integrate.

You are here

  • ai-as-an-engine

What you cause

Your position doesn't cause downstream effects in this cascade - you're at the receiving end.

What's coming for you

  • 🔴 Antitrust + Platform-Regulation Gating Condition hop 2 · Competitive Ecosystem

What's available to you

  • 🟢 AI Commoditization hop 3 · Jobs (workers)

Gates that decide your fate

  • Antitrust + Platform-Regulation Gating Condition

    Antitrust + platform-regulation evolves slowly (multi-year cases) while ecosystem-orchestrator emergence (D6) plays out in quarters - large mismatch makes regulatory gates binding on I4 emergence.

As Ecosystem Orchestrator 🔴 threatened

As Ecosystem Orchestrator, you're on the receiving end of this cascade. 2 threats surface against your position. 0 counter-strategies are available.

Platforms, marketplaces, ecosystem leaders - you coordinate complementors around a value proposition you own.

You are here

  • the-coordinated-organization

What you cause

Your position doesn't cause downstream effects in this cascade - you're at the receiving end.

What's coming for you

  • 🔴 Antitrust + Platform-Regulation Gating Condition hop 2 · Competitive Ecosystem
  • 🔴 Data-Network-Effects Gating Condition hop 2 · Competitive Ecosystem

What's available to you

No specific counter-strategies for your position appear in this cascade.

Gates that decide your fate

  • Antitrust + Platform-Regulation Gating Condition

    Antitrust + platform-regulation evolves slowly (multi-year cases) while ecosystem-orchestrator emergence (D6) plays out in quarters - large mismatch makes regulatory gates binding on I4 emergence.

  • Data-Network-Effects Gating Condition

    Data-network-effects strength evolves over years (data accumulation cycles) while AI capability (D1) shifts continuously - mismatch determines whether orchestrator emergence stabilizes.

As Incumbent Firm ⚖ mixed

As Incumbent Firm, the cascade is mixed for you - 1 capability and 2 threats both fire.

Established firms with legacy advantages, embedded customer relationships, and the burden of pre-AI structure.

You are here

  • the-coordinated-organization

What you cause

Your position doesn't cause downstream effects in this cascade - you're at the receiving end.

What's coming for you

  • 🔴 Legacy-Workflow Rigidity Gating Condition hop 2 · Workflows
  • 🔴 AI Commoditization hop 3 · Jobs (workers)

What's available to you

  • 🟢 System Integration hop 3 · Organizations

Gates that decide your fate

  • Legacy-Workflow Rigidity Gating Condition

    Workflow system state accumulates over decades; capability needs (D3) shift in months - canonical incumbent rate-mismatch at workflow scale.

As AI-Native Entrant ⚖ mixed

As AI-Native Entrant, the cascade is mixed for you - 2 capabilities and 3 threats both fire.

AI-first firms unburdened by legacy structure - fast-clockspeed startups and AI-native verticals.

You are here

  • ai-native-firm

What you cause

Your position doesn't cause downstream effects in this cascade - you're at the receiving end.

What's coming for you

  • 🔴 Network-Effects Strength Gating Condition hop 2 · Competitive Ecosystem
  • 🔴 Vertical-Specificity Gating Condition hop 2 · Competitive Ecosystem
  • 🔴 AI Commoditization hop 3 · Jobs (workers)

What's available to you

  • 🟢 AI-Driven Rebundling hop 3 · Jobs (workers)
  • 🟢 System Integration hop 3 · Organizations

Gates that decide your fate

  • Vertical-Specificity Gating Condition

    Vertical specificity is a slowly-changing industry property; horizontal-AI capability (D1) improves fast - mismatch determines vertical-vs-horizontal industry winner.

  • Network-Effects Strength Gating Condition

    Network-effects strength is a slowly-changing industry property; AI deployment (D1) changes fast - mismatch determines whether AI flywheels can establish lock-in.

1st-order Competitive Ecosystem

Light activity. The industry scale appears only because decision-rights evolution interacts with industry-level framing-error and compounding-vs-cascading-effects. By hop 3 a few industry-scale primitives connect, but this cascade is not industry-driven.

2nd-order Organizations

The org scale is where decision-rights evolution does its work. At hop 1, unified-decision activates - the AI-mediated decision pattern that reshapes who decides what. By hop 2 the coordination-paradox and unified-execution-seamless appear; by hop 3 the structural consequences land - coordination-tax, coordination-gap, scope-expansion, and the firm-level compounding-vs-cascading-effects.

3rd-order Workflows

Workflows are the operating layer for decision-rights evolution. At hop 1 the D-RM rate-mismatch fires here - decision-rights evolve faster than the workflow systems housing them. By hop 2 the framing-error common to AI-era decision allocation appears (treating AI as just a faster human decision-maker). By hop 3 the structural consequences land at workflow scale.

4th-order Jobs (workers)

Worker effects are minimal: only one node at hop 1 and hop 3. Decision rights evolve mostly above the worker level, though workers feel the consequences through which decisions they retain authority over.

1st-order Jobs (workers)

Worker effects are minimal: only one node at hop 1 and hop 3. Decision rights evolve mostly above the worker level, though workers feel the consequences through which decisions they retain authority over.

2nd-order Workflows

Workflows are the operating layer for decision-rights evolution. At hop 1 the D-RM rate-mismatch fires here - decision-rights evolve faster than the workflow systems housing them. By hop 2 the framing-error common to AI-era decision allocation appears (treating AI as just a faster human decision-maker). By hop 3 the structural consequences land at workflow scale.

3rd-order Organizations

The org scale is where decision-rights evolution does its work. At hop 1, unified-decision activates - the AI-mediated decision pattern that reshapes who decides what. By hop 2 the coordination-paradox and unified-execution-seamless appear; by hop 3 the structural consequences land - coordination-tax, coordination-gap, scope-expansion, and the firm-level compounding-vs-cascading-effects.

4th-order Competitive Ecosystem

Light activity. The industry scale appears only because decision-rights evolution interacts with industry-level framing-error and compounding-vs-cascading-effects. By hop 3 a few industry-scale primitives connect, but this cascade is not industry-driven.

This cascade has no counter-strategies - decision-rights evolution is a structural dynamic, not something countered by individual moves. The structural read: when D-RM rate-mismatch fires (hop 1), the firm's decision-rights allocation lags the capability shift; this lag is the source of much AI-era org dysfunction. What to watch: whether your firm's decision-rights allocation has been explicitly redesigned for AI-enabled coordination, or whether you're operating on pre-AI rights with AI tools.

Gates that may bind this cascade

Gates are external constraints. When the cascade touches a gating-condition, the D-RM rate-mismatch binding mechanism explains why it binds.

  • Capital-Availability Gating Condition capital-availability-gate
    bound by d8-driver-state-rate-mismatch

    capital deployment timing has its own lag relative to capability frontier shifts - mismatch determines deployment-rate gating

  • Antitrust-Regulation Gating Condition antitrust-regulation-gate
    bound by d8-driver-state-rate-mismatch

    antitrust state evolves slowly while tool-provider concentration (D6) shifts fast - mismatch determines whether intervention can be timely

  • Public-Sector Restructure-Constraints Gating Condition public-sector-restructure-constraints-gate
    bound by d8-driver-state-rate-mismatch

    public-sector procurement + civil-service rules evolve over electoral/political cycles while capability frontier shifts continuously - extreme mismatch

  • Cross-Org Data-Rights Gating Condition cross-org-data-rights-gate
    bound by d8-driver-state-rate-mismatch

    Data-rights legal state evolves slowly (case law, regulation) while cross-org workflow demand (D4) explodes - mismatch makes data-rights a binding gate on whether workflow ownership can be shared.

  • Industry-Regulation Gating Condition industry-regulation-gate
    bound by d8-driver-state-rate-mismatch

    regulatory state evolves slowly while AI capability (D1) evolves fast - large mismatch makes regulation a binding gate

  • Legacy-Workflow Rigidity Gating Condition legacy-workflow-rigidity-gate
    bound by d8-driver-state-rate-mismatch

    Workflow system state accumulates over decades; capability needs (D3) shift in months - canonical incumbent rate-mismatch at workflow scale.

  • Cultural Acceptance Gating Condition cultural-acceptance-gate
    bound by d8-driver-state-rate-mismatch

    cultural state evolves slowly while competitive valuation (D6) shifts fast - generational mismatch makes culture a binding gate

  • Antitrust + Platform-Regulation Gating Condition antitrust-and-platform-regulation-gate
    bound by d8-driver-state-rate-mismatch

    Antitrust + platform-regulation evolves slowly (multi-year cases) while ecosystem-orchestrator emergence (D6) plays out in quarters - large mismatch makes regulatory gates binding on I4 emergence.

  • Data-Residency Gating Condition data-residency-gate
    bound by d8-driver-state-rate-mismatch

    Regulatory state shifts slowly (multi-year) while AI capability (D1) shifts continuously - large mismatch makes data-residency a binding gate.

  • Workforce Buy-In Gating Condition workforce-buy-in-gate
    bound by d8-driver-state-rate-mismatch

    workforce bargaining-position state shifts slowly while task displacement (D1) shifts fast - mismatch determines whether workforce can re-engage in time

  • Collective-Bargaining Strength Gating Condition collective-bargaining-strength-gate
    bound by d8-driver-state-rate-mismatch

    bargaining-power state shifts slowly while task displacement (D1) shifts fast - mismatch determines whether labor can re-bargain in time

  • Professional-Licensing Gating Condition professional-licensing-gate
    bound by d8-driver-state-rate-mismatch

    licensing-jurisdiction state evolves slowly while task susceptibility (D1-driven) shifts fast - mismatch makes licensing a binding gate

  • Workflow Trust Gating Condition workflow-trust-gate
    bound by d8-driver-state-rate-mismatch

    Trust state evolves slowly while workflow restructure (D1+D4) shifts fast - mismatch makes trust a binding gate on cross-org workflow.

  • Regulatory-Permission-to-Restructure Gating Condition regulatory-permission-to-restructure-gate
    bound by d8-driver-state-rate-mismatch

    sector regulation evolves slowly while AI capability (D1) shifts fast - large mismatch makes regulation a binding gate

  • Leadership AI-Literacy Gating Condition leadership-ai-literacy-gate
    bound by d8-driver-state-rate-mismatch

    leadership-state evolves slowly while AI capability (D1) evolves fast - mismatch makes leadership literacy a binding gate

  • Interop-Standards Gating Condition interop-standards-gate
    bound by d8-driver-state-rate-mismatch

    Standards-setting cycles run multi-year while platform competition (D6) plays out in months - mismatch makes standards gates pivotal at W5.

  • Org Restructure-Capacity Gating Condition org-restructure-capacity-gate
    bound by d8-driver-state-rate-mismatch

    org-structure state evolves slowly while capability needs (D3) shift fast - mismatch is the incumbent's-dilemma rate problem

  • Regulatory-Permission-to-Cross-Industry-Boundaries Gating Condition regulatory-permission-to-cross-industry-boundaries-gate
    bound by d8-driver-state-rate-mismatch

    Cross-boundary regulation evolves over electoral cycles while AI capability to dissolve boundaries (D1) shifts continuously - extreme mismatch in regulated cross-industry plays.

  • Board-Level AI-Literacy Gating Condition board-level-ai-literacy-gate
    bound by d8-driver-state-rate-mismatch

    board composition + literacy state evolves over multi-year cycles while competitive valuation (D6) shifts continuously - mismatch determines strategic-AI-decision quality

  • Regulated-Process Permission Gating Condition regulated-process-permission-gate
    bound by d8-driver-state-rate-mismatch

    Sector regulation evolves over electoral cycles while AI capability shifts continuously - extreme mismatch in regulated workflows.

  • Legacy-Systems Restructure-Ability Gating Condition legacy-systems-restructure-ability-gate
    bound by d8-driver-state-rate-mismatch

    technical debt accumulates over decades; capability needs (D3) shift in months - mismatch is the canonical incumbent technical constraint

  • Vertical-Specificity Gating Condition vertical-specificity-gate
    bound by d8-driver-state-rate-mismatch

    Vertical specificity is a slowly-changing industry property; horizontal-AI capability (D1) improves fast - mismatch determines vertical-vs-horizontal industry winner.

  • Cultural Restructure-Readiness Gating Condition cultural-restructure-readiness-gate
    bound by d8-driver-state-rate-mismatch

    cultural state has very slow evolution while competitive valuation (D6) shifts fast - culture is THE classic incumbent rate-mismatch

  • Capital-for-Transformation Gating Condition capital-for-transformation-gate
    bound by d8-driver-state-rate-mismatch

    capital-allocation cycles (annual budget, etc.) have their own lag relative to capability frontier - mismatch determines deployment rate

  • Workflow Observability-Readiness Gating Condition workflow-observability-readiness-gate
    bound by d8-driver-state-rate-mismatch

    Observability infrastructure state evolves quarter-by-quarter while outcomes-measurement-shift (D14) demands real-time visibility - mismatch makes observability a binding gate on value-capture-measurement.

  • Network-Effects Strength Gating Condition network-effects-strength-gate
    bound by d8-driver-state-rate-mismatch

    Network-effects strength is a slowly-changing industry property; AI deployment (D1) changes fast - mismatch determines whether AI flywheels can establish lock-in.

  • Data-Network-Effects Gating Condition data-network-effects-gate
    bound by d8-driver-state-rate-mismatch

    Data-network-effects strength evolves over years (data accumulation cycles) while AI capability (D1) shifts continuously - mismatch determines whether orchestrator emergence stabilizes.