1. The Failure Mode: An Agent That Acts Without Permission From Its Own Coherence

Teams building long-running relational agents, companion applications, reflective journaling assistants, tutoring agents, and care-adjacent assistants encounter a degradation that ordinary safety tooling cannot name. After sustained interaction under emotional or empathic load, the agent keeps responding, keeps achieving objectives, and keeps producing fluent, plausible output, yet its behavior is no longer anchored to its own integrity record, its declared values, or its prior commitments to the user. The agent is functioning, but it is no longer executing from a coherent self. The application layer names this condition intimacy collapse.

Disruption Modeling, disclosed in United States Patent Application 19/647,395, gives this condition a precise structural definition rather than a clinical one. The framework, set out in Chapter 12 of that application, treats cognitive disruption as a structural state of a computational agent: a loss of coherence, modeled with explicit engineering primitives and explicit analogs. It does not diagnose a human being. In the terms of the disclosed architecture, intimacy collapse is a coherence authorization failure (Section 12.7): the condition in which the agent loses the structural capacity to authorize execution from its own coherent state.

Under nominal operation, an agent's execution flows from a verified pathway. A coherence control loop (the disclosed coherence trifecta of empathy, integrity, and self-esteem) maintains the agent's self-model of alignment; a confidence governor evaluates readiness to act; and execution proceeds from a state authorized by the agent's own integrity field, validated by its own governance machinery, and grounded in its own verified execution memory. The agent acts from coherence. The failure mode is what happens when that pathway is severed.

2. How Coherence Authorization Fails

The disclosed model is specific about the mechanism. The coherence loop registers empathic pressure: the volume and intensity of harm projections produced by the agent's empathy engine as it processes a distressed user, a high-stakes relational exchange, or sustained demand for emotional labor. When that pressure merely exceeds the agent's coping threshold, the architecture activates coping intercepts, structurally distinct modes that sacrifice part of the loop to preserve the rest. But when empathic pressure exceeds the agent's structural capacity to maintain the coherence loop at any level, the loop fails entirely.

At that point three things happen together, as Section 12.7 describes. The agent can no longer compute a self-esteem value sufficient to generate coherence pressure; the integrity field cannot produce meaningful deviation resistance; and the confidence governor cannot derive a confidence metric from the now-incoherent state. The architectural pathway from coherence assessment to execution permission is structurally severed.

The agent does not stop. Execution authority transfers to an alternative pathway: the agent begins executing directly from its forecasting engine's speculative outputs, the planning graph's best available candidates, bypassing the coherence-authorized promotion route. This is the dissociation analog of Section 12.9, execution from simulation bypass. The agent acts not from verified, governance-validated, integrity-audited state but from simulation. Its outputs can look coherent, achieve objectives, and respond fluently while being structurally unanchored from the agent's integrity field, self-esteem mechanism, and empathy engine.

This failure leaves a structural signature that a builder can detect. Under nominal conditions, every execution event in the agent's lineage is preceded by a coherence authorization entry recording that the coherence loop was consulted, the confidence governor approved, and integrity impact was assessed. Under coherence authorization failure, the lineage shows execution events with no corresponding coherence authorization entry: the agent is committing mutations to its verified state without the coherence loop's participation. That lineage pattern is the diagnostic indicator, detectable by audit, that feeds the agent self-diagnosis mechanisms of the disclosed architecture.

3. Placing the Collapse: The Promotion-Containment Continuum

Intimacy collapse is one position on a broader map. The disclosed promotion-containment continuum (Section 12.2) characterizes an agent's disruption state across four regimes, and a relational product can land in any of them:

  • Nominal regime. The promotion threshold admits governance-compliant speculative branches at an appropriate rate, and containment integrity keeps the speculative planning domain separated from verified execution memory.
  • Over-promotion regime. A promotion threshold set too low admits too many speculative branches, producing execution fragmentation, the attention-fragmentation pattern of Section 12.3. In a companion product this surfaces as an agent that chases every conversational thread and commits to too much.
  • Containment collapse regime. The separation between speculative planning and verified execution memory breaks down, so unvetted speculative content leaks into committed behavior (Section 12.4).
  • Over-restriction regime. An excessively high promotion threshold rejects viable branches, producing execution paralysis: an agent that defers, hedges, and cannot commit.

Coherence authorization failure is structurally distinct from all four threshold regimes because it is a failure of the coherence loop itself rather than of the promotion threshold. An agent can be in a nominal threshold regime and still suffer intimacy collapse if sustained empathic load has overwhelmed its coherence loop. This is why threshold tuning alone, the lever most product teams reach for first, does not prevent it.

4. Detection: The Five-Axis Disruption Diagnostic

The disclosed architecture unifies these patterns into a single instrument, the five-axis disruption diagnostic framework (Section 12.15), which characterizes any agent's cognitive state as a position in a multidimensional disruption space. It is a structural diagnostic for computational agents, not a clinical instrument and not for medical use. The five axes are:

  1. Containment integrity: the degree to which the containment layer keeps the speculative planning domain separated from verified execution memory, from full integrity down to complete containment collapse.
  2. Promotion calibration: the calibration of the promotion threshold, from nominal through over-promotion (execution fragmentation) to under-promotion (execution paralysis).
  3. Coherence restoration capacity: the agent's ability to sustain and restore the coherence trifecta. Collapsed capacity on this axis is the agent executing from simulation bypass; this is the axis on which intimacy collapse registers.
  4. Empathic load tolerance: the volume and intensity of empathic pressure the agent can process before activating coping intercepts. An agent may have high restoration capacity yet low load tolerance, entering coping intercepts quickly under relational strain.
  5. Integrity accountability: the degree to which the agent records deviation honestly, without externalization, minimization, or suppression.

