SCP-5496
#page-content .collapsible-block { 
    position: relative;
    padding: 0.5em;
    margin: 0.5em;
    box-shadow: 2px 1.5px 1px rgba(176,16,0,0.7), 0 0 0px 1px lightgrey;
    overflow-wrap: break-word;
}
 
.collapsible-block-unfolded{
    color: black;
    overflow-wrap: break-word;
 
}
 
.collapsible-block-unfolded-link {
    text-align:center;
}
 
.collapsible-block-folded {
    text-align: center;
    color: dimgrey;
}
 
.collapsible-block-link {
    font-weight: bold;
    color: dimgrey;
    text-align: center;
}
 
.addendumbox {
    padding: .01em 16px;
    margin-bottom: 16px;
    margin-top: 16px;
    padding-bottom: 1em;
    box-shadow:0 2px 5px 0 rgba(0,0,0,0.16),0 2px 10px 0 rgba(0,0,0,0.12);
}
 
.material-box {
    padding: .01em 16px;
    margin-bottom: 16px;
    margin-top: 16px;
    padding-bottom: 1em;
    border: 1px lightgrey solid;
    box-shadow: 1px 2px 2px 0 rgba(0,0,0,0.16);
}
 
.material-box blockquote {
    border: 1px double #999;
}
 
.wiki-content-table {
    width: 100%;
}
 
.addendumbox blockquote {
    border: 1px double #999;
}
 
.addendumtitle {
   opacity: 0.8;
   margin-bottom: 10px;
   color: #b01;
}
 
.maintitle {
   margin-bottom: 10px;
   color: black;
}
 
.scp-header {
    text-align: center;
    font-size:x-large;
    color:#b01;
}
 
.addenda-header {
    width: 100%;
    border-bottom: 2px black solid;
    color: black;
}
 
.scp-info {
    display:flex;
    justify-content:space-between;
    font-size:large;
}
 
.scp-info-box {
    display:flex; 
    justify-content:space-between;
}
 
.object-info {
    color:black;
    align-self: flex-end;
    font-size: large;
}
 
.title-style {
    opacity: 0.8;
    margin-bottom: 10px;
    color: #b01;
    font-size: large;
    text-decoration: underline;
    font-weight: bold;
}
 
.update-div-empty {
    text-align: right;
    font-size: x-small;
    color: lightgrey;
}
 
.update-div {
    text-align: right;
    font-size: x-small;
}
 
.computed {
    border: 1px black solid;
    width: 50%;
    display: inline-block;
text-align: left;
    padding: 3px;
}
.computed:before {
    content:"Computed Code";
    font-weight: bold;
border-bottom: solid 1px black;
width: 100%;
}
.rawcode {
    border: black solid 1px;
    width: 50%;
    display: inline-block;
text-align: left;
    padding: 3px;
}
.rawcode:before{
    content:"Raw Code";
    text-align: center;
    font-weight: bold;
border-bottom: solid 1px black;
width: 100%;
}
.codebox {
    display: inline-block;
    width: 100%;
    text-align: center;
}
.yui-navset .yui-nav .selected a em,  .yui-navset .yui-nav a em{
        padding: 0.25em .75em; 
        top: 0px;
        margin-bottom: 0px;
}
.yui-navset .yui-nav .selected a {
     background: gray;
}
.yui-navset .yui-nav .selected {
       margin: 0px;
}
.yui-navset .yui-nav .selected a, .yui-navset .yui-nav .selected a:focus, .yui-navset .yui-nav .selected a:hover, .yui-navset .yui-nav .selected a {
         background: gray;
}
.yui-navset .yui-nav a:hover,
.yui-navset .yui-nav a:focus {
    background: gainsboro;
    text-decoration: none;
}
.yui-navset .yui-nav a, .yui-navset .yui-navset-top .yui-nav a {
background-color: none;
background-image: none;
}
.yui-navset .yui-nav a {
background: none;
}
.yui-navset .yui-nav li{
margin: 0px;
}
 
#page-content .licensebox .collapsible-block {
    position: unset;
    padding: unset;
    margin: unset;
    box-shadow: unset;
}
 
.licensebox .collapsible-block-unfolded{
    color: inherit;
}
 
.licensebox .collapsible-block-unfolded-link {
    text-align: left;
}
 
.licensebox .collapsible-block-folded {
    text-align: left;
    color: inherit;
}
 
.licensebox .collapsible-block-link {
    color: inherit;
    text-align: left;
}
/* source: http://ah-sandbox.wikidot.com/component:collapsible-sidebar-x1 */
 
#top-bar .open-menu a {
        position: fixed;
        top: 0.5em;
        left: 0.5em;
        z-index: 5;
        font-family: 'Nanum Gothic', san-serif;
        font-size: 30px;
        font-weight: 700;
        width: 30px;
        height: 30px;
        line-height: 0.9em;
        text-align: center;
        border: 0.2em solid #888;
        background-color: #fff;
        border-radius: 3em;
        color: #888;
}
 
