Your sign-off is a Slack thumbs-up, and six weeks later in an audit nobody can prove you gave it. ArcRelease records every QA gate as it happens — timestamped, attributed, exportable — so the evidence exists at the moment of the decision.
As a governance ceremony with a named owner and a timestamp, captured when you approve rather than reconstructed from chat later, and included in a one-click audit export as PDF or JSON.
My sign-off is a Slack thumbs-up. Six weeks later, in an audit, nobody can prove I ever gave it.
The evidence is screenshots pasted into a spreadsheet before every audit.
A release shipped past my gate and I only found out when it broke.
Every QA gate is captured with your name and a timestamp the moment you approve, and it exports as evidence an auditor accepts — no screenshot archaeology before the review.
If your gate is outstanding, it shows up as a cited reason in the Gaja preflight before the release ships, not after it breaks.
No. You keep testing as you do; ArcRelease records the sign-off ceremony around it so the evidence exists without extra work.
In the release ceremony trail, exportable per release as PDF or JSON, targeting 100% coverage captured at decision time.
Tell us about your release process. Connect your stack in ten minutes, run a Gaja preflight on a real release, and see the reasons behind the verdict.
Free plan · ten minute setup · we reply in one to two business days