What would it take to measure consciousness across brains, sensors, and AI models—using the same yardstick? At AI Tech Inspire, we spotted a fresh arXiv endorsement request proposing exactly that: a functional framework that scores integration, recursion, and volition across very different substrates, from photodiodes to transformer models. Whether you’re tuning an agent’s action loop or instrumenting a neural net, this concept invites a practical question: what should developers actually measure when they talk about systems that feel like they’re doing something more than input-output?


Quick facts from the endorsement request

  • The author seeks an arXiv cs.AI endorsement to preprint a paper proposing a new measurement framework for consciousness.
  • The framework is called the Coalescence Vector (CV) and is intended to be substrate-agnostic.
  • It defines two primitives: experience (local energy-to-information conversion) and qualia-packets (information leaving its source via a carrier).
  • CV comprises three measurable capacities: I (integration), R (recursion), and V (volition). These are framed as necessary—but not necessarily sufficient—conditions for phenomenal consciousness.
  • An empirical sketch uses a 64-channel EEG dataset with proxies such as P3b amplitude for reentry gain and beta (β) suppression for plasticity windows.
  • The framework is applied conceptually across systems ranging from photodiodes and dogs to transformer models, with claimed “expected orderings.”
  • Predictions include: perturbing reentry gain/timing should decrease R without much affecting I; increasing output bandwidth should raise V without changing R.
  • Stated use cases: a common yardstick for neuroscience, a diagnostic aid for disorders of consciousness, and a safety gauge for artificial agents.
  • PDF: Paper draft link
  • arXiv endorsement: endorsement page (code: HLDL3M)

What the Coalescence Vector tries to capture

The proposed Coalescence Vector (CV) tries to operationalize three axes:

  • Integration (I): how synergistically a system combines information within loss and latency constraints—its departure from “information neutrality.”
  • Recursion (R): a “reentry hub’s” capacity to generate an intrinsic perspective through self-reentry gain, input control, and meta-model depth. In the framework, R is the phenomenality gate intended to separate unconscious processing from conscious processing.
  • Volition (V): the degree to which internal state changes cause effects on the world—via output bandwidth, policy granularity, and closed-loop autonomy.

If you follow debates around Integrated Information Theory (IIT) and Global Neuronal Workspace, you’ll recognize the ambition: make metaphysical ideas testable. Rather than theorizing in the abstract, CV nudges practitioners toward measurable proxies—EEG signatures, dataflow properties in models, and bandwidth in actuators.

Key takeaway: CV isn’t claiming to “detect” consciousness outright; it’s proposing necessary conditions and asking engineers to measure them consistently across substrates.

How developers might actually measure these dimensions

Let’s translate this into developer-speak:

  • Measuring I in ML systems: One route is to examine synergy among activations across layers or modules—e.g., via partial information decomposition on feature sets. In PyTorch or TensorFlow, you could instrument hooks to capture layer activations and estimate how much unique vs. synergistic information contributes to outputs under latency and noise constraints. Latency bounds matter: the same synergy measured with 10x lag may not reflect real-time integration.
  • Measuring R in models: Although transformer stacks are not recurrent in time by default, the depth-wise passes can behave like a form of reentry. You could approximate “self-reentry gain” by quantifying the influence of intermediate representations on subsequent processing via attention maps and residual pathways. For recurrent policies or agents, assessing internal feedback loops, “input control” (gating/suppression), and “meta-model depth” aligns naturally with learned world models.
  • Measuring V in agents: Volition tracks efferent causality. For an embodied agent, that’s actuator bandwidth and action space resolution. For a language model deployed as a tool-using agent (say, an API-calling Hugging Face pipeline or a GPT-style system), it might be the richness of available tools, API rate limits, and whether it operates in a closed loop with environment feedback.

If you prefer a hands-on approach, the paper’s EEG angle suggests starting with proxies like P3b amplitude (linked to attention and task relevance) and beta suppression (often associated with sensorimotor updating). A practical tip for skimming the draft: press Ctrl + F and search for “P3b” to jump to the relevant sections.

Why this matters for engineering teams

