Why this gate binds: the D-RM rate-mismatch between slow workflow systems and fast capability evolution.
visited
7
edges
6
hops
2
chains
4 / 4
gates
1
legacy-workflow-rigidity-gateconstraint
Legacy-Workflow Rigidity Gating Condition
Workflow GC
Existing workflow systems' restructure-ability. Heavy ERP/SAP installations, deeply-embedded workflow software, etc. gate how quickly workflow recomposition can happen. Major incumbent constraint.
Workflow system state accumulates over decades; capability needs (D3) shift in months - canonical incumbent rate-mismatch at workflow scale.
Reading the cascade
Gates are external constraints on the chain - they don't produce downstream effects in the way mechanisms do; they constrain whether other mechanisms can fire. This cascade traces upstream from one gate (legacy-workflow-rigidity-gate) to surface what binds it. The matrix is empty because gates have no causal upstream - only annotation upstream via explains-binding-of from the D-RM rate-mismatch.
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 1immediate
hop 22nd hop
1st-orderCompetitive Ecosystem
1
2
2nd-orderOrganizations
1
5
3rd-orderWorkflows
1
1
4th-orderJobs (workers)
1
2
▲inside-out
hop 1immediate
hop 22nd hop
1st-orderJobs (workers)
1
2
2nd-orderWorkflows
1
1
3rd-orderOrganizations
1
5
4th-orderCompetitive Ecosystem
1
2
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 2020-2026
AP automation stalls at 30% in SAP-heavy enterprises
Large enterprises on SAP Ariba, Oracle, Workday
AP-native vendors (Bill.com, Tipalti, Stampli) hit 80%+ touchless processing in SMBs but stall at ~30% in large enterprises running SAP Ariba or Oracle. The legacy-workflow-rigidity gate binds: ERP installations accumulated over decades encode chart-of-accounts logic, approval matrices, and exception rules that resist recomposition on the months-scale that AP-native vendors need. D-RM rate-mismatch is the mechanism - workflow system state changes in years; capability needs shift in months. The gate is what separates the SMB cascade (fires) from the enterprise cascade (stuck).
SAP's R/3 and S/4HANA installations represent decades of accumulated workflow state - custom ABAP code, configured business processes, integrated finance and HR rules. When AI-native workflow vendors approached SAP customers post-2022, the rigidity gate bound: customers could not recompose workflows fast enough to absorb the new capability. SAP's own response (Joule, Build) is gated by the same constraint. Canonical incumbent rate-mismatch at workflow scale; the gate explains why the agentic-execution cascade fires faster in greenfield environments than in installed-base ones.
Most Tier-1 banks still run COBOL-era core-banking systems. Multi-year migration programs (Lloyds, BBVA, Westpac) routinely run over time and budget, and AI-driven workflow recomposition stalls behind them. The legacy-workflow-rigidity gate is binding: state accumulated over 40+ years vs capability evolving in months. DBS Bank's coordinated-organization pivot succeeded partly because it spent a decade pre-2018 modernizing its core - DBS bought down the rigidity gate first. The contrapositive: banks that didn't modernize first cannot fire the coordination-without-consensus cascade no matter how much AI they buy.
What binds this gate is D8 driver-state rate-mismatch: workflow system state accumulates over decades (ERP migrations, embedded process software) while AI capability shifts in months. The gap between fast-driver and slow-state is what makes legacy rigidity *bind* in practice. The structural read: every binding gate in the chain has a rate-mismatch explanation - the gate is the symptom, the rate-mismatch is the cause. What to watch: the velocity of legacy-system replacement in your industry. Where it's fast (small SaaS-native firms), the gate doesn't bind. Where it's slow (large incumbents with embedded ERP), the gate is the primary reason AI-era workflow gains haven't materialized.