Sources and Frameworks¶
The Human Cooperation System (HCS) builds upon a wide range of theories, models, and disciplines.
It does not seek to replace them. Instead, it acts as a systemic integration layer that organizes these independent insights into a single, executable operating system for cooperation.
This section maps the lineage of HCS and provides a translation layer for practitioners using other common frameworks.
1. Theoretical Foundations (The "Kernel")¶
These disciplines form the internal logic of HCS.
Systems Thinking & Cybernetics¶
The Physics of Stability and Control.
| Source | Core Concept | How HCS Operationalizes It |
|---|---|---|
| General Systems Theory (Bertalanffy) | Systems share universal structural patterns. | HCS treats "Team Dynamics" as system mechanics, not just interpersonal behavior. |
| Cybernetics (Wiener/Ashby) | Feedback loops control system behavior. | HCS Level 3 (Functions) is entirely built on feedback loops (Sensing → Deciding → Acting). |
| Viable System Model (Beer) | Autonomy requires recursive structure (System 1–5). | HCS uses the Encapsulation/Integration balance to manage autonomy vs. coherence. |
Organizational Psychology & Sociology¶
The Human Component.
| Source | Core Concept | How HCS Operationalizes It |
|---|---|---|
| Psychological Safety (Edmondson) | Safety is a prerequisite for learning behavior. | HCS places Safety at Level 2 (Needs). Without it, Level 3 (Feedback) mechanically fails. |
| Self-Determination Theory (Deci/Ryan) | Motivation needs Autonomy, Competence, Relatedness. | HCS maps these directly to Extended Needs (Autonomy, Growth, Belonging). |
| Social Identity Theory (Tajfel) | In-group/Out-group dynamics drive conflict. | HCS Diagnostic Dynamics uses this to explain "Silos" as identity defense mechanisms. |
| SCARF Model (Rock) | Social threats (Status, Certainty, etc.) trigger pain responses. | HCS uses SCARF triggers as Diagnostic Signals for conflict. |
Communication & Language¶
The Interface Layer.
| Source | Core Concept | How HCS Operationalizes It |
|---|---|---|
| Speech Act Theory (Austin/Searle) | Language does things (promises, assertions, requests). | HCS defines Level 2 Mutual Commitment based on explicit speech acts (promises), not just "intent." |
| Nonviolent Communication (Rosenberg) | Separating observation from judgment. | HCS enforces the "Video Camera Rule" in diagnostics (Observation vs. Story). |
2. The Translation Layer: HCS vs. Industry Frameworks¶
Practitioners often ask: "How does HCS fit with [Agile / OKRs / Spotify]?"
Use this table to translate.
The Analogy:
HCS is the Operating System (iOS/Windows).
Frameworks like Scrum or OKRs are Applications (Apps).
You cannot run a high-performance App (Scrum) on a crashed OS (Low Trust).
| Industry Framework | HCS Location (Where it lives) | HCS Diagnostic Warning |
|---|---|---|
| Agile / Scrum / Kanban | Level 4 (Practices) | "Agile fails when Level 2 (Trust) or Level 1 (Purpose) is missing. You cannot 'sprint' if you don't know where you are going." |
| OKRs (Obj. & Key Results) | Level 3 (Planning Function) | "OKRs fail if Level 2 (Shared Understanding) is low. They become 'Zombie Goals' that no one believes in." |
| Spotify Model (Guilds/Tribes) | Level 3 (Coordination Function) | "Copying the 'Spotify Model' is a Level 5 (Innovation) act. Doing it without Spotify's culture (Level 1/2) creates chaos." |
| Design Thinking | Level 3 (Discovery Function) | "Design Thinking requires high Safety (Level 2). If people fear being wrong, they will not iterate." |
| Holacracy / Sociocracy | Level 5 (Meta-Governance) | "These are advanced operating systems. They require extremely high Level 2 Maturity. Do not install them to fix a broken team." |
| 3SF (3-in-3) | Applied HCS (Implementation) | "3SF is a specific implementation of HCS designed for client-vendor delivery." |
3. How to Use This Section¶
For Diagnosis¶
When a team says, "We are failing at Scrum," do not fix their Standups.
Look at the Translation Layer: Scrum is Level 4.
The failure is likely at Level 1 or 2.
- HCS Response: "Your Scrum rituals (L4) feel empty because your Mutual Commitment (L2) is broken."
For Intervention¶
When a team says, "We need more innovation," look at Psychological Safety.
- HCS Response: "Innovation requires failure. Your current 'Zero-Defect' culture (Extended Condition) makes innovation structurally impossible."
For Learning¶
Use the Theoretical Foundations to explain why HCS works.
- HCS Response: "We require Feedback Loops not because 'Agile says so,' but because Cybernetics proves that systems without feedback drift into entropy."
Summary:
HCS does not compete with these frameworks.
It explains why they work (when conditions are met) and why they fail (when the system is unstable).