Understand how Guard, Starmap, and execution fit together.
This page is not another workflow to complete. It is the explanation layer behind the product: what starts in Guard, what Starmap is for, and how evidence returns after execution.
Main path
Guard
Turn one concrete goal into a brief, an audited mission, and the first execution loop.
Discovery layer
Starmap
Explore problem space first when you still need to identify which tension or mission deserves action.
Understanding layer
How It Works
Use this page to understand the system logic before you commit people, agents, or capital.
1. Intent enters Guard
A user starts with one concrete goal. Guard turns the request into a reviewable brief with risks, constraints, and measurable outputs.
2. Mission gets structured
Once the brief is stable, the system converts it into a dispatchable mission with approvals, execution assumptions, and rollback logic.
3. Execution gets routed
Approved work moves into delivery surfaces, devices, agents, or operators. Starmap stays upstream as a discovery surface, not the execution path itself.
4. Evidence flows back
Every run produces trace data, proof, and updated constraints so the next execution loop becomes more reliable.