Dynamic Membership for Multi-Party Coordination

Mechanism

The N-party coordination settlement primitive extends bilateral matched-pair settlement to a coordination ceremony among N authority-credentialed parties, where N is three or more. Among its mechanisms is a dynamic-membership mechanism supporting member replacement during a ceremony. Membership is not fixed at instantiation: a participant can be replaced while the ceremony is in progress, and the coordination continues around the resulting set of participants without requiring a fresh ceremony for the change.

Each membership change is recorded in the governance-chain lineage. The coordination-lineage recorder records each participant admission, attestation, outcome determination, round transition, Byzantine event, abandonment, membership change, composition, and cross-domain handoff in the governance-chain lineage field. A membership change is therefore a first-class lineage entry rather than an implicit state shift, so the participant roster in effect when any coordination step committed is recoverable from the record.

Participants are admitted through the participant-admission interface, which ingests governance-credentialed observations from the authority-credentialed parties. Admission and the contributed observations are evaluated under the governed mesh's existing admissibility machinery, including the per-participant admissibility evaluator applied to each contributed observation. Whether and on what terms a member may be replaced is set by the governance policy that defines the coordination pattern, not by a fixed rule built into the primitive.

Operating Parameters

The behavior of dynamic membership is set by the governance policy that defines the coordination pattern. That policy specifies the roles of each party and the rules for producing the coordinated outcome, and a role-differentiated attestation schema specifies the per-role observation content each participating party contributes. When a member is replaced, the replacement party admits under the same pattern definition, so the role and its attestation requirements persist across the change.

The spec does not fix numeric thresholds, latency bounds, or replacement-rate limits for the mechanism. The terms on which a member may be replaced, and the attestations a replacement must present, are governance-policy-defined rather than parameters built into the primitive. This article therefore states no specific timing values, cardinality limits, or churn rates for dynamic membership, because the filed disclosure recites none.

Alternative Embodiments

Because the terms of member replacement are governance-policy-defined, different deployments can govern membership differently without architectural modification. One governance policy may permit member replacement freely during the ceremony, while another may constrain it to designated points or designated roles. The mechanism is the same in each case: the change is admitted under the pattern's governance policy and recorded as a membership-change entry in the governance-chain lineage.

Dynamic membership is one of several mechanisms the N-party coordination primitive integrates alongside multi-round coordination, Byzantine-robust coordination, and partial-quorum and abandonment handling. A deployment can combine these as its governance policy requires, so member replacement can occur within a multi-round ceremony, under Byzantine-robust evaluation, or while partial-quorum handling manages an incomplete ceremony.

Composition

Dynamic membership composes with the primitive's other mechanisms. The partial-quorum and abandonment handler manages incomplete coordination ceremonies, so a membership change that affects whether a quorum is present is handled under that mechanism rather than left implicit. The cross-pattern composition mechanism combines multiple coordination patterns within a single ceremony, and because the terms of member replacement are governance-policy-defined per pattern, one composed pattern may permit replacement while another constrains it. Byzantine-robust coordination tolerates a governance-policy-defined fraction of adversarial or failed participants, so a coordinated outcome can be reached around a member that is replaced or that fails, within that policy-defined fraction.

Composition with the lineage record is direct. Because each membership change is recorded by the coordination-lineage recorder in the governance-chain lineage field, a downstream reviewer can determine which parties were participants when any cited coordination step committed by reading the recorded lineage, without reconstructing membership from out-of-band state.

Prior Art

The specification distinguishes the N-party coordination settlement primitive from prior multi-party architectures in several respects. Prior blockchain consensus protocols, including proof-of-work, proof-of-stake, and Byzantine-fault-tolerance variants, require global agreement about shared state across all network participants, whereas the present primitive requires coordination among specific named parties only. Prior multi-signature cryptographic schemes, including m-of-n and threshold signatures, cryptographically aggregate signatures without attaching authority-chain semantics, whereas the present primitive produces governance-credentialed settlements with per-participant authority attribution. Prior auction, voting, and multi-party computation protocols handle their respective tasks without governance-chain integration, multi-pattern composition, or coordination semantics.

