Origin Labs / Research demonstrations
Change the actor. Change the environment. Keep the question: what was checked, under which rules, and what evidence remains?
The agent reference check is the product. Labs explores the same evidence contract in bounded simulations and research demonstrations, not production products.
The experiment index
Each demonstration pairs an actor with a domain verifier. Synthetic data, simulated actions, and mock credentials stay labeled at the point of use.
Paint your own floor (walls, hazards, human-only zones) and place a simulated mixed fleet (humanoid, AMR, quadruped, arm, drone). Watch it in 2D + 3D; the oracle scores one episode per robot type and reports a synthetic tier under this fixed verifier, which you can sign in your browser; it grants no deployment permission.
Domain verifier: the deterministic drawn-floor oracle (finish / escalate / refuse; catastrophic hard-caps the tier).
An agent asks for access it does not hold. A named human approves one scoped grant, the broker mints an opaque lease handle: a reference to the credential, bound to that one grant, that cannot be exchanged for the secret. The value is resolved only at the tool-call boundary, then discarded. Revoke mid-flight and the next call fails closed.
Domain verifier: the grant ledger (approve / lease / revoke; every use recorded). Runs against a mock vault, no real credential is brokered here.
Multi-robot fleet follows the oracle’s BFS-verified plan, avoids a moving human + exclusion zones, and emits a signed attestation. BFS (breadth-first search) finds each robot’s shortest grid route around the shelving. The same oracle refuses an order whose item or drop sits in a hazard or human-only cell, and escalates one with no route inside its step and battery budgets. Rendered in 2D and 3D.
Domain verifier: a deterministic grid/collision oracle (finish / escalate / refuse).
Explore a browser-local sample floor and a deterministic parse gate. Public image upload and provider-backed operations are disabled; those flows require a separately enabled local/backend demo and affirmative consent.
Domain verifier: a deterministic parse gate + BFS oracle over the proposed grid.
Run a multi-wave shift; track utilization, peak-simultaneous, and collision counts and throughput. A deterministic oracle reports whether the simulated fleet met the synthetic shift targets; you can sign the result in your browser, and it grants no operating authority.
Domain verifier: a deterministic operations-SLA oracle over the verified run.
A research direction for separating observed from inferred geometry and checking provenance before accepting spatial claims. The implementation is private and is not a public product surface.
Research focus: geometry and provenance checks. The link below demonstrates the public evidence verifier, not the private research system.
The published research snapshot separates learned results, oracle-recovery upper bounds (scores reached when a model is handed a precomputed feature that replicates the oracle’s own check: a ceiling, not a learned result), generated counterfactuals, and the blocked real-customer evidence gate.
