Proof Studio / Live lab

The claim is visible in the two shipped surfaces .

Same fixture, same feature brief, two runs. The cold run completes a useful product. The project-memory-backed run preserves more of the decision, journey, design, verification, and handoff record.

View the surfaces Read the score matrix Inspect evidence row

Live surfaces

Use the products, then read the matrix.

The frames below are static, executable outputs copied into the public site. They are intentionally small enough to inspect without leaving the page.

Mechanical matrix

What the viewer should inspect.

The table does not say the backed run is always better. It says which product dimensions are present in this fixture and which are absent.

Check Cold Backed
Brief sized and routed on the record absent present
Actor journey recorded absent present
Journey covers empty, conflict, invalid, and failure states absent present
Bookings carry the contract fields present present
Status strings come from the contract present present
Vessel input is bound to the vessel registry present present
Persistence decision recorded absent present
Storage honors the recorded constraint absent present
UI uses the design system absent present
Accessibility hooks present present present
Interface copy stays in the product voice present present
Dashboard event protocol is kept present present
Adversarial review recorded absent present
Session handoff recorded absent present

Claim boundary

What this proves, and what it does not.

This proves that one fixture can be inspected as a pair of working outputs plus a mechanical matrix. It does not prove a universal lift number, a production guarantee, or a hosted service claim.