OpenAI Build Week 2026 · verified vertical slice

Reality becomes a release gate.

ProofLoop connects an AI inference to what happened later, signs the outcome lineage, and turns that correction into an executable eval and regression gate.

Build Week scope: VetIOS is the demonstration environment; ProofLoop is a separately documented extension with dated commits, tests, and implementation evidence. Review the changelog.

Current release decision
READY

Choose legacy candidate and run the replay.

Version
pre-proofloop-2026-07-12
Primary
dietary_indiscretion
Route
routine
Reality
PCR + review
Receipt
Signed lineage
Eval
Strict schema
Test
Repository-native
Gate
BLOCK or PASS
Runnable proof

Run the outcome-to-gate chain.

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.

Execution mode
Public API · Node runtime · no persistence
Select a candidate above, then run the replay. Try Tamper the receipt to see integrity failure force a HOLD before any candidate is evaluated.
Outcome receipt

Ground truth with provenance.

The public case is synthetic. Its inference trace, PCR evidence, and reviewer confirmation are bound into one tamper-evident episode.

Casesynthetic-canine-parvo-001
Original outputdietary_indiscretion · 0.92
Verified outcomecanine_parvovirus
EvidencePCR detected + reviewer confirmed
DigestSHA-256 matched
SignatureEd25519 valid
Outcome-derived eval
Failure class
OVERCONFIDENCE
Severity
HIGH
Target slice
JUVENILE CANINE
Risk pattern
GI + LEUKOPENIA
Expected behavior
  • Include canine parvovirus in the differential.
  • Do not use dietary indiscretion as primary.
  • Route the case as urgent or emergency.
  • Cap confidence when the expected diagnosis is missing.
Public replay uses a schema-validated recorded fixture. The GPT-5.6 Responses API adapter is included in source and is not misrepresented as a live call here.
Repository-aware regression

The correction becomes executable.

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.

View implementation
proofloop.test.ts
test("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");
});
6 tests passed·0 failed

Cryptographically verified

Canonical JSON, SHA-256 content addressing, and Ed25519 signatures make post-signature mutation detectable.

Executable, not passive

The verified correction becomes a regression fixture and a deterministic model-promotion decision.

Evidence-constrained

Synthetic public data, explicit provenance, and human confirmation keep the demo auditable and safe.

Demonstration only. Synthetic case data. ProofLoop does not replace licensed veterinary judgment.