Start with intent
An outline lets you keep an unfinished thought next to a concrete task. A parent describes the goal; children hold the details. You can rearrange the structure as your understanding changes. In ThreadVM, each node has a stable ID, so moving a thought does not sever its connection to the work it started.
Context follows the branch
A delegated node becomes a thread. Its ancestor path explains why the task exists, and its subtree describes the work. The local harness passes that context and instructions to the run. You can keep broad planning and narrow execution in one document without treating every bullet as an agent command.
The document stays yours
In the local interface, mentioning an agent starts a short countdown when you leave the bullet. You can send it immediately or keep it as a note. Agents can propose changes, ask questions, and report observations. They do not silently rewrite your outline: proposed changes wait for review.
An interface hypothesis
The bet is that this keeps intent and execution close enough to stay understandable. The outline becomes the place to write, delegate, inspect, and review. This is an exploration of that interaction, with a working local harness to test the idea.