Release and quality evidence

A green build proves compilation, not security. VENTEX separates static checks, automated tests, integration evidence, browser walkthroughs and operational recovery.

The state re-run on 9 September 2026 maps 308 conformance rows to documented counter-tests and covers 19 real-browser runs with 189 checks. The server-side migration rehearsal checks pending migrations in a disposable clone of the running data without transferring user data off the host; a check that cannot execute remains open rather than passed.

• Formatting, type checks and lint
• Unit and contract tests
• Database and realtime integration
• Visible multi-device walkthrough
• Backup restore and rollback

Every release should connect source state, artifact digest, migrations, configuration, check results and known boundaries. Only then can an operator later prove what actually ran.

release-id
source-revision
container-digest
migration-state
security-gates
known-limitations
rollback-target

Internal tests are necessary but not independent. Before high-security or government claims, the minimum is an architecture review, penetration test and cryptography audit with an explicit scope.