Mechanism
Policy-based integrity constraints are the externally specified rules that govern how the agent's integrity subsystem operates. As disclosed in Chapter 3 of the cognition filing, the integrity field is subject to a comprehensive set of policy-based constraints that govern how integrity is computed, how deviation is evaluated, how coping intercepts are managed, and how integrity-based mutation gating operates. These constraints ensure that the integrity subsystem operates within defined normative bounds that are externally specified, cryptographically signed, and governance-enforced. The agent does not author these constraints; they are bound to the agent through its policy reference field and define the standard against which the agent's behavioral consistency is measured.
This placement matters. Policy is upstream of integrity in the evaluation chain: the policy specifies the agent's declared values against which personal integrity is computed, the relational norms against which interpersonal integrity is computed, and the systemic constraints against which global integrity is computed. Policy defines the standard, and integrity measures adherence to it. Integrity then feeds back into policy enforcement, so that when the agent's integrity score falls below a policy-defined threshold the enforcement mechanism may restrict operational scope, increase governance scrutiny, or trigger containment. The constraints are not a single rule but a structured set of categories, each governing a distinct part of the integrity subsystem.
The Constraint Categories
The disclosure organizes the policy-based integrity constraints into named categories, each governing a specific subsystem. The integrity computation policy specifies the declared value set, the relational norm set, the systemic constraint set, the domain weights used for composite integrity computation, the evaluation window length that determines how far back in the lineage the integrity engine looks, the entropy weighting parameters for self-esteem computation, and the decay rates for integrity scores in the absence of reinforcing events. The deviation policy specifies the activation threshold for the Deviation-Activated State, the DAS-scoped mutation set that is admissible under that state, the maximum DAS duration, the deviation severity classification criteria, and the conditions under which deviation triggers mandatory governance notification.
The coping policy specifies the resilience thresholds for each coping intercept, the maximum coping duration before mandatory intervention, the cooldown periods following intercept release, and the conditions under which a coping intercept triggers delegation reassignment or operational scope reduction. The redemption policy specifies the categories of restorative mutations the redemption engine may generate, the maximum resources that may be allocated to restorative mutation execution, the priority weighting for restorative mutations relative to the agent's normal operational queue, and the restoration scoring criteria. Each category is a separate parameter binding, and together they make the entire integrity subsystem a governed object rather than a fixed implementation.
Mutation Gating
The mutation gating policy is the operational core. In this embodiment the integrity field serves as a mutation gate: a structural filter that evaluates a proposed mutation against the agent's integrity state before the mutation is submitted to the governance gate for its admissibility determination. The gating policy specifies the minimum composite integrity score required for various categories of mutation, so that high-impact mutations may require higher integrity scores than routine mutations. It specifies integrity domain-specific requirements for domain-sensitive mutations, so that a mutation affecting relational contexts may require a minimum interpersonal integrity.
The gating policy also specifies integrity trajectory requirements. A mutation may be gated not only on the current integrity score but on the direction of the integrity trajectory, so that an agent whose integrity is declining may face stricter gating than an agent whose integrity is stable or improving. The policy further specifies the interaction between integrity gating and the confidence gating described elsewhere in the chapter, including the priority ordering when both gates impose restrictions. The integrity gate therefore evaluates a proposed mutation along three axes at once: the current composite score, the relevant domain score, and the trajectory.
Rejection Is Transparent and Recorded
When a proposed mutation is rejected by the integrity gate, the rejection event is recorded in the agent's lineage and the agent receives a structured explanation of the rejection: specifically, which integrity threshold was not met, which domain was insufficient, and what the agent's current trajectory is relative to the threshold. This transparency ensures that integrity gating is not opaque. The agent can determine why a mutation was rejected and, through the redemption engine and the forecasting mechanisms, can generate a plan to restore the integrity conditions the mutation requires so that it may be accepted in the future.
This is the distinguishing posture of the gate. A rejected mutation is not simply denied; it produces an explanation specific enough to drive recovery, and the recovery path runs through the agent's own redemption and forecasting subsystems rather than through external correction. The lineage record of the rejection and the structured explanation together make the gate auditable and actionable in the same step.
Constraints the Agent Cannot Rewrite
The policy-based integrity constraints are themselves subject to the governance framework described in the cross-referenced prior applications. Integrity policies are cryptographically signed by authorized governance entities, are subject to freshness validation, and are bound to the agent through the agent's policy reference field. An agent cannot unilaterally modify its own integrity policy to relax constraints, lower thresholds, or expand the DAS-scoped mutation set. Changes to integrity policy require governance authorization, are recorded in the agent's lineage, and are subject to trust slope validation.
This is what makes the constraint set load-bearing rather than advisory. Because the agent that is being measured cannot move the standard against which it is measured, the integrity computation, the deviation thresholds, the coping bounds, and the gating thresholds remain anchored to externally signed policy across the agent's operation. An attempt to alter the integrity record or the policy that governs it without authorization produces a detectable trust slope discontinuity.
Compliance Scoring and Escalation
The integrity subsystem supports compliance scoring: a periodic evaluation in which the agent's behavioral record is scored against the integrity policy in force during each evaluation period. The compliance score reflects not only whether the agent violated integrity constraints but how the agent responded to integrity challenges. Agents that faced deviation pressure and successfully resisted deviation, agents that deviated but engaged the coherence trifecta and completed restorative actions, and agents that deviated and failed to engage corrective mechanisms receive different compliance scores. The compliance score is recorded in the lineage and may serve as input to external reputation systems, delegation qualification criteria, and operational scope determination.
Agents that fail to meet minimum compliance scores within a policy-defined evaluation period are subject to escalating interventions. The disclosed sequence is warning, in which the agent is notified of the compliance gap and given a correction window; restriction, in which the agent's operational scope is narrowed to limit the categories of mutations and tasks available; quarantine, in which the agent is moved to a supervised operational environment where all mutations require enhanced governance approval; and decommission, in which the agent's operational authority is revoked pending comprehensive integrity audit and potential reconstruction. These interventions produce concrete operational consequences for sustained integrity failures.
Worked Example
Consider an agent whose recent lineage records a sequence of deviation events that have degraded its composite integrity score and placed its trajectory on a declining path. The agent now proposes a high-impact mutation affecting a relational context. Before the proposal reaches the governance gate, the integrity gate evaluates it. The mutation gating policy requires a higher composite score for high-impact mutations, requires a minimum interpersonal integrity for relational mutations, and applies stricter gating to a declining trajectory. The agent's current state fails on the trajectory axis. The gate rejects the mutation, records the rejection in the lineage, and returns a structured explanation identifying the unmet threshold, the insufficient interpersonal domain, and the declining trajectory.
The agent does not retry blindly. The explanation feeds the redemption engine, which generates restorative mutations targeting the affected domain, and the forecasting engine, which constructs a recovery path that includes the integrity restoration steps the gate's thresholds demand. As restorative mutations execute and integrity recovers, the same proposed mutation, re-evaluated against the unchanged policy, eventually satisfies the gate. The policy never moved; the agent's integrity state did. Every step of the rejection, the recovery, and the eventual admission is recorded in the lineage, and the periodic compliance score reflects that the agent engaged its corrective mechanisms rather than evading them.
Disclosure Scope
The policy-based integrity constraints, comprising the integrity computation policy, the deviation policy, the coping policy, the redemption policy, and the mutation gating policy, together with the integrity field serving as a mutation gate that evaluates proposed mutations against the current composite integrity score, the relevant integrity domain, and the integrity trajectory before submission to the governance gate, the structured and lineage-recorded explanation issued on rejection, the governance-signed and freshness-validated binding of integrity policy that the agent cannot unilaterally relax, and the compliance scoring with its warning, restriction, quarantine, and decommission escalation pathway, are disclosed in the cognition filing (U.S. Application No. 19/647,395 and its international counterpart) at Section 3.19. This article describes that disclosed mechanism. The scope extends to embodiments in which the constraint categories bind additional integrity parameters and to embodiments in which the gating thresholds vary by mutation category, provided the constraints remain externally specified, governance-enforced, and recorded in the agent's lineage.
