Overview

The evolving synthesis of this vault. It currently rests on one imported source set — the Pure VSM manuscript — so it is a synthesis of that source, not yet of the project’s whole library. Where the vault is silent, it is silent: nothing here is established beyond what the sources say.

What the model is, as the sources state it

The Viable System Model is Beer’s account of the necessary organization of any system that is to survive as a recognisable identity. In the manuscript’s reading it is not an org chart but a set of functions that any viable system must perform, whatever its structure.

  • Regulation is variety handling. Control is limited by variety, and the manager’s job is to attenuate and amplify it — variety-and-regulation.
  • A viable system is recursive. Every viable system contains and is contained in viable systems — recursion.
  • Five systems are necessary. The operations (system-one), the anti-oscillatory service that damps conflict between them (system-two), the inside-and-now management of the whole (system-three, with its audit channel Three*), the outside-and-then intelligence and adaptation function (system-four), and the closure that carries identity (system-five, monitoring the Three–Four homeostat).
  • Its rules are stated as principles and axioms — principles-and-axioms-of-organization.
  • Its signals include one that bypasses the hierarchy — the algedonic-signal, pain or pleasure routed straight to the top.
  • Cohesion across levels is governed by a law — the law-of-cohesion.
  • It can fail in describable ways — pathologies-of-viable-systems.
  • Viability is identity plus autonomy — viability-identity-and-autonomy.
  • Two epistemological commitments underpin the rest: models work by homomorphism, not analogy (homomorphism), and “system” is an act of recognition by an observer, not a given (observer-and-recognition).
  • Beer’s non-hierarchical method for group deliberation is team-syntegrity, set against the model rather than inside it.

The works it rests on

The manuscript’s authority map is Beer’s own books — brain-of-the-firm, the-heart-of-enterprise, diagnosing-the-system-for-organizations, management-science-1967, decision-and-control, think-before-you-think and beyond-dispute — written by stafford-beer, with the Chilean application documented at cybersyn.

The manuscript’s own caveat, and why it matters here

The source is Draft 0.8, not project canon. Its stated purpose is fidelity: every claim about the model should carry a locator in Beer’s texts, and interpretation, later extension and critique are kept visibly separate from what Beer wrote. The vault inherits that discipline — pages carry locators, and the appendix records where Beer’s own formulations differ between books (viability, variety, the Recursive System Theorem, the Axioms, Cybersyn’s coverage). Anyone using this wiki should read the variant, not a flattened version.

Open gaps in this synthesis

Recorded honestly, because the frontdesk will be asked about them:

  • No critique. The vault holds the model as Beer stated it. It holds no source engaging the standing objections to the VSM — that it understates power, that recursion is hard to bound in practice, that the model’s normative pull exceeds its descriptive claims. The project’s third principle — every proposed scenario carries its strongest counter-argument within it — is therefore unmet in this vault so far. Do not manufacture the counter-argument from these pages; import a source.
  • No application evidence. cybersyn is documented as Beer described it, not evaluated.
  • Draft material. Every page derived from the manuscript says so. Nothing from it should be quoted to a reader as settled project position.
  • index — the vault catalog.
  • AGENTS — schema and conventions.
  • ../AGENTS.md — the project brief and its open questions.
  • log — the vault’s history.