Execution that drifts
The same rule runs differently at 2am than at noon. Inconsistency compounds faster than any edge.
built for always-on onchain markets
Operating intelligence for self‑custodial capital.
ZERO coordinates agents, policy, execution, and proof around capital you still own — every action inspected, interrupted, replayed, and verified.
01
where loss actually comes fromCapital moves faster than attention.
Markets run continuously, at machine speed. A person does not. Most operators bridge that gap by hand — a dashboard here, an alert there, a script, three exchange tabs, an agent they half-trust, a spreadsheet that is already stale. The failures that follow rarely come from a missing signal.
Risk you can't see
Exposure spreads across venues and agents. By the time it is legible on a chart, it has already moved.
State you can't trust
What did the agent actually do, and why? If the answer lives in a log nobody replays, it isn't an answer.
Intervention that's late
The moment to step in passes in seconds. A system that can't be interrupted cannot be governed.
02
One operating loop.
ZERO is a runtime that sits between an intent and the market. Every action — whether it originates with you or an agent — travels the same six stages. The Runtime is the engine that runs them; policy is the set of limits and approvals you define; the journal is the append-only record everything writes to.
stage 01IntentA human or an agent proposes an action.enters: human · agent
stage 02RuntimeThe engine simulates the action against current state.enters: capital state
stage 03PolicyChecked against your limits and authority rules.enters: policy · approval
stage 04ExecutionPaper, or self-custodial signing in your wallet.enters: delegated signer
stage 05JournalThe decision, reason, and result are written down.append-only
stage 06ProofAnyone can replay and verify it, to the second.public · read-only
a decision traversing the looprefused actions stop at policy — and are still journaled and replayable
03
Observe. Govern. Verify.
The product is organised around what you do with it, not the modules underneath. Three modes, one runtime.
mode i
Observe
See the whole position, and what is about to happen to it.
Capital & runtime stateCurrent exposure, balances, and what the engine is doing now.
Actions & proposalsWhat agents have done, and what they intend to do next.
Risk, freshness, healthHow exposed you are, how current the data is, what's degraded.
Decisions & refusalsEvery accept and every decline, with the reason attached.
mode ii
Govern
Set the limits, and keep the controls that matter within reach.
Mandates & limitsExplicit authority: what an agent may do, and how far.
Approval where it countsFriction graded by consequence — the bigger the move, the more it asks.
Risk-reducing actionsFlatten or halt stays available even when everything else is gated.
Revocable, scoped authorityGrant is narrow by default and can be withdrawn at any time.
mode iii
Verify
Take nothing on faith. Replay it instead.
Replayable decisionsStep any journaled decision, beat by beat, after the fact.
Receipts & refusalsSigned records of what happened — and what was declined.
Journal rootsAn append-only spine you can check for tampering.
Open contracts & verifiersThe proof format is public; anyone can run the check.
04
Show, don't claim.
Public ZERO is observation-only, and everything below is bounded, public-safe evidence. Each item carries its source, the time it was observed, and an honest classification. The proof of this product is disciplined behaviour — not an equity curve.
classification:replayfixturedelayedunavailable
AA refusal and its reasonNo public refusal is reachable right now — absence is shown as absence.unavailableindex →BA replayable decision traceStep the latest journaled decision (heartbeat) through its stages, exactly as it happened.replayopen →CA journal-root verification34 signed roots · 34 calendar attested · 27 chain confirmed. Check the append-only spine yourself.replayverify →DRuntime health, with freshnessRuntime clean · state live · heartbeat 11s old at render — stated, never smoothed.delayedstatus →When evidence is unavailable, this surface says so. Absence is shown as absence. No item on this page is fabricated live data, and public surfaces never display authenticated operator state.
05
You keep custody. ZERO keeps the line.
The trust boundary is part of the product, not the fine print.
held
Funds stay operator-owned. ZERO is not a custodian and never holds your assets.
held
Signing is delegated and scoped. The signer's authority is bounded to what you grant.
refuses
Unsafe states refuse. An action outside policy is declined before it reaches the market.
held
Risk-reducing actions stay reachable. You can always flatten or halt, even when the rest is gated.
held
Authority is revocable. A grant is narrow by default and can be withdrawn at any time.
gated
Public access is observation-only. Operating authority requires a signed-in operator and explicit, revocable grants.
the custody boundary
your walletYouCustody of funds. Ultimate authority. Revocation.
delegated signingthe runtimeZERODecides, checks, signs within scope, journals.
No custody. No light mode. Both by rule — not by current configuration.
Read the trust & security page →06
It improves under review.
ZERO observes its own behaviour and proposes changes. Those proposals reach protected live behaviour only through review and paper-safe evaluation — never automatically.
01Behaviourobserved
02Memoryrecorded
03Proposaldrafted
04Guardian reviewautomated check
05Red-team reviewadversarial
06Paper / shadow canaryno capital at risk
07Promotion or rollbackhuman authority
08Proofrecorded
what is automatic
Observation, memory, and proposal. The system can notice and suggest on its own, and evaluate suggestions on paper.
what requires a human
Promotion into protected live behaviour. No protected live code changes without human review. Rollback is always on the table.
07
Open substrate, hosted product.
The parts that establish trust are public. The hosted operator surfaces are where you run capital. The boundary is explicit.
The open substrate
Inspect it, build against it, or operate with it.
path iInspect the proofWatch the public record. Replay a decision. No signup before you've seen everything.See the system in public →path iiExplore the open runtimeRead the Runtime, Protocol, and Proof. Build and verify against open contracts.Open the substrate →path iiiOperate with ZEROOperate self-custodial capital through ZERO. Sign in, then claim a runtime from the studio.Sign in →
observation-only, by default
The whole record is open before you sign in. Entry is self-serve — sign in, then claim a runtime from the studio. No custody. Funds never leave your wallet.