Back to matrix

F10-LT: Yes

Rationale

Pinned ION BPv7 maps the client critical option to BP_MINIMUM_LATENCY and stores it in the originating bundle. CGR selects a best eligible route per proximate node; sendCriticalBundle clones and enqueues copies for distinct route-entry neighbors before any loss. This is an origin-side proactive-replication witness with two provisioned distinct routes, not a claim that critical metadata survives every subsequent hop or that neighbors imply physically disjoint paths. The same source explicitly bypasses ordinary reforwarding for critical bundles, because they were already queued on eligible routes. Proactive duplication is therefore not an unconditional delivery guarantee.

Assessment method

Source audit of an explicit BP-layer witness; no execution

Source context

Pinned ION BPv7 client, CGR selector and IPN forwarder

Outstanding qualification

Integrate the selected convergence layers; send one marked bundle over two independent routes and capture both copies before any loss. Check next-neighbor suppression, forwarding duplicate guard, final delivery duplication, resource cost and metadata at subsequent hops. No physical diversity, performance or end-to-end deduplication result is claimed.

Public sources

Editorial evidence references

The following identifiers refer to research records not included in this public package; they are not public links.