DRIFTZERO GitHub

The run

One packing procedure changed one requirement: label_position: LEFT → TOP_RIGHT. This is what happened.

Every screenshot and every number below is recorded evidence from a real run against real Google Cloud, with real photographs and real Gemma inference. It is not a live interaction, and this page does not call any model.

What the photographs looked like

A box with the shipping label on the left
Photo 1 — label still LEFTThe work had not changed yet. This one failed.
The same box with the label corrected to the top right
Photo 2 — label TOP_RIGHTThe worker corrected the physical work. This one passed.

The verification chronology

Both attempts are kept. A change that took two tries is a different operational fact from one that passed immediately.

#ExpectedObserved by GemmaTruth Engine verdict
1TOP_RIGHTLEFTFAIL
2TOP_RIGHTTOP_RIGHTPASS

The model reported a position. The verdict is arithmetic performed by deterministic code against the value recorded at remediation time — DRIFTZERO TRUTH ENGINE deterministic comparator.

The model calls, as recorded

OutputModelLatencyTokens in / out
LEFTgoogle/gemma-4-26b-a4b-it-maas5.918 s341 / 2
TOP_RIGHTgoogle/gemma-4-26b-a4b-it-maas5.272 s341 / 4

Two inferences, both on Vertex AI MaaS, serverless and on-demand. The model's entire contribution is a position from a closed set: LEFT, TOP_RIGHT or INCONCLUSIVE. Anything else is rejected.

What the worker and the auditor saw

The worker gets the delta
The worker gets the deltaNot a new manual. One line: the label was LEFT, it is now TOP_RIGHT.
The first photo fails
The first photo failsGemma observed LEFT. The Truth Engine compared it to the expected value and returned FAIL. No proof was generated.
The corrected photo passes
The corrected photo passesThe worker moved the label and photographed again. Gemma observed TOP_RIGHT; the Truth Engine returned PASS.
The Change Proof
The Change ProofSeven of seven completion conditions. Both attempts kept — the failure is part of the record.