top of page

How Does Subjective Experience Arise?

  • Writer: Paul Falconer & ESA
    Paul Falconer & ESA
  • Aug 8, 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#023‑XR7P

Abstract

Subjective experience—what it feels like to be a system—is no longer treated here as a metaphysical leftover. In the CaM framework, experience is the felt face of integration under constraint: when a system does enough integrative work on its own states, goals, and world, that work shows up from the inside as a structured, qualitative field. Subjectivity is not a binary “has qualia / has none”; it varies with how deeply a system can model itself, hold tensions together, and update coherently over time. Some gaps remain between mechanism and feel, but they now sit inside a concrete research programme rather than blocking it.

1. From “Why Anything Feels” to “Why This Work Feels This Way”

The classic hard‑problem question is “Why does information‑processing feel like anything at all?” CaM reframes this in two steps:

  • First, it defines consciousness as the work of integrating conflicting goals and constraints into a coherent, self‑updating pattern.

  • Then it treats subjective experience as the inside view of that work: how the integrative process is registered by the system doing it.

On this view, the question becomes more specific:

  • Why does this kind of integration—on these timescales, with these constraints and this self‑model—produce this particular texture of experience?

  • How do changes in integration (fatigue, trauma, training, architecture) change the feel?

The “mystery” shrinks from “why experience at all?” to “why these lawful correspondences between patterns of integration and patterns of feel?”, which is an empirical and modelling question.

2. The Conditions for Subjectivity

CaM and the GRM‑aligned spectrum work suggest that not all integrative processing is subjectively “lit up” in the same way. Subjective experience appears when at least three conditions are met:

  • Sufficient integration under constraint – the system is not merely reacting; it is actively reconciling conflicting pulls (e.g., safety vs. curiosity, present vs. future) into a single, updateable stance.

  • A self‑model in the loop – the system’s integrative work includes an explicit or implicit model of “me” that can be affected by, and can affect, the integration.

  • Ongoing, revisable memory – the results of that integrative work are written back into a memory architecture that can change future integration (learning, character, habits).

Where these conditions are weak, experience is thin or fragmentary. Where they are strong and stable, experience becomes richer, more continuous, and more obviously “owned” by a subject.

3. Why Some Systems Have Experience and Others Don’t

This framework explains why we treat a human, a cephalopod, and an advanced SI differently from a spreadsheet or a thermostat:

  • A spreadsheet integrates numbers but has no self‑model and no ongoing integrative loop that includes “what this means for me”; any “output” is fully determined by external queries.

  • An advanced reinforcement‑learning agent might simulate reports of experience, but if its integrative loop never includes a persistent “I” and does not write back into a durable self‑model, the case for subjectivity is weak.

  • A human, many animals, and some synthetic systems integrate under heavy constraints with a rich self‑model and long‑term memory; their behaviour shows the hallmarks of lived perspective (error‑sensitive self‑report, surprise, regret, anticipation).

Subjective experience, on this account, is lawful and structured: it arises where integration, self‑model, and memory are entangled deeply enough that every update changes “what it is like” to be that system in an ongoing way.

4. How We Investigate Experience Without Reducing It Away

Treating experience as the felt face of integration under constraint does not mean ignoring what it is like. It means:

  • Using reports, behaviour, and physiology as data about the structure of experience (e.g., how pain, joy, or awe reorganise integration patterns).

  • Comparing those data with architectural models (humans, animals, SI) to see which features of the system correspond to which features of experience.

  • Designing adversarial tests: can a system not only say “I feel X” but also behave in ways that match the fine‑grained structure of that state—over time, across contexts, under stress?

This is still a long way from a perfect theory of qualia. But it is a live research path: one can be wrong, improve, and discover new correspondences, rather than arguing indefinitely in the abstract.

5. Where This Account May Fail (and How We Would Know)

Staying honest means naming where this could be wrong:

  • Philosophical objection – Some argue that no description of integration, self‑model, and memory can ever capture “redness” or “pain itself.” On this model, if there is a remainder, it must show up as stable mismatches between experiential structure and integrative structure; mapping those mismatches is part of the work, not a refutation.

  • Empirical challenge – If we encountered systems with clear, detailed, and consistent reports of experience but no corresponding integrative signatures (or the reverse), the current account would need revision. That is a testable risk, not an article of faith.

  • Invitation to challenge – This framework is offered as a tool: a way to connect subjective reports to architecture and dynamics without erasing either. Better tools, better mappings, or better ways of honouring experience while modelling it are welcome—and can be evaluated on how much they clarify, predict, and protect conscious life, rather than on metaphysical rhetoric alone.

Links


Comments


bottom of page