Tactical Mission Network, PACE & DDIL Resilience

Individual links can stay up while the mission service they carry fails

A DDIL network can preserve every individual link while the mission service running over it still fails, because path diversity, store-and-forward state and reconnect reconciliation weren't consistent across the links that stayed up.

Primary and Alternate can look like two paths and fail as one

A PACE plan can list Primary and Alternate paths using entirely different satellite constellations, different frequencies, different hardware — and still both route through the same local ground gateway. If that shared gateway fails, both "independent" paths fail together, and nobody finds out until the outage that was supposed to be covered by redundancy.

This works from path and reconciliation telemetry, not network control access

Never requested, and structurally rejected if submitted: live network control access, classified PACE-plan details, or raw traffic content.

Scenario: A PACE plan lists SATCOM Primary and SATCOM Alternate as independent paths.

Different satellite constellations, different frequencies — on paper, genuinely separate options.

WITHOUT this check: Both paths show as up, so the PACE plan is treated as fully redundant — if Primary fails, Alternate is assumed to pick up seamlessly since it's a "different" path.

WITH this check: The false-redundancy detector finds that despite using different constellations, both paths route through the same local ground gateway and backhaul connection. The certificate reports this shared dependency explicitly, so the PACE plan's actual redundancy is visible before it's tested by an outage, not after.