Status and trials
Current release checks
The release checks exercise the original interface, durable synthetic source/observation/tracker path and selected offline contracts. Exact checks distinguishes fresh CPU installation, real local startup, browser proof, fake transports and separate provider acceptance.
Original executed trials
These are dated development measurements retained with the source, rather than current production service guarantees.
| Work | Recorded evidence | Interpretation |
|---|---|---|
| H100 Cosmos Embed indexing | 51 assets, 176 windows, 21.82 camera-minutes; recorded worker batches | Working indexing path on a small corpus |
| Exported CPU text tower | GPU/CPU cosine comparison 0.999978; warm full query around 0.15–0.25 seconds in that corpus | Encoding/retrieval parity and measured local query path |
| Qdrant | Twelve development queries matched NumPy top-six ordering/recall; lookup medians 1.523–4.758 ms | Persistent filtered retrieval parity; separate from semantic accuracy and scale qualification |
| Detailed Cosmos inspection | Selected-clip trials, including Cosmos3-Super on B200 | Working execution/caching/provenance; retained scene/role/payment/identity errors require quality work |
| NVIDIA tracking | RTX PRO 6000 Blackwell, DeepStream9.1.0.2, PeopleNet2.6.3/NvDCF/BodyPose3DNet/MV3DT; four-camera calibrated synthetic warehouse, 7,170 messages /1,797 complete frames | An executed calibrated sample; arbitrary customer-camera calibration has separate work |
| RetailAction admission | Zero observations admitted in the narrow later commissioning trial; 17 prior candidates quarantined | Admission stayed closed while business-event quality remained unresolved |
| Custom tracker sandbox | Retained gVisor proof: 2,000 synthetic events, four periods,1.070 seconds | A prior code/executor proof; this release has separate local source checks |
Historical evidence record identifies source revisions and retained technical records. Original source footage, account receipts and raw model answers stay outside the release.
Separate acceptance
Live camera acquisition, arbitrary-camera calibration, business-event quality, real POS integration, live phone delivery, managed agent execution, GPU indexing/inspection and complete maintained PostgreSQL playback need their own owned service acceptance. The source retains those contracts and their current implementation state.
Sales and conversion derived from baskets/catalogue prices carry an estimated basis. Committed till rows carry their separate transaction basis. The fixture first result shows the actual source requirements in measures that need additional input.