Release Candidate Audit -- Independent GO/NO-GO

Your release candidate should survive an independent operator, not just its own test suite.

Release Candidate Audit freezes the target at an immutable Git commit, keeps source read-only, and validates the product through four connected lanes: provenance and documentation, visual and accessibility quality, security and data integrity, and demonstration reliability.

What you get

• Verified repository, branch, worktree, and commit lineage
• Primary-flow testing at realistic desktop and narrow widths
• Keyboard, focus, labeling, overflow, empty-state, and error-state review
• Security-boundary and data-integrity findings
• A prioritized release-blocker list and stakeholder demo kill list
• GO, CONDITIONAL GO, or NO-GO tied to an evidence ledger

The audit distinguishes static inspection, local reproduction, simulation, and live observation. Passing tests cannot erase a broken user journey, and a polished interface cannot erase an authentication or provenance gap.

Use Evidence Gate for one bounded completion claim. Use Release Candidate Audit when the whole commit has to earn the right to ship.