Refusal as a First-Class Governed Observation

Mechanism

The refusal and upstream-coordination mechanism handles the case where a downstream receiving agent cannot or should not apply a proposed cascade mitigation. Rather than failing silently, the receiving agent emits the refusal as a first-class governed observation. The mechanism comprises a refusal-evaluator that determines whether a proposed mitigation is inadmissible at the receiving agent, a refusal-reason generator that produces a governance-policy-defined refusal-reason classification, and a refusal-emission interface that emits governed refusal observations to upstream coordination agents. A refusal-lineage recorder records each refusal, its reason classification, any alternative request, solicitation, escalation, and downstream consequence in the governance chain lineage field.

Upstream coordination is explicit. A receiving agent that refuses a proposed mitigation does not merely reject it; the refusal observation enables upstream agents to respond. An alternative-mitigation requester solicits alternative mitigation proposals from upstream coordinators. A corroborating-observation solicitor requests additional corroborating observations per Section 5.8 of the disclosure. An escalation interface routes refusal events to higher-authority coordinators when local alternatives are exhausted. A rejected mitigation therefore does not result in silent failure but triggers governance-chain-preserving escalation.

Because the refusal is a governed observation, it is admitted, audited, and propagated using the same governance-chain-preserving machinery as any other cascade-propagation observation. It carries its authority chain and reason classification, and it is recorded in the lineage field alongside topology references, propagation computations, directive emissions, mitigations, and halting events. 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 of Section 14.11.

Refusal-Reason Classifications

The refusal-reason generator produces governance-policy-defined refusal-reason classifications. The disclosed classifications include, without limitation: an evidential-insufficiency refusal, where the cascade-propagation observation lacks sufficient evidential weight per Chapter 4; a capability-exceedance refusal, where the proposed mitigation exceeds the agent's capability envelope per Chapter 7; a cost-threshold refusal, where the proposed mitigation exceeds governance-policy-defined cost thresholds; and a priority-conflict refusal, where the proposed mitigation conflicts with higher-priority governance commitments.

Further classifications include an authority-insufficiency refusal, where the proposing authority lacks the appropriate credential to order the mitigation; a dispositional refusal, where the dispositional field of Chapter 3 indicates inadmissibility; and a safety-boundary refusal, where the proposed mitigation violates governance-policy-defined safety boundaries. A composite refusal combines two or more of these reasons, and the classification set extends to any governance-policy-defined refusal reason.

The classifications are governance-policy-defined rather than fixed, so the set of admissible refusal reasons is established through the governance procedure for a given deployment. The refusal-reason classification travels with the refusal observation, allowing upstream coordinators to choose between soliciting an alternative mitigation, soliciting corroborating observations, or escalating, according to the reason recorded.

Upstream-Coordination Responses

A refusal observation enables several upstream responses. When an upstream coordinator receives a refusal, it may solicit alternative mitigation proposals through the alternative-mitigation requester, replacing the inadmissible mitigation with one the receiving agent can apply. Where the refusal arises from an evidential-insufficiency reason, the coordinator may instead route the refusal to the corroborating-observation solicitor, which requests additional corroborating observations per Section 5.8 before proposing a renewed mitigation.

When local alternatives are exhausted, the escalation interface routes the refusal event to higher-authority coordinators. This escalation path matters in topologies that span multiple governance authorities, where the cascade-authority resolution mechanism resolves responsibility for a given region; a refusal at a receiving agent can surface a mitigation that exceeds the proposing authority's credential and route it to an authority that holds the necessary credential.

Because refusal outcomes contribute to the topology-learning and adaptive-refinement mechanism per Section 14.11, repeated refusals of a given mitigation class at a given region inform subsequent updates to the topology graph, propagation functions, and aggregation functions. Upstream coordinators receiving refusal observations may adapt their cascade-response strategy in subsequent propagation computations, so the refusal stream feeds back into how the primitive computes and proposes future mitigations.

Composition With the Broader Architecture

The refusal and upstream-coordination mechanism sits within the cascade-propagation primitive of Chapter 14, alongside the governance-credentialed topology graph, the per-edge propagation function, the per-node aggregation function, the cascade-computation engine, the cross-domain cascade composition mechanism, the cascade-authority resolution mechanism, the preemptive-mitigation directive generator, and the cascade-halting and containment mechanism. The refusal mechanism handles the cases those directive-generating components cannot: where a downstream agent cannot or should not apply a proposed mitigation.

Because the cascade-propagation primitive composes with the broader architecture, the refusal observation reaches the same surfaces as other cascade-propagation observations. It composes with the governed mesh protocol of Chapter 2 through cascade-propagation observation emission, with the capability envelope of Chapter 7 through the capability-exceedance refusal reason, with the dispositional field of Chapter 3 through the dispositional refusal reason, and with the composite admissibility evaluator of Chapter 4 through the evidential-insufficiency refusal reason. The refusal-lineage record, recorded in the governance chain lineage field, allows an after-action reviewer to reconstruct which agents refused which mitigations, under which credentialed authority, and with what downstream consequence.

Prior-Art Distinction

The cascade-propagation primitive is structurally distinguished from prior cascade-modeling architectures, including power-grid SCADA cascade analysis, traffic simulation, epidemic modeling, supply-chain disruption modeling, and structural-failure modeling. Among the distinguishing respects, prior architectures do not provide governance-chain-preserving refusal and upstream-coordination mechanisms, whereas the present primitive produces refusals as first-class governed observations per Section 14.10. Where a prior architecture would treat a downstream node's inability to apply a mitigation as a silent failure, the present primitive emits a governed refusal observation that propagates upstream, enabling alternative-mitigation solicitation, corroborating-observation solicitation, or escalation to higher-authority coordination, with each step recorded in the governance chain lineage field.

Disclosure Scope

This article addresses subject matter disclosed in U.S. Provisional Application No. 64/049,409. The disclosure encompasses the refusal and upstream-coordination mechanism of Section 14.10, comprising the refusal-evaluator, the refusal-reason generator producing governance-policy-defined refusal-reason classifications, the refusal-emission interface, the alternative-mitigation requester, the corroborating-observation solicitor, the escalation interface, and the refusal-lineage recorder. It encompasses the refusal-reason classifications enumerated in the disclosure, including evidential-insufficiency, capability-exceedance, cost-threshold, priority-conflict, authority-insufficiency, dispositional, safety-boundary, composite, and any governance-policy-defined refusal reason.

The disclosure further encompasses the role of refusal observations within the cascade-propagation primitive of Chapter 14, including their recording in the governance chain lineage field alongside topology references, propagation computations, directive emissions, mitigations, halting events, and topology updates, and their contribution to the topology-learning and adaptive-refinement mechanism of Section 14.11. Because each refusal is a governed observation carrying its authority chain and reason classification, an after-action reviewer can reconstruct which agents refused which proposed mitigations, under which credentialed authority, and with what downstream consequence.

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. The refusal and upstream-coordination mechanism applies wherever a downstream receiving agent cannot or should not apply a proposed mitigation within those topologies, including topologies that span multiple governance authorities, where the cascade-authority resolution mechanism resolves responsibility for the affected region.