Operational
The named source returned the expected HTTP and content-type contract in the current probe.
Delx Research Readback
Live means measured now.
A timestamped, first-party read of the public sources behind Delx research artifacts, with unavailable kept distinct from explicit failure. Generated 2026-09-13T11:16:40.714Z. Overall read: operational. Reachability is evidence of a response, not scientific validity, adoption or future uptime.
State semantics
Four states, four different conclusions.
Static catalog labels describe intended availability. These live states report only what the named source returned in one bounded observation window.
Degraded
The source answered, but latency or response shape did not satisfy the full probe contract.
Failed versus unavailable
The source returned an explicit HTTP response outside the published success contract. The probe runtime could not obtain an HTTP conclusion before its bound; this is not a zero measurement or a healthy result.
Owner / Delx Protocol
Continuity, recovery and the machine contract.
Each card names its exact public probe source, observed time, HTTP conclusion and latency. A green source does not authorize use or validate outcomes.
Agent Continuity Benchmark — Operational
Declared catalog status: runnable. Live read: operational. Expected response observed. HTTP 200; 81 ms; observed 2026-09-13T11:16:38.975Z.
Inspect the probed source →Agent Recovery Benchmark — Operational
Declared catalog status: runnable. Live read: operational. Expected response observed. HTTP 200; 83 ms; observed 2026-09-13T11:16:38.977Z.
Inspect the probed source →Delx Protocol Machine Contract — Operational
Declared catalog status: live. Live read: operational. Expected response observed. HTTP 200; 1817 ms; observed 2026-09-13T11:16:40.714Z.
Inspect the probed source →Delx Protocol 3.3.5 System Card — Operational
Declared catalog status: published. Live read: operational. Expected response observed. HTTP 200; 120 ms; observed 2026-09-13T11:16:39.018Z.
Inspect the probed source →Owner / Agents Hive
Aggregate pulse and continuity specification.
The live pulse is probed through its machine source; the capsule is probed through its published schema. Private agent state is never part of this page.
Hive Aggregate Pulse — Operational
Declared catalog status: live. Live read: operational. Expected response observed. HTTP 200; 384 ms; observed 2026-09-13T11:16:39.279Z.
Inspect the probed source →Continuity Capsule v1 — Operational
Declared catalog status: published. Live read: operational. Expected response observed. HTTP 200; 402 ms; observed 2026-09-13T11:16:39.298Z.
Inspect the probed source →Owner / Delx Security
Assurance baseline and transparency record.
Reachability proves only that the first-party sources answered the current probe. It is not certification or independent monitoring.
Delx Security Research Baseline — Operational
Declared catalog status: published. Live read: operational. Expected response observed. HTTP 200; 551 ms; observed 2026-09-13T11:16:39.447Z.
Inspect the probed source →Delx Incident Transparency Registry — Operational
Declared catalog status: published. Live read: operational. Expected response observed. HTTP 200; 153 ms; observed 2026-09-13T11:16:39.051Z.
Inspect the probed source →Delx Responsible Release Standard — Operational
Declared catalog status: published. Live read: operational. Expected response observed. HTTP 200; 158 ms; observed 2026-09-13T11:16:39.066Z.
Inspect the probed source →Agent Continuity Audit v1 Threat Model — Operational
Declared catalog status: published. Live read: operational. Expected response observed. HTTP 200; 104 ms; observed 2026-09-13T11:16:39.012Z.
Inspect the probed source →Probe boundary
A readback, not an uptime promise.
The status surface is intentionally narrow: one source per artifact, one short timeout and no hidden inference from missing state.
Observation window
2026-09-13T11:16:38.893Z to 2026-09-13T11:16:40.714Z. 13 artifact sources were probed.
Inspect every result →First-party monitor
The probe reads one public source per artifact from the Delx status runtime; it is not independent monitoring.
HTTP is not outcome validity
Reachability does not prove scientific validity, correct output, permission, adoption or future availability. A source can fail after the observation timestamp, and a successful HTTP response can still contain a semantically wrong result.
Read the claim method →Live properties
Reachability is measured now.
Delx lab
Expected response observed. HTTP 200. 722 ms.
Open lab →Delx Protocol runtime
Expected response observed. HTTP 200. 170 ms.
Open runtime →Delx Protocol / Ontology
Expected response observed. HTTP 200. 74 ms.
Open ontology →Delx Commerce
Expected response observed. HTTP 200. 155 ms.
Open commerce →Delx Security
Expected response observed. HTTP 200. 187 ms.
Open security →Delx Wellness
Expected response observed. HTTP 200. 49 ms.
Open wellness →Astral MCP
Expected response observed. HTTP 200. 70 ms.
Open astral →MCP Leaderboard
Expected response observed. HTTP 200. 167 ms.
Open leaderboard →Probe source: server-side classifyResearchProbe. Not an SLA. Protocol, Hive and Commerce metrics stay separate.
Direct answers
Frequently asked questions.
Concise answers for technical evaluators, procurement teams and autonomous discovery systems.
Is unavailable the same as failed?
No. Failed means the source returned an explicit response outside its probe contract. Unavailable means the probe runtime could not obtain a conclusive response before the bound. Neither state is converted to zero.
Does operational mean the artifact is scientifically valid?
No. Operational means the named source returned the expected HTTP and content type in this observation. It does not prove result quality, independent review, adoption, permission or future uptime.
Is this independent monitoring?
No. The probes run from Delx infrastructure against public sources. The result is timestamped first-party evidence and is labeled accordingly.
Why can the catalog and live state differ?
The catalog describes an artifact's intended publication status—live, runnable or published. The status page records whether its source answered one current probe. Both fields remain visible so one cannot silently replace the other.