About_Me.md
Infrastructure
Capabilities.rules
Daemons.conf
About_Me.md markdown
SYS_INIT_SEQUENCE

Zero-Trust Architecture.
Persistent Deployments.
Zero Tolerance for Bloat.

I am an IT Engineering student and Security Researcher operating at the intersection of infrastructure orchestration and threat intelligence. I don't just write code; I engineer the ground it walks on.

Air-Gapped Boundaries

Enforcing Network & Physical Firewall Rules

To maintain peak system performance, I enforce strict physical and network boundaries. Unauthorized requests will be timed out immediately.

🛡️ The Command Center Protocol
My Discord server is structured as a private suite and central command monitoring center. Access to this core infrastructure is strictly heavily vetted. Unauthenticated connections are dropped.
⚠️ The Hardware Sanctity Rule
I know my exact hardware specifications down to the processor threading. Unsolicited tech support or incorrect assumptions about my rig will be met with immediate firewall blocks.
⚡ The Time-Allocation Metric
System bandwidth is strictly reserved for high-yield operations. If a task does not involve leveling up in IT, hitting a new gym PR, or advancing the storyline in a top-tier game, it drops to /dev/null.
Infrastructure.conf deployments

Cloud Deployments & Infrastructure

Cloud orchestration pipelines and schema topologies
Supabase Firebase Studio Railway SecOps Heuristics Neovim (NvChad)
Project Kalasetu Full-Stack E-Commerce Infrastructure

Engineered a full-stack, web-based e-commerce platform. Handled the cloud orchestration, deployed backend schemas using Firebase Studio and Supabase, and scaled the infrastructure via Railway.

  • Designed and managed PostgreSQL schemas and RLS policies on Supabase.
  • Orchestrated host containers and backend worker daemons via Railway.
  • Integrated Firebase Studio for authentication and real-time state sync.
The Command Center Infrastructure & Status Monitor Suite

Re-architected a standard Discord server into a heavily vetted, personal suite and centralized command center. It operates strictly to monitor my technical services and infrastructure. Unauthenticated connections are dropped.

  • Integrated webhooks for real-time deployment status warnings.
  • Configured role hierarchies and MFA protocols to secure the node.
  • Automated server maintenance routines running on isolated background threads.
Capabilities.rules technical_specs

DevSecOps Capabilities

System documentation: Capabilities and offensive/defensive subsystems

If your development environment isn't portable, secure, and entirely mouse-free, you are simply a liability to the codebase. Below is the technical matrix of my operation:

Subsystem Specifications & Operational Parameters
DevOps & Infrastructure Pocket-Sized Infrastructure: Why rely on static local hardware? My entire development environment is an air-gapped, custom-configured Omarchy Linux OS running off a persistent 64GB USB drive. My operating system boots from my pocket.
Terminal Dominance Mouse-Free Runtimes: Primary interface: Neovim with an NvChad configuration. If your workflow requires graphical buttons and a mouse, we are operating on different evolutionary planes.
Threat Intelligence (SecOps) Cipherium: Lead architect of the Cipherium synthetic media detection system. If an asset is algorithmic or deepfaked, my heuristics flag it before it hits the network.
Offensive Security CTF Operations: Active participant in CTF challenges. I specialize in metadata extraction and file decoding. Your obfuscated payloads and "hidden" directories are just light cryptographic puzzles to me.

CTF Training Grounds

Daemons.conf background_threads

Hardware Sanctity

Primary host parameters | Threads monitored

Operating on a customized x86_64 host system with dedicated graphics. I know my exact threading and GPU utilization limits. Unsolicited tech support or assumptions about my rig are treated as hostile port scans and dropped.

CPU Threads [x86_64 Core]
GPU Core [Dedicated GPU]
USB 64GB Omarchy Storage

Meat-Space Maintenance

Loop status: RUNNING (PPL Framework)

Physical hardware integrity is sustained via a rigorous Push-Pull-Legs (PPL) loop, swimming, cycling, and weekly runtime deployments with local running clubs. I lift to ensure the physical hardware matches the mental firmware.

Audio Encryption

Guitar beatmaking and chord progressions

Capable of generating custom audio payloads via an acoustic-electric guitar, including acoustic-electric guitar string manipulations, beatmaking, and complex chord progression testing.

High-Elo Recreation

Downtime operations | FPS optimized

Tactical precision isn't just for servers. Downtime requires a high frame rate, executing high-elo operations in Valorant and Clash Royale, balanced with Forza Horizon.

Neovim (NvChad IDE) mouse-free
󰙅 NvChad Tree
󰢱 init.lua
 devops.json
 secops.py
󰢱 public_key.asc
 init.lua ×
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
-- Neovim init configuration (NvChad based) local opt = vim.opt -- Global system specs vim.g.hardware = { cpu = "x86_64 Core", gpu = "Dedicated GPU (6GB)", os = "Omarchy Linux", ram = "16GB DDR5" } -- Zero-tolerance for mouse bloatware opt.mouse = "" opt.number = true opt.relativenumber = true opt.clipboard = "unnamedplus" print("Evolutionary plane verified: mouse-free interface loaded.")
NORMAL
init.lua
UTF-8
instance@h4rd1k:~ (tty) sh
Type 'help' for a list of available system commands.
instance@h4rd1k:~$
Terminal
Neovim (NvChad)
About Me
Infrastructure
GitHub
Instagram
LinkedIn