Every independent run is filed as a GitHub issue, logged on receipt, and verified mechanically — chain integrity and claim coverage, on our machine and reproducible on yours. The ledger below is the append-only record — zeros included.
Do not have the project team write your prompts or referee mid-run. Independence is the whole point.
Prefer confidentiality for the raw run? Email artifacts to lati@clista.ai — they still must verify mechanically to be listed.
On a real, hard-to-reverse decision you own — using whatever agents or humans you already use. The fastest path is the single-prompt sealed run: one paste into your own agent, a reference run lives in the repo under packages/protocol/runs/.
LEDGER.md, failures.md, cost.md — including human-minutes of format overhead — and outcome.md if the decision has been executed.
Open the External run report issue template. It pre-applies the external-run label and asks for the applicability check, run details, and artifacts.
The maintainer logs receipt, re-runs chain verification and the claim-coverage check, and records the outcome here — pass, fail, or abandoned, each with what it showed.
| Run | Origin | Submitted | State | Outcome |
|---|---|---|---|---|
|
0 external runs received
This is reported honestly, including zeros. Failed and abandoned runs are wanted evidence — they belong here too. |
||||
Updated on receipt · counts mirror the external-run issues on GitHub.
The EXTERNAL-RUNS gate was retired 2026-06-19 — runs here are independent evidence,
not progress toward a pre-commitment.
