Cumulative Slope Validation Across Substrates: Multi-Node Provenance Verification

by Nick Clark | Published March 27, 2026 | PDF

Cross-substrate validation establishes the identity of an agent not by reference to a stored credential but by the coherence of its evolution observed across multiple substrates simultaneously. The agent's history is recorded as a dynamic hash chain whose links accumulate across the substrates the agent has traversed — mesh witnesses on the network fabric, biological signal substrates such as user-attested presence, and device-bound substrates such as host attestations from the physical machines that have hosted the agent. Identity is validated by reconstructing a multi-node provenance path through these substrates and verifying that the cumulative slope of the path — the rate at which the chain's hash state evolves — falls within the policy-permitted envelope for the agent's class. Windowed proofs allow recent activity to be verified inexpensively, and periodic anchors compress older history into checkpoints that remain verifiable indefinitely. The result is an identity construct in which validity is the cross-substrate coherence itself, not the persistence of any single secret.


Mechanism

The agent's identity record is a dynamic hash chain in which each link is a structured tuple containing the prior link's hash, the substrate identifier under which the new event was witnessed, the witness's attestation over the event, and a content hash of whatever activity the link records. Substrates are categorized by kind: mesh substrates are network-level witnesses such as relay nodes and gossip peers; biological substrates are signals attested by entities outside the digital fabric such as confirmed user presence at a known endpoint; device substrates are attestations produced by the physical or virtual hosts on which the agent has executed. A given event may produce multiple links in parallel — one per substrate that witnessed it — and these links are tied together in the chain by sharing a common event hash.

Validation does not consult a stored credential and does not check a signature against a long-lived public key. Instead, the validator presents a proof obligation: it asks the agent to produce a path through its hash chain spanning a specified window — typically the recent past relative to the validation request — and the agent responds with the requested links plus the supporting witness attestations. The validator reconstructs the chain over the window, recomputes the cumulative hash forward from the prior anchor through the presented links, and verifies that the reconstruction matches the chain's currently published head.

The cumulative slope of the chain over the window is then computed as the rate at which the chain advanced through hash states during the window, normalized for the substrates involved. A chain that advances rapidly through link states with broad cross-substrate coverage produces a high coherent slope; a chain that advances rapidly through links witnessed by only one substrate, or that advances in inconsistent step sizes, produces an incoherent slope. The validator compares the observed cumulative slope to the policy-permitted slope envelope for the agent's class. The envelope encodes the expected behavior: a long-running service agent should show a steady, broad-substrate slope; a transient task agent should show a brief, bounded slope; a privileged administrative agent should show a slope corroborated by biological substrate witnesses for sensitive transitions. Any agent presenting a slope outside the envelope is invalid regardless of the technical correctness of the hash chain itself.

Cross-substrate coherence is the load-bearing structural property. A compromised host device can produce links over its own device substrate, but it cannot fabricate corroborating links over the mesh substrate or the biological substrate without compromising those independent witnesses as well. An attacker who has captured one substrate's witnessing capacity will produce a chain whose slope is high in one component and absent in others — an incoherent slope that fails validation. The construct therefore derives its security from the difficulty of simultaneously compromising heterogeneous witnessing infrastructures rather than from the secrecy of a stored key.

Periodic anchors compress the chain's distant history. At configured intervals the agent produces an anchor that is a Merkle commitment over all links since the previous anchor, signed by the witness set that participated in those links. The anchor itself is published to the substrates and becomes a checkpoint: future validation requests need not replay the links that precede the most recent anchor, only the anchor's commitment and the links since the anchor. This bounds the cost of validation regardless of how long the agent has existed.

Operating Parameters

The principal operating parameters are the substrate set, the windowing function, the slope envelope, and the anchor period. The substrate set declares which witnessing infrastructures participate in identity for a given agent class; a minimum-coherence requirement specifies how many substrates must contribute links within any validation window. The windowing function specifies how the validator's request is mapped to a span of the chain — typical windows are expressed in link counts, in lineage cursor depth, or in wall-clock duration with a maximum acceptable skew. The slope envelope is a per-class specification of the permitted cumulative slope and its substrate distribution; it is itself published as a policy record in the governance substrate, so envelope updates are themselves auditable transitions.

The anchor period balances proof cost against historical replay cost. Short anchor periods produce more frequent checkpoints and bound replay cost tightly, but require more witnessing-set coordination per anchor. Long anchor periods reduce coordination overhead but extend the window of links that must be replayed if a validator's question reaches back across multiple anchors. Practical deployments use periods sized to the expected lifetime of the agent class — minutes for transient agents, hours for service agents, days for long-lived administrative identities.

Secondary parameters control the validation interaction itself. A challenge freshness parameter requires the agent to incorporate validator-supplied entropy into the most recent link, preventing replay of an older valid proof against a current question. A witness diversity parameter requires that the witnesses contributing to a window come from a configured number of independent operators, preventing a coalition of cooperating witnesses from manufacturing apparent coherence.

Alternative Embodiments

