MaaS Operator Console

Modernisation Control Room

Where the programme is, what is being worked on now, and what the evidence supports.

Service health

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

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

Repository or program Day Batch Run Auto-refresh idle

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

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 index

Run Artifacts

Select a run artifact

Controller-streamed Blob content

Loom 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

Target outcome Minimum 10 characters

Choose an application and Loom session

Model Work Orders

Backward-chained implementation planning: derive from acceptance, then execute from mandatory base task 0 with the best-fit model per work order.

Generate and verify an application specification in Phase 4 to inspect its work orders.

Order	Priority	Effort	Requirement	Dependencies	Lane	Readiness

Repositories

RepositoriesDashboard

Repository Plan

Repository plan

Local partition output

Execution Batch Ranges

Selected partition plan

Submission

Preparing batch submission

Checking the active batch gate.

Submission JSON

Submit New Plan

Repository URL Target owner Target repo Source ref Max drones Target lines/drone

Partition objective

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.

Sign in