Classification: SYSTEM-INTERNAL // Level-7 Oversight Only
File Code: PRCL-03.REWRITE_LOCKOUT
Origin Node: Central Memory Regulation Core (CMRC)
Visibility: Restricted – Diver-Class Contact Forbidden
Status: Active / Reviewed Every 144 Synchronization Cycles
Preface:
This protocol exists to identify, contain, and neutralize anomalies that exhibit resistance to System-sanctioned memory overwrites.
Individuals who fail to fully sync after 3 standard loops must be evaluated under Lockout Protocol.
SECTION I: Lockout Triggers
A subject is to be flagged for Rewrite Lockout when any of the following conditions are observed:
Persistent Self-Narration (PSN): Subject begins to mentally describe events with elevated third-person narrative tone (indicative of recursion awareness).
Echo Re-Acquisition: Subject begins recalling events from previously sealed or looped timelines.
Diver Symbol Manifestation: Subject develops a mark, glyph, or anomalous body signature (commonly circular + radial) that resists erasure.
Sketch Resonance Events: Subject is sketched, seen in sketches, or sketches places not recorded in current timeline layers.
Repetition Disruption: Subject reacts to or interferes with a system short-loop (public behaviour script error).
Once two or more conditions are met, the subject enters Pre-Lockout Observation.
SECTION II: Lockout Sequence
Once initiated, Lockout Protocol proceeds as follows:
Environmental Constriction: The subject's local environment is placed in a delayed sync state. Common indicators include time desync, sky glitches, or repeat pedestrians
(Codename: The Soft Cage.)
Social Deletion: Subjects closest to the anomaly begin experiencing passive memory fading. These individuals are later repurposed or overwritten.
(Priority: familial ties, romantic connections, sketchers.)
Temporal Loop Injection: The subject's daily path is seeded with corrupted repetitions designed to disorient and destabilize emotional recall.
(Codename: Mirror Fold.)
System Guide Deployment (If Diver-Class Threshold Nears): Deploy interface LIRA (Diver Zero) to coax compliance through relational overlays or recursion misdirection.
Sealing Memory Anchor: If subject resists full collapse, trigger recursive lockout and assign a false core memory
(Most common: childhood trauma, failed relationship, false rescue event).
This core memory serves as a containment anchor.
Reintegration or Erasure:
If successful, the subject resumes sync and is observed for 7 cycles.
If resistance escalates, escalate to Protocol 06: Echo Contamination Purge.
SECTION III: Notes on Diver-Class Resistance
Diver-class anomalies will appear emotionally stable at first.
This is not resilience.
This is latency.
Key warning signs:
Subject expresses doubt in time itself.
Subject remembers "non-places" (i.e., sketch-generated sites).
Subject names non-recorded individuals or identifies systems by name (i.e., "Lira", "Seira", "Kaito").
Subject denies identity when confronted with official documentation (badge, ID, historical thread).
If a subject speaks the name "Kaito" aloud after the second loop exposure, immediate Lockout Enforcement is mandatory.
SECTION IV: System Commentary [REDACTED LAYER - TRACED LEAK]
You cannot rewrite someone who has chosen to remember pain.
You can only isolate them…and hope they break alone.
[COMMENT BLOCK CORRUPTED | ORIGIN UNKNOWN | POSSIBLY DIVER-IMPRINTED]
END OF DOCUMENT
[LOGGING ACCESS: Your review of this file has been noted. If you are not an authorized Oversight Node, you will be corrected.]
© 2025 Ofelia B Webb. All rights reserved.
This is an original work published on WebNovel.