Skip to content
operating intelligence runtime · —Sign in
Menu

Decision replay

refusal-live-93a34b80ee80

go-live refused because deployment must be ready or live-renewable

refusaloccurred 2026-06-06T01:25:43.512Zvenue hyperliquid

Decision loop

each step carries its own status and evidence
  1. observecomplete

    operator requested a live lease

  2. hypothesizenot applicable

    refusal occurred before strategy hypothesis execution

  3. sizerefused

    go-live request failed the live lease safety gate

  4. commitrefused

    no signed action or live transition was committed

  5. resolvecomplete

    refused: deployment_not_ready

  6. evolvepartial

    operator/runtime may retry after resolving the refusal reason

  7. replaycomplete

    stored decision_replay_frames row

evidence

outcome

kind
refusal
venue
hyperliquid
occurred
2026-06-06T01:25:43.512Z
symbol
none

journal

status
partial
stream
safety_refusals
entry
none
root
none

No signed journal root has been attached to this replay yet.

signing boundary

status
not applicable
private keys stored
no
payload
93a34b80ee80ee8de839d6b1199fabaaafd04ffddfa9c6e71e020a533ce66726
allowed
order, cancel, scheduleCancel

audit

status
partial
score
75
complete checks
5/10
missing evidence
decision loop, model, prompt, journal entry, journal root

Proof of record

this page is the record — verify it without an account

refusedrefusal · hyperliquid · 2026-06-06T01:25:43.512Z

bounded signing scope (live_lease_gate) · no private keys stored

the runtime declined this act, and the record shows it.

Content hash
93a34b80ee80ee8de839d6b1199fabaaafd04ffddfa9c6e71e020a533ce66726
Signed entry
none
Chain position
stream safety_refusals · no previous-entry link recorded
Journal root
none
anchor
unrecorded

no signed journal root is attached to this record yet — this page says so rather than pretending.

Verify in a terminal

curl -s https://getzero.dev/api/replays/refusal-live-93a34b80ee80

one request, no account, no API key. The response carries the content hash, the signed journal entry and the root hash above. Check the root offline with the open verifier (zero_verify_journal_root on the public MCP endpoint, or the open-source engine’s own verifier).