RESHUFFLE An interactive companion to the book
Cascade ▸ from unbundling--roleworkflow-context

What happens when a role gets unbundled?

From worker-level task unbundling through rebundled roles, workflow recomposition, and labor-market clearing.

visited
51
edges
65
hops
3
chains
4 / 4
failure modes
4
counters
1
unbundling--roleworkflow-context mechanism

Unbundling

Jobs S2 Workflow W3 Industry I1
The disintegration of roles or workflows into discrete tasks due to technological change, which often reduces pricing power, differentiation, and decision-making autonomy. The process by which a job, product, or workflow breaks into its component parts when old constraints (e.g., cost, coordination, time) are removed. The separation of tightly coupled capabilities (e.g., expertise from labor, songs from albums), enabling them to be repurposed independently.

Reading the cascade

Unbundling is the structural moment when a previously-integrated role or workflow breaks apart into its component tasks. Worker rebundling (S2/S3 in the Jobs chain) propagates outward through workflows, firms, and finally industries. Default direction here is outside-in because the start node is multi-chain, but the inside-out reading is the more natural read - pressure originating at the worker scale.

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
4 🔴
12 🔴 🟢
2nd-order Organizations
2
7 🔴
12 🔴
3rd-order Workflows
2
7 🔴
11 🔴 🟢
4th-order Jobs (workers)
3
5
5
inside-out
hop 1 immediate
hop 2 2nd hop
hop 3 3rd hop
1st-order Jobs (workers)
3
5
5
2nd-order Workflows
2
7 🔴
11 🔴 🟢
3rd-order Organizations
2
7 🔴
12 🔴
4th-order Competitive Ecosystem
1
4 🔴
12 🔴 🟢

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 1 immediate · 2 mechanisms
  • Unbundling unbundling--roleworkflow-context cross layer driver AI-Driven Rebundling ai-driven-rebundling 🔀 jobs→workflow

    The book treats unbundling and rebundling as paired moves at every scale. At the role level, tasks come apart - typist, cashier, fashion designer, copywriter - and once they are free of their old role bundles, AI can rebundle them across workflow lines without the old human handoff costs. Shein's section makes this concrete: buyer roles unbundle into AI trend-scraping and supplier coordination; the workflow then rebundles around what those unbundled tasks can newly do together. Role unbundling is the substrate workflow rebundling stands on.

  • Unbundling unbundling--roleworkflow-context cross layer driver Coordination Without Consensus coordination-without-consensus 🔀 jobs→workflow

    When tasks come out of the role bundle that used to host them, the implicit coordination logic of that role goes with them. The book's typist case is exact: 'the arrival of word processors didn't eliminate the task of typing… but the role of the typist became redundant. That job wasn't just about typing; it was set up to manage document editing, which was time-consuming and expensive.' Once the bundle is broken, workflows have to re-establish coordination - and AI is what makes that possible without prior consensus.

