Silo IT Terminal

Deploying the Silo IT Terminal 24/7
What I built today:
I completely overhauled my Slack bot into The Silo IT Terminal (v1.0)—an immersive, dystopian mainframe inspired by the sci-fi series Silo. After writing a baseline script, I ran into some classic Git sync roadblocks and local drive space issues, but I pushed through, cleaned up my repository, and successfully deployed it to the cloud!

✨ Core Features Implemented:

status: Displays a sub-level mechanical diagnostics readout (steam levels, fan efficiency) wrapped in clean markdown.

outside: A text monitor that detects forbidden phrases. If a citizen mentions the exterior landscape, it fires back a stylized Slack Block Kit UI card flagging a Pact Violation.

scavenge: Built a Role-Based Access Control (RBAC) layer. It checks the user’s unique Slack Member ID. If anyone else searches for artifacts, access is denied. If I use it, it bypasses the system to retrieve a randomized, forbidden pre-historic relic.

Hey everyone! Just built my very first Slack bot, and unlike the rest of us, this one isn’t slacking off—it’s running 24/7 directly out of my Windsurf editor! 💻⚡️

I wanted to do something cooler than just a basic “Hello World” bot, so I’m turning it into an interactive system inspired by the Silo TV series. Right now, it mimics an ancient underground IT terminal embedded in the deep down of the Silo.

Upcoming features:

📋 System Diagnostics: Type @Bot status to get live readouts of the 144 levels, steam pressure, and sensor status.

⚠️ Judicial Overrides: Try asking about the “Outside” and the bot will flag you for a Level 1 infraction against the Pact.

🛠️ A role-based permission system recognizing the Head of IT vs. standard citizens.

🧹 A moderation system where you can sentence rule-breakers to “Go out for a cleaning.”

📦 A “Relic Archive” database where users can scavenge for forbidden artifacts from the before-times.

“In the event of a failed terminal, please contact the Head of IT. Do not look through the lens.” 👁️📟