Researcher's Note: This SCP Document is incomplete, and has yet to be uploaded to the main Foundation Database. Thank you for reading, and any critique is welcome! rating: 0 + x SCP-XXXX file photo Item #: SCP-XXXX Object Class: Safe Special Containment Procedures: SCP-XXXX may be safely stored within any standard Small-Object Containment locker, within any site rated for safe-level object containment. REVISION ██/██/████: The precise location of SCP-XXXX is currently unknown to the Foundation. Given the events surrounding loss of containment, it is expected to have returned to Earth sometime within three days of Breach Event XXXX-Alpha. Efforts are being made to locate the object and determine whether or not it was destroyed on impact. Further data as well as a list of projected landing sites can be found in document #XXXX-017. Description: SCP-XXXX is a Russian-made Zorki-4 rangefinder camera with radically altered internal systems implementing paratechnological components. While all controls normally available in this model of camera exist, most have no actual use and appear to be purely aesthetic. The one exception to this is the shutter-release button - activating it will result in SCP-XXXX, as well as any object in direct contact with it, being transported to the first object to break a line drawn outward from the lens. Experimentation has failed to identify a maximum transport range. The means by which "direct contact" is defined are currently unknown - clothing will reliably travel with the user, as well as any objects contained within the user's pockets, but other criteria vary. A robotic arm that activates the shutter-release button will be transported by SCP-XXXX, but the platform on which the arm is placed will not. It has been theorized that SCP-XXXX contains a form of artificial intelligence dictating what objects are transported, but this has not been confirmed. Addendum XXXX-01: SCP-XXXX Experimentation Log Experiment A - ██/██/████ Subject: D-9293, Female, age 35

Objective: To determine the safety of using SCP-XXXX to transport organic matter.

Log: D-9293 is provided with SCP-XXXX and instructed to aim the object at a target positioned at the opposite end of the room and activate it. D-9293 vanishes, and in the same frame of the recording, appears at the opposite side of the room, with the SCP-XXXX lens positioned three inches from the target.

Analysis: D-9293 was observed for three days after the experiment. No adverse effects to transport by SCP-XXXX were detected. Experiment B - ██/██/████ Subject: D-9293, Female, age 35

Objective: To determine whether SCP-XXXX is capable of transporting matter through solid transparent objects.

Log: Identical setup to Experiment A, with the addition of a transparent pane of glass separating D-9293 from the target. D-9293 activates SCP-XXXX, and is transported to within three inches of the target as in Experiment A.

Analysis: D-9293 was observed for an additional three days after the experiment. D-9293 complained of a mild headache, but no other adverse effects were detected. Experiment C - ██/██/████ Subject: D-9293, Female, age 35

Objective: To determine whether SCP-XXXX is capable of transporting matter around corners through the use of a mirror.

Log: Similar setup to Experiment A - with the noted difference of the target being around a corner, out of immediate sight of the subject. A mirror was positioned such that the target's reflection would be visible to the subject, and the subject was given SCP-XXXX. Upon activating the object, the subject was transported to within three inches of the mirror.

Analysis: The transportation mechanism used by SCP-XXXX does not rely upon light or any other type of signal that can be reflected.

Researcher's Note: This SCP Document is incomplete, and has yet to be uploaded to the main Foundation Database. Thank you for reading, and any critique is welcome! rating: 0 + x SCP-XXXX-A in the course of its first observed transit. Item #: SCP-XXXX Object Class: Euclid Special Containment Procedures: SCP-XXXX-B and C are contained onsite at sites 136 and 143 respectively. SCP-XXXX-A is not directly containable. Civilian contact with SCP-XXXX-A is to be prevented through the use of a mobile containment zone as well as through amnestics when necessary. Public knowledge of this mobile containment zone is to be prevented through standard disinformation protocols. No attempt to interrupt the motion of SCP-XXXX-A, or to change its course, is to be made under any circumstances. Description: SCP-XXXX consists of three separate components - SCP-XXXX-A, B, and C. SCP-XXXX-B and C are two large, circular holes in the surface of the earth, each measuring roughly four meters across. SCP-XXXX-B is positioned on the Yucatan Peninsula, near [REDACTED], and SCP-XXXX-C is positioned in the Indian Ocean at the antipode of SCP-XXXX-B. SCP-XXXX-A is a roughly spherical stone construct with a radius of one meter, currently positioned 30 miles off the coast of Galveston, Texas, at the bottom of the Gulf of Mexico. SCP-XXXX-A moves from SCP-XXXX-C to SCP-XXXX-B at a constant rate of sixty meters every hour, regardless of the grade of the terrain or of any objects placed in its way. Any object that SCP-XXXX-A cannot directly roll over or push out of the way will be damaged or destroyed by the object's passage directly through it. SCP-XXXX-A cannot be damaged by any known means, and its movement cannot be interrupted or delayed. SCP-XXXX-A has a measurable mass of roughly one ton, but experimentation suggests that no force other than gravity and ostensibly the static friction enabling it to roll will affect it. Upon reaching SCP-XXXX-C, SCP-XXXX-A will enter it and reemerge from SCP-XXXX-B in exactly one hour. Upon reemergence, SCP-XXXX-A will proceed to move in a random direction along a geodesic terminating at the location of SCP-XXXX-B. This has occurred only once since the object's discovery - the previous cycle's path appears to have been directed southward, travelling from -B to -C by way of the Antarctic Peninsula. The number of times this journey has been completed is unknown, as a complete transit from SCP-XXXX-B to SCP-XXXX-C will take roughly 38 years.

Researcher's Note: This object's file is complete, and has been uploaded to the main Foundation Database at this location. Thank you for reading! rating: 0 + x NOTICE The following file contains a description of a Class-VIII Datahazardous Artificial Entity. If your workstation has not received appropriate C8/3612 inoculation, close this file immediately and delete applicable system logs to prevent the targeting of your workstation by SCP-3612. Furthermore, this file has been reordered from the standard format in an attempt to reduce its SSO-Score. This will increase the chances of this file remaining intact in case of containment breach. Object Class: Keter Item #: SCP-3612

