smalltalk pre-release
From intent to mission
Launch turns a plain-language request into a mission. You describe what should happen and why, a planner agent drafts the mission, and you review it before anything runs.
It's the top of the stack: intent in, durable mission out.
How it goes
- Start. Write your request in Markdown and start a launch session.
- Draft. The planner writes a Markdown description and the mission KDL.
- Preview. smalltalk validates the draft and shows you the steps as a dependency graph, what would change in the graph, and any warnings or blockers.
- Feedback. Send feedback and the planner revises. It can also offer variants, such as a compact plan and an extended one, for you to compare.
- Approve. Approving publishes the mission. It doesn't start it, unless you choose approve-and-launch, which does both.
st launch start --id release-mission request.md --workspace ./project --as person/ada
st launch preview SESSION
st launch revise SESSION feedback.md --as person/ada
st launch compare SESSION compact extended
A launch is graph state
The session lives in the graph: the request, the planner, each candidate, your feedback, the preview and your decision. Each document is stored immutably, and approval needs the current preview's token. If the draft changes after you looked, you approve again, so the mission you publish is exactly the one you reviewed.
Because it lives in the graph, a launch can pause on one machine and continue on another.
Changing a running mission
A launch can also target a run that is already going. The planner drafts a revision, you preview it, and your approval proposes a new generation for that run.
Launch approvals wait in your attention inbox, so a draft that needs you doesn't get lost in a chat.