Institutional Reception of a Disinterested Signal

Question. When the bridge routes a documented friction pattern to the authority that holds the lever, does the institution act on it, a rule changes and the loop closes, or does it absorb the signal into activity that looks like a response while nothing closes, and do the bridge's design levers move reception from the second outcome to the first?

Analogy. It works like an organ transplant: a graft can be perfectly healthy and still be rejected as foreign, and what decides whether it takes is not the quality of the organ but the tissue-matching and the immune protocol around it. Worse, rejection is rarely a clean refusal; the graft can sit in place while function never takes, which looks for a long time like success. The study asks whether an institution receives a correct, disinterested signal the way a body receives a graft, rejecting it for being foreign no matter how sound it is, and whether the bridge's design levers are the matching-and-immunosuppression protocol that decides whether the signal takes or is quietly rejected as motion that never closes.

What's at stake. The deni-bridge is the far-side half of the proposal's self-improving engine: the route that carries a rule-level problem no field actor can fix to the authority that can. The proposal already concedes, from the public-administration record, that the naive version of this route fails, one complaint to the nearest official dissolves into committee activity, and builds the bridge on seven design moves meant to avoid that. But the proposal asserts the engineered route works and never tests it. The load-bearing claim is that a disinterested, aggregated, well-routed signal produces cumulative change rather than the endless motion that characterises a stalled reform. If that holds, the bridge is a genuine government-learning channel and the Northern build-out and self-funding cases rest on real ground. If it fails even with the levers, the policy-channel half of the dual-use case is rhetorical, and DRDC should fund field capability and treat rule-stuck friction as a surfaced governance signal, not a route that moves government.

The two answers it decides between. Either institutional reception is gated by incentive and trust in a way the levers can engineer, so a pattern carried with the full bridge, routed to the lever-holder, framed as the receiver's benefit, backed by an internal sponsor, and forced to a dated, on-the-record disposition, closes loops that the same pattern sent the naive way does not; or reception is dominated by the existing political order regardless of how the signal is built, so the engineered and stripped-down routes both dissolve into activity and no design moves the equilibrium. A comparison of levered against stripped routing, scored on closure rather than activity, tells them apart.

What a null result would mean. If the levered signal closes no more loops than the naive one, the engineered-channel premise the bridge rests on needs revision: the channel is articulate complaint with good process, not a government-learning instrument, and the dual-use case should drop the claim that the bridge gets government to act, keeping only the weaker boundary result that it can surface a governance signal. That is a finding about whether institutional reception is designable at all, not a sign the platform was built wrong.

Why this matters to defence. A department that runs on internal review and faces the NORAD-era multi-department coordination the Auditor General flagged needs to know whether a bottom-up signal can move a rule, not merely name one (DRDC Objective 4, the affordability and sustainability of DND and the institution; DRDC Objective 5, Defend North America). It changes a concrete decision: whether to build and resource the bridge as a government-learning channel, or to stop at field capability and accept that rule-stuck friction is surfaced but not acted on. Two risks ride alongside and are part of what the study measures: that the closure-forcing lever manufactures the appearance of a decision without its substance, the automated form of the indecision the literature documents; and that the channel cannot run at all without a partner government willing to receive the signal, which bounds when this study can be done.

How we would run it. This is the reception end, so it needs the policy-signal channel live, the signal-quality and boundary priors in hand, and a partner government willing to receive routed patterns; it runs as a Component 2 arm after its siblings, not inside the pilot. Take the documented friction patterns the network surfaces in one live domain where the authority structure is mapped, Northern procurement being the natural case, and route matched patterns two ways: the full bridge against a stripped control that forwards a single account to the nearest official with no sponsor and no deadline, the design the literature predicts fails. The primary outcome is cumulative closure, committed to in advance: did a rule, process, or coordination structure actually change, escalate with a named owner, or get declined with a stated reason. Activity counts, the committees convened and revisions drafted, are recorded as the thing to discriminate against, because the failure mode is precisely that motion masquerades as change. Because reception is slow and the number of patterns is small, the design follows a modest set of matched pattern-pairs longitudinally with process tracing, and the seven levers are peeled off one at a time across pairs to see which carry the effect, with the six documented failure modes as the named ways a pair dies. The only-us condition is a real, disinterested, aggregated signal from a naturalistic operator network routed to a real authority: an institution's response to a signal it knows is consequential is the whole phenomenon, and a managed cohort or a vignette study cannot reproduce it.

Earliest start. Stage 15: needs the policy-signal channel live, the boundary and signal-quality priors, and a partner government willing to receive routed patterns, so it runs as a Component 2 arm after its siblings. Post-funded.