Fleet Ops Lab

A missing acknowledgment can make a completed delivery look unfinished. Sending the robot again would be the wrong fix. I wanted a place to create that ambiguity on purpose and inspect what each service saw.

• An interactive order-to-receipt demo. Place an order, drop the inventory reply, and watch receiving retry. The inventory ledger lets you check that the trays were counted once.
• A blocked-aisle scenario with investigator tools to read fleet state, cite observations, and preview a reroute. The browser demo uses a deterministic investigator. The local version can give the same tools to a language model.

• The investigator can propose a route change. The operator reviews the preview and decides whether to apply it.
• The simulator tracks the actual delivery after a route change. A successful command alone cannot close the incident.

You can replay a failure and trace a proposed fix back to the observation that justified it. After an approved reroute, you can follow the robot to the station and check the delivery receipt yourself.