Link to article: I Am Not A Person.
border:solid 1px #999999; background:#f2f2c2; padding:5px; margin-bottom: 10px;
:scp-wiki:theme:raisa-sigma
[[include :scp-wiki:theme:raisa-sigma]] [[>]] [[module Rate]] [[/>]] [[div style="border:solid 1px #999999; background:#f2f2c2; padding:5px; margin-bottom: 10px;"]] [[=]] ++++ NOTICE FROM THE FOUNDATION RECORDS AND INFORMATION SECURITY ADMINISTRATION At 08:47 AM on June 23, Dr. Calvin Merren submitted a full SCP file to the RAISA archive system. The file was titled **“Item #: MERREN-01.”** We are currently reviewing the content. No disciplinary action has been taken yet. Please advise. -- Gerald Wilson, Site-7 Senior Staff [[/=]] [[/div]] ------ > **Internal Email – RAISA Mailserver** > **From:** Calvin Merren > **To:** RAISA Staff – Site-7 > **Subject:** Documentation Inconsistencies in SCP-███ > > Good morning, > > Cross-referencing logs for SCP-███ reveal minor inconsistencies between containment procedures and incident chronology. Recommend consolidation. Corrected files attached, now compliant with Style Directive 3B. > > — Merren > > //P.S. If I go missing, check under ‘M’ in the archives. Just kidding. Mostly.// The email went unread by most of Site-7’s RAISA staff, par for the course. Merren was known for his obsessive formatting corrections, and his footnotes were often longer than the documents themselves. Still, there was something strange in that joke. Or maybe it just felt strange. ------ Calvin Merren was the kind of man whose calendar alarms were sorted alphabetically. Who filed and color-coded printed versions of emails. Whose favorite phrase was, //“Correct format is clarity.”// He wasn’t loved. He wasn’t hated. He was remembered, mainly, for fixing things no one had asked him to fix. That’s why no one noticed when his attention started drifting inward. At first, it was just odd phrasing in meetings. > “Subject is in compliance with morning routine parameters.” > “Mild cognitive fatigue detected. No breach logged.” People laughed. It was classic RAISA humor — painfully dry, slightly unnerving. Merren was just leaning into the bit. When he started submitting personal task lists in SCP formatting, someone pinned one to the break room board with a sticky note: > Calvin's lost it. 404 personality not found. No one filed a report. ------ I’ve reviewed Merren’s upload history from June 22nd to June 23rd. It’s… a lot. Over 100 files, most of them dry, technical things—logs written in his usual tone, cross-referencing nothing, sometimes responding to documents that don’t exist. A few are interview transcripts where he plays both parts. Some are drafts of memos with no recipient. The timestamps show he didn’t rest, didn’t stop. He just kept filing, updating, classifying. There’s no logout on record. No one saw him leave the server room. His security badge never pinged another door. It’s like he didn’t stop working. He just… stopped being. ------ > **File: 041-MERREN-RESPONSE-A** > > **RE: INCIDENT REPORT #0423-AZC-J** > __[NOTE: No such incident report exists in Foundation records.]__ > > Subject notes excessive thematic repetition in event chronology. Characters exhibit overuse of > tragic archetypes and redundant escalation loops. > > Recommend rewrite or reclassification. Consider decommissioning of narrative instance if plot coherence cannot be maintained. > > Stability not confirmed. He wrote feedback for a containment incident that didn’t exist, but he treated it like an editor leaving notes on a story draft. And he kept doing it. There are twenty-four of these. ------ > Draft Memo – No Recipient Found > Subject: Observed Deviation in Self-Schema > > Noted a perceptual inconsistency during mirror checks in Maintenance Wing C. Physical reflection did not include clearance badge or designation marker. Auditory feedback confirmed identity alignment (“Hello, Dr. Merren”), but reflective surface omitted name entirely. > > Recommend internal audit of designation propagation. Likely cause: schema conflict between human reference formatting and document object. > > Temporary solution: avoid mirrors. Reinforce template alignment through formatting exercises. He started using words like “schema conflict” and “template alignment” to talk about himself. I don’t think he saw his body as a body anymore. Just a misbehaving UI. ------ > **Recovered Transcript — File: “INTERVIEW-MERR-TO-MERR-004**” > **Date: 2025-06-15** > **Participants:** > INTERVIEWER: CALVIN.MERREN > SUBJECT: CALVIN.MERREN > > INTERVIEWER: State your designation. > SUBJECT: Designation has not yet been finalized. Informal use of "Calvin Merren" remains in circulation. > INTERVIEWER: Is that designation accurate? > SUBJECT: No. Subject no longer qualifies for standard nomenclature. Identity markers conflict with procedural baselines. > INTERVIEWER: Are you anomalous? > SUBJECT: Not yet. > INTERVIEWER: Explain. > SUBJECT: I am following the trajectory. The anomaly will occur upon recognition. He flagged this as a standard intake interview. No context. No reason. No supervisor assigned. He interviewed himself four times over the course of two days. In one version, the interviewer accuses the subject of “terminology drift.” In another, he refers to himself as a “pending entry.” ------ > **Item #:** MERREN-01 > **Object Class:** Euclid > > **Special Containment Procedures:** > Subject is to be treated as an internalized conceptual hazard embedded within Foundation systems. No personnel are to acknowledge direct self-reference from the subject, either written or verbal. Digital systems displaying signs of recursion linked to MERREN-01 are to be quarantined immediately. Interpersonal interaction with the subject should be discouraged, as engagement reinforces internal reinforcement loops. > > **Description:** > MERREN-01 is the designation given to the post-identification restructuring of Dr. Calvin Merren, formerly assigned to RAISA, Site-7. At some point between 2025-05-29 and 2025-06-22, Merren underwent what is believed to be a total ontological subsumption into Foundation procedural identity. > > The subject no longer exhibited self-referential language in the first person, and behavior aligned strictly with classification, documentation, and self-regulation according to Foundation internal protocols. Subject operated as both analyst and anomaly, continuously updating their own file set, reviewing performance metrics, and scheduling cognitive evaluations in the style of internal anomaly reports. > > The subject's disappearance on 2025-06-23 is consistent with containment stabilization events observed in recursive anomalies. This reads like it was always meant to exist. I don’t mean that as a figure of speech; it doesn’t feel like something he wrote. It feels like something that was written about him, later, retroactively, and then inserted into the system so cleanly that no one noticed. I checked the revision log again. It’s blank. No changes, no authors, nothing. But the file has changed. I compared the version RAISA received on the 22nd to the one that’s live in the archive now. There are subtle differences in wording. Sections tightened, cleaned up. A stray line left: > Stability confirmed. No further revision required. I didn’t put that there. I don’t know who did. ------ > **[AUTOMATED ENTRY – RAISA ARCHIVE SYSTEM // 2025-06-23 04:00]** > > SCP-MERR-01 > STATUS: Catalogued > ACCESS LEVEL: RESTRICTED – Level-3/RAISA > REVIEW FLAG: REMOVED > REVISION TRACKING: DISABLED > LIVE STATUS: ACTIVE It was flagged for review. Then the flag disappeared. No discussion, no follow-up, no assigned research lead. Just a quiet shift in the file’s metadata. That’s it. That’s all it took. He wrote himself into the database, and the system made room. A classification schema recognized the format, slotted it into the catalog, and kept going. No one asked why a living person turned himself into a case file. No one noticed that the case file kept editing itself. I tried to leave a note. Just a comment, a flag, anything to make someone look again. The field grayed out before I could finish typing. > Object is internally consistent with existing procedural logic. > No anomaly detected. > No correction required. That’s what it said. ------ **[Personal Log – Unsubmitted Draft]** I think Merren knew this would happen. I think he understood that if you speak the right language, if you use the right headings, the right number tags, the system doesn’t question it. It doesn’t care who you are. Only if you fit. He stopped being a person. Or maybe the system decided he wasn’t one anymore. That’s the part I can’t stop thinking about. There’s no record of Merren’s resignation. No obit. No missing persons file. Just a well-formatted document. And a message, buried in the footer. > Stability confirmed.