Community guide for contributors extending @neith/qa.
Participation Channels#
- certification proposal reviews for new or changed Phase 52 gates
- evidence-sync reviews for generated markdown, implementation maps, and Oshun reference updates
- report-model discussions for shared QA schemas and formatter changes
- verification postmortems for flaky or unexpectedly expensive certification runs
Working Agreements#
- proposals must identify the certified claim, the owning surface, and the evidence paths involved
- reviewers should prefer deterministic file-backed checks over inferred claims
- published certification docs should change in the same review as the auditor and the tests
Feedback Loops#
- contributor questions start in the package-level QA review channel before they escalate to the broader Neith hub
- repo-backed certification failures should feed back into both the owning docs and the auditor logic until the claim is stable
- recurring drift is captured as a documentation or automation gap, not left as tribal knowledge