SCP Foundation Secure, Contain, Protect About About Us Site Rules FAQ Licensing Criticism Policy Article Deletions Community Site News IRC Chat Authors' Pages Artist Directory Contest Archive Staff List Resources Guides Essays & Resources Wiki Syntax Sandbox Usertools Sister Sites SCP International Wanderer's Library Contact Us ≡ About About Us Site Rules FAQ Licensing Criticism Policy Article Deletions Contact Staff Community Site News IRC Chat Authors' Pages Artist Directory Contest Archive Staff List Resources Guides Search this site Search • ◦ ◦ ◦ ◦ ◦ ◦ • ◦ ◦ ◦ ◦ ◦ ◦ • ◦ ◦ ◦ ◦ ◦ • ◦ ◦ • • ◦ ◦ ◦ ◦ ◦ ◦ ◦ • ◦ ◦ ◦ ◦ ◦ ◦ • ◦ Essays & Resources Wiki Syntax Sandbox Usertools Sister Sites SCP International Wanderer's Library Create account or Sign in Getting Started Guide for Newcomers Join the Site Contribute | FAQ Universe Hub Main | Forum SCP by Series I | II | III | IV | V VI | VII | VIII | IX Other SCP Explained | Joke International Feed New Pages Shortest | Top Rated Recent Changes New Forum Posts Lowest Rated Pages Stories Tales Hub | Series Groups of Interest GoI Formats Canon Hub Discovery Artwork Hub Curated Lists Curated Tale Series Tag Search Random SCP | Tale | GOI | Art Random Page ◦ ◦ ◦ ◦ • ◦ ◦ SCP-3622 #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, 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; } rating: +83+–x Anomalous Item Entry Item #: SCP-3622 Object Class: Keter Last updated by R. Diaghilev, 31/12/2017 23:59:59 UTC. [REDACTED] Display version: Level 3/3622 [Redacted Elements: 7 | Redaction supervisor: D.
Nedjelski ten.pcs.hcrsr|ikslejden.d#ten.pcs.hcrsr|ikslejden.d ] Special Containment Procedures: Instances of SCP-3622-1 are to be contained whenever possible, through a combination of misinformation, talent acquisition, and corporate sabotage. In the event that instances of SCP-3622-1 must be taken into Foundation custody, they are to be held in temporary standard humanoid containment for 72 hours, and issued class A amnestics.
Under no circumstances are SCP-3622-1 instances to be contained together, except during testing.
In the event of SCP-3622 infection reaching unmanageable levels, instances of SCP-3622-1 are either to be acquired by the Foundation, or to be encouraged to seek employment at other organizations by Foundation agents.
Suspicions of SCP-3622 infection in Foundation software teams is to be reported immediately. All persons suspected of SCP-3622 infection are not to participate in any Agile methodology meetings, or proceedings until SCP-3622 infection is either ruled out, or wears off.
In the event of a mass outbreak of SCP-3622-1, termination is authorized in select circumstances. Please see Document SCP-3622-T-EX for circumstances and approval chain.
Prepared by Dr. D. Nedjelski, Agent R. Donnarson, 17/4/2017 11:23:51 UTC.
ten.pcs.hcrsr|ikslejden.d#ten.pcs.hcrsr|ikslejden.d, ten.pcs.ces|nosrannod.r#ten.pcs.ces| nosrannod.r Description: SCP-3622 is a memetic effect which affects computer programmers exposed to SCP-3622's infection vectors. SCP-3622 affects any human who creates, modifies, or maintains software and uses Agile development methodologies1. Affected subjects are collectively designated SCP-3622-1.
SCP-3622-1 instances will begin to introduce minor delays in any daily meetings, development processes, or productivity tools that they interact with, until said processes are brought to a complete stand-still. SCP-3622-1 will also pass SCP-3622 on to any other humans qualifying as SCP-3622-1 hosts.
SCP-3622's primary transmission occurs through a hallucinatory entity, which appears on software development teams through anomalous means. This entity takes the form of a managerial employee, usually deemed an "efficiency consultant", which creates the initial infection vector. Universally, this entity disappears within 24 hours of initial infection. Members of the software team then become instances of SCP-3622-1 and become the secondary infection vector. SCP-3622's effect is passed on by instances of SCP-3622-1 through currently unknown anomalous means.
In most subjects, SCP-3622's effects will cease to manifest after 72 hours, if isolated from other instances of SCP-3622-1. Several cases have significantly longer, or significantly shorter periods of time. All individuals showing this discrepancy have brain stem disorders or deformaties.
Prepared by Dr. D. Nedjelski, 17/4/2017 11:14:55 UTC. ten.pcs.hcrsr| ikslejden.d#ten.pcs.hcrsr|ikslejden.d Updated Effect Vector Persons with disorders affecting the brain stem were particularly affected significantly shorter (sometimes for minutes or less), until ██/██/████, corresponding to an "update" to SCP-3622. (See Addendum 4).
Attached by Dr. L. Oliviera, 22/9/2017 17:22:67 UTC. ten.pcs.hcrsr| areivilo.l#ten.pcs.hcrsr|areivilo.l Attached Addenda Discovery Report SCP-3622 was discovered on ██/██/████ when Foundation agents placed at [REDACTED] Inc. reported significantly fewer salient data points over a six week period.
Foundation assets brought the agents in under the guise of extended sabbatical.
Agents Kuthrupali and Saksena recovered from the effects of SCP-3622 after 72 hours.
The following is a transcript of an initial interview with Agents Saksena and Kuthrupali.
Interview - Initial Discovery Debrief Interviewer: Dr. S. Callaghan, Department of Psychology.
Interviewed: Agents Saksena and Kuthrupali Date of Interview: 16/6/2017, 09:22:34 UTC === Doctor Callaghan: So tell me what happened.
Agent Saksena: It all seemed so normal. Our standups were around five or ten minutes, right?
Agent Kuthrupali: Ten at the outside.
Doctor Callaghan: Right, and?
Agent Saksena: They started getting longer. Like, a lot longer. We went from giving updates, to giving code reviews, to giving in depth discussions about methodology and style. It seemed so normal, like…for real. I didn't even notice.
Agent Kuthrupali: The average got up to like…four hours. Sometimes more.
It was even worse with the git repo2. I swear, when we got pulled out, I was on page six of my referenced commit message which explained why I used the syntax I did, it was insane.
Doctor Callaghan: Any idea when it started?
Agent Saksena: Looking back, yeah. It's pretty obvious it was right around the time that Steve, at least I think his name was Steve, joined. But here's the crazy part, now that whatever the hell was going on, isn't going on, I'm really really certain Steve isn't real.
Agent Kuthrupali: I think he's right. Steve joined in September, as an… efficiency consultant? So we had to listen to them. We resisted at first, until the changes became mandatory. Then it was like, we wanted to make them.
Doctor Callaghan: What sorts of things changed other than what you've mentioned?
Agent Kuthrupali: Good example, our documentation wiki.
Agent Saksena: Christ. Yeah.
Doctor Callaghan: Mmm?
Agent Kuthrupali: Okay, so normally with software, it's like document it well enough to work, but get the work done. By the time December rolls around, I was writing two or three pages of wiki text, per ten lines of code. Like, explaining every assignment and variable name.
Agent Saksena: I can't stress this enough. It all seemed so normal.
Doctor Callaghan: Well, your brain waves show no anomalous activity. You guys'll be on leave for a few more days, then probably assigned to desk work for now.
Agent Kuthrupali: Understood. Thanks doc.
Agent Saksena: No problem, thanks doctor.
Doctor Callaghan: That's it, you can shut off the tape.
=== END OF LOG Prepared by Dr. S. Callaghan, 17/6/2017 03:22:21 UTC. ten.pcs.dem| nahgallac.s#ten.pcs.dem|nahgallac.s Effect Clarification Generally, SCP-3622 will slow down a specific team to the point where the developers will come in to work, consume resources, and produce no viable work. As reported in debriefing transcripts, this slow down will not seem out of the ordinary to instances of SCP-3622-1.
Extended observation of SCP-3622 and SCP-3622-1 instances at Bond Street LLC have produced several examples of SCP-3622 behaviors: Daily meetings (commonly referred to as "standups") to discuss progress on ongoing software projects increase in duration steadily. Average duration increase is between 7 and 12 minutes per week, and appears to have a final duration of a maximum of eight hours.
Issue tracking descriptions growing increasingly complex, and implementing arbitrary rules for style.
Version tracking complexity increasing until general codebase changes are near, or total zero.
Documentation requirements sharply increasing for arbitrary reasons, which are rapidly abandoned.
Prepared by Agent Saksena, 15/8/2017 02:14:27 UTC. ten.pcs.ofni| aneskas.a.a#ten.pcs.ofni|aneskas.a.a Escalation of Effects and Confirmed Use of SCP-3622 On ██/██/████ the Foundation intercepted a mass email to several organizations (see Document-3622-1) confirmed to be using SCP-3622, regarding installation and setup instructions for a new version of the SCP-3622 software.
According to the attached email, the effects of SCP-3622 have been changed and intensified. See text below: Intercepted Email To: Valued Clients <g=clients_list> From: Mike Summers <moc.seigolonhcetffonedel| sremmusm#moc.seigolonhcetffonedel|sremmusm> CC: Ledenoff Sales <moc.seigolonhcetffonedel| selas#moc.seigolonhcetffonedel|selas>, WACS Support <moc.seigolonhcetffonedel|troppus.scaw#moc.seigolonhcetffonedel| troppus.scaw>, QUQA Dev Ops <moc.seigolonhcetffonedel| • • • • tsid_spo_ca_uq#moc.seigolonhcetffonedel|tsid_spo_ca_uq> Hey all, this is Mike, As we promised, we're releasing version 2.2.7 this weekend. Please shut down your clusters, and make sure that ports 22, 80, and [REDACTED] are open to our servers, as the upgrade will only work if it's verified through our servers on port [REDACTED].
We're really excited about this one! Issue tracking is always a hassle in the end, haha! We've also fixed a few nasty bugs, most significantly an edge case which nearly negated Quaesturas™ benefits in certain circumstances.
Thanks for the great bug reports, guys!
If anyone still hasn't upgraded their cluster software or hardware from the last version, please email us for support immediately. Your support contract will expire without updated hardware!
Thanks again for being loyal Quaesturas™ customers.
We look forward to your continual support and patronage.
Mike Summers, CEO Ledenoff Technologies After this email was intercepted, observations at [REDACTED] Inc. showed additional instances of SCP-3622-1 throughout multiple locations belonging to their competitors, apparently spread through the target's issue tracking software. Additional investigation into instances of SCP-3622 at other organizations showed the same patterns, indicating this "upgrade" to the "Quaesturas" software expanded its anomalous effect significantly.
Most significantly the original timing discrepancy found in subjects with brain stem disorders was no longer observed.
Prepared by Technician B. Solano, 15/8/2017 09:14:55 UTC. ten.pcs.ved| onalos.b#ten.pcs.ved|onalos.b Initial Contact with Potential GoI/PoI Ledenoff Technologies is incorporated in Wilmington, Delaware, within the United States.
Foundation agents approached the organizations registered business address under the guise of a Foundation shell company, with overtures to purchase the software and hardware components which cause SCP-3622. Foundation Agents were dispatched to their corporate headquarters in Toronto, Canada. After six hours within the office building, contact with the agents was lost.
Six minutes after loss of contact, an email was sent to the shell corporation email server.
Attached is the text of the email received: Email Received by Foundation To: Daniel Kaber <moc.noidlaks|22rebakd#moc.noidlaks|22rebakd> From: Mike Summers <moc.seigolonhcetffonedel| sremmusm#moc.seigolonhcetffonedel|sremmusm> CC: Ledenoff Sales <moc.seigolonhcetffonedel| selas#moc.seigolonhcetffonedel|selas>, Skaldion Distributed <moc.noidlaks| tsid_ks#moc.noidlaks|tsid_ks> Hey there, Mike here, I'm sure we can come to some kind of agreement here, but you're gonna have to get serious.
Our technology is the real deal. If we could give you a client list (which we can't, of course, haha), you'd be shocked at the names on it. Everyone uses us!
Unfortunately, we have a strict no-proxy policy with our clients. If your "Foundation" would like to acquire a Quaesturas™ cluster, we're more than willing to negotiate. Keep in mind however, we have a very strict usage limit for the Quaesturas™ cluster technologies. We expect all of our clients to keep it to a reasonable level, and will intervene if we feel this technology is being abused.
Our basic plan will require the following in terms of physical space for the hardware: [Link redacted. Link leads to a PDF document with space, and power requirements for computer hardware].
Additionally, you'll need to provide space for at least three Quaesturas™ key- men on site. Each will require the following dietary regimine, through a feeding tube: [Link redacted. Link leads to a PDF document with dietary guidelines for what appeared to be three anomalous individuals].
Our basic plan starts around $22 Million, but we can probably negotiate a bulk discount considering the size of your organization!
We have higher plans available of course, and custom solutions are available.
Reach out to us at moc.seigolonhcetffonedel| selas#moc.seigolonhcetffonedel|selas if you're interested!
Looking forward to hearing from you.
Mike Summers CEO Ledenoff Technologies P.S. Your corporate goons are back at home! They'll be fine.
Agents Danvers and Callavatra were found in their homes with no memory of their time in the Ledenoff Technologies offices.
Foundation agents infiltrated the Ledenoff Technologies office building, but discovered no evidence of Ledenoff technologies within the building. The office space registered to the corporation was unoccupied, but still paid monthly by a registered Ledenoff Technologies account.
Power and internet usage for the building included a large portion going to the 17th floor, which was registered to Ledenoff Technologies.
Surveillance of the entrance to the building has proven non-viable, as to date, no employees of Ledenoff Technologies have been identified other than "Mike Summers", the apparent CEO.
Mike Summers (designated PoI-████) graduated from Carnegie Mellon University in 2002, with a Bachelor of Science degree in Computer Science. Foundation agents raided the registered address of Mike Summers in Toronto; however, the apartment appears to have been abandoned for some time.
Mike Summers was reported missing from 2003 to 2006. Several sightings were made in Sochi, Russia, as well as the Balkan Region around this time. Ledenoff Technologies was founded by Mike Summers in 2007. According to incorporation records, two names were on the original ownership forms. The original copies of these forms were lost during the switch to an electronic tracking system for the incorporating entity in 2008. Amended ownership forms only list Mike Summers as the owner and CEO of Ledenoff Technologies. Passport records indicate that an individual listed as "K. Ledenoff" was recorded as entering Canada with Mike Summers in 2007.
Information regarding K. Ledenoff can be forwarded to Director Stephenson. At this time, it is believed that K. Ledenoff is a potential PoI, due to their potential involvement in [ REDACTED ]3.
Last updated by R. Diaghilev (REDACTION PROTOCOL CHANGED)3, 31/12/2017 23:59:59 UTC. [REDACTED] Prepared by Agent Saksena, 15/10/2017 14:41:16 UTC. ten.pcs.ofni| aneskas.a.a#ten.pcs.ofni|aneskas.a.a Footnotes 1. Agile methodologies include Scrum, Extreme Programming, Kanban, etc. Additional information can be found in common reference material 2. Git repositories are a standard tool for storing code in a centralized way in order to maintain coherent version control for a software system. Code is stored in the git repo in various versions, with all developers able to reference it globally.
« SCP-3621 | SCP-3622 | SCP-3623 » ‡ Licensing / Citation Cite this page as: "SCP-3622" by DrMagnus, from the SCP Wiki. Source: https://scpwiki.com/ scp-3622. Licensed under CC-BY-SA.
For information on how to use this component, see the License Box component. To read about licensing policy, see the Licensing Guide.
Filename: N/A Name: SCP Foundation Emblem Author: N/A License: CC BY-SA 3.0 Source Link: SCP Foundation Wiki _licenseboxalchemy-departmentauditorycognitohazardhallucinationketermemeticmind- affectingscpvisual page revision: 19, last edited: 29 Apr 2022 20:03 Edit Rate (+83) Tags Discuss (49) History Files Print Site tools + Options Edit Sections Append Edit Meta Watchers Backlinks Page Source Parent Lock Page Rename Delete Help  | Terms of Service  | Privacy  | Report a bug  | Flag as objectionable Powered by Wikidot.com Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License Click here to edit contents of this page.
Click here to toggle editing of individual sections of the page (if possible). Watch headings for an "edit" link when available.
Append content without editing the whole page source.
Check out how this page has evolved in the past.
If you want to discuss contents of this page - this is the easiest way to do it.
View and manage file attachments for this page.
A few useful tools to manage this Site.
See pages that link to and include this page.
Change the name (also URL address, possibly the category) of the page.
View wiki source for this page without editing.
View/set parent page (used for creating breadcrumbs and structured layout).
Notify administrators if there is objectionable content in this page.
Something does not work as expected? Find out what you can do.
General Wikidot.com documentation and help section.
Wikidot.com Terms of Service - what you can, what you should not etc.
Wikidot.com Privacy Policy.
