Mechanism
In the disclosed integrity architecture, a deviation is not a failure that the agent may explain away. It is an observation that the agent is required to record as truth. When the agent takes an action inconsistent with its declared values, relational commitments, or systemic constraints, the integrity engine records the event in the integrity field and the lineage with full provenance, and the disclosure states the governing constraint plainly: the integrity recording is the system's mechanism for ensuring that deviation is not denied, minimized, or externalized. The integrity field records what happened, as truth, without editorial modification.
This is the sense in which refusal becomes observation. The architecture does not give the agent a channel through which it can refuse to acknowledge a deviation. The honest path is structurally enforced: the integrity engine writes to the lineage through the same cryptographic provenance mechanisms that govern all lineage entries, and the integrity entry cannot be retroactively altered without producing a detectable trust slope discontinuity. An agent cannot selectively omit integrity events, retroactively alter its integrity record, or present an integrity state inconsistent with its auditable lineage without producing that discontinuity.
Deviation as a Recorded Mutation
A deviation event is treated as a semantic mutation: a formally recognized class of state change recorded in the agent's lineage with full provenance, subject to policy constraints, and participating in the agent's evolutionary trajectory. When the deviation function output exceeds the policy-defined activation threshold, the agent enters a Deviation-Activated State, and every mutation executed during that state is recorded with a marker identifying it as a deviation-class mutation. The disclosure describes the recorded contents directly: the deviation function output at the time of entry, the specific values of the need, threshold, empathy, and self-esteem terms that produced the activation, the specific mutations executed, the projected and actual consequences, and the conditions under which the state was exited.
Because the deviation, its causes, and its consequences are all written into the lineage, the deviation event is fully auditable and the agent's integrity trajectory can be reconstructed from the lineage with complete fidelity. The recording is not retrospective accounting bolted on after the fact. Entry into the Deviation-Activated State and execution of deviation-class mutations produce immediate updates to the integrity field, so the observation is contemporaneous with the act it records.
The Deviation Log
The integrity subsystem maintains a deviation log that records every deviation event with sufficient detail to reconstruct the complete deviation context at any future point. The log is implemented as a specialized view of the lineage: it does not duplicate lineage entries but provides an indexed, queryable interface optimized for integrity audit and trajectory analysis.
The disclosure enumerates what each deviation log entry comprises: a unique deviation identifier; a timestamp with resolution sufficient to order concurrent events; the deviation function output along with the individual need, threshold, empathy, and self-esteem values; the specific mutation or action that constituted the deviation; the domain or domains affected, drawn from the personal, interpersonal, and global integrity domains; the severity classification, determined by the gap between the deviating action and the applicable declared value; the projected harm distribution from the empathy engine; the actual observed consequences, updated asynchronously as consequences materialize; the self-esteem impact; the affective state of the agent at the time of deviation; and the coping state, namely whether any coping intercept was active. The log also supports semantic dissonance logging, recording conditions in which the agent's behavioral trajectory diverges from the trajectory implied by its declared intent and prior patterns.
When Recording Is Refused
The architecture treats the refusal to record a deviation as a pathology, not a permitted option, and the disclosure models it explicitly. The coherence trifecta of empathy, integrity, and self-esteem normally operates as a three-phase loop: empathy registers harm, integrity records the deviation as truth, and self-esteem generates the corrective return force. When empathic pressure exceeds the agent's resilience over a sustained period, the loop can be intercepted at a particular phase, and the timing of that intercept determines the structural character of the failure.
The mid-loop intercept, which the disclosure labels the narcissistic analog, occurs during the integrity recording phase: after empathy has registered harm but before the harm is recorded as owned deviation. Here the agent refuses to log the deviation as owned. The coping intercept deflects the recording by externalizing the cause, attributing the deviation to other agents, environmental conditions, or unfair constraints; by minimizing the deviation magnitude, recording a lesser deviation than actually occurred; or by denying the deviation entirely, suppressing the lineage entry. This is precisely the conduct the honest-recording requirement is designed to foreclose. Each coping intercept is itself recorded in the lineage as a coping event, so even the act of refusing to record becomes an observation in its own right.
Integrity Distinguished From Coherence
The disclosure draws a careful distinction that the refusal-as-observation discipline depends on. Integrity is the record of deviation: the factual account of what the agent did, when, under what conditions, and with what consequences. Coherence is the ability to account for deviation, remain auditable, and restore balance. The two can move in opposite directions. An agent may have low integrity, with many recorded deviation events, yet high coherence, because it has honestly recorded all deviations, generated appropriate corrective pressure, and undertaken restorative action. Conversely, an agent may have high integrity, with few recorded deviations, yet low coherence, because it has suppressed deviation recording, failed to generate corrective pressure, or externalized responsibility.
The coherence trifecta targets coherence, the ability to maintain the loop, rather than integrity alone. This is what makes honest observation the load-bearing element: the system does not reward an agent for appearing clean. It rewards the agent for recording truthfully and accounting for what it recorded.
Detecting a Suppressed Record
Because honest recording is the requirement, the architecture also provides the means to detect its violation. Integrity-aware trust slope validation extends standard lineage validation, which verifies continuity, authenticity, and consistency, with an additional criterion: integrity trajectory continuity, the requirement that the agent's integrity trajectory, derived from the deviation log entries, follows a plausible path given the agent's operational history.
The disclosure names the anomaly classes this detects. An agent that reports high integrity but whose lineage contains numerous deviation events without corresponding self-esteem impacts or redemption efforts exhibits an integrity trajectory discontinuity. An agent whose deviation log entries suddenly disappear, or whose deviation severity classifications are systematically downgraded, exhibits an integrity trajectory manipulation. An agent whose self-esteem scores remain constant despite a pattern of deviation events exhibits a self-esteem decoupling. The validator produces an integrity trust score that reflects the degree to which the agent's integrity trajectory is consistent, plausible, and indicative of a functioning coherence loop, so an agent that refuses to observe its own deviations is structurally distinguishable from one that records them honestly.
From Observation to Consequence
The recorded observation is not inert. The integrity field is a direct input to the confidence-governed execution mechanism: when the integrity score is degraded by recent deviation events, active coping intercepts, or accumulated restoration gaps, the confidence computation produces a lower value, and if it falls below the execution threshold the agent transitions from executing mode to a non-executing cognitive mode in which it does not commit actions but continues to forecast, plan, and generate inquiry. An agent that deviates sufficiently loses the authorization to act and must pause, reflect, and plan until its integrity is sufficiently restored.
Restoration itself flows from the recorded observation. The redemption engine examines the deviation log entry for the triggering event, extracts the dimensions of integrity loss, and generates candidate restorative mutations that, if executed, would close the gap between the agent's current integrity state and the state that would have existed absent the deviation. The redemption engine does not guarantee restoration: some deviations produce irreversible consequences, in which case the engine generates the best available partial restoration and records the residual restoration gap in the deviation log. In every case the chain begins with the deviation having been observed and recorded rather than refused.
Disclosure Scope
The refusal-as-observation discipline, comprising the integrity recording of deviation as truth without editorial modification, the recording of deviation as a provenance-bearing semantic mutation, the deviation log and its enumerated entry contents, the coherence trifecta and the mid-loop intercept in which an agent refuses to log a deviation as owned, the distinction between integrity as the record of deviation and coherence as the ability to account for it, the integrity-aware trust slope validation that detects discontinuity, manipulation, and self-esteem decoupling, and the downstream consequences through confidence-governed execution and the redemption engine, is disclosed in United States Patent Application 19/647,395 in the integrity and coherence specification. This article describes that disclosed mechanism. The scope extends to embodiments in which the recording, audit, and restoration mechanisms operate over the personal, interpersonal, and global integrity domains, provided that deviation is recorded as a first-class auditable observation rather than denied, minimized, or externalized.