@media (min-width: 768px) {
 
    #top-bar .mobile-top-bar {
        display: block;
    }
 
    #top-bar .mobile-top-bar li {
        display: none;
    }
 
    #main-content {
        max-width: 708px;
        margin: 0 auto;
        padding: 0;
        transition: max-width 0.2s ease-in-out;
    }
 
    #side-bar {
        display: block;
        position: fixed;
        top: 0;
        left: -20em;
        width: 17.75em;
        height: 100%;
        margin: 0;
        overflow-y: auto;
        z-index: 10;
        padding: 1em 1em 0 1em;
        background-color: rgba(0,0,0,0.1);
        transition: left 0.4s ease-in-out;
 
        scrollbar-width: thin;
    }
 
    #side-bar:target {
        left: 0;
    }
    #side-bar:focus-within:not(:target) {
        left: 0;
    }
 
    #side-bar:target .close-menu {
        display: block;
        position: fixed;
        width: 100%;
        height: 100%;
        top: 0;
        left: 0;
        margin-left: 19.75em;
        opacity: 0;
        z-index: -1;
        visibility: visible;
    }
    #side-bar:not(:target) .close-menu { display: none; }
 
    #top-bar .open-menu a:hover {
        text-decoration: none;
    }
 
    /* FIREFOX-SPECIFIC COMPATIBILITY METHOD */
    @supports (-moz-appearance:none) {
    #top-bar .open-menu a {
        pointer-events: none;
    }
    #side-bar:not(:target) .close-menu {
        display: block;
        pointer-events: none;
        user-select: none;
    }
 
    /* This pseudo-element is meant to overlay the regular sidebar button
    so the fixed positioning (top, left, right and/or bottom) has to match */
 
    #side-bar .close-menu::before {
        content: "";
        position: fixed;
        z-index: 5;
        display: block;
 
        top: 0.5em;
        left: 0.5em;
 
        border: 0.2em solid transparent;
        width: 30px;
        height: 30px;
        font-size: 30px;
        line-height: 0.9em;
 
        pointer-events: all;
        cursor: pointer;
    }
    #side-bar:focus-within {
        left: 0;
    }
    #side-bar:focus-within .close-menu::before {
        pointer-events: none;
    }
    }
}

rating: +44+x

Item#: SCP-5496
Level3
Containment Class:
euclid
Secondary Class:
truculent
Disruption Class:
keneq
Risk Class:
caution

Special Containment Procedures: Until such time that more effective and permanent containment methods are formulated and implemented, video monitoring should be maintained around the current location of SCP-5496 within Site-431 at all times. Any staff found utilizing SCP-5496 in any way, unless explicitly authorized otherwise, are subject to immediate debriefing and possible disciplinary action. Should any anomalous activity characteristic of likely SCP-5496 usage be observed by staff, it should be immediately reported to their superiors, Site-43 administration, and/or members of the SCP-5496 research team.2

No feasible methods of long-term physical containment are currently known, due to factors such as SCP-5496’s penchant for spontaneous translocation to other locations around the site if it becomes sufficiently obstructed from access by members of site staff; its super-durability against all forms of material damage tested so far; and the inability to maintain visual warnings or messages advising against use within the vicinity of SCP-5496 itself. As such, current containment tactics primarily center on recurring instruction to all on-site staff of the properties and dangers posed by SCP-5496. However, any potential paths to formulating workable methods to contain SCP-5496 through its isolation from the rest of Site-43 and its staff or neutralization of its anomalous properties remain the subject of ongoing research and testing.3

Individual Foundation personnel of sufficient clearance may submit containment and testing proposals to the SCP-5496 research team for review. While this file has been given a default clearance level of three for all other sites and posts, all Site-43 employees have been given special provisional level 1/5496 clearance to view the bulk of this file. All employees are to read this file at least once, and to be proactively apprised of any significant updates as necessary. Additionally, monthly weekly reminders are to be given to all Site-43 staff that any complaints, issues, or suggestions relating to perceived issues with some aspect of their workplace environment are to be directed through the appropriate channels via Hiring and Regulation; and that there is not now, nor has there ever been, any sort of officially sanctioned Site-43 “Suggestion Box.”

Description: SCP-5496 is a small box found affixed to various walls from all around the interior of Site-43 since its sudden appearance on February 12, 2022, with the words “Suggestion Box” prominently displayed across the front, and a smaller inscription written on its right side:

Hello, Foundation staff! Here at Site-43, we strive to push boundaries and incorporate novel and non-traditional strategies in our perpetual mission of Securing, Containing, and Protecting anomalies from the world and the world from anomalies. However, there's always room for improvements, so we'd like to hear your ideas, fellow Foundationers! Just fill out a slip, drop it in, and your concerns shall be addressed as quickly as possible!

- Chief Administrator Karen T. Hellstorm4

Suggestion_Box.JPG

SCP-5496.

Whenever these instructions are followed, a unique anomalous event will occur based on the contents of the submitted “suggestion.” The exact nature and effects of such incidents vary, but almost always involve "granting" the submitted requests primarily in senses that honor the letter of the request in an overly literal, exact, or unusual manner, while paying little to no consideration to the intended meaning itself. These requests vary in their utility to the triggering user, providing them with some overall benefit at least as often as any detriment. At the same time, particular effects almost invariably detract from broader Site-43 operational efficiency, capacity, and/or security.5

