Buyer acceptance
Verify one workflow. Prepare the buying decision.
Run technical proof and procurement preparation in parallel. Synthetic evaluation does not establish buyer authorship, institutional authority or customer-live operation.
Technical review
Five cases, a pinned scope and a reproducible report.
An authorized administrator signs in and explicitly creates the sample walkthrough. Review FINAL, NOT FINAL, CONFLICT, REOPEN and STOP. Check readiness and export the evidence package and scoped readiness report. Share the configuration digest through a separate trusted channel. Run the source verifier against that pin; retain the report package digest and software fingerprint.
Acceptance checks
Checks that still require authentic evidence.
Authenticated browser usability, customer-source permissions, buyer-authored challenge cases, receiving-environment recovery and buyer sign-off remain unverified. A login, source signature or local test does not establish independent acceptance. Report unresolved checks explicitly; no checkbox may override production admission.
Commercial preparation
Keep the decision owner, scope and delivery responsibilities explicit.
Prepare the supported workflow, acceptance criteria, data rights, security review, incident contact, delivery owner, recovery scope and evaluation agreement alongside proof. Contracts, institutional authority and funding require their real authorized decision-makers.
Operating limits
Preserve the production boundary.
The walkthrough uses synthetic records. Approved customer evaluation is scoped read-only work. Pilot remains blocked and high-assurance production remains HOLD. No model can issue approval or promote its own benchmark.