# Corrections

Public log of records corrected, retracted, disputed, superseded, or repealed on the DEPLOY registry. Append-only: corrections are recorded as new status events on the record, never as silent edits. The full history of each record is preserved.

## Journal

- **2026-07-12 · Retracted · incident** [Knightscope K5 security robot slipped down steps into a fountain at Washington Harbour, DC (2017)](/incidents/knightscope-k5-dc-fountain-2017.md)
  - Reason: Duplicate of knightscope-k5-georgetown-fountain-2017, the canonical record (linked to the knightscope-k5 model, primary-sourced, reviewed). This orphan (unlinked, unreviewed) is retracted to suppress it from aggregates; its own URL remains index,follow per the retraction policy.
- **2026-07-12 · Retracted · incident** [Knightscope K5 security robot knocked down and ran over a toddler at Stanford Shopping Center (2016)](/incidents/knightscope-k5-stanford-toddler-2016.md)
  - Reason: Duplicate of knightscope-k5-stanford-shopping-center-2016, the canonical record (linked to the knightscope-k5 model, primary-sourced, reviewed). This orphan (unlinked, unreviewed) is retracted to suppress it from aggregates; its own URL remains index,follow per the retraction policy.
- **2026-05-31 · Repealed · regulation** [EEOC AI-in-employment guidance (United States)](/regulations/eeoc-ai-employment-guidance.md)
  - Reason: Out of registry scope. EEOC AI-in-employment guidance applies primarily to non-physical AI (hiring algorithms, evaluation systems, employment selection tools), only tangentially connected to physical AI through humanoid workplace deployments. Registry scope is physical AI (robots operating in the physical world). Filed in error; suppressed from aggregate views per constitutional seam #4 while canonical URL preserves the correction.
  - Source of correction: editor:phase-4b-scope-cleanup

## Report an error

Found a record that is wrong, out of date, or missing a source? Email corrections@deploy.report.

Corrections require supporting documentation: official records, primary sources, or verifiable links. Submissions are reviewed against the same source-quality tier rubric that applies to every record on file. We correct the record by appending a new status event, not by silent edit. The original record state stays in the history for audit.

For the full editorial discipline behind corrections, see [the methodology](/methodology.md) and [editorial process](/editorial-process.md).

_Canonical URL: /corrections. JSON-LD and HTML version: [/corrections](/corrections)._