Mechanism

Pseudonymous propagation is the platform's means of letting a semantic agent be recognized as it moves across substrates without disclosing a persistent, globally registered identifier. The disclosure describes this as pseudonymous operation through identity continuity rather than persistent static keys. The agent is not addressed by a fixed key bound to a single principal. Instead it is recognized by its Dynamic Agent Hash (DAH), an entropy-resolved identity value derived from the agent's internal memory field, semantic context, mutation history, and policy references. Because the DAH is recomputed as the agent's state evolves, the agent presents an identity that changes deterministically across execution cycles, and an agent may propagate or mutate across substrates without disclosing an explicit global identifier.

The DAH is not a static key but evolves as the agent mutates. What permits recognition despite this evolution is trust slope continuity: the agent is recognized across substrates by its DAH slope, the directional trajectory of its successive hash states. A receiving substrate does not ask whether an incoming agent carries the same fixed credential it saw before; it asks whether the agent's observed slope follows an acceptable trajectory consistent with its prior state. This is what allows pseudonymity and recognition to coexist. The agent reveals a moving identity, and the substrate validates the movement.

DAH Derivation and Slope

A semantic agent instantiates identity through a Dynamic Agent Hash derived from the agent's internal memory field, semantic context, mutation history, and policy references. The DAH is described in the disclosure as a deterministic identity fingerprint generated from a semantic agent's internal memory, mutation state, and host entropy. It is not isolated from the device on which it executes. Each DAH derivation includes entropy inputs linked to the host Dynamic Device Hash (DDH) at the time of execution, forming a binding between the agent's evolution and its hardware environment.

A trust slope is defined in the disclosure as the ordered sequence of hash states over time, together with the directional deltas between them. For a semantic agent, the slope captures memory changes, semantic lineage, and context transitions. The system does not assume identity remains static; it evaluates whether the observed slope follows an acceptable trajectory defined by policy, zone, or prior state references. Because the DAH evolves as a function of the agent's own memory and mutation history, the agent's pseudonymous identity is bound to its actual behavior rather than to an externally assigned label.

Slope Entanglement With the Host Substrate

Recognition across substrates is reinforced by slope entanglement, the enforced binding between an agent's DAH and its host substrate's DDH. Each time a semantic agent mutates, the resulting DAH depends not only on the agent's internal state but also includes a reference to the host device's DDH at the time of mutation. This coupling is recorded in the agent's memory trace. During validation, the recipient substrate retrieves prior DAH and DDH pairs and confirms that each step in the agent's evolution occurred on a device with a verifiable trust slope.

Deviations in either the DAH or the DDH trajectory, or missing entanglement references, result in quarantine, rollback, or rejection under zone policy. The disclosure illustrates this across three trust zones: an agent validated in a first zone migrates and mutates in a second zone, producing a new DAH entangled with the second device's DDH, and the validation module evaluates whether the slope between the two DAH states is continuous and entangled with the respective device hashes. In a third zone a failure case is shown, in which the validator identifies a discontinuity, either an unauthorized mutation of the DAH trajectory or a DDH that no longer reflects a legitimate evolution, and execution is blocked.

Propagation Constraints in the Policy Reference Field

Pseudonymity does not remove governance. Policy references embedded in the agent object may declare propagation constraints, such as limiting execution to a particular zone, disallowing delegation, or requiring trust slope entanglement for mutation validity. These constraints are enforced by substrate-local validators using the DAH's lineage, entropic signature, and historical slope checkpoints. Propagation eligibility is therefore decided from the agent's own fields, not from an external session record or a centrally held identity table.

The disclosure ties this enforcement to the semantic router and propagation interface of the runtime middleware. When an agent reaches the propagation interface, it is evaluated for eligibility to exit the local substrate based on updated semantic context, zone alignment, and trust slope continuity, the entropy-derived alignment between the agent's DAH and the substrate's DDH. An agent may only be propagated into a new nest or across a zone boundary if its semantic state and memory lineage satisfy the requirements of the receiving environment. If validation fails, propagation is denied and the agent is retained in the current nest for rehydration or policy reconciliation.

