# Original BMP singleton interception — 3 October 2026

This source change allows one already-admitted original BMP at convoy slot 4 to use the existing interception path after at least six delivered, reconciled HQ losses. It remains a singleton alternative to the existing UAZ pair/single behavior. Fresh complete delivered crew/ammunition status, an ordinary radio route and receipt, exact original source/record/root/crew ownership, existing shared claims, token allowance, fixed expiry and two-road-query budget remain required. It creates no replacement force, ammunition, vehicle or third simultaneous member.

A footprint measured from the exact original vehicle and bounded hierarchy is retained immutably. Conservative yaw-independent road width, segment support, terrain/water and collision-volume checks reject unknown or changed geometry. The service revalidates exact footprint ownership at admission, delivery and active use; native allocation/removal/installation boundary controls cancel the owned operation on loss. Destination clearance does not establish route navigability or physical arrival.

The archived full suite passed 305 programs with unchanged inputs. Actual-method focused programs cover threshold/radio/budget/ownership, original BMP singleton behavior, preserved UAZ pairing, geometry boundaries and callback cancellation. Baseline and mutation failures remain alongside passing logs; translated native doubles are not engine execution.

**Native compilation and physical BMP behavior remain unqualified.** `root/native-deferred.json` records why the native run was deferred and that no native check started. No compiler, fixture, navigation, interception, multiplayer or FPS success is inferred from the offline suite. The earlier depot-mines runtime handoff remains a separately sealed older snapshot and does not include this interception change.

The archive preserves exact owned proposed source/tests, available working/index baselines, patches, manifests, focused evidence, the independent HQ review, root integration and full-suite evidence. No installed third-party SDK/prefab payload is included. `artifact-manifest.json` records original paths and verified copied hashes. This helper launches no tests or native process and writes only this new evidence directory when explicitly executed after the suite.