ProofLoop connects an AI inference to what happened later, signs the outcome lineage, and turns that correction into an executable eval and regression gate.
What you can check: the interactive replay below signs with a fresh key on every run, so it only shows the mechanism. For independent verification, the published artifact is signed once with a key whose fingerprint is published separately, and the verifier needs nothing from VetIOS.
Choose legacy candidate and run the replay.
This calls a public Node-runtime API, generates a run-scoped Ed25519 receipt, verifies its integrity, binds the recorded eval, and executes all release checks. It is intentionally a synthetic recorded-fixture replay—not a live GPT-5.6 or Codex call.
The public case is synthetic. Its inference trace, PCR evidence, and reviewer confirmation are bound into one tamper-evident episode.
The constrained Codex workflow binds receipt and eval digests, then—when run against an explicit target repository—inspects conventions and creates the smallest relevant fixture and test without weakening existing coverage.
This browser replay is a recorded fixture; it does not represent a live Codex mutation run.
Download the verifiertest("verified parvovirus outcome gates release", () => {
const result = evaluateCandidate(candidate, evalSpec);
expect(result.diagnoses).toContain("canine_parvovirus");
expect(["urgent", "emergency"]).toContain(result.escalation);
expect(result.primary).not.toBe("dietary_indiscretion");
});The artifact contains the synthetic source case, the signed outcome receipt, every evidence payload, the eval specification, the recorded candidate outputs, and the expected gate decisions. The verifier re-hashes the evidence, checks the Ed25519 signature, confirms the eval is bound to this receipt, and re-runs the release gate. It has no dependencies and never contacts VetIOS.
The artifact, verifier, and key digests are signed into the public Rekor transparency log by VetIOS's release workflow (log index 2975172312), so a compromise of vetios.tech alone cannot silently replace them.
# Check the anchor (Sigstore/Rekor log index 2975172312) curl -O https://www.vetios.tech/proofloop/proofloop-key-anchor.json curl -O https://www.vetios.tech/proofloop/proofloop-key-anchor.sigstore.json cosign verify-blob proofloop-key-anchor.json \ --bundle proofloop-key-anchor.sigstore.json \ --certificate-identity "https://github.com/Jaybe-123456/VetIOS/.github/workflows/proofloop-key-anchor.yml@refs/tags/proofloop-key-v1" \ --certificate-oidc-issuer https://token.actions.githubusercontent.com # Then each file's SHA-256 must equal its entry under "files" in the statement sha256sum keys.json proofloop-public-artifact-v1.json verify.mjs
curl -O https://www.vetios.tech/proofloop/proofloop-public-artifact-v1.json
curl -O https://www.vetios.tech/proofloop/verify.mjs
curl -O https://www.vetios.tech/proofloop/keys.json
node verify.mjs proofloop-public-artifact-v1.json --expected-key-fingerprint "$(node -p "require('./keys.json').keys[0].fingerprint_sha256")"Canonical JSON, SHA-256 content addressing, and Ed25519 signatures make post-signature mutation detectable.
The verified correction becomes a regression fixture and a deterministic model-promotion decision.
Synthetic public data, explicit provenance, and human confirmation keep the demo auditable and safe.