15 Verification Gates Reference
The deterministic policy reference for all 15 gates used in claim validation. Generated directly from the engine source of truth.
QUICK GUIDE
Purpose
What this is The deterministic policy reference for all 15 gates used in claim validation.
Best for
Understanding why a submission passed or failed
Read time
1 min
Next action
Find the failed gate, fix the issue, then resubmit
What this is
The deterministic policy reference for all 15 gates used in claim validation. Every gate page below is generated directly from lib/gates.ts and pinned to lib/policy.ts::GATE_DEFS at module load. If a gate is added, removed, or renamed in the engine, it updates here automatically.
How gate execution works
- Blocking gates: the first failure stops progression and the claim is rejected. Users see the specific failed gate and a remediation message.
- Non-blocking gates: (currently only
gascoin_min_hold, which is bypassed during Season 1 dry-run) do not reject the claim on failure. - Treasury solvency is NOT a policy gate — it is a pre-payout check performed by the payout worker, not the policy engine. If the treasury is low, approved claims queue until replenished. See the Payout Worker section in Technology for details.
How to use this page
- Identify the first failed gate in the Wallet Tracker
- Open the gate's section below by name (Ctrl+F the gate name or scroll chapter III)
- Apply the remediation for that specific gate only
- Resubmit with fresh inputs when required
Operator note
Gate policy is deterministic at runtime. Gate overrides by admins are exceptional and auditable — see the Admin & Anti-Fraud chapter.