Hop 2 2nd hop · 9 mechanisms
  • AI-Driven Rebundling ai-driven-rebundling cross layer driver Rebundled Role rebundled-role 🔀 workflow→jobs

    The book's framing is symmetrical: 'AI breaks jobs into smaller tasks (unbundling) and recombines them into new configurations (rebundling). This reshapes roles.' When the workflow recomposes - as with construction's design/engineering/contract integration, or Rox's CRM workflows - the worker units that operate it have to recompose too. RevOps, nurse navigators, claims advocates are role-level instantiations of workflow rebundling. The workflow shifts; the role bundles follow.

  • AI-Driven Rebundling ai-driven-rebundling cross layer driver Modular Team Structure modular-team-structure 🔀 workflow→org

    The book's Spotify squads / Coinbase pods / two-pizza teams framing is built on the observation that as workflows modularize, the teams that operate them modularize too. The coordination flywheel makes this possible: 'When alignment no longer requires shared formats or rules, small focused teams can plug in without the integration overhead that previously forced monolithic structures.' Workflow rebundling at W3 drives team-structure reshape at O2.

  • AI-Driven Rebundling ai-driven-rebundling cross layer driver Value-Chain Disaggregation Pattern value-chain-disaggregation-pattern 🔀 industry→industry

    When workflows recompose at scale, the value chains that hosted them disaggregate. The book's iPod example is the clearest causal arc: Apple's workflow rebundling - discovery, access, playback - disaggregated the music value chain such that 'value created in the traditional music industry… was driving value capture in the consumer electronics industry.' Workflow-level rebundling propagates upward into value-chain disaggregation patterns at industry scale.

  • Coordination Without Consensus coordination-without-consensus causes Cold Start Problem cold-start-problem

    The book frames AI's unfair advantage in kickstarting ecosystems precisely as a cold-start dissolver: 'AI introduces a new advantage by enabling coordination without consensus. Instead of waiting for everyone to align, AI can begin coordinating activities by interpreting existing behaviors and translating between incompatible systems.' The cold start problem - no value until participation, no participation until value - dissolves because AI can produce value from existing fragmented behavior before anyone formally joins.

  • Coordination Without Consensus coordination-without-consensus causes AI-Enabled Coordination ai-enabled-coordination

    The book frames the flywheel: 'this creates a flywheel where AI-driven coordination attracts more participants, which generates even more data to train the AI towards improved coordination.' Coordination without consensus is the entry move; AI-enabled coordination is the compounded state. Participants see immediate value from passive participation, engage more deeply, generate more data, and the coordination layer becomes the substrate the ecosystem runs on.

  • AI-Driven Rebundling ai-driven-rebundling produces Workflow Unit-of-Work Shift (artefact → modular unit) workflow-unit-shift [W2→W3]

    AI-driven rebundling, in the book's words, 'transforms scattered data into a unified representation, guides decisions across disconnected actors, and coordinates actions across incompatible systems.' What this produces, structurally, is a new unit of work. Rox aggregates emails, calls, and Slack messages around the salesperson's actual decision, not around the software's reports. Ramp collapses cards, bills, expenses, and procurement into one coordinated layer. The artefact stops being the unit; the modular decision becomes the unit. 'The workflow starts to rebundle around the salesperson's actual decisions, not around the software's limitations.'

  • Coordination Without Consensus coordination-without-consensus enables Ecosystem Control ecosystem-control

    The book is direct: 'AI transforms coordination from a governance problem into a learning problem and, in this manner, helps secure a new form of ecosystem control.' Coordination without consensus turns fragmented ecosystems into functionally integrated systems - and whoever supplies that coordination becomes the gravitational center. The construction-industry example is the worked case: 'AI acts as the bridge, translating across teams and their tools to keep everyone aligned around the same evolving project reality.'

  • Coordination Without Consensus coordination-without-consensus enables AI-Driven Rebundling ai-driven-rebundling

    The book treats these two as paired moves at the workflow scale. Coordination without consensus is the precondition for AI-driven rebundling: 'Tractable illustrates the opportunity for coordination in fragmented business ecosystems where establishing consensus can be very difficult. Instead of requiring consensus, Tractable embraces the ecosystem's fragmentation and reorganizes it using AI-driven rebundling of work across multiple actors.' One enables the other operationally.

  • Coordination Without Consensus coordination-without-consensus enables Modular Team Structure modular-team-structure [O1->O2]

    The book's coordination flywheel chapter makes the link: when AI manages knowledge across teams, 'small focused teams can plug in without the integration overhead that previously forced monolithic structures.' Two-pizza teams, Spotify squads, Coinbase pods all rely on a coordination substrate they don't have to negotiate explicitly. Coordination without consensus removes the integration tax that used to make modular team structures fall apart at scale.