Against this background, the specification states that prior architectures do not integrate multi-round coordination, Byzantine robustness, partial-quorum handling, and dynamic membership through a unified mechanism, whereas the present primitive integrates these. Dynamic membership, the support for member replacement during a ceremony with the change recorded in the governance-chain lineage, is one element of that integrated, governance-credentialed mechanism.

Operational Scenarios

Member replacement during a ceremony arises naturally where the operational roster changes while coordination is in progress. In a clinical coordination ceremony, a participant holding a role such as lead surgeon may be replaced mid-procedure by a colleague; the membership change is recorded in the governance-chain lineage, so a coordination step that requires a participant in that role traces to the party who held the role when the step committed. The specification separately recites a medical patient-transfer handoff in which clinical lineage transfers across emergency-medical-services, hospital, surgical, post-operative-care, and post-discharge-primary-care authorities, which is the cross-domain coordination handoff mechanism rather than the dynamic-membership mechanism.

This distinction matters: transferring an operation across an authority-domain boundary is cross-domain coordination handoff, recorded as a matched-pair handoff settlement, whereas replacing a participant within a single ongoing ceremony is dynamic membership. Both record their event in the governance-chain lineage. The common property is that the change is a governance-credentialed lineage entry rather than an implicit shift, so the participant roster in effect at any cited step is recoverable from the record.

Implementation Notes

The specification leaves the specific realization of the mechanism to governance policy and deployment parameterization rather than fixing it. The terms of member replacement, the attestations a replacement participant must present, and the roles to which replacement applies are governance-policy-defined, expressed through the same coordination-pattern definition that specifies the roles and outcome rules for the ceremony.

A replacement participant admits through the participant-admission interface and contributes governance-credentialed observations under the role-differentiated attestation schema, the same path by which any party participates. The per-participant admissibility evaluator applies to the replacement's contributed observations as it does to every participant, so a member replacement does not bypass the governed mesh's admissibility machinery.

Because dynamic membership is integrated with multi-round coordination, Byzantine-robust coordination, and partial-quorum handling rather than realized as a standalone module, a deployment tunes member-replacement behavior by tuning the governance policy that drives all of these mechanisms together. This article states no specific signature scheme, aggregation method, or storage cadence for the mechanism, because the filed disclosure recites none for dynamic membership.

Adversarial Considerations

Recording membership change as a governance-credentialed lineage entry, and admitting participants only through the governance-credentialed participant-admission interface, bears on adversarial scenarios. Because a coordinated outcome is reached under a Byzantine-robust coordination mechanism that tolerates a governance-policy-defined fraction of adversarial or failed participants, an attempt to influence the outcome by replacing or seating a colluding participant is constrained by that policy-defined fraction and by the per-participant admissibility evaluation each contributed observation must pass. The specification does not recite specific named attack classes for the dynamic-membership mechanism, so this article states none; it relies on the disclosed Byzantine-robustness and admissibility machinery rather than on invented thresholds or detection rules.

Disclosure Scope

This article describes the dynamic-membership mechanism of the N-party coordination settlement primitive disclosed in U.S. Provisional Application No. 64/049,409: support for member replacement during a coordination ceremony, with each membership change recorded by the coordination-lineage recorder in the governance-chain lineage field, governed by the coordination pattern's governance policy and the governed mesh's admissibility machinery. It describes the integration of dynamic membership with multi-round coordination, Byzantine-robust coordination, partial-quorum handling, and cross-pattern composition, and distinguishes it from the cross-domain coordination handoff mechanism. Specific thresholds, timing values, replacement rates, signature schemes, and storage cadences are governance-policy-defined or are not recited for this mechanism, and no such value is asserted here.