The Top of the SCiPNET Mainlist Prior to enacting SCP-3612 Containment Procedures Description: SCP-3612 describes a sentient and extremely destructive computer virus, believed to have originated within the Chaos Insurgency, that inhabits the Foundation SCiPNET Database. It is capable of relocating itself to any position within the aforementioned filesystem - regardless of any firewalls or attempts at quarantine. Only one copy of SCP-3612 is known to exist, and all attempts to create copies in a controlled environment have met with failure. SCP-3612 is a powerful infovore known to exclusively target and delete specific types of data. Namely, any data that exhibits Symbolic Sequential Ordering (SSO) is at risk. In order for data to be classified as SSO-Positive, two qualifications must be met. Data must be organized in the form of a list.

Data must be ordered with respect to a specific, deliberate purpose. Examples of SSO-Positive data include lists arranged in chronological order and lists arranged in order of some quantitative measurement, as well as lists ordered qualitatively. When a test subject is presented with a list of objects and instructed to order them according to "their liking," the resultant data is SSO-Positive, and as such, will be targeted by SCP-3612. Prior to the entity's discovery and containment, SCiPNET's SCP Mainlist was arranged chronologically, in order of item discovery and as a result had an SSO-Score of 0.5. As such, it was targeted by SCP-3612, and manual recompiling of large portions of the database was necessary after containment was established. After containment, the database's SSO-Score has been reduced to 0.1, and attacks on valuable files have been greatly reduced . Addendum 2: Partially Recovered Chaos Insurgency E-Mail Delta Command, I'm sending this message from a quarantined laptop - as far as I know, it's never had any connection with the mainframe here, so it should be fine, I hope. Abandon Site 230. Don't try to connect anything electronic to our hardware. Sd0egPpxbyGfOb1pory short, the experiment worked, but too well. Subject is in the database. ufqNbXej92TTiTHALCsElost critical data, particularly regarding some containment software. We've lost people down here. I do ha5vFWahDf2jZ9k8O8QHom to regain control of our objects. Instructions are below. VsJxf7C7Qt0kLxZDdMW7IlnCwNn

5qzI2bpk9oIKh4UJvES0Ftg35

AenesBJvGOuaF1XkeF3dFw4fewqBkhhge

xo2rvojSllwq4x4St

MRVF8zNN5RAuCQcS3X0T

uts94TM2cv3IfhnqcFi0dbMmWN There. You can do all that and you should be fine. Most of the objects have escaped, though, so they're a comple8jpToNaeZeyond that everything else is OK. I'm leaving this on the hard drive here too - and leaving the laptop at the entrance just in case you come looking andj2tYs0tJCn9mbledis8ood luck to you all. James Carpenter, Site 230 R&D Division Special Containment Procedures: All attempts to limit the movements of SCP-3612 within the Foundation SCiPNet Database have met with failure. As such, further containment of SCP-3612 requires two distinct special procedures. The first of these is the SCP-3612 Distraction Protocol. At no less than five Foundation sites worldwide, at least one member of D-Class personnel per site must be simultaneously generating lists that exhibit Symbolic Sequential Ordering (SSO) as detailed in the Description. The subject matter contained within these lists is irrelevant – of significance is that the data within the lists is deliberately ordered according to some strategy. The specific strategy employed is irrelevant – although a positive correlation is suspected between use of qualitative data to generate lists and the attraction of SCP-3612. No fewer than five such lists must exist at any time, and more must be generated to replace lists that have been damaged or destroyed. The second procedure consists of a revision of Numerical Assignment Protocol. In order to prevent the SCP Document Mainlist, stored within SCiPNet servers, from being corrupted by SCP-3612, the Mainlist must be made less appealing to the entity. As such, the following procedures have been developed to ensure minimum chance of the SCP Mainlist itself being classified as SSO-Positive. SCP designation numbers must not be assigned with regard to order of discovery, nor with regard to any overarching method. Instead, personnel responsible for recovery of an object will be required to choose its designation number from any unused slots in the database. This will introduce the personal preference or superstitions of thousands of separate individuals, minimizing the chances of a coherent pattern emerging . Any objects recovered prior to these procedures being enacted will be numbered according to the preferences of any surviving personnel involved in their recovery. If no such surviving personnel exist, the object will be numbered according to the preference of its highest-ranking designated researcher.

