foundations-cybernetics-vsmDiagnoses stalled teams or agent hierarchies with Beer's VSM and Ashby's Law. Use when orchestrators overload, escalations pile up, or team boundaries need redesign.
Independent GitHub snapshot · Automated classification · Original documentation governs
Apply cybernetics-VSM when:
Skip and use simpler alternatives when:
11 canonical cybernetics and VSM primitives for designing viable organizations, control hierarchies, and adaptive systems. Each primitive solves a specific failure mode in how complexity is absorbed, coordinated, and governed.
| # | Primitive | Core Function | When to Reach For It |
|---|---|---|---|
| 1 | Feedback Loops | Regulate behavior via negative (balancing) or amplify via positive (reinforcing) loops | Any adaptive control mechanism; stability vs. growth dynamics |
| 2 | Ashby's Law of Requisite Variety | Only regulator variety can reduce outcome variety (lower bound, log units) | Diagnosing under-instrumented control; scaling management layers |
| 3 | VSM System 1 — Operations | Autonomous operational units that do the actual work | Defining work units, microservices, squads, agent executors |
| 4 | VSM System 2 — Coordination | Anti-oscillation coordination layer between S1 units | Preventing interference and thrashing between operational units |
| 5 | VSM System 3 — Internal Control | Here-and-now optimization of the operational environment | Performance management, resource allocation, policy enforcement |
| 6 | VSM System 3* — Audit Channel | Sporadic direct channel from S3 to S1 bypassing routine reports | Spot-checks, audits, compliance sampling; detecting reporting distortion |
| 7 | VSM System 4 — Intelligence | Outside-and-future scanning; adaptation intelligence | Strategy, environmental scanning, roadmaps, horizon sensing |
| 8 | VSM System 5 — Identity/Policy | Ultimate authority; closure and identity of the whole | Mission, values, constitutional rules, governance closure |
| 9 | Recursion Levels | Every viable system contains and is contained in viable systems | Multi-level organizational design; nesting teams, divisions, products |
| 10 | Variety Engineering | Amplifiers, attenuators, and transducers to balance variety across channels | Reducing information overload; designing dashboards, APIs, interfaces |
| 11 | Algedonic Channels | High-priority pain/pleasure signals that bypass normal hierarchy levels | Incident escalation, crisis bypass routes, critical alerts |
Load references/formal-theory-map.md when the task needs more than a primitive lookup: defining the system-in-focus, distinguishing first-order vs. second-order cybernetics, proving an Ashby/requisite-variety claim, mapping VSM systems 1-5 across recursion levels, or separating S3 control, S3* audit, S4 intelligence, S5 policy, and algedonic escalation.
Stafford Beer: VSM systems 1–5, algedonic channels, recursion levels and variety engineering are defined in Beer 1972 (Brain of the Firm), 1979 (The Heart of Enterprise) and 1985 (Diagnosing the System for Organizations). Cite Brain of the Firm by section title, not by a per-system chapter number; the book has no one-system-per-chapter structure. Chapter numbers cited for Beer 1985, Hoverstadt 2009 and Schwaninger 2006 are unverified; treat them as approximate.
Project Cybersyn (Chile, 1971–1973): the most-cited VSM deployment is also the most mythologised. Medina 2011 (Cybernetic Revolutionaries, MIT Press) is the archival history; read the fact-vs-myth table in references/patterns-scenarios-traps.md before citing the case. The figures in that table have not been re-checked against Medina; confirm them there before quoting.
W. Ross Ashby: the Law of Requisite Variety is in Ashby 1956 (An Introduction to Cybernetics, ch. 11; PDF). §11/7 gives a lower bound on outcome variety: V(O) ≥ V(D) − V(R) in logarithmic units, i.e. only regulator variety can reduce outcome variety, and by at most its own amount. In counts (§11/6): with d disturbances, r responses and no two equal outcomes in a response column, the regulator cannot hold the outcomes to fewer than d/r. Never subtract raw counts ("20 states − 5 levers = gap of 15"); use the response coverage audit. Siegenfeld & Bar-Yam (2025, Entropy 27(8), 835, DOI 10.3390/e27080835) generalise the law across scales; treat it as a clarification for recursive architectures, not a revision.
Requisite variety in AI-oversight regulation: Human oversight of an agent fleet needs enough variety to cover the fleet's disturbance classes, as in composition-recipes.md. Telukunta, Lilis & Baron (2026, arXiv:2608.10153, submitted 10 August 2026) apply Beer's VSM to enterprise agent fleets. Evidence grade: C (preprint, not peer-reviewed). Treat the CASE architecture as a conceptual proposal, not a validated quantitative condition; operational evidence must come from disturbance-response coverage and intervention tests. The underlying cybernetic sources are stronger evidence for the qualitative need for requisite variety, not for multiplying raw oversight counts. On the regulatory hook: EU AI Act Article 14 obligations differ by high-risk category and date; verify the applicable provision before making a current compliance claim.
Norbert Wiener: Feedback and cybernetics foundations from Wiener 1948 (Cybernetics: Or Control and Communication in the Animal and the Machine). Positive/negative feedback terminology is consistent with Wiener's original usage.
Espinosa & Walker: VSM applied to complexity and sustainability in A Complexity Approach to Sustainability (2011). Recursion and viable-systems analysis in real organisations.
Schwaninger: Intelligent organisations and VSM application in Intelligent Organizations (2006). Apply numeric claims (e.g., performance improvement percentages) only when derived from primary case studies, not secondary summaries.
Hoverstadt: Practical VSM application in The Fractal Organization (2009). Patterns cited from this source are practitioner heuristics — verify against Beer's original formalism before treating as universal.
Mechanism effectiveness is context-specific. Test variety-engineering interventions on a constrained scope before rolling out system-wide.
Load references/patterns-scenarios-traps.md before turning VSM into an org chart, central control layer, dashboard scheme, escalation policy, or agent hierarchy. It contains operational scenarios, anti-patterns, known traps, and a compact audit sequence.
| Anti-Pattern | Cybernetics/VSM Diagnosis | Fix |
|---|---|---|
| System 3 collapses System 1 autonomy (micromanagement) | S3 is consuming all operational variety — no recursion depth; Ashby violation | Restore S1 autonomy; S3 sets policy and limits, not execution steps |
| System 4 disconnected from System 3 (strategy-execution gap) | S4 output never reaches S3; no S3/S4 homeostat | Build explicit S3/S4 interface: shared planning cadence, mutual translation layer |
| Ashby's Law violated by under-instrumented control | Disturbance distinctions that require different responses are collapsed or unreachable | Define the disturbance classes and response repertoire; add attenuation or amplification where a tested control distinction is missing |
| Algedonic channel never used — S5 blind to crises | Pain signals absorbed by normal hierarchy; S5 receives filtered reports only | Implement direct bypass route with trigger threshold; test at an interval justified by hazard, disturbance rate, consequence deadline and change events |
| Recursion confusion — applying VSM at wrong organisational scale | S1/S3/S5 roles assigned to the wrong recursion level | Re-identify the level of recursion; redraw the system boundary before assigning roles |
| Positive feedback loop with no balancing loop (runaway dynamics) | Reinforcing loop unchecked — growth, debt, or failure cascades | Design an explicit negative feedback loop with a goal variable and measured deviation |
| S2 coordination layer absent — unit thrashing | S1 units interfere without coordination signals | Introduce S2 scheduling, resource-sharing protocols, or synchronisation mechanisms |
| S3* audit channel treated as normal management reporting | Spot-check becomes routine; S1 adapts and Goodharts the signal | Keep S3* sporadic and surprise-based; vary timing and scope |
| Variety amplified without attenuation at higher levels | Upper levels receive raw operational noise; decision paralysis | Apply variety attenuation (aggregation, exception filters) before variety reaches S3/S4 |
| S5 identity undefined — policy vacuum | S3/S4 conflicts escalate without resolution; ad-hoc decisions contradict each other | Define S5 closure: mission, constraints, values; run S3/S4 conflicts through S5 reference frame |
| Human oversight of an agent fleet staffed, not engineered | Reviewer headcount is added without mapping outcome-relevant agent behaviours to detectable signals and effective interventions | Add triage, summarisation, tiered escalation, and tested intervention paths; publish the mapping and escalation SLA, not only a rota |
Full stacks, checks and outputs: references/composition-recipes.md. Read it when a diagnosis needs several primitives in order.
| Recipe | Use when | Primitives |
|---|---|---|
| Agent-Team Topology Audit | An orchestrator re-reviews every subagent result, escalations pile up, or you must size human oversight of an agent fleet | #3, #4, #5, #2, #10, #11 |
| Organisational Design for a Startup | Founders are the bottleneck as layers appear | #9, #3, #6, #7, #8, #1 |
| Incident Escalation as Algedonic Channel | Crises sit in ticket queues or reach authority late | #11, #8, #1, #6, #10 |
| Scaling a Platform Team | A platform team queues every consumer request | #2, #10, #4, #5, #1 |
Map a concrete agent harness or Team Topologies structure onto S1–S5, collect evidence that human oversight works, run a POSIWID check, or decide whether a small team needs S3*: references/org-and-harness-mappings.md.
Fillable response-coverage matrix and completed synthetic diagnosis
Composition recipes — full stacks for the four recipes above
Org and harness mappings — agent harness and Team Topologies crosswalks, oversight evidence pack, POSIWID, when not to prescribe S3*
Per-primitive playbooks: assets/templates/cybernetics-vsm/ (one file per primitive)
Composition guide: assets/templates/cybernetics-vsm/README.md
Primitives overview: references/primitives-overview.md
Formal theory map: references/formal-theory-map.md
Patterns, scenarios, and traps: references/patterns-scenarios-traps.md
Sources: data/sources.json
When prior decisions or pitfalls are relevant, consult learnings.consolidated.md if present; use learnings.md only for needed history or as the available fallback. Otherwise skip both.
After applying it, if you encountered a pattern worth remembering, a mistake worth preventing, or a domain fact that surprised you, append one dated bullet to learnings.md via agents-skills-feedback-loop/scripts/append_learning.py. Do not modify SKILL.md itself.