Mechanism
Upstream coordination is the refusal-handling mechanism of the cascade-propagation primitive. When the cascade-computation engine produces a preemptive-mitigation directive routed to a downstream receiving agent, that agent may not be able to apply the proposed mitigation. A refusal-evaluator determines whether the proposed mitigation is inadmissible at the receiving agent. Rather than failing silently, the agent emits the refusal as a first-class governed observation. A refusal-reason generator produces a governance-policy-defined refusal-reason classification, and a refusal-emission interface emits the governed refusal observation to upstream coordination agents.
The refusal is not merely a rejection. It enables upstream agents to seek alternative mitigations, solicit additional corroborating observations, or escalate to higher-authority coordination. An alternative-mitigation requester solicits alternative mitigation proposals from upstream coordinators. A corroborating-observation solicitor requests additional corroborating observations. An escalation interface routes refusal events to higher-authority coordinators when local alternatives are exhausted.
Every step is recorded. A refusal-lineage recorder records each refusal, reason classification, alternative-request, solicitation, escalation, and downstream consequence in the governance-chain lineage field. Because the refusal observation is governance-chain-preserving and admissible through the composite admissibility evaluator, downstream audit can reconstruct which upstream coordinators were engaged, what was refused and why, and what alternatives or escalations followed.
Upstream coordination reuses the same credential and lineage surfaces the mesh maintains for its other governed observations. The refusal observation is emitted through the governed mesh protocol and routable through the observation routing primitive under authority-filtered propagation, so it is auditable on the same terms as any other admissible observation.
Refusal outcomes feed back into propagation. Upstream coordinators receiving refusal observations may adapt their cascade-response strategy in subsequent propagation computations, and the refusal outcomes contribute to the topology-learning and adaptive-refinement mechanism that updates the topology graph, propagation functions, and aggregation functions from observed propagation outcomes.
Operating Parameters
Refusal-reason classifications are governance-policy-defined. The disclosure recites them without limitation: evidential-insufficiency refusal, where the cascade-propagation observation lacks sufficient evidential weight; capability-exceedance refusal, where the proposed mitigation exceeds the agent's capability envelope; cost-threshold refusal, where the proposed mitigation exceeds governance-policy-defined cost thresholds; priority-conflict refusal, where the proposed mitigation conflicts with higher-priority governance commitments; authority-insufficiency refusal, where the proposing authority lacks appropriate credential to order the mitigation; dispositional refusal, where the dispositional field indicates inadmissibility; safety-boundary refusal, where the proposed mitigation violates governance-policy-defined safety boundaries; composite refusal combining two or more; and any governance-policy-defined refusal reason.
Each classification is generated by the refusal-reason generator and carried in the governed refusal observation, so an upstream coordinator can distinguish a refusal grounded in insufficient evidence from one grounded in a capability limit, an authority limit, or a safety boundary, and can respond accordingly. A refusal grounded in evidential insufficiency invites the corroborating-observation solicitor; a refusal grounded in capability exceedance invites the alternative-mitigation requester; a refusal that local coordinators cannot resolve invites the escalation interface.
The escalation interface routes refusal events to higher-authority coordinators when local alternatives are exhausted. The disclosure does not recite numeric response windows, severity tiers, or fixed escalation deadlines for upstream coordination; escalation is conditioned on the exhaustion of local alternatives rather than on a declared timer.
Alternative Embodiments
Refusal-reason classifications vary by embodiment, and the disclosure recites the classification set as non-limiting: any governance-policy-defined refusal reason may be added. A composite refusal combines two or more reasons, so a single refusal observation can record, for example, that a proposed mitigation both exceeds the receiving agent's capability envelope and conflicts with a higher-priority governance commitment.
Refusal observations enable multi-agent cascade coordination in which a rejected mitigation does not result in silent failure but triggers governance-chain-preserving escalation. Because the refusal is a first-class governed observation rather than an out-of-band message, the same lineage structure applies whether the refusal is resolved by an alternative mitigation, by additional corroborating observations, or by escalation to a higher-authority coordinator.
Upstream coordinators receiving refusal observations may adapt their cascade-response strategy in subsequent propagation computations. The refusal outcomes contribute to the topology-learning and adaptive-refinement mechanism, which updates the topology graph, the per-edge propagation functions, and the per-node aggregation functions from observed propagation outcomes through the training governance primitive. A persistent pattern of capability-exceedance refusals along a given edge, for instance, can inform how subsequent cascades are projected across that edge.
Composition
Upstream coordination composes with the other primitives of the mesh. The cascade-propagation primitive itself composes with the governed mesh protocol through cascade-propagation observation emission, and refusal observations travel those same surfaces. With the multi-authority coordination primitive, an escalation to a higher-authority coordinator can be resolved through role-differentiated attestation and a governance-policy-defined quorum, so that no single compromised signer determines the coordinated outcome. Cross-domain cascade composition combines cascade propagation across two or more topology domains, producing composite, cascade-of-cascade determinations, so a refusal in one domain can be evaluated in light of cascades projected from another.
Composition with the cross-mesh reconciliation mechanism enables coordination across mesh boundaries: a lineage-preserving import mechanism preserves original mesh identity in imported observations, and a partitioned-operation interface supports intentionally-disconnected meshes with selective inter-mesh observation admission through authorized gateway channels. A refusal observation produced while a mesh was disconnected is reconciled by the temporal reconciliation engine on interconnection rather than lost.
Composition with the matched-pair settlement primitive and its conditional-settlement mechanism allows a bilateral commitment to be made conditional, and composition with the cascade-authority resolution mechanism resolves responsibility when a topology spans multiple governance authorities. In each case the cascade-lineage recorder retains the topology reference, the directive emission, the refusal, and any resulting escalation in the governance-chain lineage field.
Prior-Art Distinction
The disclosure distinguishes the cascade-propagation primitive from prior cascade-modeling architectures: power-grid SCADA cascade-analysis, traffic simulation, epidemic modeling, supply-chain disruption modeling, and structural-failure modeling. Prior architectures operate on centrally-maintained models with ad hoc trust assumptions, whereas the present primitive operates on governance-credentialed topologies with authority-chained custody. Prior architectures produce unstructured alerts or central dashboards, whereas the present primitive produces governance-chain-preserving cascade-propagation observations admissible through the composite admissibility evaluator and routable through the observation routing primitive.
As to upstream coordination in particular, prior architectures do not provide governance-chain-preserving refusal and upstream-coordination mechanisms, whereas the present primitive produces refusals as first-class governed observations. In prior systems a rejected mitigation results in silent failure; here it triggers governance-chain-preserving escalation, with the refusal, its reason classification, any alternative-mitigation request, any corroborating-observation solicitation, and any escalation recorded in lineage. Prior architectures also do not support authority-resolution across multi-authority topologies, do not support cross-domain cascade composition producing cascade-of-cascade determinations, and do not support governance-chain-preserving topology learning, each of which the present primitive provides.
Disclosure Scope
U.S. Provisional Application No. 64/049,409 discloses upstream coordination as the refusal-handling mechanism of the cascade-propagation primitive, a first-class architectural primitive of the governed spatial mesh. The cascade-propagation primitive operates across power, transportation, fluid, thermal, structural, biological, communication, logistics, economic, and cyber-physical topologies, and admits extension to any future topology class through governance-policy-defined topology registration without architectural modification. Wherever a downstream receiving agent cannot or should not apply a proposed mitigation, the refusal and upstream-coordination mechanism applies. As propagation outcomes are observed, the topology graph, propagation functions, and aggregation functions update through the topology-learning and adaptive-refinement mechanism under the training governance primitive.
The disclosure recites the upstream-coordination mechanism as comprising a refusal-evaluator, a refusal-reason generator producing governance-policy-defined refusal-reason classifications, a refusal-emission interface, an alternative-mitigation requester, a corroborating-observation solicitor, an escalation interface routing refusal events to higher-authority coordinators when local alternatives are exhausted, and a refusal-lineage recorder. This article reflects U.S. Provisional Application No. 64/049,409 and states no figure, threshold, or numeric parameter beyond those disclosed there.
