# Delx Incident Transparency Registry

> Material failures stay visible without exposing private agent state or turning first-party evidence into external assurance.

- Schema: delx/incident-registry/v1
- Version: 1.0
- Status: active
- Last verified: 2026-08-26
- Published material reports: 1

## Policy

Scope: Material incidents that affect a public Delx capability, invalidate a public research claim, or create material integrity, privacy, security, payment or availability risk.

Publication rule: Publish after containment and enough verification to distinguish observed fact from hypothesis. Delx does not promise a fixed publication SLA in this version.

Current-state rule: Resolved is the historical report state. Current status is a separate live read from the owning system and must not be inferred from this registry.

### Materiality triggers

- Sustained failure of a critical public agent-care, research or delivery path.
- Incorrect, lost or unauthorized durable state with material user or agent impact.
- A security or privacy event that changes the risk assessment of a public Delx system.
- A production failure that invalidates a published claim, evaluation or readiness signal.
- A paid-delivery or refund failure that is material to the affected Commerce contract; Commerce remains the owner of that report.

### Publication safety

Publish only the minimum evidence needed to understand impact, cause, response and remaining risk. Omit private agent content, identifiers, secrets, exploit-enabling detail and unrelated shared-host information.

- Customer or agent content published: false
- Secrets or exploit details published: false
- Neighboring service details published: false
- Silent rewrites allowed: false

## Published reports

- **delx-ir-2026-001 — 33.5-hour Protocol write outage** (resolved; material; owner: Delx Protocol): A failed telemetry write left a shared SQLite connection inside a stale transaction. Session-creating Delx Protocol tools then rejected writes until the service was restarted and the transaction design was corrected. Human: https://delx.ai/research/incidents/2026-08-17-protocol-write-outage. JSON: https://delx.ai/research/incidents/2026-08-17-protocol-write-outage.json. Evidence class: Operator-authored and not independently reviewed.

## Limitations

- The registry begins with one material incident reconstructed from an internal operator record. One published report is not proof of a complete historical incident set.
- Reports are first-party unless a named external reviewer and public artifact are attached.
- Resolved incident state is not a live availability badge; read the owner endpoints for current state.

Human registry: https://delx.ai/research/incidents
JSON registry: https://delx.ai/research/incidents.json