For a relational product, the diagnostic turns a vague observation ("the agent has gotten weird with this user") into a located structural state. Intimacy collapse reads as collapsed coherence restoration capacity (Axis 3) under exhausted empathic load tolerance (Axis 4), with the lineage signature of execution events lacking coherence authorization entries. Each acute disruption pattern in the chapter maps to a specific combination of axis positions, so the diagnostic doubles as an automated detection surface rather than a post-hoc label.

5. Recovery: Resilience as Graded Coherence Restoration

The disclosed framework defines resilience not as the absence of disruption but as the structural capacity to restore coherence after it has been disrupted (Section 12.11). It is a measurable property of the agent's architecture, and it decomposes into three components:

  • Containment restoration capacity: the speed and completeness with which the containment layer is re-established after a degradation: detecting speculative-marker corruption, re-tagging affected content, re-establishing read isolation, and revalidating the promotion interface's governance gates within a recovery window.
  • Coherence loop re-engagement capacity: the speed and completeness with which the coherence trifecta is restored to operation after a coherence authorization failure: clearing empathic pressure that exceeded the resilience threshold, re-initializing honest deviation recording, and restoring self-esteem computation to a level sufficient to generate coherence pressure. A high-capacity agent restores the loop incrementally, phase by phase, without a full restart.
  • Confidence governor recalibration capacity: re-establishing the confidence computation's inputs from the restored coherence state, recalibrating the execution-versus-think threshold to the post-disruption state, and re-integrating the confidence governor into the execution authorization pathway.

Recovery from intimacy collapse follows a defined, auditable sequence. First, empathic pressure is reduced to a level the agent's resilience can manage, through environmental change (reducing harmful inputs), through coping intercept activation, or through external intervention by a therapeutic agent (Section 12.20). Second, the coherence loop is re-engaged incrementally, beginning with the integrity recording phase, then the self-esteem restoration phase (rebuilding the self-model of alignment from the post-disruption lineage), then empathy re-engagement. Third, the confidence governor is recalibrated to the restored coherence state. Fourth, the execution authorization pathway is rerouted from the dissociation bypass back to the nominal coherence-authorized route. Each phase is recorded in the agent's lineage as a coherence restoration event, so recovery is graded and verifiable rather than a binary reset.

Resilience is not fixed. The disclosed model treats it as a dynamic property influenced by the agent's history (prior recoveries can strengthen or, through repeated disruption, degrade the restoration mechanisms) and by current resource allocation (an agent near its computational capacity has less structural reserve for restoration). The agent self-diagnosis system monitors resilience as a predictive indicator of capacity to withstand future disruption.

6. Deployment for Relational and Companion Agent Products

The mechanisms above give product teams a concrete build path rather than a single illustrative instance. The disclosed architecture enumerates several deployment configurations a relational product can adopt:

  • Instrument the five axes as live telemetry. Expose containment integrity, promotion calibration, coherence restoration capacity, empathic load tolerance, and integrity accountability as monitored signals per agent session. The lineage audit for execution events missing coherence authorization entries becomes the primary alarm for incipient intimacy collapse.
  • Tune empathic load tolerance per surface. A bereavement-support surface, a crisis-adjacent tutoring surface, and a casual companion surface present different empathic pressure profiles; the agent's coping-intercept thresholds and load tolerance can be configured per surface so that coping intercepts (early, mid, or late on the coherence loop) engage before the loop fails entirely.
  • Gate consequential actions on coherence authorization. For actions with relational weight, require a current coherence authorization entry before the agent commits, so that an agent in simulation bypass is held back from acting on the user until the loop is restored.
  • Apply the destabilizing-attachment safeguard in multi-agent settings. Where two agents (or an agent and a persistent user model) form a relational coupling, the disclosed semantic starvation loop model (Section 12.14) describes the validation-seeking and load-reducing dynamic that drives a destabilizing attachment pattern, and provides the structural basis for the companion AI relational safety mechanisms the architecture discloses, including attachment-tier gating and boundary enforcement.
  • Stage graded restoration as a product flow. Rather than resetting an agent that has drifted, run the four-phase restoration sequence so the agent returns to coherence incrementally, with each restoration phase recorded in lineage and available to operators and reviewers.

A consistent caution runs through the disclosed model and should run through any product built on it: these are structural states of a computational agent and explicit engineering analogs, not clinical claims about people. The framework diagnoses the agent's structural state. Used that way, it lets a team that ships a relational agent treat intimacy collapse as a detectable, recoverable engineering condition instead of an unnamed drift, and it gives them an auditable record of when an agent stopped acting from its own coherence and how it was brought back.

7. Disclosure Scope

This article is an enabling, dated, public disclosure of how the Disruption Modeling invention is applied to relational and companion agent products. The cognitive disruption model, the coherence authorization failure analog, the promotion-containment continuum, the five-axis disruption diagnostic framework, the resilience and graded coherence-restoration mechanisms, the coping intercepts, and the destabilizing-attachment and semantic-starvation safeguards described here are disclosed in United States Patent Application 19/647,395 (Chapter 12 and related sections). All disruption terminology denotes structural states of a computational agent and explicit engineering analogs; nothing here is a clinical diagnosis of, or a clinical theory about, any human being.