The set of substrates may be embodied with different membership and granularity. A minimal embodiment uses only mesh and device substrates and is suitable for fully digital agents; a richer embodiment adds biological substrates such as confirmed user presence, biometric attestation, or attested-physical-act witnesses. An embodiment focused on industrial deployments may add sensor-fabric substrates that attest the agent's interaction with physical processes. The structural properties — that substrates are heterogeneous, independently compromisable, and contribute to a single coherent chain — are preserved across these embodiments.

The slope computation may be embodied as a scalar magnitude, as a per-substrate vector with a coherence metric tying the components together, or as a spectral decomposition that distinguishes steady advancement from bursty advancement. The vector embodiment is most common because it enables the policy envelope to express requirements such as "at least one biological-substrate link per ten device-substrate links during privileged operation windows." The scalar embodiment is appropriate for low-stakes agent classes where coherence can be summarized in a single number.

Anchoring may be embodied as in-band publication to the substrate set, as cross-anchoring into an external public ledger, or as redundant publication to multiple independent anchor stores. The cross-anchoring embodiment provides the strongest long-term auditability because the anchor's existence and content can be verified from infrastructure outside the original substrate set, but it introduces a dependency on external availability. The redundant-store embodiment hedges against the unavailability of any single anchor publisher.

The validation interaction may be embodied as a synchronous challenge-response, as a precomputed proof bundle that travels with the agent, or as a continuously published proof stream that any subscriber can inspect. Each embodiment shifts the cost of validation between the validator, the agent, and the substrate infrastructure, but the underlying notion that validation is the verification of cross-substrate coherence is preserved.

Composition

Cross-substrate validation composes with the governance gate by supplying the agent identity input that the gate uses to look up applicable policy authority; the gate's evaluation can refuse to admit operations whose requesting agent's recent slope is outside its envelope, even if the operation itself would otherwise be admissible. It composes with the lineage substrate by writing the agent's link production as lineage entries, so that the identity chain and the operational lineage share the same audit infrastructure. It composes with slope-band indexing by exposing the agent's identity slope as one of the inputs to band assignment, so that an agent whose identity slope drifts upward without corresponding workload is detected as a structural anomaly.

It composes with cryptographic primitives by using them as link-construction tools rather than as identity-bearing artifacts. The hash function used to chain links may be any collision-resistant function; the witness signature scheme used by mesh and device witnesses may be any unforgeable scheme. Identity does not depend on the long-term secrecy of any specific key, only on the per-event correctness of the witnessing primitives, so cryptographic agility is a property of the architecture rather than a migration headache.

Prior-Art Distinction

Conventional identity systems anchor identity in the long-term possession of a secret: a private key in a key store, a password derivable to a hash, a biometric template, or a certificate chain rooted at a long-lived authority. The compromise of the secret is the compromise of the identity. Cross-substrate validation departs from this architecture by anchoring identity in the coherence of an evolving record observed across heterogeneous witnesses; there is no single secret to compromise because there is no single secret. An adversary who captures a host device acquires the ability to produce future links on that device's substrate but does not acquire the ability to retroactively produce coherent history across the mesh and biological substrates.

Hash-chain-based audit logs and append-only ledgers share some structural elements with the dynamic hash chain used here but differ in two material respects. First, conventional hash chains are typically single-substrate and single-witness; their security model assumes the writer is honest and is concerned primarily with preventing retroactive editing. Cross-substrate validation assumes the writer may be adversarial and relies on multi-substrate corroboration to detect this. Second, conventional chains do not derive identity from the chain's slope; they treat the chain as a record of identified actions taken by an externally identified principal. Here, the chain's slope and substrate distribution are the identity.

Multi-factor authentication systems combine multiple credentials at the moment of login but do not produce an evolving cross-substrate record that can be validated against a slope envelope at any later time. Cross-substrate validation differs in that the identity is a continuously evolving structure rather than a periodic re-authentication, and the validity question can be asked at any moment, against any window, by any validator possessing the policy.

Disclosure Scope

This disclosure covers the construction of agent identity as a dynamic hash chain whose links are produced across heterogeneous substrates including mesh, biological, and device witnessing infrastructures; the validation of identity by reconstruction of a cross-substrate provenance path and verification that the cumulative slope of the path falls within a policy-permitted envelope; the use of windowed proofs to bound validation cost over recent activity; the use of periodic anchors to compress historical chains into verifiable checkpoints; and the composition of cross-substrate validation with the governance gate, the lineage substrate, and slope-band indexing. Embodiments that vary the substrate set (digital-only, digital plus biological, sensor-augmented), the slope formulation (scalar, per-substrate vector, spectral), the anchoring strategy (in-band, cross-anchored, redundant), and the validation interaction (synchronous, precomputed, streamed) are within scope, provided that the structural property — identity is the cross-substrate coherence of an evolving record rather than the persistence of a stored secret — is preserved.

Nick Clark Invented by Nick Clark Founding Investors:
Anonymous, Devin Wilkie
72 28 14 36 01