Warehouse
RoadmapTask assignment. Pick-face allocation. Labor scheduling. Slot optimization. In-warehouse decisions at sub-second cadence, informed by the same world model the supply plan writes into.
What makes this a distinct decision domain
Warehouse operates at the smallest granularity, task-level decisions in seconds, with exogenous information dominated by labor availability, pick-face state, and equipment utilization. The policy class is PFA: fast heuristic policies that execute at throughput speed.
Of all the domains, warehouse requires the most new state, facility-level slots, equipment, labor pools, congestion, which is why it's sequenced later on the roadmap.
Why it belongs on the same platform
The warehouse is where supply plans become physical movement. If the world model stops at the dock, every internal slip becomes opaque to the rest of the planning stack. Autonomy extends the shared state into the facility so task-level outcomes feed directly back into the inventory and transport views.
Roadmap
Warehouse is on the longer-horizon roadmap, sequenced after portfolio, production, and transport. Design partners welcome, particularly operators running multi-site DC networks.
This plane intersects with
Where the collaboration contract lives, not an integration project.
Warehouse as an extension, not an island
See how the shared world model turns task-level decisions into a signal everyone benefits from.