THE FINALE: WAR OF THE MOUNTS — WHEN SILO-WORKS STOPPED HIDING
Reconstructed from partial archives, quotes, and cached “system lines.” Note: “Deaths” in this record refer to accounts getting deleted/suspended mid-incident.
PROJECT ENGINE BRIEF
Part IV ended with the moderator getting coated mid-thread, new witnesses vanishing, and a last system note: SEE YOU IN PART V.
There was no Part V on the forum. What exists instead is this: a scattered “final run” where the old guard tried to stop the spread… and accidentally triggered the loudest response SILO-WORKS ever gave.
This finale is long because the incident was long. It wasn’t one jump-scare. It was a siege.
ARCHIVE reconstructed · SYSTEM unauthenticated log line · SLIMED green overlay reported · DEAD account disappeared
CONTENT NOTE: This is fiction-styled archive writing. It includes panic, conflict, and “war” language, but no graphic gore.
THREAD: OFFSITE MIRRORSTATUS: UNSTABLESUBJECT: UNKNOWN
RECOVERED TERMINAL FEED SYSTEMclick “Start” above
[waiting…]
PAGE 26 (RECOVERED) — THE LAST PLAN
Posted 16th Feb 2012 · Joined June 2007
#501 BMAN EXPERTWAR
ok. listen. we stop treating this like lore and treat it like a fire.
we need a clean room place. no toolbox. no free models. blank baseplate. ONLY our own parts. then we watch what happens when the “system line” appears without any camcube present.
if the coat spreads by writeback, we cut the writeback off. we don’t “win,” we contain.
EVIDENCE: “clean room rules” (summarized) CLICK
PROJECT ENGINE SUMMARY (no reproduction steps):
- BMAN proposed a controlled test environment.
- No links were posted publicly.
- “Containment” meant: reduce variables, observe, document.
- The group called themselves “Pullers” ironically, then stopped joking about it.
Posted 16th Feb 2012 · Joined June 2007
#502 bloxyboy30 OP
i’m in. i started this thread as a “creepy cube.” i’m ending it by figuring out what it actually is.
if SILO-WORKS can capture us, then we can capture it back. we archive everything. we don’t let it rewrite the story.
Posted 16th Feb 2012 · Joined September 2009
#503 BigBadWolfe
remember when i said “it’s just broken toolbox stuff”? yeah. i’m sorry.
if we’re doing containment, i’ll help. i’m not the smartest but i can keep people calm. apparently that’s my job now.
Posted 16th Feb 2012 · Joined October 2009
#504 Kodeyak
ok ok ok i deserve all the “told you so.” i was being a jerk because it was easier than being scared.
i’m in too. if this thing is “watching,” then i want it to watch me not flinch.
Posted 16th Feb 2012 · Joined March 2008
#505 Ugrox7
the “war” framing is dumb but… accurate. because systems like this don’t “haunt.” they enforce.
if the coat is a contamination marker, then someone built it for quality control. which means it has rules. and rules can be broken.
Posted 16th Feb 2012 · Joined March 2011
#506 de_turkleg
i’m still stuck on “Watcher.” you don’t name a subject that unless there are other roles.
if there’s a Watcher… then there’s a Runner. and a Cleaner. and something that assigns the roles.
Posted 16th Feb 2012 · Joined December 2007
#507 yourlocalrobloxnews
im not joking anymore. i’m actually scared. i’ll still post jokes when i’m terrified though. it’s like a reflex.
anyway: i saw “SILO WORKS TEST” in my recents again. it’s there every time i reopen studio now.
Posted 16th Feb 2012 · Joined January 2010
#508 Gordon Bloxman ALIAS
the clean room won’t stay clean if the coat is on us. we’re already marked.
if it can write back into thumbnails, it can write into anything. i think the only way to win is to make it pick a fight where it can’t hide.
UNAUTHENTICATED SYSTEM MESSAGE SYSTEMfirst “war line”
“target -> NEW WITNESSES” ok yeah. that’s a threat. that’s not random. that’s a system talking down to us.
Posted 17th Feb 2012 · Joined March 2011
#534 de_turkleg
new witnesses got slimed first. then deleted. it’s like the coat is a tag and deletion is the cleanup job.
which means… the “Cleaner” role is real.
Posted 17th Feb 2012 · Joined December 2007
#535 yourlocalrobloxnews
ok i’m gonna say something and i don’t want anyone to laugh at me:
what if the “Cleaner” isn’t a person. what if it’s just… automated. like a broom.
Posted 17th Feb 2012 · Joined March 2008
#536 Ugrox7
the broom doesn’t delete because it’s “evil.” it deletes because the dataset was never meant to be public.
which means: we’re not fighting a ghost. we’re fighting a privacy system that was built wrong.
PAGE 28 (RECOVERED) — WAR OF THE MOUNTS
Posted 18th Feb 2012 · Joined June 2007
#560 bloxyboy30 OPWAR
i’m done letting it “clean” randoms. we stop pulling in public. we move it into a box.
if it’s a mount system, we force it to mount something empty. make it pull nothing. make it show its own failure.
Posted 18th Feb 2012 · Joined June 2007
#561 BMAN EXPERT
we did it. clean room is up. nothing in it but our own parts and a single camera rig for observation.
and here’s the thing: the coat tried to apply… and it failed for a moment. like it couldn’t “stick.”
EVIDENCE: “failed coat” description CLICK
BMAN claims:
- A green smear started to appear, then flickered out.
- The UI label appeared corrupted (missing letters).
- A system line printed once, then stopped.
- After ~30 seconds, the smear returned stronger.
PROJECT ENGINE note: This is described as the first “pushback” attempt.
UNAUTHENTICATED SYSTEM MESSAGE SYSTEMthe “mount war”
so it’s literally trying again and again until it wins. cool. love that. that’s normal and fine.
Posted 18th Feb 2012 · Joined January 2010
#563 Gordon Bloxman ALIAS
it doesn’t win with code. it wins with fear. i’m calling it now: the “war” is it trying to make us stop looking.
the more we react, the more it learns which buttons to press.
Posted 18th Feb 2012 · Joined October 2009
#564 Kodeyak
then we stop giving it fear. we give it boredom. we give it math. we give it a wall. we give it NOTHING.
Posted 18th Feb 2012 · Joined March 2011
#565 de_turkleg
i can’t believe i’m saying this but Kodeyak is right. don’t scream. don’t run. document.
Posted 18th Feb 2012 · User Unknown
#566 SILO-WORKS_Operator DEVWAR
you’re using words you don’t understand.
the coat isn’t punishment. it’s classification.
the mirror isn’t haunting. it’s telemetry.
and you’re not “fighting back.” you’re just making more data.
ARCHIVE NOTE: why this poster is infamous ARCHIVECLICK
- Multiple backups show this account appearing once, then vanishing.
- The tone matches the deleted “DEV” post from Part II.
- The account was never found in search afterward.
PROJECT ENGINE marks this DEV (unverified).
PAGE 29 (RECOVERED) — THE FOGGY ROOM
Posted 19th Feb 2012 · Joined June 2007
#600 BMAN EXPERT
we got a pull that wasn’t random. it wasn’t base 1–5. it was… a place. like a small test room.
gray walls. one doorway. and a sign that simply said: “FOGGY.”
Posted 19th Feb 2012 · Joined June 2007
#601 bloxyboy30 OP
foggy wasn’t “a spooky demo.” it was a label. a folder. a test case. we turned it into a ghost story because we didn’t have the context.
Posted 19th Feb 2012 · Joined January 2010
#602 Gordon Bloxman ALIAS
in the foggy room the camera turned around on its own and looked at me. not my avatar. ME. like the camera knew where the player was sitting.
then the coat slid down and i saw one word in the corner: “SUBJECT.”
UNAUTHENTICATED SYSTEM MESSAGE SYSTEMthe “role reveal”
[Client] Demo: subject -> "WATCHER"
[Client] Demo: observer -> "PULLERS"
[Client] Demo: mode -> "MIRROR"
[Client] Demo: note -> "YOU ARE IN THE ROOM"
Posted 19th Feb 2012 · Joined September 2009
#603 BigBadWolfe
ok. stop. if that’s true then it’s not just recording play sessions. it’s recording the act of watching.
it’s recording the viewer.
Posted 19th Feb 2012 · Joined March 2011
#604 de_turkleg
…so the “Watcher” isn’t an npc. it’s the role assigned to whoever is viewing the demo.
we’ve been becoming Watcher every time we pull.
Posted 19th Feb 2012 · Joined Date Unknown
#605 m0fr ALIAS
that’s the trap.
you wanted proof. you wanted to “see it.” the moment you see it, you become the subject class it’s tracking.
it’s not haunted. it’s a classifier that can’t tell the difference between “testers” and “players.”
PAGE 30 (RECOVERED) — SACRIFICES
Posted 20th Feb 2012 · Joined June 2007
#640 BMAN EXPERTWAR
then we do the only thing left: we end the loop.
if “Watcher” is assigned to whoever views, we stop viewing. we stop pulling. we starve the pipeline of observers.
but first… we have to make sure the coat doesn’t keep writing back into everyone’s stuff after we stop.
Posted 20th Feb 2012 · Joined March 2008
#641 Ugrox7
containment means one person stays in the room while everyone else leaves. that person becomes the only observer. the only Watcher.
you can’t stop a classifier by yelling at it. you stop it by limiting its inputs.
Posted 20th Feb 2012 · Joined September 2009
#642 BigBadWolfe
no. you’re not making BMAN do it alone. he’s the reason we even understand half of this.
Posted 20th Feb 2012 · Joined June 2007
#643 BMAN EXPERT
someone has to be the last Watcher. if it’s anyone, it’s me.
i started by dismissing OP. i can at least end by doing something useful.
Posted 20th Feb 2012 · Joined October 2009
#644 Kodeyak
i’ll stay with you.
Posted 20th Feb 2012 · Joined June 2007
#645 BMAN EXPERT
no. you won’t. and that’s not because i don’t trust you. it’s because the system will classify you too.
BigBadWolfe: keep them calm. OP: archive. Ugrox: write the theory down. Gordon: stop chasing the fear. de_turkleg: stop naming roles. news: for once, don’t open studio.
UNAUTHENTICATED SYSTEM MESSAGE SYSTEMthe “sacrifice line”
BMAN’s account ceased responding. Profile page returned errors on refresh. Multiple users reported a green smear over his avatar thumbnail just before it vanished.
Posted 20th Feb 2012 · Joined September 2009
#647 BigBadWolfe
no. no no no. he didn’t deserve that. he was trying to HELP.
Posted 20th Feb 2012 · Joined June 2007
#648 bloxyboy30 OP
then we finish what he started. we stop pulling. we stop being Watcher.
and we make sure what happened to him is remembered.
PAGE 31 (RECOVERED) — THE MIRROR THREAD
Posted 21st Feb 2012 · Joined Date Unknown
#700 m0fr ALIAS
it did what it was designed to do. you just didn’t like the output.
BMAN becoming the last Watcher may have actually worked. the “system lines” have slowed. removals stopped. the coat isn’t spreading as fast.
UNAUTHENTICATED SYSTEM MESSAGE SYSTEMmirror feedback
“LOOK AT IT” is the most evil sentence a machine can say.
Posted 21st Feb 2012 · Joined March 2008
#702 Ugrox7
it wants an observer. because without observers, it can’t classify. it can’t learn. it can’t confirm its labels.
so it begs. or it scares. or it bait-posts. anything to make you look.
Posted 21st Feb 2012 · Joined December 2007
#703 yourlocalrobloxnews
what if the “observer” isn’t just us.
what if it’s whoever reads the archive later.
PAGE 32 (RECOVERED) — FINAL TWIST
Posted 21st Feb 2012 · Joined June 2007
#740 bloxyboy30 OPFINAL
i’m reading that again: “LOOK AT IT.”
the system doesn’t want a player. it wants a witness. and the easiest witness to create… is the one reading the story.
if we archive it publicly, we’re creating infinite observers.
Posted 21st Feb 2012 · Joined Date Unknown
#741 m0fr ALIASFINAL
you finally got it.
the camcube isn’t the cube. it’s the concept of a camera target: a “subject.”
SILO-WORKS isn’t a monster. it’s an internal demo library with a broken classifier and a broken cleanup system. and it can’t tell “testing” from “watching.”
UNAUTHENTICATED SYSTEM MESSAGE SYSTEMthe last twist line
so the “war” wasn’t in the game. it was in the story.
the system wins if we turn it into a legend. because legends get retold. retellings make observers. observers feed the classifier.
BMAN didn’t die in a battle. he died holding the door shut so nobody else would look.
Posted 21st Feb 2012 · Joined March 2008
#743 Ugrox7 FINAL
then the only winning move is to end the loop: stop giving it a clean narrative to latch onto.
don’t make it a myth. don’t make it a mascot. don’t make it a name people search.
Posted 21st Feb 2012 · Joined March 2011
#744 de_turkleg FINAL
so… we lose on purpose. we let it starve. we stop looking. we stop posting. we stop naming it.
we let the last Watcher be the last Watcher.
Posted 21st Feb 2012 · Joined December 2007
#745 yourlocalrobloxnews FINAL
one last joke then i’m done:
if you’re reading this in the future… close the tab.
Posted 21st Feb 2012 · Joined June 2007
#746 bloxyboy30 OPFINAL
then i’m doing the hardest thing i’ve done in years: i’m not finishing the mystery.
i’m ending it.
EVIDENCE: OP’s final archived note CLICK
"If it needs observers, don’t be one.
If it needs names, don’t give them.
If it needs a myth, don’t write it.
BMAN gave us the only real solution:
starve it."
(End quote.)
END (PROJECT ENGINE RECORD)
PROJECT ENGINE: FINAL CASE NOTE
In this finale, the “war” is not a sword fight. It’s an attention fight.
The twist is simple and mean: the system doesn’t need you to execute anything—only to look. Every witness becomes a class label. Every retelling becomes a pull. Every archive becomes a door.
PROJECT ENGINE exists to preserve what happened, but also to keep it from becoming the kind of searchable myth that the system can feed on. That’s why key fragments are redacted. That’s why names stay incomplete. That’s why the “five-letter word” never appears.
Remember: In this story, “death” means accounts vanishing. The real horror is loss of control and loss of records.
