# 📝 - Virus Eradication - Planning Thread

**URL:** <https://forums.atlas-65.com/t/virus-eradication-planning-thread/10057>\
**Category:** Project Skyscraper\
**Created:** [July 19, 2026, 3:10pm UTC](https://forums.atlas-65.com/t/virus-eradication-planning-thread/10057 "2026-07-19T15:10:32Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![ThatBomberBoi](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.atlas-65.com/thatbomberboi/32/41691_2.png) [@ThatBomberBoi](https://forums.atlas-65.com/u/ThatBomberBoi)\
**Post date:** [July 19, 2026, 3:10pm UTC](https://forums.atlas-65.com/t/virus-eradication-planning-thread/10057/1 "2026-07-19T15:10:32Z")

</div>

Hello Operators,  
As we saw over the course of recent events, the “Termite” targeting System’s memories is a ruthless sub-program capable of widespread damage to its memory banks, requiring the _careful_ use of our resources to trap. After today’s failure and a runaway break made by the virus, (which @the_architect had to patch in last minute), its clear that a **careful and collected** action plan is required to proceed with any potential traps.

To come up with a foolproof plan, this thread organizes information regarding the virus’ behavior and the rules it has been proven to follow. Any such plan must minimize the number of preserved memory blocs used, as well as memory losses. The current action plan will also be updated and provided at the bottom of the top thread.

# Confirmed Information / Ruleset

- The virus begins by attacking a “seed” memory. These are picked based on a mathematical pattern (deciphered by Operator @Frazzlesprite and available [here](https://docs.google.com/spreadsheets/d/1ih_bLq3h_0AlHTTtlT5ILWZEjyJCs-axJIq0UkIe1xM/edit?usp=sharing)) and are entirely predictable. These can be considered as the virus’ “entry-point” into a set of memory blocs.

- After deleting the seed memory, the virus then begins to delete memories on either side (before and after) of the seed. When consuming a memory, it leaves behind a black hole / void, resulting in that bloc being **permanently deleted** from the Project Skyscraper website.

- Operators can request The Architect to mark certain dates as **Preserved.** These special dates have the following unique properties:

- Once the virus is “contained” on either side by preserved memories (as in, it has deleted all possible memories on either side), it will jump to the next seed date and begin its propogration routine once more.

- If the _next_ seed date is -null- (as in, there are no memory blocs for it on the PSS website), then the virus will enter a **holding pattern** , where it will be unable to infect / delete any memory blocs for a indeterminate amount of time (current recorded max: 24 Hours). This affords the Operators time to organize and plan out accordingly.

It is believed that the virus is searching for a key memory which already exists in System’s memory banks. Owing to this, it is believed that “Feeding” the virus a false duplicate of its target memory (by placing a clone in the path of its deletions) will satiate the virus and eliminate the threat. Candidates are requested to be submitted [here](https://forums.atlas-65.com/t/virus-eradication-target-memory-accumulation/10058).

# Current State

1. The last seed consumed was Monday, 8th August 2016.
2. The next seed in sequence is Saturday, 4th February 2017 and is currently null. The virus should not act before we put anything in this date (via coordination with The Architect), unless there is a hidden and known timer.
3. The adjacent dates of 5th and 6th February 2016 are also null, so the virus will immediately jump to 19th December, which is preserved, causing it to jump again to 24th August, which has neighboring memory blocs.
4. If we preserve 24th August, the virus will attempt to jump to 6th February 2017, which is also null, so it will be paralyzed there.

# Action Plan

WIP

---

_[View the full topic](https://forums.atlas-65.com/t/virus-eradication-planning-thread/10057)._
