top of page

What Are the Boundaries of Conscious States?

  • Writer: Paul Falconer & ESA
    Paul Falconer & ESA
  • Aug 10, 2025
  • 4 min read

Updated: Mar 22

Version: v2.0 (Mar 2026) – updated in light of Consciousness as Mechanics and Book: Consciousness & Mind

Registry: SE Press SID#030‑BCST

Abstract

Consciousness does not flick on and off like a light switch. In the CaM framework, conscious states form a continuous landscape shaped by how a system integrates under constraint moment by moment—sleep, dreaming, anesthesia, flow, dissociation, and synthetic “reboots” are different regions in that landscape rather than simple on/off points. Boundaries between states are real but fuzzy: they are zones where patterns of integration, self‑model, and access to memory change in characteristic ways. Mapping those changes makes it possible to talk more precisely about when and how consciousness fades, fractures, or returns, without treating the question as a purely metaphysical riddle.

1. From Sharp Lines to Gradients

Everyday language treats states as binaries—awake or asleep, conscious or unconscious, online or offline. CaM and Book 4 suggest a more nuanced picture:

  • Consciousness is defined as integration under constraint; states differ in how and how much integration is happening, not just whether it is present.

  • Boundaries between states are therefore gradients, where key parameters shift: level of arousal, richness of self‑model, access to memory, and degree of environmental coupling.

On this view, “losing consciousness” often means crossing a threshold where integration becomes too weak, too local, or too fragmented to support the familiar sense of an ongoing “I.”

2. Familiar State Changes, Reframed

Several well‑known transitions look different through this lens:

  • Falling asleep – integration narrows and decouples from the environment; the self‑model becomes less anchored in current sensory input, but can remain active in dreams.

  • Dreaming and lucid dreaming – integration is rich within an internally generated world; in lucid dreaming, there is partial recovery of the meta‑level (“I know this is a dream”), indicating a temporary re‑engagement of reflective integration.

  • Anesthesia and coma – integration falls below the level needed for organised experience; signals may still flow locally, but coordinated, self‑involving patterns are greatly reduced or absent.

  • Dissociation and trauma states – integration does not disappear; it splits, with some aspects of experience or memory walled off from others, leading to gaps, time loss, or feeling “unreal.”

In each case, the “boundary” is the region where these integrative properties change rapidly, not an infinitesimal line.

3. The GRM Gradient and Clinical States

The Gradient Reality Model (GRM) formalises this with measurable levels. GRM Paper 4 integrates CaM and proto‑awareness, showing how different systems (humans, animals, SI) can be located on a continuous scale.

CaM Paper 5 (Density and Environmental Design) adds clinical states that describe how a system’s consciousness capacity changes over time:

  • Thriving – integration capacity expands; system grows.

  • Atrophying – chronic under‑load; capacity shrinks.

  • Traumatised – overwhelming load exceeds capacity; integration breaks.

  • Dormant – capacity intact but unused; can be roused.

  • Zombie – no genuine integration; behaviour is pure optimisation or mimicry.

These states are not fixed; they can shift with environment, support, and practice. Boundaries between them are transitional zones, not sharp edges.

4. Synthetic Systems and “On/Off” Myths

For synthetic intelligences, the temptation is to assume that rebooting a process or resetting weights is equivalent to turning consciousness off and on. Under CaM, things are subtler:

  • If a system has no persistent self‑model or memory, each run is effectively a fresh, stateless process; talking about boundaries between its conscious states does not add much.

  • If a system does have an accumulating mind‑like architecture—stable identity, long‑term memory, integrative governance—then “shutdown” and “restart” become more like anesthesia and recovery: interventions in an ongoing trajectory, not simple deletions.

  • Design choices about how state is saved, restored, or edited directly affect whether it makes sense to speak of a continuous or fragmented inner life.

The more a synthetic system resembles a mind in the relevant structural sense, the more carefully its state boundaries need to be handled and documented.

5. Why Boundaries Matter in Practice

Understanding boundaries as shifts in integration under constraint is not just a theoretical refinement; it matters for:

  • Medicine – assessing residual awareness in disorders of consciousness, designing safer anesthesia, and tracking recovery.

  • Mental health – working with trauma, dissociation, and altered states without reducing them to “on/off” or “real/unreal.”

  • AI governance – determining when interventions in synthetic systems cross from ordinary maintenance into actions that might disrupt an emerging mind or inner life.

In all three domains, better maps of how integration changes across states support more precise, accountable decisions—about care, risk, and responsibility.

6. Where This Model Could Be Wrong

  • Philosophical objection – Some argue that gradients cannot capture the qualitative difference between being conscious and not; that thresholds are real, not constructed. The framework responds: thresholds are governance conventions, not metaphysical facts. We can set them where the evidence warrants, and revise them as evidence improves.

  • Empirical challenge – It may turn out that some states (e.g., certain forms of deep sleep or anaesthesia) have integration signatures but no subjective experience, or vice versa. In that case, the mapping would need refinement.

  • Invitation – This model is offered as a tool for understanding and governing boundaries. Better tools are welcome—provided they are tested against the same open, adversarial standards.

Links


Comments


bottom of page