Per 
- Temporal Contingency
- Temporal Contingency Escalation
- Temporal Contingency Escalation Draft 2
- Temporal Contingency Escalation Draft 3
Item #: SCP-XXXX
Object Class: Euclid
Special Containment Procedures: Live SCP-XXXX instances are to be captured in kinetic-gravitational temporal dilators1. Instances are to be stored inside until the death of the SCP-XXXX entity, the death of SCP-XXXX-A, or activation of recursive diachronic protocol.
SCP-XXXX-A is to be examined for any data stored within its body, interrogated, and amnesticized. SCP-XXXX-A is to be monitored until death or activation of recursive diachronic protocol.
Description: SCP-XXXX is a short lived species of humanoid each of which hunts a given human being, henceforth designated SCP-XXXX-A.
Instances are pale white humanoids lacking all facial features with single sharp hoof-like nails in place of hands. SCP-XXXX instances have a 24 hour life span during which they age and grow rapidly. Height ranges from one meter at generation to 3 meters upon death. Strength and intelligence increase throughout the first 23 hours of an instances lifespan. Instances rapidly deteriorate during the last hour of their life span. SCP-XXXX instances spontaneously generate at the beginning of their life and disintegrate upon death.
During the 24 hour period, SCP-XXXX will hunt SCP-XXXX-A. If SCP-XXXX-A dies, SCP-XXXX will immediately disintegrate. However, if the target survives all 24 hours of SCP-XXXX's life span or SCP-XXXX is killed, the target will be returned to the beginning of the 24 hour period with all injuries and memories remaining2. This loop continues inevitably until SCP-XXXX-A's death.
Special Containment Procedures uses artificial time dilation to extend the life span of SCP-XXXX until the natural death of SCP-XXXX-A.
Addendum: Diachronic Recursive Protocol
SCP-XXXX can be used to transmit data to the past with project overseer O5 approval.
To do so, an SCP-XXXX-A of a time dilated SCP-XXXX instance, is to be inserted with a data storage device. Then, SCP-XXXX is to be killed, sending SCP-XXXX-A back to the beginning of his time loop. The foundation can then retrieve the data during containment.
All information sent to the past should include data on SCP-XXXX itself. On average, a 5 percent increase in the occurrence of SCP-XXXX instances is observed in the new timeline relative to the recorded data.
Item #: SCP-XXXX
Object Class: Euclid
Special Containment Procedures: Live SCP-XXXX instances are to be captured in kinetic-gravitational temporal dilators3. Instances are to be stored inside until the death of the SCP-XXXX entity, the death of SCP-XXXX-A, or activation of recursive diachronic protocol.
SCP-XXXX-A is to be examined for any data stored within its body, interrogated, and amnesticized. SCP-XXXX-A is to be monitored until death or activation of recursive diachronic protocol.
All staff who are exposed to temporal anomalies are to be briefed on SCP-XXXX and monitored.
Description: SCP-XXXX is a short lived species of humanoid each of which hunts a given human being, henceforth designated SCP-XXXX-A.
Instances are pale white humanoids lacking all facial features with single sharp hoof-like nails in place of hands. SCP-XXXX instances have a 24 hour life span during which they age and grow rapidly. Height ranges from one meter at generation to 3 meters upon death. Strength and intelligence increase throughout the first 23 hours of an instances lifespan. Instances rapidly deteriorate during the last hour of their life span. SCP-XXXX instances spontaneously generate at the beginning of their life and disintegrate upon death.
During the 24 hour period, SCP-XXXX will hunt SCP-XXXX-A. If SCP-XXXX-A dies, SCP-XXXX will immediately disintegrate. However, if the target survives all 24 hours of SCP-XXXX's life span or SCP-XXXX is killed, the target will be returned to the beginning of the 24 hour period with all injuries and memories4 and continue being hunted. This loop continues inevitably until SCP-XXXX-A's death.
Prior to use of Diachronic Recursive protocol and incident-XXXX-1, SCP-XXXX instances only manifested in relation to an SCP-XXXX-A who had previously been exposed to a temporal anomaly. Manifestation was especially likely for those who actively caused or altered temporal anomalies.
Special Containment Procedures uses artificial time dilation to extend the life span of SCP-XXXX until the natural death of SCP-XXXX-A.
Addendum: Diachronic Recursive Protocol
SCP-XXXX can be used to transmit data to the past with project overseer O5 approval.
To do so, an SCP-XXXX-A of a time dilated SCP-XXXX instance, is to be inserted with a data storage device. Then, SCP-XXXX is to be killed, sending SCP-XXXX-A back to the beginning of his time loop. The foundation can then retrieve the data during containment.
All information sent to the past should include data on SCP-XXXX itself to allow examination of temporal changes in the anomaly.
Following the first implementation, researchers observed a ten percent increase in SCP-XXXX manifestations compared to recovered data describing the previous iteration and foundation agents with no previous exposure to temporal anomalies began to be targeted as SCP-XXXX-A.
As a result of the second implementation confirming these results, diachronic recursive protocol is now only implemented with O5 permission.
Incident-XXXX-42
On March 30, 2019, foundation agents successfully recovered an SCP-XXXX instance and SCP-XXXX-A despite conflict with the Chaos Insurgency.
A Chaos Insurgency data drive was recovered from within SCP-XXXX-A.
Data within pertained primarily to a foundation raid on an insurgency facility in July 2025. As opposed to allowing foundation agents to capture contained SCP-XXXX instances, insurgency forces activated diachronic recursive protocol for all 30 of its contained instances.
Deviations with SCP-XXXX materialization began with the generation of the SCP-XXXX instance on March 25. There was an immediate 150% increase in occurrences and instances began to involve SCP-XXXX-A with no association to the anomalous. Deviations in individual instance, behavior occurred as well. After the event, multiple SCP-XXXX instances have been associated with a single SCP-XXXX-A and lifespan has occasionally varied from 24 hours. One instance of SCP-XXXX has been recorded in which temporal loop would reset to a random time period within the 24 hours.
Erratic behavior has continued to increase since recovery of the data drive.
I propose that SCP-XXXX is meant to prevent anomalous anthropocentric agitation of timeline. This is to say that it's the timeline's immune system against human interference. As such, SCP-XXXX was originally associated only with humans who had interacted with temporal anomalies and particularly focused on those who had manipulated or caused temporal anomalies.
At first, diachronic recursive protocol would result in a single increase in the occurrence of SCP-XXXX. But this effect was limited to the foundation. I believe that this was the immmune response to our manipulation of the timeline. Data slows slight increases in frequency associated with major foundation intervention in the timeline, but none as severe as that caused by the diachronic recursive protocol. It is likely that the foundation policy of merely containing temporal anomalies prevents major effects on SCP-XXXX in general temporal procedures.
Most concerning is the effect on SCP-XXXX caused by incident 42. The continuously increasing frequency and varying behavior of SCP-XXXX appears differs from the response to single activations of diachronic recursvie protocol.
I believe that the mass implementation of the protocol has resulted in a run away immune response. Like a bodies immune response my damage cells in the surrounding area, SCP-XXXX damages the timeline itself. The initial immune response to the event was destructive enough to the timeline that SCP-XXXX has begun to respond to itself as a danger. I am unable to postulate as to the end result of such a cycle if it continues indefinitely.
If we wish to avoid such an eventuality, we must minimize temporal distortion. The first step would be to prevent all optional interaction with temporal anomalies, but this is unlikely to be enough on its own.
The next step is to allow the immune system to do its job. By preventing SCP-XXXX from terminating SCP-XXXX-A instances, we are preventing the immune system from finishing its task. I believe that when we prevent the death of an SCP-XXXX-A instance, the temporal immune system continues to detect the temporal distortion associated with the instance. Out containment procedures are preventing time from healing.
Human beings have encountered temporal anomalies for as long as we have existed. If every manipulation of temporal anomalies resulted in a permanent increase in SCP-XXXX, then the frequency of materialization at initial containment should have been much higher. Permanent increases in SCP-XXXX have only been observed or occurred since containment began. We are causing the increase through our containment procedures.
I propose that containment procedures to be revised to immediate termination of SCP-XXXX-A instances to maximize reduction in temporal distortion. This is a necessary step and the longer we wait, the more SCP-XXXX-A instances will have to be terminated.
Item #: SCP-XXXX
Object Class: Euclid
Special Containment Procedures: Live SCP-XXXX instances are to be captured in kinetic-gravitational temporal dilators5. Instances are to be stored inside until the death of the SCP-XXXX entity, the death of SCP-XXXX-A, or activation of recursive diachronic protocol.
SCP-XXXX-A is to be examined for any data stored within its body, interrogated, and amnesticized. SCP-XXXX-A is to be monitored until death or activation of recursive diachronic protocol.
All staff who are exposed to temporal anomalies are to be briefed on SCP-XXXX and monitored.
Description: SCP-XXXX is a short lived species of humanoid each of which hunts a given human being, henceforth designated SCP-XXXX-A.
Instances are pale white humanoids lacking all facial features with single sharp hoof-like nails in place of hands. SCP-XXXX instances have a 24 hour life span during which they age and grow rapidly. Height ranges from one meter at generation to 3 meters upon death. Strength and intelligence increase throughout the first 23 hours of an instances lifespan. Instances rapidly deteriorate during the last hour of their life span. SCP-XXXX instances spontaneously generate at the beginning of their life and disintegrate upon death.
During the 24 hour period, SCP-XXXX will hunt SCP-XXXX-A. If SCP-XXXX-A dies, SCP-XXXX will immediately disintegrate. However, if the target survives all 24 hours of SCP-XXXX's life span or SCP-XXXX is killed, the target will be returned to the beginning of the 24 hour period with all injuries and memories6 and continue being hunted. This loop continues inevitably until SCP-XXXX-A's death.
Prior to use of Diachronic Recursive protocol and incident-XXXX-1, SCP-XXXX instances only manifested in relation to an SCP-XXXX-A who had previously been exposed to a temporal anomaly. Manifestation was especially likely for those who actively caused or altered temporal anomalies.
Special Containment Procedures uses artificial time dilation to extend the life span of SCP-XXXX until the natural death of SCP-XXXX-A.
Addendum: Diachronic Recursive Protocol
SCP-XXXX can be used to transmit data to the past with project overseer O5 approval.
To do so, an SCP-XXXX-A of a time dilated SCP-XXXX instance, is to be inserted with a data storage device. Then, SCP-XXXX is to be killed, sending SCP-XXXX-A back to the beginning of his time loop. The foundation can then retrieve the data during containment.
All information sent to the past should include data on SCP-XXXX itself to allow examination of temporal changes in the anomaly.
Following the first implementation, researchers observed a ten percent increase in SCP-XXXX manifestations compared to recovered data describing the previous iteration and foundation agents with no previous exposure to temporal anomalies began to be targeted as SCP-XXXX-A.
As a result of the second implementation confirming these results, diachronic recursive protocol is now only implemented with O5 permission.
Incident-XXXX-42
On March 30, 2019, foundation agents successfully recovered an SCP-XXXX instance and SCP-XXXX-A despite conflict with the Chaos Insurgency.
A Chaos Insurgency data drive was recovered from within SCP-XXXX-A.
Data within pertained primarily to a foundation raid on an insurgency facility in July 2025. As opposed to allowing foundation agents to capture contained SCP-XXXX instances, insurgency forces activated diachronic recursive protocol for all 30 of its contained instances.
Deviations with SCP-XXXX materialization began with the generation of the SCP-XXXX instance on March 25. There was an immediate 150% increase in occurrences and instances began to involve SCP-XXXX-A with no association to the anomalous. Deviations in individual instance, behavior occurred as well. After the event, multiple SCP-XXXX instances have been associated with a single SCP-XXXX-A and lifespan has occasionally varied from 24 hours. One instance of SCP-XXXX has been recorded in which temporal loop would reset to a random time period within the 24 hours.
Erratic behavior has continued to increase since recovery of the data drive.
I propose that SCP-XXXX is meant to prevent anomalous anthropocentric agitation of timeline. This is to say that it's the timeline's immune system against human interference. As such, SCP-XXXX was originally associated only with humans who had interacted with temporal anomalies and particularly focused on those who had manipulated or caused temporal anomalies.
Single instances of diachronic recursive protocol resulted in a single constant increase in SCP-XXXX materializations. However, there has been a steady increase in materializations since incident 42.
I believe this to be a run away immune response. Significant damage to the timeline caused by the immune system itself has resulted in immune detecting itself as temporal damage. If this temporal response continues to grow, the foundation will be unable to contain the situation.
We only began to observe increases in materializations following the implementation of current containment procedures and diachronic recursive protocol. It is logical that the protocol would increase materialization because it is anomalous intervention in the timeline by humans.
However, I worry that containment procedures themselves may be exacerbating the issue. By preventing the deaths of SCP-XXXX-A, we may be preventing the timeline eliminating what it sees as a threat. As such, the timeline is continuously sensing more and more damage and responding accordingly.
If we wish to prevent a run away immune effect current containment procedures need to be revised. We need to allow SCP-XXXX-A to be eliminated. In the case of contained SCP-XXXX instances, we will need to terminate SCP-XXXX-A ourselves.
While this response is ethically dubious, we have no choice. The longer we wait, the more people become SCP-XXXX-A, the more difficulty the foundation has maintaining the veil, and the more people will have to be terminated in the end.
Item #: SCP-XXXX
Object Class: Euclid
Special Containment Procedures: Live SCP-XXXX instances are to be captured in kinetic-gravitational temporal dilators7. Instances are to be stored inside until the death of the SCP-XXXX entity, the death of SCP-XXXX-A, or activation of recursive diachronic protocol.
SCP-XXXX-A is to be examined for any data stored within its body, interrogated, and amnesticized. SCP-XXXX-A is to be monitored until death or activation of recursive diachronic protocol.
All staff who are exposed to temporal anomalies are to be briefed on SCP-XXXX and monitored.
Description: SCP-XXXX is a short lived species of humanoid each of which hunts a given human being, henceforth designated SCP-XXXX-A.
Instances are pale white humanoids lacking all facial features with single sharp hoof-like nails attached to the wrist in place of hands. SCP-XXXX instances have a 24 hour life span during which they age and grow rapidly. Height ranges from one meter at generation to 3 meters upon death. Strength and intelligence increase throughout the first 23 hours of an instances lifespan. Instances rapidly deteriorate during the last hour of their life span. SCP-XXXX instances spontaneously generate at the beginning of their life and disintegrate upon death.
During the 24 hour period, SCP-XXXX will hunt SCP-XXXX-A. If SCP-XXXX-A dies, SCP-XXXX will immediately disintegrate. However, if the target survives all 24 hours of SCP-XXXX's life span or SCP-XXXX is killed, the target will be returned to the beginning of the 24 hour period with all injuries and memories8 and continue being hunted. This loop continues inevitably until SCP-XXXX-A's death.
Prior to use of Diachronic Recursive protocol and incident-XXXX-1, SCP-XXXX instances only manifested in relation to an SCP-XXXX-A who had previously been exposed to a temporal anomaly. Manifestation was especially likely for those who actively caused or altered temporal anomalies.
Special Containment Procedures uses artificial time dilation to extend the life span of SCP-XXXX until the natural death of SCP-XXXX-A.
Addendum: Diachronic Recursive Protocol
SCP-XXXX can be used to transmit data to the past with project overseer O5 approval.
To do so, an SCP-XXXX-A of a time dilated SCP-XXXX instance, is to be inserted with a data storage device. Then, SCP-XXXX is to be killed, sending SCP-XXXX-A back to the beginning of his time loop. The foundation can then retrieve the data during containment.
All information sent to the past should include data on SCP-XXXX itself to allow examination of temporal changes in the anomaly.
Following the first implementation, researchers observed a ten percent increase in SCP-XXXX manifestations compared to recovered data describing the previous iteration and foundation agents with no previous exposure to temporal anomalies began to be targeted as SCP-XXXX-A.
As a result of the second implementation confirming these results, diachronic recursive protocol is now only implemented with O5 permission.
Incident-XXXX-42
On March 30, 2019, foundation agents successfully recovered an SCP-XXXX instance and SCP-XXXX-A despite conflict with the Chaos Insurgency.
A Chaos Insurgency data drive was recovered from within SCP-XXXX-A.
Data within pertained primarily to a foundation raid on an insurgency facility in July 2025. As opposed to allowing foundation agents to capture contained SCP-XXXX instances, insurgency forces activated diachronic recursive protocol for all 30 of its contained instances.
Deviations with SCP-XXXX materialization began with the generation of the SCP-XXXX instance on March 25. There was an immediate 150% increase in occurrences and instances began to involve SCP-XXXX-A with no association to the anomalous. Deviations in individual instance, behavior occurred as well. After the event, multiple SCP-XXXX instances have been associated with a single SCP-XXXX-A and lifespan has occasionally varied from 24 hours. One instance of SCP-XXXX has been recorded in which temporal loop would reset to a random time period within the 24 hours.
Erratic behavior has continued to increase since recovery of the data drive.
I propose that SCP-XXXX is meant to prevent anomalous anthropocentric agitation of timeline. This is to say that it's the timeline's immune system against human interference. SCP-XXXX were originally sent out to kill humans who had interfered in the timeline and prevent further interference.
However, SCP-XXXX now targets a large variety of humans not associated with the anomalous. The source of this change can be directly traced to foundation actions.
A steady but mild increase in materializations began with the implementation of current containment procedures. Diachronic Recursive protocol has resulted in a moderate increase in materializations each activation and since incident 42, materializations have been increasing rapidly and behavior has become erratic.
In current containment procedures, we prevent the elimination of SCP-XXXX in the 24 hour period selected by the timeline. This results in the timeline detecting increased damage and human interference and thus a steady increase in materializations. Diachronic Recursive Protocol results in a greater increase which data shows is strongly correlated to the increase in the materializations between initial containment of the SCP-XXXX instance and activation of the protocol. This suggests that the timeline is continuing to detect unresolved damage from the rewritten timeline. Oddities in behavior also begin to emerge at this point. I believe this is due to the immune system itself being used to manipulate the timeline.
Finally, there has been an exponential increase in materializations since incident 42. The simultaneous activation of multiple protocols coupled with the high amount of damage has seemed to result in a runaway immune response. The timeline is detecting an excessive amount of damage not linked to anomalies in this timeline and such attacks random humans. It is also detecting its own actions as temporal manipulation resulting in a feedback loop.
The exponential increase of materializations shows no sign of stopping with current containment procedures. The number of affected humans and the difficulty of containment continues to increase.
The only solution to this runaway effect is to alter containment procedures. We must allow the termination of SCP-XXXX-A instances to allow the timeline to reduce distortion naturally. If more conducive to maintaining the veil, the foundation must terminate SCP-XXXX-A instances itself. The longer we wait to change procedures, the greater number of people will have to be culled.
