This document clarifies the distinction between **flow**, **group flow**, and **vibe**, and explains why *vibe work* names a coordination state that is related to — but not reducible to — existing theories. The goal is not to replace prior frameworks, but to **locate vibe precisely within them**. --- ## Flow (Individual) **Flow** is a well-studied intrapersonal cognitive state characterized by: - intense focus - loss of self-consciousness - distortion of time perception - intrinsic reward - balance between challenge and skill Flow is: - internally generated - neurocognitively bounded - dependent on individual attention and skill - fragile under interruption Flow theory explains **how humans enter optimal cognitive states**. It does not explain how those states persist across: - interruptions - external systems - collaborators - long time horizons Flow is *human-only* in the sense that: - the locus of coherence is the individual - tools are external supports, not co-participants --- ## Group Flow (Human–Human) **Group flow** extends flow theory to teams. It describes moments where: - participants are mutually attuned - communication is fluid - roles are implicitly coordinated - collective performance exceeds individual capacity Group flow depends on: - shared goals - trust - social cues - synchronized attention - low friction communication Critically: - group flow remains a **human–human phenomenon** - tools are still passive substrates - memory and continuity are socially maintained Group flow explains **why great teams feel unstoppable**. It does not explain how coordination persists when: - teams change - work is asynchronous - memory is externalized into systems - machines become active contributors --- ## The Coordination Gap Modern knowledge work introduced a structural break: - work is fragmented across tools - teams are asynchronous - memory is externalized - decisions span weeks or months - participants rotate in and out This creates a **coordination gap**: - flow collapses - group flow cannot be sustained - humans compensate with planning, meetings, and documentation See: - [[99-00 Coordination Gap.md|The Coordination Gap]] - [[99-09 Fragmentation.md|Fragmentation]] Existing flow frameworks do not address this gap. --- ## Vibe (Human–Machine Coordination) **Vibe** names a coordination state where: - alignment is maintained *across time* - intent persists beyond a single session - context does not need to be restated - sequencing emerges naturally - momentum compounds instead of resetting Vibe is not an emotional state. > **Vibe is sustained low-friction co-orientation between human intent and machine response.** Key properties: - inter-agent (human + system) - longitudinal (not momentary) - infrastructure-dependent - continuity-driven, not attention-driven Where flow is about *immersion*, vibe is about *continuity*. --- ## Why Vibe Is Not Just “Flow with Better Tools” A common critique is that vibe is simply flow enhanced by better interfaces. This is incorrect. Flow: - requires uninterrupted attention - collapses when context is lost - is session-bound Vibe: - survives interruption - resumes after gaps - depends on preserved state, not sustained focus In vibe work, the system: - remembers what mattered - maintains sequence - preserves rationale - re-orients the human on return The burden of continuity shifts from the person to the environment. --- ## Why Vibe Is Not Group Flow with Machines Added Another critique is that vibe is simply group flow extended to include AI. This also fails. Group flow depends on: - shared human cognition - social signaling - mutual awareness Machines do not participate in group flow in this way. Vibe does not require: - trust in a social sense - emotional attunement - shared consciousness Instead, it requires: - reliable state tracking - intent inference - predictable response - low coordination tax Vibe is **structural**, not social. --- ## Coding as the First Observable Case Vibe became visible first in coding because: - feedback is immediate - correctness is legible - intent can be inferred - AI competence crossed a threshold “Vibe coding” is not a new form of flow. It is the first domain where **human–machine continuity** became experientially obvious. Coding was the probe. Vibe work is the generalization. --- ## Summary Comparison | Dimension | Flow (Individual) | Group Flow | Vibe | |------------------|------------------|------------|------| | Locus | Human mind | Human group | Human–machine system | | Time horizon | Momentary | Session-based | Longitudinal | | Fragility | High | Medium | Low (by design) | | Depends on focus | Yes | Yes | No | | Depends on memory| Human | Social | Environmental | | Scales with complexity | Poorly | Poorly | Well | --- ## Why This Distinction Matters Mislabeling vibe as flow leads to: - underestimating infrastructure requirements - over-optimizing for UX - blaming humans for breakdowns caused by systems Vibe work requires: - persistent memory - passive observation - intent modeling - sequence preservation These are **system-level properties**, not psychological ones. Understanding this distinction is critical to: - product design - category clarity - defensible positioning --- ## Related Concepts - [[01 Vibe Work.md|Vibe Work]] - [[99-08 Coordination Tax.md|Coordination Tax]] - [[99-11 Failure Modes of Vibe Work.md|Failure Modes of Vibe Work]]