GENESIS · Product update
GENESIS now checks browser behavior before applying changes
Velora Code adds real browser checks for buttons, forms, navigation and local API responses to its GENESIS Proof Engine workflow.
Check what the app does
A successful build does not establish that a button works or that a form produces the expected result. GENESIS can now run specified browser scenarios against a separate candidate copy before you approve changes.
Checks can fill fields, click buttons, select options, press keys, follow navigation, assert visible content and verify local HTTP responses. Each scenario must include an expected outcome.
Results become part of the proof
Step results, browser runtime errors and HTTP failures are included in the verification record. A failed check blocks approved apply. Existing source fingerprints and protected-path constraints remain in the workflow.
The results distinguish command-only verification from browser scenarios. Passing scenarios cover the specified outcomes; they do not certify every feature of an application.
Use it with your local workspace
Connect the Desktop Agent and open Agent → Task settings → Add browser behavior check. Set selectors and expected results for the actual project, review the proposed changes, then run the checks in Future + Proof.
Static HTML runs from the candidate copy. Local Next.js and Vite projects can use a candidate dev server after an explicit dependency-install check. This local engine requires the Desktop Agent and its installed testing browser; publishing the website alone does not run tests on a visitor’s computer.
Validation and current scope
The Windows installation verification completed with 19 passed tests, zero failures and one skipped test. The production build also completed. The browser checks exercise form submission, persistence and navigation, dummy-handler failure, runtime-error detection, candidate API assertions and proof-gated apply.
Scenarios currently need project-specific configuration. This release does not automatically generate every test or autonomously repair every failure. Tests use a fresh browser context, exclude production credentials and block external browser HTTP resources. It is a functional verification update, not a claim of AGI.