Big thank you to everyone who helped critique and mold this take. If I could remember you all I'd give full credits.
What even is clearance level omega? The highest clearance level is 5. We know this because that's what the 5 in O5 Council stands for
I'm guessing it's a nod to the (unaffiliated) game where there's an "Omega Keycard" I think?
Within the canon of the article, Omega clearance is given to the O-5's plus the senior staff of the Site itself.
Out of canon it's the exact reference Zyn mentioned.
I was under the impression that was just something SCP-914 made up on it's own to justify a "Fine" clearance 5 card.
I like it, interesting take on the seeming finality of SCP articles in-universe. Nice presentation, from containment procedures, descriptions, to the actions and deliberations of Foundation staff. +1
I do have some suggestions/questions though, witten in the order they appear in the file.
BERRYMAN-LANGFORD memetic kill agent
Minor, but I think it would be better as just "memetic kill agent".
(the pictures)
They look interesting, but it's not clear to me what they are or why they're in the article. Are they supposed to be captionless?
relating to SCP-4121 are to be suppressed monitored.
I expected there to be some kind of justification for the change, but I didn't see any. Is the anomaly becoming very well-known, or is the anomaly itself preventing long-term management?
Site Ω-1
Site-Ω-1, though later I see the name as "Site MΩ1"? So shouldn't this be "Site-Ω1"? I think some clarification on this point is needed either way.
MTF Psi-58
No listing in the list of Task Forces. As such, I would highly recommend adding a nickname.
GOIs
GoIs
O5 council
Later you use "O5 Council" consistently, I'm going to guess the lack of capitalization was an oversight.
23/06
I don't want to start a fight over DD/MM vs MM/DD, but I will just say that given it lacks a year, I think it might be cleaner to write the date out in full. (e.g. "July 23rd")
SCP-096
SCP-2399
…
I would recommend making these links.
XK Class
XK-Class
Dr Emily Horan
I would suggest making the "Dr"s into "Dr."s
DOI
NOI
Given that you need footnotes to explain these, I think it would just be better to write out "Date of Incident" and "Nature of Incident". Also I echo the above point about dates, though here simply adding a year (possibly redacted) would likely be better.
self terminate
self-terminate
[DATA REDACTED BY ORDER OF O5-1.]
[DATA REDACTED BY ORDER OF O5-1]
Site [REDACTED]
Site-[REDACTED] or Site-██
O-5 Council
O5 Council
O5-3: Enough insubordination Director.
Add a comma: "Enough insubordination, Director."
O5-1:…you have made your case Director?
Missing space and comma: "O5-1: …you have made your case, Director?"
Interviewed is dismissed.
I would recommend changing this and the above to "Interviewee".
O5-1: Yet we still must come to a verdict. Terminate the interview.
The interview already ended. I would change this to "Stop the recording" or something.
Thank you for the deep dive, I'm glad you liked the article.
Addressing/explaining some of the points:
The naming of the kill agent is a reference to the 001 articles, which are guarded by the same defence measure.
The change from suppression to monitoring is(in my own headcanon) because of the near impossibility to prove the anomaly exists. Anyone who figured out the truth would be a desirable employee for the Foundation, as they've proven how intelligent they are. Although you could also just say the anomaly is stopping the Foundation from taking direct measures.
I thought it'd be a nice little indicator of the seriousness of the anomaly. The DOI and NOI were originally structured the way you suggested, but it appeared more messy then desired, so I switched to footnotes.
The naming of the kill agent is a reference to the 001 articles
I'm aware, I just think given how big the font is it looks a bit clunky on the banner.
Anyone who figured out the truth would be a desirable employee for the Foundation, as they've proven how intelligent they are.
I guess, but that could be part of suppression. Prevent any research about it from coming out, and acquire anybody who learns about it. But I guess it's not an important detail.
SCP-001 | [REDACTED] | [REDACTED]
I really liked this little touch first time I read through it, but now that it's an overseer reading the file I'm not sure it makes a lot of sense. The O5 know which 001 is the correct one.
Also thanks for adding a caption to the image. Still a good scip, too bad it's underrated.
Hey, this is pretty good. I like the causal relationship it forms between other SCPs. It provides a good explanation why the Foundation has so many of these world-ending anomalies, yet they don't destroy the world.
Eta: although, I would like an explanation for the image in the article. It seems weird to just leave it there and not justify it.
This article is quite incredible, and I upvoted! However, if I may ask, what is that image? It looks pretty cool, but I'm not sure how it relates to the SCP.
I liked it before and I like it now. Though I am a bit disappointed the object class had to change, I understand why since that was the main complaint initially.
Actually, on the subject of object classes, why would it be classified as hiemal? IIRC, hiemal refers to a balanced system of two or more anomalous phenomena that keep each other in check and if there's a shift in power then it causes large-scale damage. I think Thaumiel => Keter would make more sense, even Thaumiel => Keter => Pending could work.
Also, I don't think this qualifies as level Black. Threat levels are based on beneficialness/harmfulness, with Black level being anomalies that can cause a K-Class scenario. If anything this is a level Blue.
The main reason I declared this as Hiemal is that the effects of the anomaly actively contain other items and stop them from causing an K-Class event. The threat level is more potential, if the anomaly should fail, a K-Class scenario would be inevitable. I was gonna make it blue/black to demonstrate the current situation vs the potential situation, but I couldn't get the format to work properly.
The main reason I declared this as Hiemal is that the effects of the anomaly actively contain other items and stop them from causing an K-Class event.
If that's the case, then "Archon" seems like a better fit.
Is the 682 entry a jab at it’s supposed “plot armor?” Regardless, I like it. If it didn’t have the stigma attached to it, this could be an Apollyon.
Bang on with that 682 reference. I originally threw this up under a unique class because I didn't really think any of the others applied, but Hiemal is closest so settled with that.
“Heimal” is one of the only esoteric classes that actually has a definition; being “used to contain other anomalies but dangerous and uncontrollable.” Looking back, I agree with your choice of it.
Why the hell would this be Apollyon? That's for things that have irrevocably breached containment and are imminent massive threats. This anomaly is basically the opposite, while you could argue about whether it's "contained" or not, it actively prevents the world from progressing to a distinctly different state, which also precludes end-of-world scenarios.
But yes, this scip is basically the mechanism of "plot armor" in-universe.