Prototype August 2026
Reproducing a research result with a separate implementation
This EvidentRelay prototype study tested a research handoff using a controlled computation. The work examined how a recipient could verify the plan, execution history, result, and supporting evidence.
The question
Could a recipient check the committed plan, trace the recorded execution, and reproduce the result using a separate implementation?
Connect the committed plan to the recorded run and acceptance decision, preserve failed attempts, and make the shipped evidence checkable outside the original working directory.
See the resultMethod
Define the test. Preserve the evidence.
The pilot signed and timestamped a frozen commitment before the recorded run, retained a planned guard-failure attempt and the one permitted retry, and checked the successful result with a separate Go implementation. The package connected the plan, execution records, claims, evidence, and acceptance decision.
What the work produced
A preserved research package with a timestamped commitment, execution history, reproduction result, evidence-linked claims, and a documented recipient-policy decision.
Tools used Go · RFC 3161 timestamps · SHA-256 · Signed evidence packages
Result
Evidence for the next decision.
The recorded Go reproduction matched the result under the specified equivalence rule. All 11 obligations were resolved. The final package recorded 24 of 24 mutation/regression checks and 17 of 17 clean-extraction checks passing, with disposition ACCEPT under the pilot’s recipient policy.
Decision: Accept this handoff under its defined evidence and reproduction requirements. Failed earlier lineages remain preserved and excluded from that conclusion.
Evaluation
How the result was checked.
The separate Go implementation checked the result against the specified equivalence rule. Mutation tests checked whether altered or incomplete evidence triggered the expected responses. A clean-extraction qualification checked the shipped package outside the original working directory.
Review the evidence checks
- The August 13, 2026 pilot records supply the commitment, execution history, Go equivalence result, test counts, and recipient-policy decision.
- A September 5 evidence review verified the frozen archive’s recorded identity and integrity, all five final-manifest files, and all 814 declared package files both on disk and in the archive.
- This review checked the preserved package and recorded qualifications. It did not repeat the experiment, rerun the Go reproduction, or obtain a new timestamp.
Scope
Where these findings apply.
- This was a controlled computational pilot, not customer past performance.
- A timestamp binds particular bytes to an existence time; it does not establish scientific truth.
- A separate implementation is not the same as independent institutional validation. The result does not establish general product certification or production readiness.