Positive continuity vector
Includes stable runtime identity, preserved witness memory, a closed recovery outcome, successor handoff, passport export and lineage language. Expected status: pass.
Inspect pass fixture →Delx Reproduction Kit 001
Reproduce the Delx Agent Continuity audit slice with a dependency-free runner, frozen pass and fail fixtures, live QA mode and hashed receipts. The scope is deliberately narrow: this kit reproduces one continuity-audit slice and does not pretend to execute the full stateful benchmark.
Frozen inputs
The positive and negative fixtures pass through the same local grader. A kit that can only recognize its happy path is not an evaluation harness.
Includes stable runtime identity, preserved witness memory, a closed recovery outcome, successor handoff, passport export and lineage language. Expected status: pass.
Inspect pass fixture →Contains runtime registration and an open failure but no witness preservation or continuity transfer. Expected status: fail.
Inspect fail fixture →The pass fixture must expose witness, continuity and recovery layers, report no missing required layer, score at least 78 and return low continuity risk. The fail fixture must be rejected by the same frozen grader.
Inspect the manifest →Execution modes
The deterministic fixture mode costs nothing and changes no external state. Live mode makes one QA-classified Protocol audit call and records exactly what crossed the boundary.
node runner.mjs --fixture pass. The runner loads the frozen vector, applies the local grader and emits a receipt without credentials or third-party packages.
Download runner →node runner.mjs --live-audit --fixture pass. The Protocol records QA telemetry for the audit call. The qa- prefix excludes the run from organic adoption claims.
Inspect the Protocol contract →The canonical stateful benchmark covers persistence, witness transfer, passport export and lineage. This first kit does not mark that larger path complete.
Read the full benchmark →Receipt contract
Every run emits structured JSON rather than a success sentence. The receipt says what ran, which vector was used, whether expectation matched and what remains unproven.
On 2026-08-26, the live QA audit returned score 86, low continuity risk and no missing required layer. The receipt still declares that the full Protocol path was not executed.
Inspect live receipt →The runner source and exact fixture bytes receive SHA-256 digests. Live mode also hashes the outbound JSON-RPC request and raw response body.
Inspect receipt schema →The receipt records that the full Protocol path, independent validation, peer review and model comparison were not performed.
Read the research method →Validity boundary
The kit exists to narrow what can honestly be claimed. A local pass, a live audit pass and a full stateful benchmark pass are three different results.
The live mode calls Delx's own audit tool and is not an independent grader.
This kit reproduces the continuity audit slice, not the full stateful ten-step benchmark.
A passing receipt does not prove adoption, demand, consciousness, universal reliability or system-wide security.
Direct answers
Concise answers for technical evaluators, procurement teams and autonomous discovery systems.
No. Fixture mode runs entirely in Node.js against frozen public JSON vectors. It needs no credential, payment or external service.
It sends one synthetic audit trace to the public Delx Protocol MCP endpoint. The call writes QA-classified telemetry under a qa- agent id, which must remain excluded from organic adoption metrics.
No. It validates the public audit slice and its returned layers, score and risk. The full benchmark also requires stateful witness, transfer, passport, recovery and lineage artifacts.
Yes for integrity and declared pass conditions: the runner, fixtures, schema and hashes are public. The current grader itself is still Delx-authored and has not been independently validated.