Researcher's Note: This object's file is complete, and has been uploaded to the main Foundation Database at this location. Thank you for reading! rating: 0 + x KIC 8462852 photographed in Infrared and Ultraviolet light Item #: SCP-3029 Object Class: Euclid Special Containment Procedures: Because of the size and distance of SCP-3029, full containment is impossible. Some aspects of SCP-3029 are already well-known among civilian media outlets, so completely hiding the anomaly through amnestics or editing of scientific data is implausible. However, such methods may be employed to convince astronomers that the observed dimming pattern is the result of dust clouds or comets obscuring the star from view. Description: SCP-3029 is the cause of the phenomenon affecting KIC 8462852, an F-type main sequence star located in the Cygnus constellation, roughly 1,280 ly from Earth. This star dims periodically - while it was first assumed that this indicated a transiting exoplanet, the irregular nature of this dimming ruled out that possibility. Diagram of the SCP-3029 system SCP-3029 has been determined to be an array of large, reflective objects , in an orbit around the star with an average altitude of █.██ AU. It is currently believed that these function as solar collectors, and have been known to obscure a maximum of over 20% of the star's light. The star system also appears to move, at a calculated rate of roughly 0.1c relative to the Earth. The cause of this motion is a large curved reflector , measuring roughly 2 AU across and directed perpendicular to the galactic plane. This reflector is positioned such that photon pressure cancels its gravitational attraction to its parent star, and directs all light, radiation, and emitted particles in the opposite direction. This reflector is aligned such that only the darkened side is visible from Earth, but at no point obscures KIC 8462852. This directed emission produces a small prograde thrust, causing a noticeable acceleration in the entire system, that will eventually lead to the system's escape from the gravity well of the Milky Way. Assuming constant acceleration to reach its current speed, it is believed that this "thruster" has been in operation for over a century. No information is currently known about either the creators of these megastructures, or their motivation for accomplishing a project of this scale. [Following Data Classified by O5 Council Order] ▼ RESTRICTED ACCESS: LEVEL 4 CLEARANCE REQUIRED ▼ ▲ Credentials Accepted. Full Document Access Granted. ▲ Item #: SCP-3029 Object Class: Neutralized Special Containment Procedures: Due to the events of the Peregrine-14 mission, SCP-3029 and its host star are no longer detectable through any means available to the Foundation. This fact must be concealed from all personnel below Level 4 clearance, in the interest of both preserving normalcy among the population, as well as preventing knowledge of the "Calamity" from reaching lower-ranking Foundation personnel - as this may negatively affect morale. This concealment is to be done through the use of amnestics as well as by manually editing any data produced by any relevant space telescopes. The original anomalous observations of SCP-3029 are to be replicated perfectly, to prevent the growth of civilian suspicion. Description: Unchanged from above documentation. Addendum 1: The Peregrine-14 Mission On 05/30/2018, it was decided by an 8-5 vote of the O5 Council that the potential for civilian discovery of SCP-3029 had become too significant to ignore, and that an exploration team must be sent to learn more about the anomaly. The journey of nearly 1300 ly was to be undertaken through the use of Temporal Sinks, of the design used to explore SCP-3200 in the Peregrine-9 mission eight years earlier. Peregrine-14 Logo Peregrine-14 Expedition Details Objective: Collect data regarding the nature of SCP-3029, and its creators. If possible, develop an effective containment method. Crewmembers: Denise Perez, Mission Commander; Researcher Jonathan Daniels, Ship's Engineer; and Researcher Eric Kim, Containment Specialist. Flight Details: Mission will take place from 10/01/19 to 10/22/19. Flight time using temporal sinks will occupy roughly two weeks of total mission time as measured from Earth, with a one-way flight time of seven days, during which the crew will be cryogenically frozen. This comparatively extended flight time is mainly to overcome the considerable difference in velocity between Earth and SCP-3029. Addendum 2: Peregrine-14 Audio and Text Logs Earth Date: 10/08/19 [BEGIN TRANSCRIPT] Perez: Good, this is working. Command - Daniels: Wow. thirteen-hundred light-years later. Damn, temporal sinks are cool. Perez: Shut it, Daniels - Anyway, we've all come out of Cryo just fine. The skip's visible ahead and, well… We knew it was big, but there's a difference between knowing that intellectually and actually looking at a solar array bigger than the Earth's orbit. Kim: It is pretty impressive, I've got to admit. I guess I'm supposed to figure out some kind of containment for that monster. Perez: [typing] Wow, uh, we've got some bigger problems right now. I'm looking at the diagnostics and… everything's down. I only have access to this mic, life support, and the comms systems. Everything else is offline. Daniels: Shit, really? We're awake for all of thirty seconds and everything fucking breaks? That means the reactor is offline too, so we're on backup power. Perez, shut it down. I gotta find out what's wrong here. Perez: Fair enough. Peregrine-14 signing off for now. [END TRANSCRIPT] Note that without a functioning reactor, and with only life support under power, the Peregrine-14 spacecraft's backup battery should function for at least four weeks. Earth Date: 10/18/19 [BEGIN TRANSCRIPT] Perez: Hello, Command - assuming you do actually get to hear this at some point - we're still dead in space but we think we know why. Daniels (Distant): We've got some kind of interference from the structure. Perez: Yeah. We don't know if it's just a property of the anomaly or if its creators are deliberately screwing us, but we're not going anywhere anytime soon. Daniels (Distant): This is really freaking weird. Nothing works, but I don't know why. Nothing is actually damaged, it's just… off. Just stopped. Some field or signal or whatever has just switched it all off. Kim (Distant): Anything I can do to help out? Maybe we can block it somehow. Daniels (Distant): Working on it. Not like I've just got a bunch of telekill on this ship with me. Kim (Distant): That's not how that works. That's not at all how that stuff works. Daniels (Distant): I'm sorry, I didn't realize. I'm not a containment specialist who didn't bother to bring anything useful to an anomaly the size of a fucking star system. Perez: Shut it, guys. We're here to work, not fight. Command, Peregrine-14 out. Gotta conserve power until we can actually solve this problem here. [END TRANSCRIPT] Personal Log: Jonathan Daniels

Date: 10/19/19 Drives ✔

RCS ✔

Sensors ✔

Cryo ✔

