Correction review queue
Static moderator workflow for future `/api/corrections` submissions. The production Worker stores records in KV; this page defines how those records move from intake to signed-off content changes.
Queue states
| State | Owner | Action |
|---|---|---|
| New | Operator | Open the KV record, confirm the page and record fields, and reject obvious spam. |
| Needs evidence | Operator | Request or find owner’s-manual/OEM evidence before any content change. |
| Ready for reviewer | Reviewer | Compare the proposed correction against the cited source and sign off or reject. |
| Applied | Editor | Patch content/data, run the local release gate, and append the sign-off log. |
Record shape
- KV key
-
corrections/YYYY-MM-DD/{uuid}.json - Required fields
-
page, record, correction, source, createdAt - Reviewer evidence
-
manual page, OEM page, service bulletin, or source note - Closeout
-
content patch, verification command, reviewer decision, date