Dry mode
Preview before mutation
Run can show the exact change it would make before live execution, so the operator sees scope and target before anything mutates.
ArkheOS / Proof
Proof means receipts, artifacts, and changed paths.
Run is not presented as a concept. The product already executes bounded commands, produces artifacts, and writes durable receipts that show what changed and where.
Live mode
One bounded result
The live path executes one adapter once, returns a visible success receipt, and leaves behind both artifact and trace.
Sale proof
Live checkout exists
The public product page already points at a real Stripe payment link, so proof now includes both product execution and sale-path readiness.
Receipt excerpt
Actual Run execution trace
{
"owner": "Run",
"status": "completed",
"mode": "live",
"adapter": "blender",
"command": "create product render",
"changed": ["render artifact created"],
"artifact": ["...\\demo-project\\renders\\product-render.png"]
}
What gets proved
- Commands are project-scoped instead of free-floating.
- Invalid instructions are rejected instead of being “interpreted.”
- Live execution causes real file or artifact changes.
- Receipts survive as durable evidence after the run completes.
Why it matters
Most AI surfaces stop at language. Run stops only after a bounded instruction creates a visible result and leaves behind proof that the result actually happened.