Mechanism
Trust-weighted voting is the operation by which the Adaptive Consensus Protocol (ACP) decides whether a mutation proposal carried by an agent is authorized. ACP is a memory-native mechanism that lets distributed nodes evaluate mutation proposals without relying on centralized coordination or globally synchronized state. Unlike traditional consensus systems that require fixed validator sets or persistent governance registries, ACP dynamically scopes quorum eligibility using policy references embedded within an agent's memory field. Each node independently determines its own eligibility, voting weight, and policy alignment using only the information carried by the agent.
The process begins when an agent proposes a mutation, such as adding an alias to a semantic index, encoded within its payload and described in its memory field. The memory field includes a policy reference, a lineage trace documenting the proposal's origin, and a quorum type descriptor indicating the trust-weighted voting structure required for approval. These values together define the eligibility criteria, the weighting logic, and the approval thresholds for the proposed mutation. The consensus rules travel with the proposal rather than being imposed by the network.
Eligibility and the Policy Agent
Upon receiving the agent, a node verifies the cryptographic signature generated over the agent's unique identifier, memory field, and payload using the sender's private key, and validates that signature against the sender's public key. The node then inspects the memory field to resolve the referenced policy agent. The policy agent is an agent whose purpose is to encode governance logic: it defines quorum logic including eligibility roles, voting structure, and weighting parameters, along with mutation eligibility criteria and role definitions.
If the node qualifies under the referenced policy, it participates by evaluating its trust path to the proposing agent and determining alignment with the embedded governance constraints. A node that is eligible to participate in, initiate, or validate quorum decisions under ACP is termed a consensus node. Eligibility as a consensus node is dynamic and scoped to the agent's transport header, policy references, and trust domain. It does not require persistent identity, fixed validator roles, or a global registry.
Casting and Weighting Votes
Each participating node submits its vote as a new agent containing a reference to the original mutation proposal, the node's trust score, and justification metadata. The vote is not counted as a unit. Votes are weighted according to domain scope, trust profile, and policy-defined metrics, then aggregated using the quorum logic contained within the original agent's memory field. The trust score a node carries is drawn from its trust graph, the evolving, memory-informed model that maps prior interaction outcomes to trust scores used in routing and quorum weighting.
Votes may be accumulated locally or forwarded via the dynamic routing protocol to additional quorum participants. Because the vote, the trust score, the justification, and the quorum logic are all carried by agents and cryptographically committed, evaluation does not depend on a central tabulator.
Quorum Evaluation and Outcome
Votes are aggregated against the quorum logic defined in the proposing agent's memory field. As an illustrative example, a mutation may require a minimum of three votes out of five, with a cumulative trust weight exceeding a defined threshold, for approval to occur. The specific eligibility, weighting, and threshold values are supplied by the referenced policy rather than fixed by the protocol.
If quorum is reached, the ACP module appends an approval entry to the originating agent's memory trace, documenting the voting outcomes and embedding quorum context for downstream audit and validation. If quorum fails or a proposal is rejected, a rejection or quarantine flag is appended instead. In each case, the agent's memory field becomes a complete, cryptographically verifiable execution trace of the consensus process, allowing subsequent nodes to confirm compliance with the scoped policy constraints and trust rules.
Stateless and Memory-Aware Modes
ACP supports both stateless and memory-aware modes of operation. In stateless mode, quorum logic is determined exclusively by the agent's memory field and the active policy at runtime, so a node without persistent memory can still participate using only the data embedded in the received agent. In memory-aware deployments, nodes may additionally reference prior mutation outcomes, trust scores, or policy participation history to inform quorum formation or trust weighting. This optional historical context informs quorum formation, weighting decisions, or eligibility forecasting while preserving fully localized decision-making.
Because consensus may be scoped entirely to the identity, memory context, and mutation parameters of a single agent, ACP does not require persistent governance hierarchies, external registrars, or global alias systems. Trust-weighted vote propagation, memory-based quorum formation, and policy-governed mutation validation occur without centralized coordination.
Health-Driven Adjustment of Quorum Parameters
Quorum behavior is not static across the life of a deployment. The network health monitoring system emits health agents carrying operational signals such as congestion, trust volatility, propagation entropy, and cache pressure. When a node receives a health agent, it may execute one or more adjustments to the parameters of ACP for one or more semantic classes. The disclosed adjustments include raising or lowering quorum thresholds, excusing or reinstating specific participants from quorum eligibility, and re-weighting participant votes.
Through this feedback path, trust volatility indicated by health-state reports can modify quorum eligibility, weight assignments, or required thresholds, which prevents unstable nodes from disproportionately affecting mutation events. The adjustment is local and policy-bound rather than centrally orchestrated.
Distinction From Conventional Consensus
Conventional consensus systems require fixed validator sets or persistent governance registries and treat agreement as a problem solved over a known roster. ACP differs in that it forms ad hoc voting quorums based on trust graphs and policy references embedded in the agent memory. Eligibility, weighting, and thresholds are carried by the proposal itself and are scoped to a trust domain rather than applied globally, and the outcome is recorded as a verifiable trace in the agent's own memory field. By embedding consensus logic in the agent, ACP enables fine-grained, verifiable mutation control across dynamic and trust-scoped environments without requiring global consensus layers or fixed validator infrastructure.
Disclosure Scope
The trust-weighted voting mechanism described here, comprising the Adaptive Consensus Protocol's resolution of a referenced policy agent, the dynamic scoping of quorum eligibility from policy references in an agent's memory field, the casting of votes as new agents carrying a trust score and justification metadata, the weighting of votes by domain scope, trust profile, and policy-defined metrics, the aggregation of those votes against the quorum logic's threshold, the appending of approval, rejection, or quarantine outcomes to the agent's memory trace, the stateless and memory-aware modes of operation, and the health-agent-driven adjustment of quorum thresholds, eligibility, and vote weights, is disclosed in U.S. Application No. 19/366,760. This article describes that disclosed mechanism. The scope extends to embodiments implemented in hardware, in software, or in a combination, and to deployments across stateless, memory-aware, edge, and federated configurations, provided that eligibility, weighting, and thresholds remain governed by policy references carried in agent memory and that the consensus outcome is recorded as a verifiable trace.
