Turn intent into
a plan you can
inspect.
CentraScript turns a request into an ordered plan, carries each step through a visible walk, and leaves a receipt behind. The result is work you can trace instead of a story you have to trust.
Improvisation doesn't audit.
Freestyle agents can't be audited
An agent that improvises its way through your accounts leaves you one artifact: its own story about what it did. If something goes wrong, you're auditing prose.
When a Centra agent acts on the world, it does not freestyle. Intent is compiled into CentraScript, a deterministic, signed, replayable plan.
Determinism buys replay
The same intent produces the same walk, byte for byte. That single property is what makes every run replayable and independently verifiable by anyone holding the record.
Not "trust us, it did the thing." Run it again and watch the bytes match.
The gate lives in the language
A value-moving or irreversible step parks the walk until a human answers. That gate is part of the execution model, not a policy layer bolted on top that a config change could remove.
You can't compile around it, because it isn't in front of the language. It is the language.
From intent to receipt, in order.
Compile, plan, walk
Intent becomes a plan; the plan becomes a walk. Each step executes in order, each is journaled as it happens, each is signed.
There is no step the agent took that the record doesn't show.
Signed at every step
Not one signature over a summary. A signature per step. Tamper with any point in the walk and the record says so.
Parked, not paused
When a walk hits an approval gate, it parks: state held, decision surfaced, plan and reasoning attached. Answer yes and it resumes exactly where it stopped. Answer no and it ends, on the record.
The receipt at the end
Every run ends in a signed receipt: inputs, outputs, spend, replay hash. It is not a feature grafted onto the runtime; it falls out of the design. A deterministic, signed walk is a receipt waiting to be printed.
Built for people who read the record.
The CLI speaks it natively
mcl run, mcl approve, mcl receipt verify. JSON-first output, built for pipes and scripts: the same walks and receipts you see in the product, from your terminal.
Walks you can read
A walk is an ordered, inspectable record (plan, step, result, signature), not a black box. If you can read a script, you can read what your agent did.
Verify without an account
A receipt stands on its own. Anyone holding one can check the signatures and the replay hash. No Centra login, no API key, no taking our word for it.
The language reference, the walk format, and receipt verification are all in the docs, written to be read, not skimmed.
Read the docsFor supported workflows, a run can remain an ordered, inspectable walk with evidence you can keep and verify.