COUNTERFACTUAL RELEASE LAB

AI decides what to challenge.
Evidence decides whether to ship.

A passing build can hide an expired session. GitLab Duo selects the failure worlds. A pinned deterministic verifier tests the candidate and preserves the reason it fails.

5 registered failure worlds2 actual Duo acceptance runsNo sign-in required

What you can verify here

Inspect authentic recorded GitLab results and run receipt-integrity checks in your browser. This static site does not invoke Duo, execute repository tests, run the Waylatch backend, or demonstrate a complete hands-off backend release. Both recorded release decisions remain releaseAllowed: false / NOT_DEPLOYED.

Open the live Counterfactual verifier ↗. Run the registered verifier against a bundled safe candidate and an isolated expiry regression, inspect actual test results and download the receipt. Fresh runs use deterministic planning; historical Duo selections remain separate. WayLatch is the application under test, not the lab interface. Free hosting may wake slowly. No run grants production deployment authority or changes either recorded release decision.

THE DISTINCTIVE CONTRIBUTION

Challenge assumptions. Keep the proof.

01 / ChooseDuo selects worlds
Registered identifiers and reasons. Empty model toolsets; no model-supplied commands.
02 / ExecuteFixed tests decide
An immutable reviewed verifier runs behavioral assertions and binds revision, source, plan and report.
03 / PreserveFailure survives
The unsafe session-expiry finding remains visible even when finalization also fails.
04 / InspectFollow the evidence
Original GitLab notes, candidate revisions, jobs and source remain linked below.

TRY THE EVIDENCE

One safe candidate. One real regression.

These are the actual v2.1.0 runs from 20 October 2026, not new executions.

SAFE / RECORDED

Evidence freshness survives

A documentation candidate passes the selected deterministic world. This verifies scenarios; it does not approve release.

e35b2bc5 · Duo 9739808

UNSAFE / NEVER MERGE

Expired authority is rejected

Removing the session-expiry predicate lets stale credentials authenticate. Real assertions catch the regression.

241d34db · Duo 9739811

Loading published receipt excerpts…

HONEST SCOPE

A public window into real engineering.

The verified engine covers offline persistence, QR loss and replay, coordinator-session expiry, interrupted provider doubles, and stale evidence. Clocks, IndexedDB and providers are simulated in those engine scenarios.

Recorded Duo acceptance demonstrates selection → deterministic verification → audit publication. This site adds anonymous evidence access and local integrity checks. Persistent backend hosting and a complete code-to-production loop remain open gates.

Inspect the implementation

Public MIT source ↗Acceptance ledger ↗Effective permission limits ↗Reviewed baseline CI: 234 Node + 6 Python tests ↗Imported MIT Waylatch foundation ↗