Evidence

Evidence for mission resilience.

Current results are simulation-backed and demonstrate the intended behaviour of HOLDFAST and VERITY under controlled degraded-communications scenarios.

What the Evidence Shows

More critical traffic delivered under degradation.

Across the complete 580-run abstract-bearer dataset, HOLDFAST Core and Adapt configurations produced higher mean C2 delivery than the AODV-labelled abstract baseline proxy. VERITY adds trust-assessment evidence without changing packet delivery — by design.

Finding

Communications continuity

In controlled simulations, HOLDFAST configurations delivered more critical traffic than the modelled baseline across the complete abstract-bearer dataset.

Finding

Custody through disruption

The model exercises custody and store-forward behaviour intended to preserve critical messages across temporary loss of connectivity.

Finding

Bounded adaptation

Adaptation depends on reliable evidence and must remain bounded when network conditions change faster than confidence can accumulate.

Finding

Trust-assessment evidence

VERITY produced additional confidence, uncertainty and review evidence without claiming packet-delivery improvement.

Simulation-backed today. The next gate is the Resolvix Node Runtime and platform-adapter architecture; live RF/GNSS, hardware-in-the-loop and controlled field validation follow in later phases.

Two Simulation Workstreams

Two separate evidence families with different model boundaries.

These are preserved legacy simulation evidence from the pre-Node-Runtime architecture, retained as the platform is re-packaged around the Node Runtime and versioned adapters. Evidence is drawn from two separate simulation workstreams. Evidence Family A is an abstract-bearer simulation (580 paired runs per comparison) that models custody, continuity, uncertainty and trust-assessment proxy metrics. Evidence Family B is an ns-3 stack comparison using a custody-favourable scenario.

The two families are not combined. Family A attributes a modelled adaptation gain to HOLDFAST Adapt. Family B shows Adapt as assessment-only and behaviour-neutral, with delivery gain attributed to HOLDFAST Core.

Evidence Family A · Abstract-bearer Simulation

HOLDFAST improves C2 delivery in the abstract simulation.

HOLDFAST Core lifts mean C2 delivery from the abstract baseline through custody, priority and store-forward behaviour. In this simulation, HOLDFAST Adapt adds a modelled adaptation gain. VERITY adds trust-assessment evidence without changing delivery.

Approximate weighted mean C2 delivery — four configurations

AODV-labelled abstract baseline proxy0.613

Abstract baseline mode; no AODV protocol or network stack was executed

HOLDFAST Core0.680

Custody, priority, store-forward gain

HOLDFAST Core + Adapt0.753

Modelled adaptation gain (abstract-bearer simulation)

HOLDFAST Core + Adapt + Sentry + VERITY0.753

Same PDR. Additional trust-assessment evidence.

Bearer simulation · 580 paired runs per comparison · Topology weighting: 180 no-relay / 200 one-relay / 200 two-relay · AODV-labelled abstract baseline proxy — no AODV protocol, network stack or packet-level routing was executed in this evidence family · Source data and methodology documentation are available to qualified partners under NDA. Simulations are deterministic and reproducible from a pinned commit.

Aggregate mean C2 delivery gain

AODV-labelled proxy → HOLDFAST Core + Adapt · across all 580 runs

+13.95 pp

Key message

HOLDFAST improved C2 delivery. VERITY contributed trust-assessment evidence — operating exactly as designed, above the delivery layer.

Evidence Family B · ns-3 Stack Comparison

Core delivers the gain. Adapt is assessment-only in this comparison.

In the pinned ns-3 custody-favourable scenario, HOLDFAST Adapt operates as assessment-only and behaviour-neutral. The observed delivery difference between the ns-3 AODV baseline and HOLDFAST modes is attributed to HOLDFAST Core custody and store-forward behaviour alone.

C2 delivery ratio — custody-favourable ns-3 scenario

ns-3 AODV baseline84.7%

ns-3 AODV baseline

HOLDFAST Core90.3%

Custody and store-forward gain

HOLDFAST Core + Adapt90.3%

Adapt operating in assessment-only mode — no behaviour change

HOLDFAST Core + Adapt + Sentry + VERITY90.3%

Behaviour-neutral — no change to delivery

ns-3 simulation · Route-aware custody-favourable scenario · Seed 1 · Duration: 900s · Four independent stack-mode runs · Adapt operating in assessment-only mode — no behaviour change · Simulation evidence · RF, SDR, HIL and field validation at later phases · Single-seed run · Multi-seed aggregation planned for a later phase · Source data and methodology documentation are available to qualified partners under NDA. Simulations are deterministic and reproducible from a pinned commit.

Interpretation

What the simulation demonstrates. What later validation adds.

What this demonstrates in simulation

  • The pinned abstract simulation produced deterministic, reproducible outputs for its configured model.
  • Across the complete 580-run abstract-bearer dataset, HOLDFAST Core and Adapt configurations produced higher mean C2 delivery than the AODV-labelled abstract baseline proxy.
  • In the ns-3 comparison, HOLDFAST Core custody and store-forward behaviour accounts for the observed delivery difference; Adapt is behaviour-neutral.
  • VERITY produced deterministic trust-assessment proxy metrics and review signals without changing delivery.

What later validation establishes

  • Live RF, GNSS, SDR and waveform validation — later hardware phases.
  • Operational and field validation — the controlled field-pilot phase.
  • Representative adversary emitter and threat behaviour — live RF testing.
  • Performance under representative constrained-node hardware — later hardware phases.
  • Multi-seed ns-3 aggregation with confidence intervals — planned for a later phase.
Next Validation Gate

Next: the Node Runtime. Live RF / GNSS / HIL follows.

Current state

Simulation-backed architectural prototype.

Next gate

Phase 1 — standalone modules and a deterministic Node Runtime MVP. Adapter SDK, platform adapters, hardware-in-the-loop and a controlled field pilot follow in later phases.

Not yet claimed

Field validation, RF validation, GNSS anti-spoof validation, anti-jam validation, SDR validation, waveform validation, operational deployment or combat validation.

Claim Boundary

All findings on this page are preserved simulation evidence from two separate workstreams. They are not field, RF, GNSS, anti-jam, anti-spoof, SDR or operational validation. The next technical gate is the Node Runtime and platform-adapter architecture.