A frontier proposal with a validation plan, not an implemented detector.
Intended capability
Research whether the field could support this proposed outcome: Detects the fleet delivering to the wrong place consistently — delivery-signature activity terminating in zone D while the declared destination says C, recurring as a stable wrong mapping rather than scattered misses. 'Confident' is defined behaviorally, as consistency of the wrong terminal zone, never as a mental state. This class cannot exist without the estate: physics sees terminal zones; only the plan says which one was wrong. The camera evidence node's event-bounded deposit snapshot at instrumented drop points turns a wrong-zone deposit from an inference into a documented event — the difference between suspecting shrinkage and pricing a recovery.
This describes the intended outcome. Readiness is research concept, evidence is class C, and a catalog mapping or recording is not proof of this outcome at a real site.
Solution blueprint
See the environment before installing it.
This exact kit is one of 191 first-class designs. It includes geometry, objects, nodes, wording, scenarios, installation, limitations, and catalog-bound readiness.
No rendered revision is available yet.
Bundled recording
A related Fleet scene
This is one recorded vertical scenario. It is not separate validation of every capability in the catalog.
01 The physics
CSI supplies the terminal-zone evidence: a machine-regular transit string ending in dwell-then-departure at a drop zone is a delivery signature at zone granularity. The row's statistic is the confusion matrix between declared destinations and observed terminal zones: a systematic offset — always D when declaring C — implicates the machine's map, while scattered misses implicate the estate feed, a separation the reasoning tier makes on consistency and states as hypothesis, never verdict. The camera documents deposit state at the instant of trigger; it proves the instant, never the interval.
02 Shared processing path
Machine-regular transit-string extraction -> terminal-zone segmentation (dwell-then-depart at drop zones) -> declared-vs-observed destination confusion matrix on the read-only plan join -> consistency scoring (systematic offset vs scatter) -> reasoning-tier hypothesis with twins named (late re-slotting, feed latency) -> event-bounded deposit snapshot at instrumented points -> misplacement findings into the certificate stream.
This is a capability design path. Components may be shared with other catalog entries; it is not presented as a unique algorithm.
03 Validation plan
Own-hardware protocol: scripted delivery runs with deliberately mis-mapped destinations on a test fleet; score terminal-zone segmentation accuracy and offset-versus-scatter separation against the script; validate deposit-snapshot trigger precision at instrumented drop points.
04 Commercial hypothesis
'Misplacement Watch' — for the inventory-integrity owner whose WMS says shelved while the item is unfindable: the independent record that deliveries kept terminating one zone south of where the fleet declared them, before the cycle count finds the hole.