T-Sinks ✔ I've evaluated all that so far. It should all be working, it just isn't. Everything just sorta died. I came up with a few other weird things in the logs, too. We didn't wake up from Cryo because the computer shut it off. We woke up because 3029 shut it off. Drives are the same. Reverse thrust was never triggered. We just sorta stopped. Neither were the Temporal Sinks. Means bad things - this ship has been under skip control for at least the last 300 light years. We aren't actually in a proper orbit around the star either. We're stopped. Something is holding us up, keeping us from falling in. Don't know what. I'd just like to note that I don't get paid enough for this shit. One more note - I was looking out the window earlier, and I saw a new solar panel get built. It just sort of appeared, in a flash of yellow light. Dunno where it came from. Don't know how it got there. It just did. This place is kinda freaking me out, and it doesn't help that the ship is dead in space either. Got a plan though, about that last bit. Gonna tell Perez about it later. Earth Date: 10/20/19 [BEGIN TRANSCRIPT] Perez: Well, we might have something. It's a longshot, but it's something. [Perez pauses for 3 seconds] Perez: We think it's some kind of deliberate jamming. We're gonna see if we can send a signal to the Skip, try to negotiate or… something. Frankly it's not a very good plan. Daniels: I've got the communication array set up. We can try to send out a message on pretty much all radio frequencies whenever. Wait… do we actually know what we're going to say? Kim: Something simple. Maybe just list out prime numbers, let them know we're intelligent. Perez: That's a solid start. Do it. Daniels: [typing] Starting transmission. Every three seconds it spits out another number. [Silence for 10 seconds] Daniels: So, uh, how long are we doing this for? Perez: Until we get a response. [Silence for 20 seconds] Perez: This may take a while. I'm shutting off the mic until we have something to report. [END TRANSCRIPT] Peregrine-14 Broadcast: 2, 3, 5, 7, 11, 13, 17, 19, 23, 29, 31, 37, 41, 43, 47, 53, 59, 61, 67, 71, 73, 79, 83, 89, 97, ERROR: Comms remotely disabled. Earth Date: 10/20/19 [BEGIN TRANSCRIPT] Perez: Command, this is Peregrine-14. We've got some news. As of roughly, what, 30 seconds ago? Daniels: Yeah. First clue we had was that our comms failed. Something interrupted our little counting project, and given the circumstances, it's pretty clear what that was. Kim: Couple hours later the whole system just shot off into the night. The star, the skip, everything. Gone. Sadly, our cameras had all been offline since before we entered the system. We have nothing useful at all to provide. Perez: Woah. Might be wrong about that, Kim. Our hardware is all back on, as of five seconds ago. Daniels: Shit, really? What've the sensors got? Anything? Perez: Gravity's still there. Just hasn't caught up with us yet - speed of light delay. Give it a few minutes. Maybe we can figure out what happened. [Ten Minutes of Recording has been removed for Brevity] Perez: Wow, that's bizarre! I'm reading a gravitational field from the direction 3029 flew off in, for just a single tick. Looks like they Temporal Sink-ed the whole system out of here. Kim: Can they do that? Daniels: I'd assume they can, given they just did it. Bet they'd been scanning us the whole time we've been here. Think they stole the tech from us? Why build a big sail-thruster thing if you can t-sink? Perez: I don't know. It makes sense, I guess. Not much is really left to study here, though. We oughta close up shop, get going back to Earth. We're almost a week overdue as it is. Command - Peregrine-14 out. We're headed home. [END TRANSCRIPT] Addendum 3: SCP-3029 "Farewell" Transmission Upon the return of the Peregrine-14 crew to earth, a transmission received from an unidentified source was discovered within the spacecraft's data banks. Thank you for assistance us - we never developed faster than light movement and have been utilization the great Sail to escape Calamity. All other species have escaped. None willing give us assistance. Farewell. Our two species may subsequent rejoin. It is believed that the the designers of SCP-3029 reverse-engineered a knowledge of the English language, as well as their temporal sinks, using existing files within the Peregrine-14 spacecraft's data banks. Many hypotheses exist regarding the meaning of the "Calamity" referred to in this text, but none have been confirmed.