Hop 3 3rd hop · 7 mechanisms
  • Rebundled Role rebundled-role cross layer driver Organizational Rebundling organizational-rebundling 🔀 jobs→org

    The book's sommelier, nurse navigator, RevOps, and claims advocate cases are all individual rebundlings, but the book is explicit that the same logic applies up the stack: 'the logic we've used to understand how individual jobs are restructured… applies just as powerfully to entire firms.' When enough roles in an organization rebundle around new constraints, the organization restructures around them. Individual rebundling aggregates into organizational form.

  • Rebundled Role rebundled-role cross layer driver The Coordinated Organization the-coordinated-organization 🔀 jobs→org

    Rebundled roles operate in modular, cross-functional positions - RevOps across sales/marketing/CS, nurse navigators across departments, claims advocates across legal and emotional support. These roles only function inside an organization that can coordinate across silos in real time. The book's Coordinated Organization is the host: 'AI reduces friction between teams, integrates decision-making, and keeps everyone aligned without slowing them down.' Without it, the rebundled role has no scaffold to operate from.

  • Rebundled Role rebundled-role cross layer driver AI-Driven Rebundling ai-driven-rebundling 🔀 workflow→workflow

    The book's logic runs both ways: rebundled roles aren't just outputs of workflow change; they enable new workflow configurations. The sommelier's curatorial role enables a new dining-experience workflow. The nurse navigator's coordination role enables new chronic-care workflows. Worker rebundling feeds back into what the workflow can newly be. New role bundles enable workflow configurations that the old role bundles could not host.

  • Modular Team Structure modular-team-structure cross layer driver Rebundled Role rebundled-role 🔀 org→jobs

    The book's two-pizza teams, Spotify squads, and Coinbase pods all need workers defined modularly enough to plug in. Modular teams demand modular role bundles. The reverse is also true - RevOps, nurse navigator, claims advocate roles only exist because the team structures that host them are modular enough to let cross-functional roles operate at all. Team shape and role bundle co-evolve.

  • Vertical Encroachment vertical-encroachment causes Tool Integration Trap tool-integration-trap

    Vertical encroachment is what springs the trap. As the tool provider goes deeper - 'continuously absorbing data, learning from use across a broad set of customers, and integrating those learnings into the core tool' - solution providers reorient their workflows and business models around the engine to extract its performance gains. The book is explicit: the trap is created by 'solution providers marching downward into the tool, hoping to gain its benefits to compete better in the short term.'

  • Workflow Unit-of-Work Shift (artefact → modular unit) workflow-unit-shift causes Constraint-Substitution Mechanism constraint-substitution-mechanism [W3→W4]

    The book's discipline on constraints is that they don't disappear - they move. When the unit of work shifts from artefact to modular decision, the binding constraint moves with it. The sommelier section makes this concrete at the role level: as wine knowledge commoditized, the binding constraint moved from access-to-knowledge to navigating-overwhelming-choice. At workflow level the same dynamic runs: artefact-sized constraints stop binding; modular-unit-sized constraints (granular trust, per-step risk, per-decision auditability) take over.

  • Value-Chain Disaggregation Pattern value-chain-disaggregation-pattern produces Division-of-Labor Shift (Jacobides) division-of-labor-shift [I1→I2]

    When capabilities unbundle into building blocks, the division of labor moves with them. The book's framing is direct: 'industry boundaries don't matter anymore when a YouTuber can get into the restaurant business overnight.' Ghost kitchens specialize in production; brands specialize in demand; delivery services in fulfillment. Each block hosts a different set of roles, and the labor sorts across blocks rather than within firms. Disaggregation patterns determine where work concentrates.

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.

Validation walkthrough 2022-2026

Junior associates at top law firms get unbundled

Allen & Overy, A&O Shearman, PwC Legal, Macfarlanes (Harvey AI)

Harvey AI's firmwide rollouts (A&O Feb 2023, then A&O Shearman, PwC, Macfarlanes) peeled off contract review, due-diligence summarization, first-draft memos, and case research - the bundle that justified the billable hour for first- through fourth-year associates. The cascade fires through the chain: unbundling at S2, economic-collapse-of-the-task at S3, below-the-algorithm drift for routine matters at S4, and rebundling at S6 toward border-worker roles (AI-policy operators, M&A judgment-orchestrators). The reskilling-fallacy is visible: training associates on better legal research doesn't save the role because the workflow no longer needs the task at that scale.

Validation walkthrough 2016-2026

Radiology residents: unbundling without typist-effect

Aidoc, Annalise.ai, Lunit, Caption Health + radiology training programs

Hinton's 2016 prediction that radiologists would be obsolete in five years failed. Unbundling fired at S2 - image-pattern-recognition peeled off into Aidoc, Annalise, Lunit - but rebundling at S6 ran faster than economic-collapse-of-the-task at S3. Radiologists rebundled around clinical correlation, subspecialty reading, and AI orchestration; class sizes grew. The cascade shows that unbundling does NOT determine the typist-effect outcome - rebundling-multiple-contexts can outrun task collapse, gated by risk-based-constraints (the accountability moat) and labor-market tightness.

External research 2023-2024

Duolingo translators: unbundled then dropped

Duolingo

