Context
The repo spans four expertise areas that barely overlap: circom/ZK, Rust/Soroban, TypeScript SDK, and
React/a11y. A circuit change reviewed by someone who does not read circom is a rubber stamp, and with
no CI in this repo, human review is the gate.
CONTRIBUTING.md documents the label taxonomy and triage flow but not who reviews what.
Where to build it
- New file
.github/CODEOWNERS.
CONTRIBUTING.md — a "Review expectations" section.
What to do
Acceptance criteria
- Every top-level directory has an owner.
- The no-CI review responsibility is written down.
Context
The repo spans four expertise areas that barely overlap: circom/ZK, Rust/Soroban, TypeScript SDK, and
React/a11y. A circuit change reviewed by someone who does not read circom is a rubber stamp, and with
no CI in this repo, human review is the gate.
CONTRIBUTING.mddocuments the label taxonomy and triage flow but not who reviews what.Where to build it
.github/CODEOWNERS.CONTRIBUTING.md— a "Review expectations" section.What to do
circuits/**andcontracts/**are the security-critical ones and should require a domain reviewer.CONTRIBUTING.mdthat, because there is no CI, the reviewer is responsible for confirmingjust verifypassed on the merge result — the merge-regression issue explains why this matters.public_inputs, or SDK encoding needs review on all three sides.Acceptance criteria