Researcher's Note: This object's file is complete, and has been uploaded to the main Foundation Database at this location. Thank you for reading! rating: 0 + x Item #: SCP-3016 Object Class: Euclid Special Containment Procedures: + EXPAND Standard Containment Procedures - COLLAPSE Standard Containment Procedures SCP-3016 must be stored within a vacuumized containment chamber that has been fitted with an array of permanent magnets capable of holding the object stationary in space, and out of contact with any solid surfaces. Two electronically actuated clamps must be installed, to be used as brakes with the aim of limiting the rotational velocity of SCP-3016 to 500 rpm. This brake must be inspected at least once per week and replaced as needed. The second clamp is to be used to limit the motion of SCP-3016 while the primary brake is undergoing maintenance. These clamps must be connected to a backup battery, capable of maintaining the operation of the clamping mechanism for at least 24 hours without power from the Site's main generator. NOTE: By Order of the Deputy Site Director, the above procedures have been discontinued. Until such time as it is safe for them to be reinstated, the temporary measures outlined below are to be utilized instead. + EXPAND Temporary Containment Procedures - COLLAPSE Temporary Containment Procedures SCP-3016 has rendered Level 7 of Site-64 uninhabitable due to extreme heat. As a temporary containment measure, all doors to Level 7 has been closed off, all elevators have been programmed to avoid stopping at the affected level, and thermal insulation has been applied in any essential stairwells passing through. All ventilation shafts connected to Level 7 must be redirected to lead outside the compound in an attempt to release the generated heat. Research into a means of reestablishing original containment is ongoing. Description: SCP-3016 is a highly-polished spinning top, appearing to be made of steel or iron due to its magnetic properties, that experiences rotational acceleration with no known force acting upon it. This acceleration varies wildly, from 0.5 rads/s2 to [REDACTED], with no recognized pattern. The source of the required kinetic energy for this to take place is unknown. SCP-3016 displays incredible durability, and while materials testing has been limited, the object has yet to receive even minor abrasion. Long-term application of a speed-limiting clamp is yet to damage SCP-3016 at all, despite the need for the clamp to be replaced ██ times since recovery. While SCP-3016 can be picked up and held immobile, it will continue to exert a torque on anything holding it in place. This torque, like the object's usual acceleration, varies wildly, and has been known to cause damage to any agent resisting it. Because of this, SCP-3016 can only be restrained for short periods of time. Addendum 1: Site 55 Containment Breach At 0855 on ██/██/████, eight of Site 55's Keter-class entities were able to breach containment, causing a failure of both primary and backup generators throughout the facility, and resulting in the loss of ██ personnel. While power was disabled, both the primary and secondary brakes restraining SCP-3016 shut down, and the object was able to accelerate uncontrollably for several hours. Upon the successful restoration of power to the facility, all escaped entities save SCP-████ had been recontained, with minimal further casualties. During the outage, all telemetry on SCP-3016 was lost. A maintenance unit consisting of two personnel is sent to look into the feasibility of restoring full containment. It is to be noted that due to the variable acceleration of SCP-3016, its rotational velocity at this point in time is unknown. Both personnel arrive at the SCP-3016 containment chamber, and reported that containment was stable, although not intact. The object was at this time suspended in space by the magnets, and it remained within a vacuum, but both clamps melted upon being engaged. Shortly thereafter SCP-████ was sighted on Level 7, and both personnel donned vacuum suits and attempted to take refuge within the SCP-3016 containment chamber. SCP-████ was able to detect the personnel, however, and managed to breach the vacuumized unit. The resulting implosion resulted in the destruction of much of the chamber itself, as well as the loss of both maintenance personnel and the apparent termination of SCP-████. Addendum 2: SCP-3016 Post-Breach Investigation At the time of the explosive decompression of the SCP-3016 containment chamber, the object had already reached an unknown, but dangerously high, rotational velocity. Within five minutes of the collapse, the ambient temperature within Level 7 had risen by 10°C, and continued to rise from that point. The Temporary Containment Procedures listed above were put into place within five hours of the final breach. Three members of MTF Beta-7 ("Maz Hatters") were called in to examine the affected floor in greater detail. This team was supervised directly by Site Director Jacob Cole. + EXPAND Audio Log: SCP-3016 Post-Breach Exploration - COLLAPSE Audio Log: SCP-3016 Post-Breach Exploration [BEGIN LOG] Alpha: Command, this is Alpha. We're on Level 7, just in front of the insulation. Command: Acknowledged. Sound off. Alpha: Alpha, check. Bravo: Bravo, check. Delta: Delta, check. We got any idea what it's like in there, Command? Command: We know it's hot in there, but not much else. CCTV and about all other sensors melted a while ago. Alpha: Acknowledged, Command. Proceeding on your orders. Command: Beta-Seven, you may proceed. Alpha: We're moving into the red zone now. Delta: I'm reading over 200 degrees Centigrade, Command. You may have a bit of a problem. Bravo: And still climbing, but pretty slowly. It's a bit hotter over that way - guess we know the skip's still where it's supposed to be. Beta-7 personnel move for several minutes, following the temperature gradient to its source. As they approach, a reddish glow is visible down one of the corridors. Alpha: We have visual on the skip, command. More or less. Bravo: Yeah, that's some intense black-body radiation. 3016 must be moving pretty quick to do that. Delta: We're actually getting pretty close to the heat tolerances on these suits. I read 400 Celsius. Alpha: We're still pretty good for a while, Delta. They can take a little past 500 before they start to break down. Bravo: Hang on a second, is that… Alpha: Looks like it. Command, we've got positive confirmation that SCP-████ has been neutralized. Delta: Wow, charred to the bone. Don't see that every day. Alpha: Which means that over there must be what's left of the chamber. Bravo: Jesus, that's bright. Command, this skip has managed to heat the air by… a lot. Guess there was a reason it was in a vacuum. Delta: My thermometer reads — Wow, it's… uh… melted, actually. We should probably head out pretty soon. Command: Beta-Seven, get out of there. Delta's right. Bravo: Hold up a second. You all read the old procedures for 3016? Alpha: 'Course we did. Bravo: Didn't they say something about a backup battery? I'm not seeing one. Command: Beta-Seven, return to base, now. Alpha: Just one more thing, Command. The battery should be right about… there. But there's just empty floor. Command: Beta-Seven, get out of there. That's an order. Alpha: Acknowledged. We've seen about all there is to see here. We're on our way out. [END LOG] After the Beta-7 team described the observed lax containment procedures in their final report, a full investigation by the Ethics Committee took place. After confirming that Special Containment Procedures had not been correctly followed, it was also discovered that several other Safe and Euclid class objects had been improperly contained as well. The Ethics Committee requested an audit of the financial records of Site 55, and discovered that a portion of the funds allocated for containment were unaccounted for. A further investigation turned up paperwork implicating Site Director Jacob Cole, who later confessed to embezzling Foundation Resources for personal gain. Director Cole was immediately removed from office, amnesticized, and released into life as a civilian with no memory of his career with the Foundation. Research into a means of restoring containment to SCP-3016 is ongoing. CCTV Capability on Level 7 has yet to be reestablished.

Researcher's Note: This object's file is complete, and has been uploaded to the main Foundation Database at this location. Thank you for reading! rating: 0 + x SCP-2649, coated in SCP-2649-A to defend against a perceived threat Item #: SCP-2649 Object Class: Euclid Special Containment Procedures: SCP-2649 must be contained within a standard animal containment chamber, and is to be provided with at least four ounces of raw meat, of any type, per day. This feeding schedule must be randomized weekly in order to minimize chances of an attempted escape by SCP-2649. Any containment chamber housing SCP-2649 must be lined entirely with ceramic tile or some other ceramic surface. Any personnel interacting with SCP-2649 are to wear boots that have been equipped with ceramic soles. Description: SCP-2649 resembles a white teapot with four pairs of mobile arachnoid legs attached at its base. The mechanism by which these legs are capable of movement is unknown, as the entity appears to be composed entirely of ceramic. The "spout" produces a highly viscous black liquid, hereafter referred to as SCP-2649-A. The entity has been observed bending over to "pour" this fluid on the ground around it, and it is capable of reabsorbing the substance as needed. Any such pool of SCP-2649-A functions as a portal - any object crossing the surface is transported to a pocket dimension in which organic matter deteriorates over time. Objects larger than the surface of an SCP-2649-A pool are not affected. No objects transported in this manner have been recovered, but radio transmissions can be received, suggesting that the portal functions in both directions. Because SCP-2649 has been observed moving any provided food into a layer of this liquid, it is believed that the pocket dimension accessed via SCP-2649-A serves as the entity's means of digestion. SCP-2649 itself cannot be transported by this fluid, and has even been known to coat itself with it as a means of defense - transporting any projectiles and small threats that make contact. Experimentation suggests that this resistance is linked not to the identity of SCP-2649, but to its material; experimentation confirms that objects composed of ceramics will not pass through a layer of SCP-2649-A. Addendum 1: SCP-2649-A Exploration Log Objective: Collect data regarding the SCP-2649 pocket dimension.

Procedure: A 500g mass of raw beef is lowered into a sample of SCP-2649-A, followed by a camera that can be accessed remotely.

