I realize that there is approximately no chance in hell of this ever being adopted, but I've been kicking it around in my head for a while and I wanted to get it down somewhere.
The current system of object classes (Safe/Euclid/Keter) lacks both nuance and precision. I would prefer a two-axis system, as follows.
Containment Class
The containment class of an SCP object describes how difficult it is to contain.
Passive
Object passes the "locked room test". Examples: SCP-185, any given sample of SCP-008.
Active
Object requires ongoing intervention in order to maintain containment, but its properties are understood and reliable containment procedures are known. Examples: SCP-173, SCP-447.
Unstable
No reliable containment procedures are known, but object is currently in containment. Examples: SCP-354, SCP-682.
Uncontained
Object is currently not in containment. Examples: SCP-990, SCP-732.
Threat Class
The threat class of an SCP object describes the scope of the potential consequences if its containment is breached.
Local
Containment breach affects one or a few individuals, small objects, or a small area. Cleanup procedures are limited to containing or terminating affected individuals, isolating or neutralizing affected objects or areas, and administering amnesiacs to bystanders. Examples: SCP-342, SCP-173.
Broad
Containment breach affects many individuals or a large area, on the scale of a town or city. Cleanup procedures generally require extensive coverup. Examples: SCP-682, SCP-233.
Global
Containment breach affects the entire planet or species. In the event that the Foundation survives the breach, cleanup procedures consist of reclassification as SCP-EX. Examples: SCP-123, SCP-435.
Existential
Containment breach affects a significant portion of the future light cone, the universe, continuity, or existence. Cleanup procedures are generally impossible. Examples: SCP-196, SCP-185.
Note: Further examples available as document SB-T8E6 Analysis.
I want to have a way to refer uniquely to things still in draft stage. The identifier should be short and probably-unique, without requiring sitewide coordination. I believe that a random 4-character alphanumeric string should work for this purpose. The mandatory SB- prefix stands for SandBox, and indicates unambiguously that the indicated material is of draft status.
Including usernames would have also worked, but "Draft-Lireci-003" sounded weirdly egocentric.
SB-01W2-001
Something that only happens in broad daylight, because Darkness = Scary is overdone. SCP-272 doesn't quite count because of the strong reliance on Shadow.
SB-01W2-002
Something infectious that has an incubation(?) period during which subject is contagious but displays no symptoms.
SB-01W2-003
EX: Ice-9 style miswater; previously, water didn't freeze. Containment breach resulted in completely wiping out Antarctic civilization.
SB-01W2-004
A simplistic carving or painting of an eye. Occasionally blinks.
- SB-01W2-004-b
Anything that implies it's watching you but doesn't otherwise interact. (At least, not something that eventually escalates into "and then it leaps out and kills you". Keep it on the level of unconsummated dread.)
SB-01W2-005
-J: SPC article detailing Standard Punching Conventions. Already been done.
SB-01W2-006
A contagious tattoo of a stylized eye. Every once in a while, the eye winks, and anyone who sees it gets their own tattoo. (Is this too similar to Palimpsest? I wasn't thinking of that when I came up with it, and it's a fairly obscure reference anyway. Probably fine.)
Now reclassified as SCP SB-RIQ3.
Document SB-BGWO The Sad Little Dragon
SCP SB-RIQ3





