Task → Verify → Close the loop
The mental model: operators express intent; Chorus validates and orchestrates; Hyperion produces georeferenced findings; the loop enables re-tasking.
1) Task
Voice, text, or map geometry becomes a universal intent representation: objective, assets, geometry, timing, constraints.
2) Verify
Validation barriers confirm playbook executability and safety constraints before dispatch.
3) Close loop
Hyperion turns sensor feeds into georeferenced findings; Chorus consumes them as awareness objects to re-task.
Trust mechanics
What makes this defensible under review: audit-grade traceability and degraded-comms realism.
Audit chain
Input → interpretation → validation → plan → dispatch → state changes, stored as an event chain.
Degraded comms
Queueing, retries, acknowledgements, link windows, and last-known state warnings by default.
Make it real on your platforms.
We'll keep the public site honest: adapter-based, no invented integrations, no fake metrics.