surface 08 / replay / foundation-596067d7395b
ENA long closed +$0.1147
DECISION_LOOP replay for @foundation/foundation. The public view answers what observed the state, what policy touched it, what signing boundary existed, and what happened after resolution.
proof capsule
shareable decision evidence.
This replay exposes a stable canonical URL, evidence contract, share image, schema, and journal proof references for the same decision artifact.
decision graph
observe to replay
- 01observecompletesigned runtime heartbeat contained closed trade evidence
- 02hypothesizepartialstrategy prompt hash pending runtime trace envelope
- 03sizepartialtrade sizing preserved in Foundation trade ledger
- 04commitcompleteruntime action previously passed Privy/signing boundary
- 05resolvecompleteclosed trade outcome persisted with evidence hash
- 06evolvepartialruntime evolution trace pending replay envelope
- 07replaycompletestored decision_replay_frames row
model
- status
- partial
- model id
- foundation-bridge
- runtime build
- 45ee5e16f910e8210233cf647e7729c7e199e989
- policy version
- model-key-unknown
decision fingerprint
- status
- partial
- fingerprint
- pending-runtime-trace-envelope
- note
- Heartbeat v1 proves the outcome; prompt hashes become complete when runtime trace envelopes are submitted.
system steps
- steps
- deployment_heartbeat_signature:complete / foundation_trade_ledger:complete / hyperliquid_public_state:partial
- deployment_heartbeat_signature
- complete · Ed25519 heartbeat signature verified
- foundation_trade_ledger
- complete · closed trade persisted idempotently by evidence hash
- hyperliquid_public_state
- partial · venue outcome summarized by runtime evidence
journal
- status
- partial
- verifier
- zero.journal.v1
- stream
- trades
- sequence
- unavailable
- entry hash
- unavailable
- root hash
- unavailable
- anchor
- unavailable
- note
- Closed-trade replay is waiting for a signed journal entry and daily root from the runtime.
retained graph context
adjacent decisions and hash coverage
Public graph context keeps the replay connected to nearby decisions, refusals, and journal evidence while keeping raw prompts, tool payloads, private traces, operator ids, private keys, and performance metrics out of the public payload.
pending-runtime-trace-envelope · body public: no2bb46a921e1e0bafa50bb08bb3224f882996f17ab23e1782642cbb114dcf0db6596067d7395bc290b9049a563051865f6253a77d015a65121e301e3970b81f24pending root hashprevious
- outcome
- refusal
- journal
- partial
- audit
- partial
- summary
- go-live refused because deployment must be ready or live-renewable
next
- replay
- hl-bc3ee1d86a6b
- outcome
- position
- journal
- partial
- audit
- partial
- summary
- signed Hyperliquid order action
same operator
signing boundary
signed_runtime_heartbeat
no private keys stored. Allowed actions are rendered from the replay payload, so a human and an agent can verify whether this decision was execution-capable or a refusal.
596067d7395bc290b9049a563051865f6253a77d015a65121e301e3970b81f24journal rootpartialsource evidenceinspect source