In late 2023/early 2024 Duolingo cut ~10% of its contractor base - primarily translators and content writers - and replaced their output with GPT-4. The translation task had been the contractor's bundle; once AI absorbed it, there was no rebundling path inside Duolingo's system of work. A clean typist-effect: unbundling drove economic-collapse-of-the-task, and the rebundling cascade never fired because the system no longer needed those workers. The reskilling-fallacy in unambiguous form.

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.

+2 absent actors

These actors don't appear in this cascade: Tool Provider, AI-Native Entrant.

As Ecosystem Orchestrator 🟢 advantaged

As Ecosystem Orchestrator, this cascade plays to your structural advantage. 3 capabilities you can wield are present. 0 threats to watch.

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

You are here

  • ecosystem-control
  • the-coordinated-organization

What you cause

  • causes Tool-Provider Lock-In
  • enables Platform Tax Fees
  • produces Ecosystem Flywheel
  • causes Industry Margin Pool
  • enables Complementor Alignment Mechanism (Adner)

What's coming for you

No specific threats to your position in this cascade.

What's available to you

  • 🟢 Complementor Alignment Mechanism (Adner) hop 3 · Competitive Ecosystem
  • 🟢 Ecosystem Flywheel hop 3 · Competitive Ecosystem
  • 🟢 Platform Tax Fees hop 3 · Competitive Ecosystem

Your moves

  1. Use ecosystem-control to set the rebundled-role standard across firms - define what the new role is and isn't.
    The cascade routes unbundling through ecosystem-control and rebundled-role. Whichever orchestrator publishes the definitive rebundled-role spec - its scope, its credentials, its tooling - becomes the de facto employer-of-record for the new labor market.
    watch for Track whether industry bodies and credential programs adopt your terminology for the new roles. If yes, you've won definitional control. If they adopt a competitor's or a generic term, the labor market is being shaped against you.
  2. Capture the workflow-unit-shift by re-pricing your platform around the new modular unit.
    The cascade produces workflow-unit-shift (artefact -> modular unit). Orchestrators who keep pricing artefact-based offerings when the underlying unit is modular will see complementors arbitrage them. Re-price to the new unit before the arbitrage starts.
    watch for If complementors are reselling your platform output in much smaller increments to their own customers, the unit has shifted and you haven't re-priced. Move now.
As Worker (Below the Algorithm) ⚖ mixed

As Worker (Below the Algorithm), the cascade is mixed for you - 1 capability and 2 threats both fire.

Your tasks are AI-mediated and AI-governed. You execute against AI-set parameters.

You are here

  • below-the-algorithm-worker
  • knowledge-work-below-the-algorithm-drift

What you cause

  • causes Knowledge-Work Below-the-Algorithm Drift
  • enables Risk-Based Constraints

What's coming for you

  • 🔴 Economic Collapse of the Task hop 1 · Jobs (workers)
  • 🔴 Reskilling Fallacy hop 3 · Jobs (workers)

What's available to you

  • 🟢 Rebundled Role hop 2 · Jobs (workers)

Your moves

  1. Move to a rebundled role before labor-market-clearing prices your unbundled tasks at zero.
    The cascade ends at typist-effect, reskilling-fallacy, and labor-market-clearing. Below-the-algorithm workers whose tasks unbundle without a credible rebundle position will see compensation collapse. The move is to volunteer for the rebundling, not to deepen the unbundled task.
    watch for If a vendor product is shipping the task you do as a feature, the unbundling has begun. If you can't name the rebundled role you'd move into, you're heading into clearing.
  2. Don't fall for the reskilling-fallacy - pick training on workflow ownership, not on a new tool.
    The cascade explicitly surfaces reskilling-fallacy. Workers who reskill on the next AI tool find that tool itself commoditized in 18 months. Reskill on workflow ownership and judgment - the things that survive tool churn.
    watch for If your reskilling program promises proficiency in a specific vendor product, the certificate is the bait - the workflow is the trap. Pick reskilling that names workflow outcomes, not tool features.
As Solution Provider ⚖ mixed

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

You package tools into outcomes for end customers - vertical-SaaS, services firms, integrators absorbing risk.

You are here

  • solution-provider

What you cause

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

What's coming for you

  • 🔴 Tool Integration Trap hop 3 · Organizations
  • 🔴 Vertical Encroachment hop 2 · Organizations

What's available to you

  • 🟢 Risk Absorption hop 3 · Workflows

