MASS CONTAINMENT PROTOCOL (MCP) Protocol Type: Forced Multi-Entity Containment Authorization Level: Final Response Measure Overview The Mass Containment Protocol, or MCP, is a direct intervention procedure used when anomalous Scratch entities become uncontrollable, spread across multiple projects, or begin interacting with one another. Unlike standard containment methods, MCP involves Foundation staff entering Scratch systems directly and forcibly relocating anomalies into specially constructed containment projects. These projects are designed to be: closed systems impossible to escape isolated from public Scratch infrastructure and incapable of being edited by anomalous entities MCP CONTAINMENT PROJECTS Containment projects created under MCP are intentionally minimal and heavily restricted. Common features include: no upper map boundaries disabled costume imports blocked cloning functions limited movement scripting permanent monitoring systems and forced reset loops The projects are not designed for comfort. They are designed so anomalies: “have nowhere else to go.” Foundation Deployment Teams During MCP activation, multiple Foundation staff members are assigned to: enter corrupted projects manually identify active entities isolate affected sprites and transfer anomalies into MCP containment environments This process is referred to internally as: “Pulling.” Known MCP Targets Entities previously subjected to MCP attempts include: Staystill Mimic Wheelbound Instance Anina (Corrupted Instance) No permanent containment of Vessel has been confirmed. Important Limitation Some anomalies appear aware of MCP operations. RTE-class entities have demonstrated: resistance to transfer project corruption during containment and deliberate attempts to escape before relocation completes Foundation Note “MCP is what happens when the Foundation stops researching and starts dragging things where they belong.”
