MaaS Runtime Control
Controller-owned runs, service health, evidence gates, and useful-document proof status.
Signed out
Drone Orchestration Status
| Run | Status | Kind | Updated | Resource group |
|---|
Run detail
Event trail
Remote telemetry
New Fleet Provision
What Must Be Proven Next
- Use the run detail panel to prove click a run → controller events, VM state, model progress, generation state, output pointers, and no raw secret leakage.
- Redesign the stop/delimiter contract without putting the active stop word in the prompt.
- Rerun source-aware documentation only after that redesign.
- Require useful section content, no process prose, no cap hit, no repeated tail, clean terminator, and
contract_ok=true. - Prove Loom weave cleanly accepts the useful document thread.
- After three stable runs, revisit whether MaaS moves out of Hart OS into its own service boundary.