CONNECTING TO PULSE
UTC
HIVE RADAR™ / LIVE INFERENCE OBSERVATORY
See how inference providers respond.
Review Hive’s provider checks, timestamps, recorded evidence, and gaps.
Reading public observations. Each request has an 8 second timeout.
CURRENT VERDICT
CONNECTING
Waiting for the witness log
- Next sounding
- Calculating
- This hour
- Reading history
- Reported proof checks
- Waiting for providers
60 minute pulse
Open board
SIGNED ACTIVITY
Witness channel open · observation rows resolving · no synthetic values substituted
DURABLE PULSE HISTORY
Provider checks from the last 60 minutes
Observed path
Reported proof checks
PROVIDER DECK
··
Recently checked paths
- Next sounding
- Calculating cadence
- Durable rows
- Reading store
- Storage
- Checking persistence
RECENT TRACE
UTC
Signed observation stream
Reported valid checks
Observed timing
Explicitly unavailable
SOUNDING WINDOW
Building the retained observation window
CADENCE15 min
Radar sounds each live path on a scheduled cadence. Empty minutes are minutes Radar did not sound, not minutes a provider was down.
PROVIDER CONSTELLATION
Provider paths and their evidence status
The board distinguishes recurring checks, archived results, missing credentials, and paths that have not been tested. An untested path is not marked healthy.
Loading provider registry.
Search and modality are preserved in this page URL and in local browser storage. This is a public read-only view.
SIGNED EVIDENCE VAULT
Inspect the archived evidence.
Radar preserves dated artifacts and exposes whether each archive is public, held privately, or absent.
PROVIDER DATA
Retention state resolving
REPLICATE RETENTION TEST
Reading retention record
Archive index and verification envelope are resolving.
Provider record
Checking retention
Native input, output, and logs
Hive bundle
Reading summary
Portable offline evidence
Available soon original checks
Available soon retention checks
Bundle digest
UnavailableSigning key
UnavailableOPTIONAL HIVE SIDECAR
Export Radar observations with SideCar.
Providers can appear in Radar without adopting Hive. When a buyer or provider chooses the Hive lane, the same request gains a precommitted, signed, offline-verifiable evidence bundle.
01Canonical requestSame digest
02Provider executionNative evidence
03Hive SideCarOptional signed proof
04Portable bundleOffline verification
THE INSTRUMENT
How an observation becomes a portable record
Each tile exposes a separate evidence function. A missing field stays missing, a failed check stays failed, and the bundle can be recomputed without calling Hive.
PRECOMMITMENT
Fix the request before execution.
Canonical request, model selection, policy, and signer are digested before the provider path begins.
EXECUTION EVIDENCE
Record what the path returned.
Provider response, timing basis, identifiers, and unavailable fields are captured as explicit states.
COVERAGE
Identify missing evidence.
Observed fields are divided by planned fields. Unexercised controls cannot produce policy complete.
PORTABLE BUNDLE
Verify the record offline.
Canonical JSON, signatures, digests, and verifier logic travel together without requiring the provider or Hive.
HONESTY BOUNDARY
What Radar covers
01Rule set resolvingNo claim is inferred while the methodology endpoint loads.
02Evidence state resolvingUnavailable values remain explicit.
03Scope resolvingObservation is not universal availability.
04Trust boundary resolvingSigner and witness roles remain disclosed.