The Synthesis

Where the
frameworks
came from.

The frameworks did not emerge from business literature or consulting methodology. They emerged from pattern recognition across domains most people keep separate. This is the record of which domain contributed what, and why the connection was not obvious until it was.

The cognitive engine

I think in multi-causal, n-dimensional patterns. Not as a method. As a cognitive architecture.

Most people trace linear paths through problems. A causes B causes C. Fix A, solve the problem. I cannot process problems that way. Not even when I try. I see multiple causes creating single effects, single causes creating multiple effects, and problems existing at multiple layers simultaneously.

This is not something I learned. It is how my brain processes complexity. Years of biology, physics, and biochemistry at university taught me that systems exist at multiple levels at once: cellular, organ, organism. You cannot understand one without understanding all three simultaneously. Dante showed me that reality has layers that coexist rather than stack. Homer showed me multi-causal narrative threads across time and space. Leibniz gave me language for the observer effect. Schrödinger showed me that enterprise systems exist in multiple states simultaneously until you measure them. The measurement does not reveal the state. It creates it.

AME and ANIM are not frameworks I designed through abstract reasoning. They are how my brain naturally organises complexity, formalised into something others can use.

The domains
01
How I See Things
Feeds into
AMEAll frameworks
The pattern beneath the chaos
I cannot play a game without deconstructing its systems. I cannot study a language without mapping its evolution patterns. I cannot ride a trail without reading the terrain's underlying logic. For years I thought this was just how my brain worked. Maybe even a distraction from real work. It turned out to be the operating principle behind everything that followed. The AME framework did not come from MBA textbooks. It crystallised from decades of pattern recognition across radically different domains. When I tell clients to treat their organisation like a living ecosystem rather than a machine, I am not using a metaphor. I am applying principles observed in mycelial networks, language evolution, rowing synchronisation, and modular game mechanics.
Finding the deep structure beneath surface complexity. This is the work that precedes every framework.
Read on System Decoder →
02
Dungeon Mastering
Feeds into
AMEANIM
Ecosystem orchestration. Creating conditions, not outcomes
Early in my D&D campaigns I scripted everything. Planned NPCs, predetermined outcomes. The players always broke it. The best sessions emerged when I stopped orchestrating outcomes and started orchestrating possibilities: clear rules, rich environments, meaningful choices, and consequences that rippled through the world. A great campaign operates like a living ecosystem. You do not dictate. You enable discovery. When a Fortune 500 client faced supply chain disruptions, we did not create a rigid playbook. We created an AME ecosystem where intelligent nodes had clear objectives and adapted locally. The system discovered solutions engineers had not predicted.
Orchestration is not control. It is creating the conditions where intelligence can emerge.
Read on System Decoder →
03
Gloomhaven
Feeds into
AMEMLPlat
Composability beats optimisation
I had a card I almost retired: weak damage, mediocre range, strange timing. Then I discovered that combined with two teammates' abilities it created devastating synergies. What looked like a design oversight was elegant systems thinking. Most enterprises optimise individual components to perfection, then wonder why systems cannot adapt when markets shift. Each piece is perfect in isolation. None can recombine to meet unexpected challenges. The AME framework emphasises composability over optimisation: capability modules designed to be mixed and recombined as needs evolve.
The power is not in individual components. It is in emergent synergies that players discover.
Read on System Decoder →
04
Rowing
Feeds into
ANIMAME
Distributed intelligence. The crew that stops watching and starts feeling
From 1992 to 2011 I taught rowing at the University of Greifswald. New rowers would try to watch the stroke seat, waiting for visual cues. They would fall behind, disrupt the rhythm, fight the boat. Then something would shift. They would stop watching and start feeling. The real coordination happened through distributed sensing: hull pressure, rigger vibration, blade resistance. I recognised this pattern during a manufacturing implementation. Centralised orchestration was too slow. Switching to distributed intelligence, with quality control nodes sensing problems and immediately signalling production nodes, the system found its flow. This is what ANIM does.
You cannot orchestrate an enterprise ecosystem with detailed central commands. You set strategic rhythm, then trust the system to find its flow.
Read on System Decoder →
05
Linguistics
Feeds into
AMEDrift Detection
Organic evolution. No committee decided to change Old English
No committee decided to change Old English into Middle English into Modern English. No CEO issued a memo. Yet organically, through millions of individual interactions over centuries, English evolved from an unrecognisable Germanic dialect into the global lingua franca. Complex adaptive systems do not transform through central planning. They evolve through distributed mutation and selection pressure. Early in my platform transformation work I tried to force centralised data platform transitions. Teams resisted, workarounds proliferated. Switching to composable modules that teams could adopt piecemeal, one team discovered real-time data mesh made their work faster, word spread, another adapted the approach, and adoption exceeded what months of mandates could not achieve.
You cannot design evolution. You can create conditions that favour it.
Read on System Decoder →
06
Dental Anatomy
Feeds into
AME Foundation LayerANIM
Hierarchical modularity with precise interfaces
I spent three years studying dentistry before switching to communication sciences. A molar is an intricate modular system: the crown handles stress, the roots anchor, the pulp houses nerves, the dentin provides structure. Each component is specialised and precisely interfaced. If one fails, you can often save the tooth by treating that module alone. When I built the Foundation Layer of AME, dental architecture was the model. The root canal system taught me about communication networks: redundant and localised, so when one pathway fails, others compensate. The periodontal ligament creates feedback where each tooth senses pressure and communicates with surrounding teeth. This is what intelligent platform nodes should do.
The precision of biological interfaces is what software engineers miss. No gap, no overlap. That is what your API boundaries should look like.
Read on System Decoder →
07
Snowboarding
Feeds into
AME Connectivity LayerHAO
Momentum creates stability. Slow is not safe
When linking turns down a steep slope, going slower feels safer. It is not. Slow turns are unstable. You lose edge control and your board chatters rather than carves. Speed gives you stability. When you commit to the fall line with momentum, your edges bite and you can make precise adjustments. At speed, micro-changes in snow texture come through immediately. You are processing dozens of terrain signals per second. Slow down and those signals blur: you are guessing instead of sensing. Enterprises try to slow down to reduce risk when markets shift rapidly. They add approval layers, demand more analysis. This creates the same instability as slow snowboard turns. The AME Connectivity Layer is designed for momentum-based sensing.
In complex adaptive systems, momentum is not reckless. It is what gives you the stability to sense accurately and respond precisely.
Read on System Decoder →
08
Two Bows
Feeds into
AME FoundationAME ExecutionHAO
Two architectures. Kyudo and English longbow
I learned English longbow as a LARP regiment captain: how different woods behave, how arrow weight affects trajectory, how wind reads through the shaft. Then I experienced Kyudo in a dojo in Hiroshima. Everything I knew about archery became irrelevant. In Kyudo there is no iteration. There is only perfecting the way through repetition. Same weapon. Incompatible operating systems. Enterprises try to run both simultaneously. The answer is both, at different layers. Foundation layer operates like Kyudo: perfect the form, maintain discipline, do not iterate your way to data integrity. Execution layer operates like English longbow: shoot, observe, adjust. Most organisational failures come from applying the wrong system to the wrong layer.
You need both systems. The failure is not choosing one. It is applying the wrong one to the wrong layer.
Read on System Decoder →
09
Warhammer 40k
Feeds into
ANIMAMEDrift Detection
Two armies, two architectures. Swarm intelligence and entropy resilience
I paint Tyranids and Death Guard: two completely different architectures, both valid. Tyranids are swarm and emergent complexity through composition: simple organisms, specialised roles, no master controller. Death Guard are decay, slowness, and inevitability: systems that have accepted entropy as an operational parameter. A plague marine covered in corrosion still has full combat effectiveness. The system does not fight degradation. It incorporates it. Most enterprises treat technical debt and legacy complexity as problems to eliminate. Death Guard show a different approach: build systems that remain functional despite entropy. Tyranids show how ANIM nodes work: distributed intelligence emerging from composition, not central command.
You do not need unified architecture. You need appropriate architecture for each component's function.
Read on System Decoder →
10
The Cognitive Engine
Feeds into
All frameworks
N-dimensional multi-causality. The engine beneath everything
During my IBM years I noticed something. When colleagues approached challenges, they traced linear paths. I did not process problems that way and could not, even when I tried. I saw multiple causes creating single effects, problems existing at multiple layers simultaneously, and systems in superposition states until acted upon. During the transition from IBM to AWS I recognised this was not just multi-causality: it was n-dimensional thinking. Holding multiple perspectives, layers, and causal pathways simultaneously without collapsing them into a single linear sequence. Traditional architecture assumes linear causality. AME assumes multi-causality. Traditional architecture optimises single dimensions. ANIM operates in n-dimensional state space. This cognitive engine is not a methodology. It is how my brain processes complexity, and everything else in this series emerges from it.
The frameworks are not designed artefacts. They are my cognitive pattern, externalised.
Read on System Decoder →
11
The Synthesis
Feeds into
All frameworks
I see connections where everyone else asks: which connection?
When I built the Foundation Layer, I was applying dental architecture principles. When I designed the Intelligence Layer, I was implementing mycelial coordination. When I created the Connectivity Layer, I was encoding momentum-based sensing from snowboarding. When I structured the Value Creation Layer, I was enabling D&D-style emergence. Every principle has roots in multiple domains: composability from gaming and linguistics and dental structure; distributed intelligence from rowing and fungi and language evolution; ecosystem orchestration from D&D and terrain reading and biological systems; dual operating systems from Kyudo and English longbow. Most consultants study enterprise transformation by reading about enterprise transformation. Breakthrough insights do not come from inside your domain. They come from asking how other complex adaptive systems solve the same problem.
I decode systems. Then I build frameworks that work the way those systems work.
Read on System Decoder →
System Decoder Series

This page is the distilled record of the System Decoder series published on schwarzpfad.substack.com. Eleven parts documenting the domains, the patterns, and the connections that produced the frameworks. The series is published in full on System Decoder. Read it there for the complete arguments.

Read the full series on System Decoder →