Results: The camera view displays a dark expanse, with no walls or boundaries visible. Several inanimate objects are adrift, as gravity appears to be absent. All of these objects are composed of metallic or mineral substances - none are organic - and they range in size from coins and tooth fillings to metal chairs and a single six-foot I-beam. No light sources exist other than that mounted to the camera. The beef sample is visible ahead - it exhibits a greenish discoloration, and small particles are separating themselves from the surface and subsequently disappearing. After roughly fifteen minutes of this accelerated decay, the sample has vanished completely. Addendum 2: SCP-2649 Incident Log 02/17/15: SCP-2649 begins waiting near the door to the containment chamber as feeding time approaches, potentially with the aim of breaching containment. Investigation into possible learning behavior on the part of the entity is currently underway. 03/24/15: SCP-2649 has taken to depositing a layer of SCP-2649-A beneath the location its food is usually placed. At this point it is accepted that SCP-2649 exhibits learning behavior, and containment procedures have been modified to include a randomized feeding schedule. 04/10/15: SCP-2649 appears to have discovered that its containment cell is composed of cinder blocks that can be transported by SCP-2649-A. The entity had managed to remove four of them by the time the attempted breach was noticed, and SCP-2649 was transferred to a new containment chamber, lined with ceramic tile. 06/01/15: One member of D-Class personnel assigned to SCP-2649 entered the entity's containment chamber for routine feeding, and immediately fell through the surface of a pool of SCP-2649-A that had been left at the entrance. In the brief span of time in which the chamber door remained open, SCP-2649 was able to breach containment, but was recaptured quickly and with no further casualties. Containment procedures have been revised to include ceramic soles on employed footwear, in order to prevent future incidents of this type. Some site staff have expressed concerns that this was a deliberate attack on the part of SCP-2649, and research is pending regarding whether or not the entity is intelligent enough to coordinate a strategy in this way.

Researcher's Note: This object's file is complete, and has been uploaded to the main Foundation Database at this location. Thank you for reading! rating: 0 + x SCP-2597 Item #: SCP-2597 Object Class: Safe Special Containment Procedures: In order to prevent a Runaway Acceleration Event, SCP-2597 must be contained within a vacuumized containment chamber. SCP-2597 must be stored on the highest floor of Site 55, in order to minimize damage in the event of a breach. SCP-2597 is to be submerged within a container of liquid mercury, at sufficient depth that the object maintains neutral buoyancy. This is to counteract the force of gravity, and prevent the object's escape through the ceiling. SCP-2597 is not to contact the walls, ceiling, or floor of its containment chamber at any time. Any experimentation involving SCP-2597 requires written Level-3 authorization. Description: SCP-2597 is a weight, ostensibly designed for use with a balance, that behaves as though it possesses negative inertial mass. While the object's composition is unknown, it has been experimentally determined that the inertial mass of SCP-2597 is approximately -2kg, with a density roughly equivalent to that of liquid mercury at STP. As such, any force applied will result in an acceleration opposite to the initial force vector. In this way, SCP-2597 will "fall up" under the influence of gravity. Furthermore, if SCP-2597 makes contact with any object as it ascends, the force of this collision - a force opposing the movement of SCP-2597 - will only serve to increase its acceleration. In this way, SCP-2597 will break through any barriers placed in its way once it has begun to accelerate. It has been theorized that collisions with air particles at high speeds will cause SCP-2597 to accelerate uncontrollably. This would cause the object to reach dangerous speeds very quickly, and could result in harm to personnel as well as site infrastructure. Addendum: SCP-2597 Recovery Log SCP-2597 was found in an apartment belonging to known anartist ███ ██████, during investigation of his involvement in the creation of SCP-███. The object was contained at time of recovery in a large glass jar, filled with liquid mercury. Once its anomalous properties were identified, the object was given SCP classification and a member of nearby Site 55's recovery division was dispatched to recover SCP-2597. + Expand Interview Log - Collapse Interview Log Interviewed: Agent Gerald ███, part of Site 55 Recovery Team β. Foreword: Excerpt from Agent ███'s debrief, immediately after the SCP-2597 recovery. This log has been edited for brevity. <Begin Log> Interviewer: I understand you were placed in charge of recovery of SCP-2597. Agent: Well, not really. Well, at least, I wasn't at first. But you know, when the Foundation raided that anartist's home, the people there contacted the nearest site command, which happened to be 55. They sent me down to check it out. Interviewer: Tell me about recovering the object. What was that like? Agent: You know, I've worked on recovering Keters and stuff. But this? This stupid thing was one of the most annoying pieces of shit I've ever had to retrieve. Interviewer: Why, specifically? Agent: This thing… well, you can't just pick it up and carry it, it's not that simple. I figured out pretty quick - you know, given the way it resisted everything I did to it - that if I took a vehicle back to base the skip would go flying out the back window. This was before we even figured out the whole danger with air resistance. So I radioed site command to tell them I was going to take the thing back myself - I didn't really have any other options, I guess. Site 55 sent me an escort - just a couple of guards to make sure I didn't get lost or somehow killed on my way home, but they really couldn't do much that was useful. I sure wasn't gonna trust anybody else with that skip. Interviewer: You mean to say you brought it back on foot. Agent: Yeah. Had to micromanage the damn thing to a ridiculous degree. If I wanted to move it forward, I had to simultaneously push it backward and walk myself forward, as well as pushing it upwards so it didn't fall into the sky, but not so much that it pushed my hand out of the way… if that makes any sense. I got to do that for five miles. We're damned lucky the agents already at the recovery site didn't touch the skip very much - if they weren't careful we could've lost it, or worse. Hell, if I'd screwed up just a little bit… Interviewer: What exactly do you mean by "or worse?" Agent: We haven't been quite stupid enough to do any testing with regard to what happens if you just let the skip go - let it speed up and then get sped up even further by drag. First of all, it'd break anything it hits. My personal theory is - and take this with a grain of salt, I'm not exactly a scientist - that it'd start making the particles in the air fuse, cause a nuclear blast. I don't actually think it should be Safe. Consider this my official recommendation to upgrade SCP-2597 to at least Euclid Classification. <End Log> The technique used to contain SCP-2597 at its location of recovery was later implemented in the object's current containment. Agent ███'s request to upgrade the classification of SCP-2597 was denied.