Lineage, Memory Trace, and Auditability

Although the agent propagates pseudonymously, its trajectory remains auditable. Each step of the agent's evolution is recorded in the memory field, which operates as a tamper-evident, cryptographically linked record of the agent's evolution. Mutation events are appended to the memory trace, each referencing a prior semantic state, the mutation descriptor invoked, and the policy reference governing the transition. The entangled DAH and DDH checkpoints are stored in the agent's lineage, so that a verifier can examine the agent's historical entanglement with trusted DDH checkpoints without being given a persistent global identifier.

This separates recognition from disclosure. Privacy is preserved through pseudonymous operation and trust-local validation, while attribution remains enforceable through entropy-resolved slope lineage. A downstream node, governance entity, or third-party auditor can reconstruct the conditions under which any given mutation occurred from the memory-resident trace, because each mutation is recorded with sufficient metadata to validate the legitimacy of the transformation under the governing policy reference. The agent carries the record of how it traveled within itself.

Propagation Under Degraded Conditions

The mechanism remains intact for agents that propagate into constrained or stateless environments. A partial agent, one missing one or more required fields, is routed to fallback resolution in a memory-native nest, where missing fields are reconstructed from environmental scaffolds, lineage inference, or policy templates. After rehydration, the resulting agent is evaluated for trust slope coherence: its regenerated memory field is used to recompute its DAH, which is then validated against the local DDH of the nest. If the directional slope between the prior state and the rehydrated agent falls within accepted bounds, the agent is authorized for execution.

Agents operating in partial form may temporarily store mutation intents or policy decisions without immediate memory field updates, and upon rehydration in a memory-native substrate those deferred actions are reconciled and appended to the memory field, restoring full traceability. The slope continuity of the DAH is verified against prior known states before mutation is finalized, so that an agent that has traveled through a degraded substrate still re-enters governed execution under verified pseudonymous identity rather than under a relaxed one.

Application: Accountable Pseudonymity

The disclosure applies pseudonymous propagation where an agent must be recognized and held accountable without being persistently named. In decentralized finance deployments, memory-resident agents carry transactions and governance proposals, and identity is resolved using slope-validated DAH structures, enabling agents to maintain pseudonymity while remaining cryptographically accountable across distributed financial environments. In privacy-focused identity systems, the platform supports agents that model users, devices, or contextual identities without revealing persistent identifiers, with authentication performed through dynamic DAH and DDH slope evaluation rather than keypair validation.

In each case the same property is being used: identity that is continuous enough to recognize and audit, but not fixed enough to correlate into a persistent global identifier. The disclosure frames this as enabling trust-based interaction without centralized identity providers or persistent correlation risk, and as supporting scalable, pseudonymous, and behaviorally auditable propagation across trust zones with differing enforcement scopes.

Disclosure Scope

Pseudonymous propagation, comprising recognition of a semantic agent by its Dynamic Agent Hash and trust slope continuity rather than by persistent static keys, the entropy-resolved derivation of the DAH from the agent's memory, mutation history, and policy references, slope entanglement between the agent's DAH and the host substrate's DDH, the enforcement of propagation constraints declared in the policy reference field by substrate-local validators, and the recording of entangled identity checkpoints in the memory and lineage fields for auditable attribution, is disclosed in U.S. Application No. 19/230,933, principally at the stateless identity and trust slope sections and the policy enforcement via identity discussion. This article describes that disclosed mechanism. The scope extends to deployments in which pseudonymous, slope-validated agents propagate across centralized, federated, decentralized mesh, and edge substrates, and to partial-agent fallback rehydration in which DAH slope coherence is re-established before governed execution resumes, provided that recognition continues to rest on entropy-resolved identity continuity rather than on persistent credentials.