# scp_classification ## Purpose It measures the containment difficulty of a SCP. An exceptionally lethal anomaly can be classified as Safe if it remains idle when left alone. While a completely harmless anomaly can be classified as Keter if it is impossible to physically secure. --- ## Classic SCP classes ### Safe * Pose predictable or easily managed containment difficulties. * These SCPs can be reliably locked in a box without risk of escape. ### Euclid * Pose unpredictable or poorly understood containment difficulties. * These SCPs require active monitoring and complex procedures, often because they are alive or sentient. ### Keter * Pose extreme containment difficulties. * These SCPs are actively hostile to containment, exceptionally complex, or impossible to fully secure with current technology. --- ## Non-classic SCP classes ### Neutralized * Pose no further anomalous risk. * These SCPs have been destroyed, killed, or have permanently lost their anomalous properties. ### Pending * These SCPs are undergoing initial evaluation. ### Thaumiel * These SCPs are actively used to contain, counteract, or manage other highly dangerous anomalies. ### Apollyon * These SCPs are completely impossible to contain. * They are actively expected to breach all barriers and trigger an unavoidable "end-of-the-world" scenario. --- ## Note on Non-Classic Classes *While non-classic classes exist in the database (ENUM), they are excluded from standard documentation entries to prevent classification conflicts.* *Because certain anomalies possess dual traits, such as an uncontainable entity (Keter) that also functions as a containment tool (Thaumiel), combining utility and containment status into a single primary class can lead to vague data. To maintain strict data integrity, active entries are limited exclusively to the classic Safe/Euclid/Keter framework, which focuses solely on containment difficulty. Non-classic classes remain supported in the schema for potential future sub-classification or external scalability.*