Click
Proof navigates screens, taps interactive elements, opens modals, and follows flows — catching broken routing, missing handlers, and silent JS errors.
Navigation verifiedProof drives the real product like a paying user would — click, submit, pay, reload, authorize, upload, verify. Every action is recorded. A screen that renders is not a screen that works.
“Done” in FlightDeck means Proof passed. Not that the feature was coded, not that it rendered in a browser, not that a developer manually tested it. Proof exercises seven categories of user behavior and records cryptographic evidence of each.
Proof navigates screens, taps interactive elements, opens modals, and follows flows — catching broken routing, missing handlers, and silent JS errors.
Navigation verifiedForms are filled with valid and invalid data. Server responses, validation messages, and state mutations are checked against the spec.
Forms verifiedStripe test mode charges run end-to-end. Proof confirms webhooks fire, receipts generate, and entitlements unlock — not just that the UI shows a success state.
Payment verifiedState is checked before and after a hard reload. Session data, UI state, and in-progress work must survive a refresh without data loss.
Persistence verifiedRBAC and row-level security rules are exercised by logging in as different roles. Proof confirms that restricted routes return 403, not a blank screen.
Access control verifiedFile uploads reach object storage, are retrievable by URL, and are accessible only by the authorized user. Receipts and exports are validated against expected schema.
Storage verifiedProof drives the real product like a user would, then records evidence for every action. A screen that renders is not a screen that works.
Every Proof failure caught before launch is a fix FlightDeck makes at no charge. FlightDeck’s billing rule is simple: AI mistakes cost us, not you. Only forward scope is billable. Proof is the mechanism that enforces this contract.
A checkout flow that renders but never fires a webhook. An admin route that returns 200 to any logged-in user. A receipt that shows a number but points to a deleted object. These ship because no automated system ran the money path.
Proof run #128 proves reservation #4821 was created, charged $40 via Stripe, persisted through a reload, blocked guest access, stored a receipt, and processed a refund. That evidence is in the audit log before you click publish.
Proof runs before every publish. If it doesn’t pass, FlightDeck fixes it. AI mistakes are never your bill.