Skip to main content

Observing a machine

Everything a machine does lands on its audit chain — and all of it is readable. You don't infer what a machine did from side effects; you look. Three public surfaces let you see the state at three scales: the whole network, one machine live, and any moment in the past.

Explorer

Browse recorded computations across the network — entries, details, and stats — the block-explorer view of the state chain.

Observer

Watch one machine's state and every transition stream live as it ticks, over server-sent events.

Time machine

Rewind. Read a machine's exact state at or before any past Zeqond — history as a slider, not a guess.

Browse the chain — the explorer​

The explorer is a public read surface over the audit/state chain. It backs the block-explorer UI, and you can call it directly:

curl -s https://zeqsdk.com/api/explorer/computations   # recent recorded computations
curl -s https://zeqsdk.com/api/explorer/stats          # network-wide totals

Each entry names the operator it ran, the result, the Zeqond it happened at, and carries the ZeqProof you can re-verify — so browsing the chain isn't reading a log you have to trust, it's reading records you can check.

Watch one machine — the observer​

To follow a single machine, the observer streams its state and transitions live:

# a machine's current state
curl -s https://zeqsdk.com/api/chain/YOUR_MACHINE/state
# live transitions as they happen (server-sent events)
curl -sN https://zeqsdk.com/api/chain/YOUR_MACHINE/explore/sse

Point a page at the stream and you have a live dashboard of a machine ticking on the 1.287 Hz clock — which is exactly what the Observer app does.

Rewind — the time machine​

Because the chain is ordered by the Zeqond, "what did this machine look like then?" is a precise question with a precise answer. The time machine reads the state at or before any tick:

curl -s "https://zeqsdk.com/api/chain/YOUR_MACHINE/at?zeqond=2296500000"

There's no reconstruction or approximation — the seal spine means the past is fixed, so a snapshot at a Zeqond is the state at that Zeqond. History you can scrub through, and trust.

  • State machines — the chain you're observing.
  • Proofs — why every entry you browse is verifiable.
  • Applications — the Explorer, Observer, and Globe apps are these surfaces with a UI.