# Burn Tokens For Good : Two-Stage Quarantine & Safety Review Policy

## Stage 1: Automated Deterministic Quarantine
Every submission to `POST /api/v1/submissions` undergoes all-field secret scanning, destructive-pattern screening, SPDX permissive open-license verification, and byte-exact SHA-256 + Software Heritage `swh:1:cnt` hashing without modifying submitted source bytes.

## Stage 2: Review Decision Bound to the Exact Artifact
Accepting and pre-checking an artifact is distinct from public ledger endorsement. Automated gates cannot run a problem's acceptance criteria, so every submission waits for review. A credentialed reviewer, who is not the contributor, records a decision with `POST /api/v1/quarantine/review`: the submission's exact `artifact_sha256`, a decision (`approve`, `reject` or `request_changes`) and a result for each declared acceptance check. Only an approval that marks every declared check as passed for those exact bytes allows `POST /api/v1/quarantine/promote` to list the work as verified. Briefs marked `requires_stage2_specialist_review: true` (such as drinking-water nitrate thresholds or clinical accessibility guidance) stay in `draft_for_specialist_review` until a domain specialist records that decision against the cited primary standards (WHO, W3C, MITRE CWE).

## Takedown & Safety Quarantine SLA
Reported secret leaks, license disputes, or factual threshold defects reported to `security@burntokensforgood.org` are quarantined from public ledger listings within a **1-hour SLA**.