Noting that Stardust Bread (account age 4 days) recently applied for site membership. They have the following sandbox, which has common indicators of AI-generation: http://scp-sandbox-3.wikidot.com/chroma
Most recent revision 14 retained:
[[include :scp-wiki:theme:black-highlighter-theme]]
[[include :scp-wiki:theme:the-foundation-theme |dark=--]]
[[module CSS]]
/* ===== CORRUPTED / GLITCHING TEXT ===== */
/* Used for data that is unstable because the ANOMALY resists measurement, */
/* NOT because it is hidden from the reader. O5 sees everything; the data itself breaks. */
#page-content .corrupt {
color: #d11;
font-family: "Recursive", monospace;
letter-spacing: -0.5px;
position: relative;
animation: chroma-flicker 2.6s infinite steps(1);
text-shadow: 0.04em 0 rgba(255,0,40,0.55), -0.04em 0 rgba(0,200,255,0.45);
}
@keyframes chroma-flicker {
0% { opacity: 1; text-shadow: 0.04em 0 rgba(255,0,40,0.55), -0.04em 0 rgba(0,200,255,0.45); }
47% { opacity: 1; text-shadow: 0.04em 0 rgba(255,0,40,0.55), -0.04em 0 rgba(0,200,255,0.45); }
48% { opacity: 0.75; text-shadow: -0.08em 0 rgba(255,0,40,0.8), 0.08em 0 rgba(0,200,255,0.7); }
49% { opacity: 1; text-shadow: 0.12em 0 rgba(255,0,40,0.6), -0.1em 0 rgba(0,200,255,0.6); }
50% { opacity: 0.85; text-shadow: 0.04em 0 rgba(255,0,40,0.55), -0.04em 0 rgba(0,200,255,0.45); }
100% { opacity: 1; text-shadow: 0.04em 0 rgba(255,0,40,0.55), -0.04em 0 rgba(0,200,255,0.45); }
}
/* ===== HAZARD-STRIPED WARNING BOX ===== */
.glitchwarn {
border: solid 2px #900;
background: repeating-linear-gradient(
45deg,
rgba(150,0,0,0.06),
rgba(150,0,0,0.06) 10px,
transparent 10px,
transparent 20px
);
padding: 0.5em 1.2em;
margin: 1em 0;
}
/* ===== EMAIL / MEMO BOX (replaces fragile email component, tab-safe) ===== */
.email {
border: solid 1px rgba(160,160,170,0.4);
border-left: solid 4px #555;
background: rgba(255,255,255,0.03);
padding: 0.4em 1.1em 0.8em;
margin: 1em 0;
font-size: 0.95em;
}
.email .hdr {
font-family: "Recursive", monospace;
font-size: 0.82em;
color: #9a9aa2;
border-bottom: solid 1px rgba(160,160,170,0.25);
padding-bottom: 0.3em;
margin-bottom: 0.6em;
}
.o5memo {
border: solid 1px #3a0000;
border-left: solid 4px #900;
background: rgba(120,0,0,0.07);
padding: 0.4em 1.1em 0.8em;
margin: 1em 0;
font-size: 0.95em;
}
.o5memo .hdr {
font-family: "Recursive", monospace;
font-size: 0.82em;
color: #c98;
border-bottom: solid 1px rgba(160,0,0,0.3);
padding-bottom: 0.3em;
margin-bottom: 0.6em;
letter-spacing: 0.5px;
}
/* ===== FADE-IN ENTRANCE (on page load, reliable; not scroll-triggered) ===== */
#page-content .fade-in {
animation: fade-rise 900ms ease-out both;
}
#page-content .fade-in-slow {
animation: fade-rise 1600ms ease-out both;
}
@keyframes fade-rise {
from { opacity: 0; transform: translateY(14px); }
to { opacity: 1; transform: translateY(0); }
}
[[/module]]
[[=]]
[[size smaller]]//Author's note: this might be the scariest thing you've ever seen, but it's worth it.//[[/size]]
[[/=]]
[[include :scp-wiki:component:anomaly-class-bar-source
|item-number= 9744
|clearance= 5
|container-class= esoteric
|secondary-class= apollyon
|secondary-icon= https://scp-wiki.wikidot.com/local--files/component:anomaly-class-bar/apollyon-icon.svg
|disruption-class= amida
|risk-class= critical
]]
[[include :scp-wiki:component:acs-animation]]
[[>]]
[[module Rate]]
[[/>]]
[[=]]
[[div class="glitchwarn fade-in"]]
+ ⚠ BY ORDER OF THE OVERSEER COUNCIL ⚠
----
The anomaly described in this file is **a load-bearing component of active Foundation containment.** It cannot be deactivated. It cannot be destroyed. It cannot be reduced. It grows every day that it is contained, and it is contained every day that it grows.
This file is Level 5/9744 classified. There is no procedure in this document that ends with SCP-9744 being gone. Do not look for one.
[[/div]]
[[/=]]
[[collapsible show="► [ INPUT LEVEL 5/9744 CREDENTIALS ]" hide="▼ [ ACCESS GRANTED — O5 EYES ONLY ]"]]
----
[[div class="glitchwarn"]]
Some figures in this file (composition, mass, projected failure date) will appear [[span class="corrupt"]]unstable or corrupted[[/span]]. This is **not** redaction. You are cleared for all of it. The data corrupts because the anomaly cannot be measured, not because it is hidden from you. What you cannot read here, no one can read anywhere.
[[/div]]
**Item #:** SCP-9744
**Object Class:** Esoteric ([[span class="corrupt"]]Apollyon[[/span]])
[[div class="glitchwarn"]]
**STANDING NOTICE:** SCP-9744 has been formally classified Apollyon. This classification is not a prediction of failure. It is an acknowledgment that containment is finite and that the date of failure is calculable. See Addendum 9744.4.
[[/div]]
**Special Containment Procedures:** SCP-9744 is held at Site-78, a facility built around it and dedicated solely to it. SCP-9744 is restrained by a continuous suppression field generated by the Site's primary array. The field does not stop SCP-9744. Nothing stops SCP-9744. The field slows it to a rate the Foundation can survive.
The suppression field does not act on SCP-9744's composition; it acts on its access. The array surrounds the containment vessel with a sustained, high-density energy barrier that occupies the same physical space SCP-9744 would need to expand into were it touching unrestricted metal. Conversion can still occur at the single feedstock channel permitted through the barrier, but it cannot spread sideways into the vessel wall, because the wall is not metal the field allows SCP-9744 to reach. The field does not weaken or interrupt the reaction itself, it simply denies it surface area to grow into. Increase the field's strength and the boundary holds more tightly, channeling growth through the feedstock line alone; weaken it, even briefly, and that boundary becomes metal again, which is precisely what happened in Incident 9744-77.
The suppression field is powered by SCP-9744. A regulated stream of feedstock metal is fed into SCP-9744 at a fixed rate; the energy of its conversion powers the field that restrains it, and the surplus powers the containment of four (4) other anomalies designated in Document 9744-D. SCP-9744 therefore powers its own cage and four others besides.
Because of this, SCP-9744 has no shutdown procedure, no decommissioning procedure, and no contingency that results in its removal. Halting SCP-9744 collapses its own suppression field and cuts power to all dependent containments simultaneously. SCP-9744 is to be maintained, fed, and survived, indefinitely.
Feedstock supply is held at quadruple redundancy following Incident 9744-77. Interruption of feedstock for longer than ##red|two hundred seconds## is a confirmed XK-Class scenario trigger and is to be escalated to the Overseer Council the instant it is detected, not after it is resolved.
Feedstock is to be held above ##red|400 K## prior to introduction. This is not a tolerance, it is a requirement: feedstock temperature directly governs whether SCP-9744's conversion yields the energy this facility and its dependents require, or yields mass growth in its place. Any fault in feedstock heating is to be treated with the same urgency as a fault in feedstock supply.
MTF Epsilon-11 ("Nine-Tailed Fox") maintains a standing detachment at Site-78. Their role is not external defense; SCP-9744 has no need of it. Their role is internal: any deviation in suppression field load, feedstock temperature, or conversion rate is to be treated as an active breach scenario, and Epsilon-11 is to respond accordingly, on-site, within the response windows established after Incident 9744-77.
In the event that suppression fails outright, whether through feedstock interruption, array failure, or any other cause, and SCP-9744 begins unrestrained propagation, Site-78's protocol calls for the immediate broadcast of CODE: GRAY and the mobilization of MTF Nu-7 ("Hammer Down"). It is noted in this file for the sake of honesty that Nu-7's mandate in this scenario is not recontainment. By the time Nu-7 could arrive, recontainment will no longer be a live option. Their mandate is regional evacuation and the destruction of anything still capable of being destroyed.
----
**Description:** SCP-9744 ("Chroma") is a mass of anomalous metal, presently massing approximately [[span class="corrupt"]]███[[/span]] kg. It is dark, faintly iridescent, and reflects almost no light. What it is made of is unknown, and the word "unknown" is doing more work than usual here: every instrument turned on SCP-9744 returns a different answer, and none of the answers are possible. Particle counts come back negative. Mass readings disagree with one another taken seconds apart. The Foundation does not know what SCP-9744 is, has stopped trying to find out, and has classified the question itself as a waste of clearance.
None of the figures in this file come from instruments aimed at SCP-9744 itself; those instruments are unreliable by nature and have been disregarded as a data source since early in containment. Every number in this document is instead derived from the systems around SCP-9744, which behave like ordinary equipment because they are ordinary equipment. Bulk mass is tracked by load cells beneath the containment vessel, the same kind used to weigh shipping containers, which do not care what they are weighing. Energy output is read directly off the suppression array's own power meters and the regional grid draw of its four dependents, both standard electrical instrumentation. The temperature relationship in particular was first suspected after Incident 9744-77, when auditors comparing that incident's energy shortfall against its mass gain found a ratio that did not match any prior feedstock cycle, and traced the discrepancy to the only variable that had also been abnormal that night: the temperature of what SCP-9744 had been eating. One incident does not establish a correlation, and was not treated as having done so; the relationship was confirmed separately, under controlled conditions, in Test 9744-T4 (see Addendum 9744.T), and the 400 K feedstock requirement was adopted only once that confirmation existed. The Foundation does not know what SCP-9744 is. It knows, with ordinary engineering precision, what comes out of the room it is kept in.
What SCP-9744 *does* is simple enough to state in one sentence: **it turns metal into more of itself, and gives off energy doing it.**
When SCP-9744 touches any metal that is not SCP-9744, that metal becomes SCP-9744. The new SCP-9744 can do the same to the next metal it touches. There is no stopping point built into this process. It does not slow as it spreads. It speeds up: a single point of contact becomes two points of contact as the converted material's own surface joins the reaction, those two become four as each spreads independently, and the growth compounds with every fresh surface that comes into contact with metal, the way a crack does not stay one crack once it starts branching. The Foundation does not contain SCP-9744's reaction; it contains its *surface area*, by keeping it sealed away from any metal except the single, narrow feedstock channel allowed to touch it. Each conversion releases energy far beyond anything the converted mass should contain, and that is the only reason the Foundation tolerates it: SCP-9744 is the most efficient energy source ever discovered, and it is the most efficient energy source ever discovered because it is converting the universe into fuel and the universe is very large.
For scale: the steel paperclip converted in Test 9744-T1 (see Addendum 9744.T), at full energy yield, released power output comparable to several hours of a regional power plant's total generation, from a single gram of feedstock, in under two seconds. Site-78's entire surplus contribution to four dependent containments is currently produced from a feedstock stream the weight of a housecat, fed continuously, around the clock. The Foundation did not discover an energy source. It discovered a hole in the universe's accounting, and built a meter on it.
Left unrestrained against open metal, SCP-9744 is modeled to propagate through all contiguous metal on Earth (wiring, rebar, vehicles, the planetary core) within ##red|days##. It is an extinction event that has not been allowed to happen yet. The suppression field is the "yet."
The split between energy and mass output is not fixed. It depends on the average temperature of the contacted material at the moment of conversion, measured across its entire mass rather than at any single point. Material at higher temperature converts mostly into energy, with comparatively little added to SCP-9744's own mass. Material at lower temperature converts mostly into added mass, with comparatively little energy released. There is no sharp cutoff; the relationship is a continuous slope, falling off most steeply in the region around ##red|100 K## and below, where conversion yields almost no energy at all and SCP-9744 instead grows by very nearly the full mass of whatever it touched.
This relationship is the reason feedstock temperature is a managed operational variable at Site-78, rather than an incidental detail. Feedstock is held warm by design, both to maximize the energy surplus the Foundation depends on and to minimize the rate at which SCP-9744 itself grows. Any failure that allows feedstock, or anything else SCP-9744 might reach, to cool substantially below operating temperature is treated as a containment-relevant event, because it converts SCP-9744 from a power source back into what it was recovered as: a thing that only gets bigger.
----
[[tabview]]
[[tab ▸ 9744.1 — HOW WE GOT HERE]]
**Addendum 9744.1: How We Got Here**
SCP-9744 was recovered as a Keter-class hazard and contained at ruinous cost. For the first fourteen months of containment, SCP-9744 was held in a sealed reinforced-polymer vault at Site-78, a containment medium SCP-9744 cannot convert and cannot propagate through. The polymer vault was, by every available measure, a complete success. SCP-9744 was inert, isolated, and required no active suppression system at all. It sat. It did not grow. It was, for fourteen months, the cheapest and safest object in the Site.
It was also, in the words of the original feasibility review, "a waste." A Keter-class anomaly of unknown composition, releasing measured energy yields on contact with metal far beyond any known reaction, sitting untouched in a box, was flagged by Site-78's resource office as an opportunity cost the Foundation could not justify indefinitely. The polymer vault was never breached and never failed. It was decommissioned on purpose, by administrative decision, to make room for the suppression-and-harvest architecture that replaced it.
The original vault remains in storage at Site-78, intact and unused, listed in Site inventory as Containment Asset 9744-A. It has been formally reviewed for reinstatement on three occasions, most recently following Incident 9744-77. All three reviews concluded that reinstatement is no longer possible, for the same reason termination is no longer possible: the energy SCP-9744 currently supplies to four dependent containments cannot be replaced in time to re-seal it without releasing what it currently powers. The box that would have kept SCP-9744 perfectly safe still exists. It is sitting in a warehouse, ninety meters from the thing it was built for, and it has not been usable for decades.
Replacing the vault with active containment meant building something from nothing: a suppression array with no existing power allocation, sized for a Keter-class object, at a Site that had not budgeted for one because the vault had never needed one. The array's power demand nearly bankrupted the regional budget within its first year of operation. An engineer, whose name survives in the record only as a footnote, proposed the obvious, terrible solution: let SCP-9744 power its own cage. Feed it a trickle, capture the energy, run the field off the thing the field restrains. A closed loop. Self-sustaining. Elegant.
It worked. It produced surplus. And surplus, in a Foundation that is permanently short on power for permanently dangerous things, does not go unused.
[[div class="email"]]
[[span class="hdr"]]**FROM:** [REDACTED]@scp.foundation • **TO:** site78-admin@scp.foundation • **RE:** Surplus allocation[[/span]]
Approving the tie-in. SCP-[[span class="corrupt"]]████[[/span]]'s field has been browning out for three years and we have a unit next door producing more power than it knows what to do with. This is free. Route it.
For the record I don't love that we're making more things depend on 9744, but "I don't love it" has never once beaten "it's free and it works." Route it.
//[REDACTED], Regional Containment Director (Ret.)//
[[/div]]
The second tie-in followed eleven months later, approved by a different administrator who had never read the first request and did not need to; by then, "route surplus to whichever containment is struggling" had become standing policy rather than a decision anyone made twice. The third followed within the same fiscal year, justified in a budget line item that did not mention SCP-9744 by name. The fourth, approved most recently, was the only one accompanied by an internal objection, from a junior auditor who asked, in writing, what would happen if SCP-9744 ever needed to be shut down. The recorded answer, from a supervisor two levels above her, was a single line: "It won't need to be." She was reassigned to a different department the following quarter. The objection remains in the file. It was never answered again.
Four anomalies now draw their primary power from SCP-9744. Each tie-in was, on its own day, the cheap and sensible call. No one ever decided to make SCP-9744 un-removable. They decided it four separate times without noticing, and then it was done, and then it was load-bearing, and then it was too late to be undone without releasing five catastrophes at once.
This is the part of the file the Overseer Council asked to be written plainly, so it is written plainly: **the trap was not built by SCP-9744. It was built by us, one reasonable email at a time.**
[[/tab]]
[[tab ▸ 9744.2 — INCIDENT 9744-77]]
**Addendum 9744.2: Incident 9744-77**
The standing reference example of what SCP-9744 does when the feeding stops. Reconstructed from Site-78 logs and retained in full by order of the Site Director.
The containment vessel is a sealed steel chamber roughly four meters across. SCP-9744 occupies its center, with the feedstock delivery apparatus, the only permitted metal contact, mounted through one wall. The vessel's inner lining is itself steel, separated from SCP-9744 only by the suppression field's boundary; this lining was never meant to be touched, only to exist as a structural backstop behind a field that was assumed reliable. Beyond the lining, roughly six meters out, sits the suppression array's primary coupling, the single point where the field's entire power supply physically connects to the chamber. There is no redundant coupling. If SCP-9744 reaches it, the field that depends on that coupling has nothing left to draw power through, and the field that restrains SCP-9744 collapses at the exact location where the most SCP-9744 currently exists to come pouring through.
At 02:14, feedstock delivery faulted. SCP-9744, denied its trickle, did the only thing it does. It reached for the nearest metal. The nearest metal was the inside of its own containment vessel.
> **02:14:00** — Feedstock fault. Conversion rate begins climbing. SCP-9744 contacts delivery apparatus and begins consuming it.
> **02:15:00** — Primary reserve fails to engage. SCP-9744 reaches inner vessel wall. Vessel is metal. SCP-9744 begins eating the vessel.
> **02:15:20** — MTF Epsilon-11 detachment mobilized to the suppression array floor per standing order. Their role at this stage is not to touch SCP-9744. It is to be present, in position, in case the next sixty seconds require something no automated system is authorized to do.
> **02:16:00** — Suppression field load spikes. To hold a faster-converting SCP-9744, the field pulls more power. More power requires faster conversion. Faster conversion makes more SCP-9744. The loop begins to run the wrong way. Site logs the words ##red|"POSITIVE EXCURSION"## for the first time in the facility's history.
> **02:16:40** — Conversion front [[span class="corrupt"]]████[[/span]] cm from suppression array primary coupling. The coupling is metal. If it converts, the field dies. If the field dies, everything in this file happens at once.
> **[[span class="corrupt"]]02:1██[[/span]]** — [[span class="corrupt"]]t̷e̸r̷t̶i̵a̷r̸y̴ ̶r̶e̵s̷e̴r̵v̸e̷ ̶m̷a̴n̸u̴a̵l̴ ̷o̶v̶e̴r̵r̶i̷d̴e̸ ̷ca̸r̷r̴i̵e̶d̴ ̷o̵u̶t̷ ̸b̴y̴[[/span]]
> **02:17:30** — Tertiary reserve delivers. SCP-9744 is given a target again and disengages from the array. Conversion front retreats from the coupling.
> **02:19:00** — Throttle nominal. Excursion arrested. Duration: five minutes, six seconds.
In five minutes SCP-9744 grew by fourteen kilograms, all of it eaten from the machine built to hold it, and stopped ##red|approximately ninety seconds## short of the coupling that would have ended containment for it and four other anomalies. None of those fourteen kilograms returned as energy. The vessel and array were structural steel at ambient temperature, far below the 400 K feedstock baseline, and SCP-9744 converted them accordingly: almost entirely into more of itself. The incident did not merely interrupt the energy supply. For five minutes, it ran the entire relationship in reverse.
[[div class="email"]]
[[span class="hdr"]]**FROM:** [REDACTED]@scp.foundation • **TO:** site78-all@scp.foundation • **RE:** for the file[[/span]]
I am the one who hit the tertiary override. I want something on the record while my hands are still shaking.
People keep calling this thing a reactor. A reactor turns off. You can scram a reactor. You cannot scram this. This is a fire that we keep exactly big enough to be useful, and the only way we stop it eating the building is to keep throwing things into it forever. Tonight it was ninety seconds from the building.
We are not containing SCP-9744. We are feeding it on a schedule and calling the schedule "containment." Put that in the file. Put it where the new people will read it.
//[REDACTED], Site-78 Containment Engineer, Night Shift//
[[/div]]
[[div class="email"]]
[[span class="hdr"]]**FROM:** director@site78.scp.foundation • **TO:** site78-all@scp.foundation • **RE:** for the file[[/span]]
It stays in the file. Unedited.
The engineer is correct, and the new people should read it, because the worst thing we could do is let anyone work here who believes we have this under control. We do not have this under control. We have this on a leash made of the same thing it eats, and the leash gets shorter every day.
Feedstock redundancy is now quadruple. A fifth line is approved. None of this changes what we are. It only changes the date.
//[REDACTED], Director, Site-78//
[[/div]]
[[/tab]]
[[tab ▸ 9744.91 — INCIDENT 9744-91]]
**Addendum 9744.91: Incident 9744-91**
A second standing reference example, distinct from 9744-77 in cause and character. Where 9744-77 was a supply failure, 9744-91 was a heating failure, and the two are not interchangeable. Feedstock continued to arrive on schedule throughout 9744-91. It simply arrived cold.
A fault in the feedstock preheating coil, undetected for six hours due to a sensor miscalibration, allowed incoming feedstock to drop to within a few degrees of ambient temperature before introduction, well below the ##red|400 K## operating requirement and uncomfortably close to the region where energy yield falls off steeply. No alarm was raised at the time, because every sensor downstream of the coil reported normal feedstock flow. Flow was normal. Temperature was not.
> **14:02:00** — Preheating coil fault begins (later determined by retrospective log review; undetected at the time).
> **14:02:00 to 20:11:00** — SCP-9744 receives feedstock at sub-baseline temperature continuously for over six hours. Conversion proceeds normally in every respect except output ratio. Energy yield falls roughly in proportion to the temperature deficit. Mass yield rises to compensate.
> **20:11:00** — Routine mass audit flags SCP-9744 as 340 kg heavier than projected for the elapsed feedstock volume, with a corresponding energy shortfall recorded by the regional grid serving its dependent containments. The shortfall had been silently absorbed by reserve capacity for over six hours without triggering escalation, because reserve capacity existed precisely to absorb minor fluctuations, and 340 kg of unplanned growth produced no fluctuation large enough to look like anything other than noise.
> **20:14:00** — Coil fault identified and corrected. Feedstock temperature restored to baseline within nine minutes.
[[div class="email"]]
[[span class="hdr"]]**FROM:** [REDACTED]@site78.scp.foundation • **TO:** site78-all@scp.foundation • **RE:** 9744-91 preliminary findings[[/span]]
I want to flag something that the numbers alone don't communicate well. 9744-77 was loud. Alarms, an excursion, a margin we could measure in seconds. Everyone who was on shift that night still talks about it.
9744-91 was nothing. No alarm fired. No one noticed for six hours. SCP-9744 grew by more mass in one quiet Tuesday than it did during the entire five-minute excursion in 9744-77, and the only reason we caught it at all was a routine audit that could just as easily have run a day later, or not at all if someone had been out sick.
77 taught us what SCP-9744 does when it's starving. 91 taught us something worse: it doesn't need to be starving. It just needs to be a little bit cold, for a little while, and nobody watching closely enough to notice. We have built our entire safety margin around catching loud failures. This was a quiet one. I don't know how many quiet ones we've had that an audit never caught.
//[REDACTED], Site-78 Instrumentation Lead//
[[/div]]
[[div class="email"]]
[[span class="hdr"]]**FROM:** director@site78.scp.foundation • **TO:** site78-all@scp.foundation • **RE:** Re: 9744-91 preliminary findings[[/span]]
Received, and escalated to the Council in full.
Sensor redundancy on the preheating coil has been tripled, with independent thermal logging that does not route through the same system as flow monitoring, so that a fault in one cannot hide a fault in the other. This closes the specific gap that allowed 9744-91 to go undetected. It does not close the category of gap.
The Instrumentation Lead is right that we have built our margins around alarms, and an alarm only fires for a failure someone anticipated. We are now actively looking for the failures we have not anticipated, which is a much harder thing to schedule a response for, and I do not have good news about how that search is going.
//[REDACTED], Director, Site-78//
[[/div]]
[[/tab]]
[[tab ▸ 9744.T — TESTING]]
**Addendum 9744.T: Permitted Testing**
Testing on SCP-9744 is almost entirely prohibited. The reason is simple: every test requires introducing metal to it, and introduced metal is converted and lost forever, which both feeds its growth and risks the throttle. The only sanctioned tests are those that can be performed with trivial, expendable samples under maximum suppression, and even these require Director sign-off.
The complete sanctioned testing record consists of three entries.
> **Test 9744-T1.** A single steel paperclip was introduced to SCP-9744 under full suppression. It converted in 1.4 seconds, releasing energy consistent with the standard conversion curve. The resulting SCP-9744 was indistinguishable from the parent mass. **Conclusion:** small samples behave identically to large ones. No threshold of "too small to bother" exists.
> **Test 9744-T2.** A non-metallic sample (a ceramic disc) was placed in direct contact with SCP-9744 for ten minutes. No conversion occurred. **Conclusion:** confirmed, as expected, that SCP-9744 acts only on metal. The disc was undamaged.
> **Test 9744-T3.** A 1-gram gold sample (99.99% pure) was introduced. It converted normally, ruling out any hope that purity or nobility of the metal might resist the effect. **Conclusion:** there is no metal SCP-9744 will not take. Proposals to line containment with "a metal it won't eat" are formally closed. No such metal exists.
> **Note, Dr. [REDACTED]:** I want to flag that T1 through T3 cost us, in total, roughly four grams of permanent growth. That sounds like nothing. It is not nothing. Every test we run, however small, moves the date in Addendum 9744.4 closer by a measurable amount. I am recommending we stop testing entirely. There is nothing left to learn that is worth feeding it to learn.
> **Addendum, filed after Incident 9744-77.** The recommendation above held for nine years. It was overridden once, by Director authorization, following 9744-77's anomalous energy-to-mass ratio. A single incident is a data point, not a correlation, and the Director's office was unwilling to set a facility-wide operating requirement, the ##red|400 K## feedstock baseline now governing every shift at this Site, on the strength of one uncontrolled event. Test 9744-T4 was approved as the one exception to the standing prohibition, specifically to confirm or rule out the hypothesis before it became policy.
> **Test 9744-T4.** Five 1-gram steel samples were introduced sequentially under full suppression, held at controlled temperatures of 90 K, 150 K, 250 K, 400 K, and 600 K immediately prior to contact. Energy and mass output were measured for each via array power draw and load cell delta, per the standard methodology. Yield shifted from almost entirely mass at 90 K to almost entirely energy at 600 K, with the four intermediate readings falling smoothly along the slope between them and no point at which the relationship broke or reversed. **Conclusion:** the hypothesis drawn from 9744-77 is confirmed as a genuine, repeatable, monotonic relationship rather than a coincidence of that incident. The 400 K baseline was adopted the same week.
> **Note, Dr. [REDACTED]:** Five grams this time, not one. I was the one who recommended we stop, and I was the one who signed off on the exception, because the alternative was running this facility on a guess. I want that contradiction on the record rather than quietly resolved. We did not stop testing because we ran out of reasons. We stopped because we decided four grams of damage was an acceptable price for an answer we could trust, and not one gram more than that.
[[/tab]]
[[tab ▸ 9744.3 — IT IS GROWING]]
**Addendum 9744.3: It Is Growing**
SCP-9744 weighs more today than it did yesterday. It has to. The conversion that powers its own containment turns feedstock into more SCP-9744, and conversion is one-way. It cannot be shrunk. Every gram of fuel it burns to power its cage makes the thing in the cage bigger.
A bigger SCP-9744 needs a stronger field. A stronger field needs more power. More power needs faster conversion. Faster conversion makes a bigger SCP-9744. Read those four sentences again and notice that they form a circle, and that the circle only turns one direction, and that the direction is "up."
[[/tab]]
[[tab ▸ 9744.4 — THE DATE]]
**Addendum 9744.4: The Date**
[[div class="glitchwarn"]]
The following projection is Level 5/9744 restricted and is not to be summarized, paraphrased, or removed from this file.
[[/div]]
The suppression array has a maximum field strength. SCP-9744's growth has a curve. The two lines cross.
At the crossover, the field required to hold SCP-9744 will exceed the field the array can produce from SCP-9744's own output, meaning SCP-9744 will, on that day, begin producing exactly enough energy to require more restraint than that same energy can provide. The loop that has held for decades will, by simple arithmetic, stop closing.
A successor array is under construction. It moves the date. It does not remove the date. A third array has been modeled against the second array's crossover; it, too, moves the date and does not remove it. Every solution the Foundation has found to SCP-9744 has the same shape: it is an extension, not an answer, and each extension is more expensive than the last for less time than the last bought.
Current best projection to crossover: [[span class="corrupt"]]██ years, ███ days[[/span]].
This number decreases on its own. It has never once increased.
MTF Nu-7 ("Hammer Down") maintains standing orders against the day this number reaches zero. Their briefing materials, on file separately, do not contain the word "recontainment." They contain evacuation radii and demolition schedules. This is not an oversight. It is the most honest document the Foundation has produced regarding SCP-9744, because it is the only one that does not pretend a solution is coming.
There is no version of this file, in any drawer, at any clearance, that ends with SCP-9744 contained. There is only this one, which ends with the date, and the date is always sooner than it was the last time someone checked.
[[/tab]]
[[tab ▸ 9744.P — PERSONNEL]]
**Addendum 9744.P: Personnel Notes**
Site-78 maintains a standard four-year rotation for staff with direct operational responsibility for SCP-9744, shorter than the Foundation default for comparable facilities. The shortened rotation was instituted after the third year of operation, when exit interviews and mandatory psychological evaluation began to show a consistent pattern across personnel with no obvious relation to incident exposure. Staff who had never been on shift during 9744-77, 9744-91, or any other notable event showed the same pattern as those who had.
The pattern has no official diagnostic name. Internally, staff refer to it as "the math," after its most common presenting symptom: an inability to stop performing the crossover calculation in Addendum 9744.4 in idle moments, regardless of whether new data exists to justify recalculating it. Site psychological staff describe it as a fixation rather than a disorder, distinct from anxiety or obsessive-compulsive presentations in that affected personnel do not report the behavior as distressing. They report it as appropriate.
[[div class="email"]]
[[span class="hdr"]]**FROM:** psych-services@site78.scp.foundation • **TO:** director@site78.scp.foundation • **RE:** Quarterly evaluation summary, redacted for file[[/span]]
Of this quarter's twelve evaluations, nine included some version of "the math" without my prompting for it. Representative excerpt, anonymized: "I know the number doesn't change between checks. I check anyway. If I stopped checking it wouldn't change the number, but it would change whether I knew it, and not knowing feels worse than the number does."
I want to be careful not to pathologize a response that may simply be accurate. These are not staff misperceiving their situation. They are staff perceiving it correctly and finding that the correct perception does not go away when the shift ends. I am recommending the rotation shortening proceed as discussed, not because four years is long enough to do harm, but because I no longer believe any duration is short enough to avoid it, and four years is what we can sustain operationally.
//Dr. [REDACTED], Site-78 Psychological Services//
[[/div]]
Personnel completing their rotation are offered standard post-assignment support and, per a policy unique to this Site, an open invitation to return for any subsequent reclassification review or major addendum, regardless of current clearance or assignment. Attendance is voluntary. It has never once gone unattended.
[[/tab]]
[[tab ▸ 9744.O5 — COUNCIL CORRESPONDENCE]]
**Addendum 9744.O5: Overseer Council Correspondence**
The following exchanges are appended at Level 5/9744 only. They are not operational documents. They are retained because the Council determined that future members should understand not only what SCP-9744 is, but how it is regarded by those who carry final authority over it.
[[div class="o5memo"]]
[[span class="hdr"]]O5 SECURE CHANNEL • AGENDA ITEM 9744 • ANNUAL REVIEW[[/span]]
Item 9744 carried again this cycle. Vote to continue current containment doctrine: unanimous. No alternative proposal reached the floor.
For the minutes: there is no objection to record. There is also no one in this room who would describe the vote as a decision. We continue because there is nothing else to do. I would like that distinction preserved.
//— O5-█//
[[/div]]
[[div class="o5memo"]]
[[span class="hdr"]]O5 SECURE CHANNEL • PRIVATE • NOT FOR MINUTES[[/span]]
You asked me last cycle whether I sleep. I told you I do. That was the answer the seat required, not the true one.
I have read every projection. I have read the one we do not circulate. I know the number in 9744.4 better than I know my own staff's names, and I know it gets smaller while I am asleep, which is the part I cannot put down. We did not inherit a monster. We inherited an arrangement, and the arrangement is reasonable, and the arrangement ends the world on a schedule, and every one of us has signed it forward one more year because the alternative is to be the Council that let four other things loose to avoid a fifth.
I am not writing this to be acted upon. There is nothing to act upon. I am writing it because someone who sits here after me should know that we were afraid, and that we were quiet about it, and that the quiet was the only professional thing left to be.
//— [REDACTED], O5[[span class="corrupt"]]█[[/span]]//
[[/div]]
[[div class="o5memo"]]
[[span class="hdr"]]O5 SECURE CHANNEL • RE: above • PRIVATE[[/span]]
Received. Logged to the sealed annex, not the minutes, as you intended.
For what it is worth: every seat that has ever held this file wrote something like what you just wrote, sooner or later. They are all in the annex. I have read them. You are not the first to be afraid in this exact way, and you will not be the last, and that continuity is the closest thing to comfort this office contains. We hold it because we are the ones holding it. That is the whole of it.
Sleep if you can. The number does not move faster for being watched.
//— O5-█[[span class="corrupt"]]█[[/span]]//
[[/div]]
[[/tab]]
[[/tabview]]
[[/collapsible]]Excerpts of note:
Feedstock is to be held above 400 K prior to introduction. This is not a tolerance, it is a requirement: feedstock temperature directly governs whether SCP-9744's conversion yields the energy this facility and its dependents require, or yields mass growth in its place. Any fault in feedstock heating is to be treated with the same urgency as a fault in feedstock supply.
What SCP-9744 *does* is simple enough to state in one sentence: it turns metal into more of itself, and gives off energy doing it.
When SCP-9744 touches any metal that is not SCP-9744, that metal becomes SCP-9744. The new SCP-9744 can do the same to the next metal it touches. There is no stopping point built into this process. It does not slow as it spreads. It speeds up: a single point of contact becomes two points of contact as the converted material's own surface joins the reaction, those two become four as each spreads independently, and the growth compounds with every fresh surface that comes into contact with metal, the way a crack does not stay one crack once it starts branching. The Foundation does not contain SCP-9744's reaction; it contains its *surface area*, by keeping it sealed away from any metal except the single, narrow feedstock channel allowed to touch it.
This is the part of the file the Overseer Council asked to be written plainly, so it is written plainly: the trap was not built by SCP-9744. It was built by us, one reasonable email at a time.
Permanently banned, PM sent.