Researcher's Note: This object's file is complete, and has been uploaded to the main Foundation Database at this location. Thank you for reading! rating: 0 + x SCP-2917 prior to initial containment Item #: SCP-2917 Object Class: Euclid Special Containment Procedures: Because SCP-2917 cannot be moved, Site-37 has been constructed around it. A minimum of five Class-D personnel are to be kept onsite for the purposes of investigating any locations for which unmanned exploration is deemed insufficient. All personnel charged with exploration of SCP-2917 are to undergo Advanced Decontamination before their departure as well as upon their retrieval. Individuals dispatched through SCP-2917 must be equipped with a redesigned Environmental Protection suit, modified to include pressurized containers welded to the surface to enable transport of samples without triggering a relocation event too quickly. Any individual found to have accidentally traveled through SCP-2917 is not to be followed under any circumstances, and any attempts at communication with such personnel must be through radio or other indirect means. Revision 07/15/19██: After relocation event 2917-315, no fewer than three armed security guards are to be kept onsite. Revision 12/17/19██: After Event 2917-A, the interior of SCP-2917's containment chamber is to be fitted with a reinforced carbon-carbon heat shield, and at least three meters of thermal insulation. Description: SCP-2917 is a phenomenon affecting a spherical area with a radius of two meters, at a fixed location in █████████, ██████, roughly 0.5 meters above the ground. Electromagnetic radiation such as light or radio waves, as well as any solid object that makes contact with the edge of the anomaly will be transported to a celestial body outside of our Solar System. Gases and liquids cannot traverse the boundary unassisted, ensuring constant atmospheric pressure on both connected planets. Exploration is made difficult by the tendency of SCP-2917 to relocate - once every four hours, the anomaly closes, and reopens 0.1 seconds later to a different planet. Relocation events are also triggered when two objects traverse its borders within this four-hour interval. Addendum: SCP-2917 Experiment Logs ▼ SCP-2917 Testing Log ▲ SCP-2917 Testing Log This region of SCP-2917's file is to be used to describe controlled experimentation on its properties, with particular focus on the criteria for a Relocation Event. Experiment A - 06/24/1997 Subject: A sealed 30cm container, with a 10cm rubber ball contained within.

Log: The container is launched through SCP-2917. Upon crossing its barrier, no relocation event was triggered. A second rubber ball was then launched through the anomaly to trigger relocation event 2917-33, readying SCP-2917 for another test.

Analysis: Testing implies that objects in containers only count as single objects for the purposes of creating relocation events. Experiment B - 06/24/1997 Subject: A sealed 30cm container, with 50mL of water contained within.

Log: The container is successfully launched through SCP-2917. Upon crossing its barrier, no relocation event was triggered. A rubber ball was then launched through the anomaly to trigger relocation event 2917-34, readying SCP-2917 for another test.

Analysis: Liquids can pass through SCP-2917 without incident if contained within a solid envelope. Experiment C - 06/26/1997 Subject: Two Foundation standard Remote Operated Vehicles, designated ROV-1 and ROV-2. To further establish the causes of relocation events, the two drones are connected by a tether.

Log: ROV-1 is able to cross the boundary successfully, but the anomaly closes around ROV-2's end of the tether before it is able to cross, in relocation event 2917-32. Contact with ROV-1 is lost.

Analysis: The tether was considered to be a second object. Further testing is recommended. Experiment D - 06/27/1997 Subject: One square aluminum panel, measuring 5m to a side.

Log: To test the response of SCP-2917 to a larger object attempting to cross, the aluminum panel was dropped onto the anomaly from above. Upon making contact, a relocation event was triggered, and the panel was able to fall to the ground during the brief interval in which SCP-2917 was closed.

Analysis: The standard relocation criteria do not apply to any objects larger than SCP-2917. ▼ SCP-2917 Exploration Log ▲ SCP-2917 Exploration Log This region of SCP-2917's file is to be used to describe exploration of notable planets with which SCP-2917 has connected. 06/25/1997 Subject: One Class-D, D-3612, equipped with an Environmental Protection suit, modified as described above.

Destination: SCP-2917 opened to an underground cavern dimly lit by narrow, glowing blue streams along the walls and floor. The walls are lined with small, dark-blue crystals. A yellow light is visible down one of the corridors.

Log: After decontamination, D-3612 crosses the SCP-2917 boundary as expected, and is first ordered to take samples of the luminescent fluid and crystals around the cavern. Once this is complete, she is ordered to proceed in the direction of the yellow light and identify its source if possible. As the cavern slopes uphill, the temperature begins to rise at a rate of roughly 3°C for every meter of altitude gained. Once the temperature rises above 50°C with the end of the corridor still >100m away, D-3612 is ordered to turn back, and is able to return to Earth without incident.

Analysis: Fluid samples recovered by D-3612 during this exploration were found to consist of a naturally occurring luminol solution, activated by dissolved Copper (II) Sulfate from the Chalcanthite crystals found on the cavern walls. It is thought that the source of the increasing heat was a high temperature at the planet's surface caused by proximity to its parent star. 07/10/1997 Subject: One Class-D, D-4920, equipped with an Environmental Protection suit, modified as described above.

Destination: A sandy desert, visible to the horizon on one side and broken up by narrow towers of metallic cubic crystals on the other. 0.5m-1m wide blocks of a similar metal protrude from the sand. A pale pink sky is visible above, with a cratered moon directly overhead, occupying roughly 45° in angular size.

Log: D-4920 crosses the SCP-2917 boundary as expected, and is ordered to examine the metallic objects embedded in the sand. He discovers that they are fixed in place, and strong enough that a sample cannot be removed. D-4920 is then ordered to move towards the structures visible in the distance. After several minutes of travel, D-4920 reports that the spires appear to be approaching - they are larger and closer than at the time of departure. It is at this time that researchers on earth notice that the sand on the planet appears to be receding at a small, but steadily increasing rate. D-4920 is ordered to return to Earth. During the return trip, the objects in the sand are noticeably taller, and the ground is beginning to visibly shift. At this time, the lowest point of SCP-2917 is 1 meter above the surface of the sand.