SCP-5496 itself is made of an unknown, extremely durable material visually reminiscent of rusted metal. Small pencils and slips of paper are also present next to a horizontal opening at the top.6

Discovery: SCP-5496 was unwittingly “discovered" and utilized by a number of staff over a three-day period; namely, staff who did not initially recognize its anomalous properties or a potential connection to the recent major increase in the number of on-site accidents, technical failures, and maintenance issues. Most staff outside of either the Quantum Supermechanics or the adjacent Research and Experimentation sections, including those in Hiring and Regulation and administrative positions, remained initially unaware of the appearances of SCP-5496. It wasn't until the morning of February 14, 2022, that any staff members directly noted the apparent anomalous results which followed submissions to SCP-5496. Dr. Xinyi Du, Chair of Quantum Supermechanics, reported the appearance of SCP-5496-1 and his team's suspicions of its anomalous nature. A video log is available below;


Addendum 5496.01: Activation Incidents


Initial incidents later linked to SCP-5496 usage were determined via cross-reference with security footage of the room where SCP-5496 initially appeared, and questioning of staff seen using SCP-5496 as to exact requests when necessary.

Additionally, even since the implementation of site-wide warnings and explicit instruction against the usage and activation of SCP-5496, several instances of staff doing so anyway have occurred since. Approved examples are outlined below.

Note: Only one Foundation employee (Jr. Researcher Phil Grady) has admitted to deliberately ignoring warnings. Other users have almost universally claimed to have forgotten the instructions against use. Investigation into such claims is ongoing, especially as a potential indication of previously-undiscovered antimemetic and/or infohazardous secondary properties related to SCP-5496.


Addendum 5496.02: Previous Containment Strategies


The following is a running log summarizing prior SCP-5496 containment strategies and the results of their attempted implementations. This log may be updated as necessary should current tactics be found insufficient, and modified accordingly at any point in the future.


Addendum 5496.03: D-Class Incident


Background: On March 11, 2022, a member of maintenance staff moved a large potted plant from beside SCP-5496’s contemporaneous location to directly in front of SCP-5496, in order to vacuum the area underneath. This apparently exceeded SCP-5496’s obstruction threshold, as the instance translocated immediately after. After moving the plant back and noticing the absence of SCP-5496, the employee alerted his superiors, and search for its new location began.

For two days, despite intensive search, the object could not be located, until Dr. Eileen Vaskaar of the Identity and Cryptotechnography Department reported that SCP-5496’s new location had been determined (further information on its rediscovery is restricted to Level 5 clearance due to its inherent information security concerns).

Shortly after its rediscovery and the intentional triggering of SCP-5496's translocation property, it was quickly identified to have moved to Security and Containment Area 4b in the first sublevel of Site-43, where it currently remains.

At 4:34 PM on March 14, 2022, an unrequested allotment of eight D-Class Personnel arrived at Site-43.13 Despite this, available records confirmed the request for and approval of this D-Class allotment, and its redirection from the original destination of Provisional Site-███

The anomalously redirected D-Class were moved to a more securable area within the topmost sublevel, while a quickly organized internal investigation traced the modification of the D-Class request and destitnation records to shortly after SCP-5496's March 11 relocation event.

Four site security officers led the D-class to their ad-hoc, temporary housing area that was arranged to hold them until their situation was straightened out internally, and the D-class once again transported to a new site. Unfortunately, neither security staff nor those particular members in Hiring and Regulation that had been placed in charge of arranging accommodations had yet been alerted to SCP-5496’s current location, and allowed the new D-Class to enter into the same hall in which the object now resided.

During this time, one of the D-Class was later observed via security footage to have made two submissions to SCP-5496, which are outlined below along with their respective effects.

As the accompanying internal security agents were all conversing amongst one another across the room at this time (with none actually facing the D-class they were ostensibly guarding), they failed to directly witness the event. The only in-person witness was Dr. William Wettle, who had somehow gotten lost again on the way back to his office after lunch.16 Dr. Wettle reported wondering into the hall and seeing "ten D-class just disappear out of thin air".17 causing him to jump back and trip over a stray chair in shock, leading to a twisted ankle and fractured hip.

Debriefing took place from his medical bed, but was ultimately deemed of minimal value upon confirmation of much more reliable video footage capturing the event. Dr. Wettle has since made a full though slow-going recovery from his injuries, with only modest-to-moderate complications.

D-04576 was successfully relocated from Site-43 on March 15, 2022, where he remained prior to his expiration on March 18, 2022 as a natural result of his assigned research duties his new Site. The rest of the D-Class contingent's current whereabouts remain unknown at this time. Foundation efforts since the incident at identifying and recapturing these individuals, who are now considered to have effectively escaped Foundation custody, have failed up to this point. Attempts at discovering any evidence of any additional anomalous effects related to their disappearance, or the exact wording and/or nature of the triggering SCP-5496 submission, are ongoing.


Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License