Modernisation Control Room
Your single view of where the programme is, what evidence supports, what is unknown, and what requires human judgement.
Completions
Live Work
What MaaS is doing right now: active work units, their last observed progress, and anything that has gone quiet.
Outcomes
Measured programme outcomes and compute economics. Nothing here is a promise; every number traces to run evidence or Azure billing.
Understanding delivered
Compute economics
Decisions
Consequential judgements requiring named human authority, with evidence context.
Service Health
Run Administration
Kill a live run or reconcile a stale run summary after teardown has already completed.
| Run | Status | Application / work unit | Model | Updated | Resource group | Action |
|---|
Drone Orchestration Status
Auto-refresh idle
Execution outcome
Journey coverage
Active now · All programs
Checking queued work units...
History
Select a repository or program, then choose a run.
| Run | Work unit | Status | Kind | Updated | Runtime | Context | Recovery | Resource group |
|---|
Repository journey
Work-unit attempts
Current finding
Evidence
Attempt journey
Run detail
Stream idle
Failed-attempt investigation
Controller record
Event trail
VM status / callback stream
Output artifacts
Completion event
Teardown
Runs
Every run the controller holds, by day, application, batch and work unit.
Loading run index
Select a date
Run indexRun Artifacts
Select a run artifact
Controller-streamed Blob contentLoom Weave
Consolidate application artifacts into HLD, LLD, diagrams, requirements, tests, and open questions.
Select an application
Application cloth
Waiting for application selection
Generated artefacts
Browse durable Loom sessions and their generated documentation files.
Choose a generated file
Loom session exports
Choose a date and application
Choose a session and generated file to preview it.
Application Specification
Generate a governed draft from a completed Loom session and a proposed operator target outcome.
Choose an application
Phase 4 draft
Choose an application and Loom session
Draft package
Choose a specification file
Modernisation Plan
Plan before execution: assemble evidence and specification context, then generate a governed plan draft for human review.
PLAN-### v#
Draft
No plan loaded.
Work Orders
Bounded implementation units derived from an approved modernisation plan.
Work order generation blocked. An approved modernisation plan is required before implementation work can be proposed.
| Work order | Status | Owner | Gate | Dependencies | Evidence |
|---|
Investigations
Bounded collaboration contexts showing delegation, findings, challenges, evidence links, and required human review.
Repositories
Repository Plan
Repository plan
Execution Batch Ranges
Selected partition plan
Submission
Preparing batch submission
Checking the active batch gate.
Submission JSON
Submit New Plan
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.