Mission Computing.
A different computational model: instead of a conversation that ends when the window closes, a mission is a persistent object that continues until it's actually done.
A mission, not a prompt
Traditional computing is interface-and-event: you open an application, issue a command, get a result. Mission computing treats the goal itself — the mission — as the persistent thing, with ASH coordinating agents, models, and tools toward it over however long it takes.
The flow
You state the mission. ASH coordinates agents, models, and tools — local and, where appropriate, cloud — against it. ER hardware provides the local compute and memory. The result comes back with a record of how it was produced, not just the output alone.
Full detail
See the architecture diagram on the ASH A(π) page for the complete coordination model.