Review submissions
Apply Mission rules consistently, protect Member privacy, and record an explainable decision.
Review the submission against the Mission policy that was visible when the Member started. Do not add private requirements afterward.
A reviewer should be able to see the relevant proof, policy version, automated signals, prior decision state, and any permitted Member note. Access should remain limited to people who need it.
Make one clear decision
- Approve when the published conditions are met.
- Reject with a reason tied to a specific condition.
- Hold when a safety or policy check must finish first.
- Request more only when the policy permits additional evidence.
Keep comments factual and respectful. Avoid guessing about a Member’s motive when the evidence only supports a narrower conclusion.
Review queues need ownership and timing expectations. If the team cannot keep up, reduce Mission capacity or simplify the policy rather than letting Members wait without explanation.
The testnet Beta includes the review queue, evidence viewer, and decision controls. Production accessibility and operating review remain release gates.