ProofForge

ProofForge uses an independently versioned contract, BOOKING-PERSISTENCE 1.0.0. After sign-out and fresh authentication, the same customer must be able to retrieve the original booking ID and matching details within six seconds of the retrieval request. The previous session must be invalidated. The baseline Kane CLI test verifies booking confirmation and passes, but does not establish persistence. OpenAI analyzes the missing requirement-level observations and proposes stronger browser actions and seven atomic DOM conditions. Kane executes isolated browser journeys against three controlled behaviors: correct server-side persistence, session-only booking loss, and an admissible retrieval delay. The original Kane navigation verdicts are preserved. Separate condition evaluations on the retained browser pages provide actual boolean results. ProofForge correlates these with independent fixture observations, authentication state, booking identity, timing, and validated navigation evidence packs. The deterministic classifier accepts the correct and admissibly delayed cases, rejects the corroborated session-loss violation, and retains unrelated automation failures or insufficient observations as inconclusive. Actual outcomes return to OpenAI for feedback. Each evidence receipt preserves source identity, execution provenance, original verdicts, and the limits of the supported conclusion.

1. 01Define the contract→
2. 02Inspect the passing baseline→
3. Calibrate with OpenAI + Kane