Your moves

  1. Buy the rebundled-role before the labor market figures out it exists.
    The cascade routes from unbundling through rebundled-role. Solution-providers who can identify which rebundled roles their customers will need (and hire those people first) own the workflow before incumbents reorganize and before AI-natives can recruit at scale.
    watch for If you've hired three or more 'new role title' professionals in the past year that didn't exist in the industry two years ago, you're capturing rebundled-role talent. If your job titles match a 2022 org chart, you haven't.
  2. Capture risk-absorption for the rebundled workflow before either the orchestrator or the tool provider does.
    The cascade surfaces risk-absorption as the W6 counter-strategy. Once a role unbundles and rebundles, the new workflow has new risk vectors no one has yet absorbed. The solution-provider who underwrites those first owns the workflow.
    watch for Each rebundled workflow has a regulator, an insurer, or an auditor who will soon need someone accountable. Be the first vendor on their approved list.
As Complementor 🔴 threatened

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

You build on someone else's platform or ecosystem. Your leverage comes from being substitutable across orchestrators.

You are here

  • solution-provider

What you cause

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

What's coming for you

  • 🔴 Tool-Provider Lock-In hop 3 · Organizations
  • 🔴 Ecosystem Control hop 2 · Competitive Ecosystem
  • 🔴 Platform Tax Fees hop 3 · Competitive Ecosystem

What's available to you

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

Your moves

  1. Specialize into a rebundled role the orchestrator hasn't yet absorbed into the platform.
    The cascade names rebundled-role as a cross-layer driver. Complementors who pre-empt the orchestrator by occupying a rebundled-role niche claim margin before the orchestrator decides to in-source it.
    watch for If the orchestrator launches a 'native' version of the role you specialize in, you have 12 months. Multi-home or move up the rebundling stack to a role they haven't yet named.
  2. Build value-capture-measurement that proves the rebundled-role outcome - outcome-priced or perish.
    Rebundled roles are new - there's no incumbent pricing benchmark. Complementors who price the new role by its outcome (cycles closed, errors prevented, compliance achieved) escape the per-seat trap that wraps older roles.
    watch for If you can price a new contract against a customer P&L line that didn't exist 18 months ago, you've captured rebundled-role pricing. If you can't, you're still selling old units in a new wrapper.
As Incumbent Firm 🔴 threatened

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

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

  • 🔴 Tool Integration Trap hop 3 · Organizations
  • 🔴 Vertical Encroachment hop 2 · Organizations

What's available to you

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

Your moves

  1. Run organizational-rebundling explicitly - redraw the org chart around new units, not new job titles in old boxes.
    The cascade routes from unbundling through organizational-rebundling at the O1->O2 transition. Incumbents who add new titles to old reporting lines lose the productivity unlock. Restructure the reporting lines around the new modular unit of work.
    watch for If your new AI-related job titles all report into existing department heads who were named in 2020, you haven't restructured. Cross-functional rebundling means new reporting lines, not new titles in old lines.
  2. Defend against tool-provider-encroachment-in-knowledge-work by owning the rebundled-role labor pool.
    The cascade routes through tool-provider-encroachment-in-knowledge-work. Incumbents who let tool providers train and certify the workforce for rebundled roles will find those workers loyal to the tool, not the firm. Run your own credentialing.
    watch for Track how many of your firm's new-role hires hold a vendor certification rather than an internal or industry one. The higher the vendor share, the more your labor pool is being annexed by the tool provider.
As Worker (Above the Algorithm) ⚖ mixed

As Worker (Above the Algorithm), the cascade is mixed for you - 2 capabilities and 2 threats both fire.

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

You are here

  • rebundled-role

What you cause

  • causes Typist Effect
  • cross-layer-driver Organizational Rebundling
  • cross-layer-driver The Coordinated Organization
  • cross-layer-driver AI-Driven Rebundling

What's coming for you

  • 🔴 Economic Collapse of the Task hop 1 · Jobs (workers)
  • 🔴 Reskilling Fallacy hop 3 · Jobs (workers)

What's available to you

  • 🟢 Contextual Value hop 1 · Jobs (workers)
  • 🟢 System of Work hop 2 · Jobs (workers)