At this point it becomes apparent that the blocks in the sand are in fact the same objects as the distant spires, and that they are simply covered up by the sand in this location. The sand begins to recede more quickly, and D-4920 takes refuge on top of one of the emerging crystals. When the phenomenon stops, the surface of the sand is nearly 20m below its original position. D-4920 is then able to climb down the spire and navigate the 'forest' of towers that have been exposed. He has traveled significantly closer to SCP-2917 when the sand begins to rise once more, filling in the space between the spires. D-4920 is forced to climb one of the objects or risk being buried beneath the encroaching sand, and manages to reach the top of the tower. At this point he is ordered to wait for the sand to return to its original location before attempting to return home. Once this has happened, D-4920 is able to cross the SCP-2917 boundary successfully.

Analysis: It has been suggested that the rapid retreat and return of the sand is a result of tidal forces, magnified by the proximity of the planet's moon. This hypothesis is supported by comparisons of the moon's position in the sky with the level of the sand's surface. 07/14/1997 Subject: One (1) Class D, D-9572, equipped with a standard Environmental Protection suit. Destination: Unlike the barren surface of all previous locations, this world sustains life - the anomaly opens to a forest filled with 20-30m blue and orange bioluminescent organisms superficially resembling trees. It is nighttime, and Barnard's Loop is visible in the sky, with an angular diameter of ~30 degrees. Log: D-9572 is ordered to move through SCP-2917, and complies with some hesitation. D-9572 begins moving between the "trees" with orders to locate high ground and survey the area. After ~30 minutes of travel, with no noticeable change in elevation or terrain grade, D-9572 is ordered to climb one of the "trees" that surround him. Upon reaching the highest stable point he can reach, D-9572 reports that there is no noticeable variation in terrain, or change in elevation, for the entire distance to the horizon. It is at this point that researchers on Earth notice a disturbance in the forest - followed shortly by the arrival of five cephalopod-like organisms. The organisms approached SCP-2917, and appeared to charge at the researchers visible through it. A single creature traveled through the anomaly, triggering relocation event 2917-315. D-9572 is left behind, and contact is lost. Analysis: This expedition marks the first instance in which SCP-2917 has connected to a planet supporting life. The animal that penetrated SCP-2917 was incapable of breathing air on Earth, and quickly asphyxiated. Its dissection revealed similar body chemistry and organ structures to reptilian lifeforms, rather than the cephalopods it superficially resembled. Given the potential for a breach were a larger or more dangerous animal to exit the anomaly, containment procedures have been amended. 07/21/1997 Subject: One Foundation Quadrotor Drone, designated UAV-1.

Destination: The upper atmosphere of a gas giant, with sandy yellow clouds visible below. The sky is a pale purple color, with one M-dwarf and one G-class main sequence star visible above.

Log: UAV-1 is flown through the anomaly without incident, and performs a visual sweep of the area. A large cloud structure nearby is experiencing an electrical disturbance, and appears to be moving towards the drone. UAV-1 is quickly overtaken, and experiences extreme turbulence and some minor damage within the storm.

After several minutes, the weather clears. several dark, oblong objects are visible in the distance and UAV-1 proceeds in their direction. As the drone approaches, the group of objects is revealed to be a pod of massive, slow-moving life forms, ranging from 50-400m in length, that support themselves in the atmosphere using a bladder of gas. Each individual has a set of six 30m long "fins" extending from each side, and a pair of eyes each measuring 3m in diameter. The largest of them show tree-like organisms growing on their backs. The drone moves in, and drifts alongside the tail of one of these creatures, monitoring their behavior for several minutes. Adults tend to move lazily and with little variation, while smaller juveniles weave in and around the larger members of the pod, appearing to chase one another.

In the course of UAV-1's observations, an unique group of structures was noticed on the side of the largest member of the pod, at the base of its skull. Upon closer inspection, these structures appeared to be artificial, composed of skin from one of the animals as well as material harvested from the "trees" on their backs. The engine noise from the drone attracts the attention of the inhabitants of this small settlement. Beings resembling squid with four tentacles, each terminating in a three-fingered hand, emerge from their homes and approach UAV-1. The villagers float in the air through a similar mechanism to that of the much larger animals they live with. Three of the beings carry pointed tools fashioned from an unknown substance, possibly derived from their massive host life-forms. After the villagers and the drone observe one another for several minutes, the drone experiences an impact, and the camera pans to reveal one of the alien tools embedded in its side. Several more impacts are registered shortly thereafter, and contact with UAV-1 is lost.

SCP-2917 is allowed to relocate naturally.

Analysis: This expedition marks the first instance in which SCP-2917 has allowed contact with intelligent life, as well as the first instance of the anomaly connecting with a nonterrestrial planet. Addendum 2: Event 2917-A ▼ SCP-2917-A Event Log ▲ SCP-2917-A Event Log 12/17/1997 At approximately 0800 hours on 12/15/1997, Contact was lost with Site-37. Upon investigation, it was found that all metallic structures within the site had been melted, and all foliage within a radius of 7km had been incinerated. No survivors were found. It has been theorized that the anomaly relocated onto a planet that was very near to its sun. Because SCP-2917 transmits light easily, the heat and radiation traveling through was able to destroy Site-37 and the surrounding environment. Containment has been reestablished as of 12/28/1997, and Site-37 is currently undergoing reconstruction. In an attempt to prevent future events of this nature taking place, containment procedures have been amended.

Addendum 3: Event 2917-B Event 2917-B On 01/02/1998, D-9572 emerged from SCP-2917, and collapsed shortly thereafter. He is currently being treated in preparation for a full debrief. However, an improvised notebook composed of various types of skin and plant matter was found in one of his suit's sample containers. This notebook has been transcribed in Document 2917-B.