First-Clean Verification
A founder or supervisor inspects the first few cleans per crew member before they solo. The process below describes who is allowed to inspect, how many cleans are required, and what happens on a passed, failed, or conditional result. Every sign-off is recorded as a row in the QA Inspection log — see the QA history for an auditor’s view.
Required count: 2 first-clean sign-offs per crew member before solo release.
When firstCleansPassed reaches firstCleansRequired (2), the crew member is solo-cleared and the inspection counter stops. The QaInspection history page surfaces this so an auditor can review it at any time. Future installs of dashboard-shell + better-auth can harden this by gating the inspection form to an authenticated supervisor, but the current lightweight posture treats inspector identity as a recorded string.
On a FAILED result, the inspector logs the failed items in notes and SMSs the supervisor. The crew member performs the re-clean, then a fresh inspection is logged (this counts toward the same 2-cleans-required counter when it passes). A CONDITIONAL_PASS counts as PASSED for counter purposes only when the inspector logs the outstanding item — typically a host-fix rather than a crew re-clean.