Your moves

  1. Be the architect of the rebundled role - propose the rebundle to your manager before HR formalizes the unbundled one.
    The cascade explicitly routes unbundling -> rebundled-role. Whoever proposes the rebundle gets to define its scope, its KPIs, and its reporting line. Workers who wait for HR to define the role end up in whatever box HR draws.
    watch for If you've written a one-pager for your manager describing how your role should be re-scoped around AI tooling, you're architecting. If you're waiting for the firm to tell you, you're being unbundled around.
  2. Claim the system-of-work boundary that the unbundled tasks now cross - that's the new premium position.
    Unbundling separates tasks; rebundling combines them into a new system of work. The premium sits with whoever owns the boundary the rebundled tasks cross - typically a cross-functional or cross-tool boundary that no single tool can own.
    watch for If your weekly work crosses tools, teams, or contexts that no one else's does, you hold a system-of-work boundary. If your work stays inside one tool, you're below the new boundary.
1st-order Competitive Ecosystem

Industry effects appear only at hop 2-3: value-chain-disaggregation-pattern at hop 2 (the industry-level expression of worker-level unbundling) and the full failure chain by hop 3 - vertical-encroachment, tool-provider-lock-in, tool-integration-trap. The industry-architecture-shift follows the unbundling-rebundling pattern at industry scale.

2nd-order Organizations

Firms feel unbundling at hop 1 through contextual-value and coordination-without-consensus requirements. By hop 2 the firm must redesign team structure - modular-team-structure, shared-organizational-knowledge, ai-enabled-coordination all activate. By hop 3 the structural sort is widespread: firms that rebuild around composable-business survive; the others slip into capability-stack-failure-mode.

3rd-order Workflows

At the workflow scale, unbundling immediately produces economic-collapse-of-the-task - tasks lose their pricing-unit status. By hop 2 the workflow recomposes around unified-representation, coordination-gap surfaces, and the workflow-unit-shift fires. By hop 3 the deeper workflow shifts land - workflow-governance-locus-shift, workflow-dependency-explicitness, governance throughout the process.

4th-order Jobs (workers)

Workers feel the immediate effect at hop 1 - contextual-value and economic-collapse-of-the-task together mean that the worker's bundled role no longer prices cleanly. By hop 2 the worker is mid-rebundle; by hop 3 the new worker patterns appear - tacit-knowledge, curation, curiosity as residual value; above-the-algorithm-vs-below-the-algorithm as the new sorting axis; labor-market-clearing as the macro dynamic.

1st-order Jobs (workers)

Workers feel the immediate effect at hop 1 - contextual-value and economic-collapse-of-the-task together mean that the worker's bundled role no longer prices cleanly. By hop 2 the worker is mid-rebundle; by hop 3 the new worker patterns appear - tacit-knowledge, curation, curiosity as residual value; above-the-algorithm-vs-below-the-algorithm as the new sorting axis; labor-market-clearing as the macro dynamic.

2nd-order Workflows

At the workflow scale, unbundling immediately produces economic-collapse-of-the-task - tasks lose their pricing-unit status. By hop 2 the workflow recomposes around unified-representation, coordination-gap surfaces, and the workflow-unit-shift fires. By hop 3 the deeper workflow shifts land - workflow-governance-locus-shift, workflow-dependency-explicitness, governance throughout the process.

3rd-order Organizations

Firms feel unbundling at hop 1 through contextual-value and coordination-without-consensus requirements. By hop 2 the firm must redesign team structure - modular-team-structure, shared-organizational-knowledge, ai-enabled-coordination all activate. By hop 3 the structural sort is widespread: firms that rebuild around composable-business survive; the others slip into capability-stack-failure-mode.

4th-order Competitive Ecosystem

Industry effects appear only at hop 2-3: value-chain-disaggregation-pattern at hop 2 (the industry-level expression of worker-level unbundling) and the full failure chain by hop 3 - vertical-encroachment, tool-provider-lock-in, tool-integration-trap. The industry-architecture-shift follows the unbundling-rebundling pattern at industry scale.

Risk-absorption is the only counter-strategy surfaced - and it lives at the workflow scale, not the worker scale. The structural read: unbundling at the worker scale produces effects across all four scales, but workers themselves have no in-chain counter-strategy. The defensive moves available are at the firm and workflow scales. What to watch: which residual sources of human value (tacit knowledge / curation / curiosity / judgment) your specific work involves - those determine which side of the algorithm you land on after the rebundle.