FAQ

What Are the 11 Mechanisms in the CEM Framework?

CEM Methodology

Key Takeaways
  • The CEM framework contains exactly 11 mechanisms organized into four groups: Core Engine (Foundation, The Pendulum, Nested Cycles, Sweeps), Growth (Regroup, The Governor), Problem-Solving (Micro-Triage), and Execution Architecture (Multi-Thread Workflow, Bridge, Scaffold, Burst).
  • No single mechanism carries the system -- the compounding comes from all 11 operating in concert, each pulling from Foundation and feeding back into it.
  • The SWEBOK (Software Engineering Body of Knowledge) identifies process areas that traditional methodologies address individually: configuration management, quality assurance, project management, maintenance.

The CEM framework contains exactly 11 mechanisms organized into four groups: Core Engine (Foundation, The Pendulum, Nested Cycles, Sweeps), Growth (Regroup, The Governor), Problem-Solving (Micro-Triage), and Execution Architecture (Multi-Thread Workflow, Bridge, Scaffold, Burst). No single mechanism carries the system -- the compounding comes from all 11 operating in concert, each pulling from Foundation and feeding back into it.

The SWEBOK (Software Engineering Body of Knowledge) identifies process areas that traditional methodologies address individually: configuration management, quality assurance, project management, maintenance. CEM compresses these into mechanisms that operate simultaneously rather than sequentially, removing the ceremony overhead that traditional methodology components carry.

Here are the canonical 11:

Core Engine. (1) Foundation is the self-feeding asset store -- templates, stored work, retrievable stash. Every cycle draws from it and feeds back. (2) The Pendulum is the binary decision filter: does this advance the Target? Yes = advance. No = stash to Foundation. No middle state. (3) Nested Cycles are self-similar timeboxed execution at four magnitudes: Micro (15 min-3 hours), Sprint (1-2 days), Build (1-7 days), Integration (1-14 days). (4) Sweeps are continuous background maintenance running parallel to primary work -- documentation, storage, technical hygiene.

Growth. (5) Regroup is the scheduled ecosystem review at two cadences: every 2 weeks and every 30-45 days. (6) The Governor is macro-level awareness of system limits -- quality gates that protect velocity from the speed/quality death spiral.

Problem-Solving. (7) Micro-Triage is tactical escalation for execution spirals: a six-step diagnostic loop timeboxed to 15-30 minutes.

Execution Architecture. (8) Multi-Thread Workflow is the physical screen layout enabling parallel execution across three screens. (9) Bridge connects information across the ecosystem -- when something reaches 80%, it becomes a connection candidate. (10) Scaffold provides instant structure from Foundation for new projects, eliminating cold-start cost. (11) Burst is controlled divergent explosion: 3-5 parallel iterations at 80% when stuck or facing irreducible uncertainty.

During validation, these 11 mechanisms operated across 596,903 lines of code with 95%+ template reuse, 60% of active days showing parallel project execution, and 4-5 day MVPs at maturity. The 12-15% AI drift tax is absorbed by the system's recovery chain (Micro-Triage, Stop/Pause/Reset, Stop and Recap, Stop Run It Back) -- supporting concepts that keep the 11 mechanisms functioning.

Related: FAQ #44 (What Is CEM), FAQ #49 (The Governor)

References

  1. IEEE Computer Society (2014). SWEBOK: Software Engineering Body of Knowledge, v3.0. Methodology component taxonomy.
  2. Keating, M.G. (2026). "The Compounding Execution Method: Complete Technical Documentation." Stealth Labz. Browse papers