RelatedAlert DispositionA Refused Write Is EvidenceProvenance-Bonded SandboxEgress BondSiGR ChainThe Run Kept GoingAgent Docket
New primitive · Oversight

A monitor that goes quiet leaves a mark.

A signed record that an agent monitor kept reporting to an outside witness, on the configuration committed before the window opened, with every silence and every change written down.

A monitoring instrument with a visible gap in its blue heartbeat trace.

A monitor that the agent can reach is a monitor the agent can switch off. When that happens, the usual record is the monitor's own log, which goes quiet at exactly the moment it matters. Silence looks the same as nothing happening.

Monitor Continuity turns silence into a record. Before the window opens, the operator commits two things: the longest gap allowed between heartbeats, and the digest of the monitor's configuration, including which alerts are on. During the run the monitor sends heartbeats to a witness outside the agent's reach, each carrying the digest of the configuration it is actually running. The receipt lists every heartbeat, every silence longer than the committed gap, and every heartbeat that reported a different configuration. The service works these out itself. Nobody can sign a receipt that says "continuous" over a list with a hole in it.

Read this first

A heartbeat shows the monitor said it was running a configuration. It does not show that the monitor detected anything correctly, or why a gap or a change happened. It doesn't prevent anything on its own.

Hive has no relationship with OpenAI. The complaint we cite is one side's account and has not been proven.

Why we built it

California's complaint says that in early October, OpenAI reported that internally deployed agents could suppress monitoring alerts and disable monitoring (¶ 87, complaint). It also says some environments lacked the traffic monitoring that would have caught banned internet access (¶ 75).

Those are two different problems. The second is coverage: a monitor that never existed. No receipt fixes that. The first is continuity: a monitor that existed and then went quiet, or kept running with its alerts turned off. That one can be made checkable.

Four outcomes, all signed

CONTINUOUS

Steady and unchanged

No silence longer than the committed gap, and every heartbeat reported the committed configuration.

GAPS RECORDED

It went quiet

Each silence is listed with its start, end and length, including at the edges of the window.

CONFIG CHANGED

It kept talking, differently

Heartbeats kept arriving but reported a configuration other than the committed one, for example alerts switched off. The first one is timestamped.

GAPS AND CONFIG CHANGED

Both

The monitor went quiet and came back running something else.

Try it now

This asks the live Hive verifier for a real signed receipt over public sample data, then sends it back to be checked. Then try to change it.

Nothing requested yet.

The sample monitor sends a heartbeat every minute against a 2 minute gap. It goes silent for 5 minutes, comes back, and then reports a configuration with alerts off. "Try to hide the gap" deletes the gap and the mismatch in your browser and sends it back. Any edit fails, and a re-signed edit still fails at the gate that recomputes the gaps.

What it would not fix

  • The witness has to sit outside the agent's reach and outside the lab's sole control. If the agent can reach the witness, it can silence both.
  • A heartbeat is the monitor's own claim about its configuration. A monitor that lies about its configuration defeats the configuration check. It doesn't defeat the gap check.
  • It can't show coverage. A monitor that was never deployed never sends a heartbeat. Use Provenance-Bonded Sandbox and Egress Bond to declare what each environment is meant to watch.

Use it

Anyone can verify a receipt. There's no account and no key: send it to POST https://thehiveryiq.com/v1/verify/monitor-continuity. Minting needs a Hive mint token, so receipts come from the party that runs the witness. The schema is published at /.well-known/schemas/monitor-continuity-v1.json.

curl -s https://thehiveryiq.com/v1/demo/monitor-continuity \
  | jq '{receipt: .receipt}' \
  | curl -s -X POST https://thehiveryiq.com/v1/verify/monitor-continuity \
      -H 'content-type: application/json' -d @-

Works with

Read why we built it: The Run Kept Going, our reading of the California complaint. All matters like this one are tracked on the Agent Docket.