Milkyway
The orchestration layer of PLUTO.
PLUTO already flies missions from plain language. Milkyway is what makes the platform understand them. It is an intelligence layer across the whole fleet that watches everything the operation produces (telemetry, detections, swarm state), reasons over it, and proposes what a human should consider next. It can want anything. It can do nothing without you.
The World Graph
Every drone, mission, waypoint, detection, sensor, and area of interest in your operation lives as a node in a live graph we call the World Graph. The relationships between them (which drone flew which corridor, which camera saw which object, which mission covered which field) are the edges.
The graph is always now: PLUTO's event backbone streams the fleet's state into it continuously, so it behaves as a live digital twin of the operation. And it is always history: every state change is preserved, so last month's flights are as queryable as the one in the air right now.
This is what grounds Milkyway's reasoning. Before proposing a survey, the mission planner can ask what previous flights over that terrain actually found. Before flagging an anomaly, the system can compare against every similar moment the fleet has ever recorded. Shared memory is what turns a fleet of aircraft into a single operation.
The Model Orchestrator
On top of the World Graph runs a supervisor whose only job is judgment: what deserves attention, which specialist should reason about it, and whether the result is worth a human's time.
Under it sit specialist agents, each scoped to one slice of the operation:
- Mission Planner Turns operator intent into mission structure, grounded in what the graph already knows about the terrain and past flights.
- Telemetry Reasoner Sleeps until a deterministic prefilter flags an anomaly, then reasons over full graph context: a battery burning faster than modeled, a margin that collapses four waypoints ahead.
- Swarm Policy Sits above PLUTO's deterministic deconfliction engine and may only suggest role changes the engine certifies as safe. The math stays math.
- Perception Supervisor Owns every camera stream. Edge detectors run at full rate on the aircraft; only the frames worth deeper thought reach richer models; sightings of the same object from multiple cameras are fused into a single fact in the graph.
Deterministic systems handle the fast, repetitive work. Models are reserved for judgment. That is the latency budget, the cost budget, and the safety story, all one design decision.
The Proposal Gate
No agent in Milkyway holds a connection to an aircraft. Structurally, agents have read access to the World Graph and exactly one write path: a Proposal.
Every proposal carries the agent's reasoning and the graph facts it reasoned from. It then passes through a deterministic validator, a 3D rehearsal the operator watches, and a human approve/deny gate. The aircraft's onboard system re-validates everything on receipt and contains no AI in its control path.
This is not a policy written into a prompt. It is enforced at the permission layer and in a single endpoint write gate. Milkyway grows smarter with every flight, and its authority never grows at all.