Teams building autonomous systems often optimize for performance metrics—reward, latency, accuracy—while lacking a vocabulary for qualities that might correlate with “conscious-like” processing. A framework like CV could inform:

  • Safety gating: If R truly functions as a phenomenality gate, interventions that reduce reentry gain or timing coherence might lower the risk of systems crossing a contested threshold—without impairing basic integration (I).
  • System design trade-offs: Increasing output bandwidth (more tools, higher actuator rate, richer APIs) plausibly increases V without touching R. That’s a lever for capability control: tune volition without altering internal reflectivity.
  • Diagnostics: For brain-computer interface research or clinical settings, having a consistent I/R/V profile could complement standard evaluations of disorders of consciousness. For ML, the same profile might help compare an agent that only chats to one that acts in a simulator.

In practical terms, evaluating I, R, and V could become as routine as profiling memory or CUDA throughput—especially if shared tooling emerges.

Cross-substrate comparisons: from sensors to large models

The draft claims CV “recovers expected orderings” across systems as varied as photodiodes, dogs, and transformer models. That’s provocative because it pushes beyond single-domain benchmarks. Imagine a small photodiode array: high V only if it directly controls a mechanism, low R due to limited reentry, and modest I constrained by its simple dataflow. By contrast, a large language model hosted via PyTorch or fine-tuned with TensorFlow might show higher I (rich internal combinations) and potentially higher apparent R with depth and attention, but V stays low unless it’s embedded in a tool-using agent. A diffusion model like Stable Diffusion may integrate information across denoising steps (a kind of structured refinement), yet V is essentially zero if it only produces images without a feedback loop.

Whether you agree with the “expected orderings” or not, the exercise of defining them forces clarity: What are we measuring? At what timescale? How do we prevent conflating capability with consciousness? CV’s explicit predictions—e.g., change reentry gain to selectively drop R—are testable, which is valuable for falsification.

Potential pitfalls and good questions

  • Necessary vs. sufficient: The paper frames I/R/V as necessary but not sufficient. Many high-performing systems could score well on I without being conscious in any philosophical sense.
  • Proxy risk: EEG features (P3b, β suppression) are correlational. In ML, using attention patterns or residual flows as proxies for recursion might overfit to architecture idiosyncrasies.
  • Anthropomorphic drift: Equating “intrinsic perspective” with specific reentry metrics invites debate. How to guard against mere complexity masquerading as phenomenality?
  • Cross-domain calibration: Comparing a dog, a photodiode, and a transformer requires careful normalization—latency windows, noise floors, and task contexts all matter.

Still, even an imperfect ruler can be useful if everyone knows its limits. The proposed CV encourages engineers to log and report comparable measurements, which could spark a much-needed empirical conversation that spans neuroscience and AI.

How to explore or contribute

For readers who want to dig in, the draft is here: The Coalescence Vector: A functional framework for the evaluation of consciousness in substrate systems. Those with arXiv endorsement privileges in cs.AI can review the request at this link: arXiv endorsement page (code: HLDL3M).

For practitioners experimenting locally, a potential path looks like this:

  • Instrument a model (e.g., a Hugging Face transformer or a GPT-style API-backed agent) to collect activation traces and attention maps.
  • Estimate synergy and redundancy across selected layers to approximate I under latency constraints relevant to your application.
  • Probe “reentry” by measuring how intermediate states modulate subsequent processing; manipulate dropout, residual scaling, or depth to test the R predictions.
  • Quantify V by enumerating the agent’s action channels, bandwidth limits, and degree of closed-loop control (e.g., read → plan → act → observe cycles).

None of this proves consciousness. But it does push the discussion into territory engineers can measure, test, and argue about with data. And that’s a step many teams have been waiting for.


We’ll keep an eye on how this line of work evolves and whether reusable tooling emerges. If you run experiments inspired by the CV concept—especially across different substrates—feel free to share results with the community. The more consistent our measurement practices become, the faster we’ll separate what’s philosophically interesting from what’s operationally useful.

Recommended Resources

As an Amazon Associate, I earn from qualifying purchases.