pom × 2 · pom² · handle only
pom squared.
security handle, tool builder, permanent argument with default settings. i build the things i wanted to already exist, then point them at problems that push back. pomx2.sh is where the evidence lives.
nsa codebreaker challenge · 2025–2026 · division 1 · first place
scroll — the field reacts
01 / thesis
reject the defaults.
every environment arrives with somebody else’s opinion baked in. the shell prompt, the editor theme, the window chrome, the agent harness, the colour of a title bar nobody chose. none of it was written for this machine, or this work, or me.
so it gets rebuilt from source — one place where the values live, and everything downstream generated from it. the projects below are the evidence, not the pitch. the messy middle between “i have an idea” and “it works” is the interesting part, and it is mostly what is on this page.
02 / command center
fuck your os.
a native command center for orchestrating ai coding agents: the claude, codex, grok and antigravity clis under one roof, plus local models through ollama and ramalama running my own tool-calling loop — so nothing leaves the machine unless i say so. model manager, command palette, kanban, routines. it is alpha and it is honest about that.
fleet mode · one prompt template, many targets, live findings extraction
template recon.v3 · concurrency 6 · findings parsed on the wire · nothing leaves the box
// ui simulation. not live data.
03 / one source
one palette, everywhere.
a fresh box becomes a full synthwave desktop from one colour source. it propagates into bash, vim, konsole, plasma colour schemes, aurorae window decorations, an icon theme, a firefox theme, a vs code extension packed as a .vsix, and a system-monitor widget. every step checks state before it touches anything, so running it twice is boring on purpose. the theme is generated, never hand-copied.
// colour source
value #00E8FC
the slider only travels the identity gradient. the background field takes the same value.
04 / infiltration
the portfolio you break into.
a cyberheist first-person game that is secretly the portfolio. night, rain, a corporate arcology tower. you get in, you go up, you reach the executive office, and the terminal on the desk boots a fully interactive fake linux desktop with the payload sitting in it. the whole world — tower, rain, interiors, the desktop inside the desktop — is built in code. nothing is downloaded.
// route
the route unlocks as you scroll. in the build it unlocks when you earn it.
05 / operations
machines that push back.
ongoing hack the box and tryhackme work, run through overwatch so the boring half — enumeration, note-taking, findings extraction — happens in a fleet while i think about the interesting half. the numbers below are wired to real readouts and deliberately empty until there is something true to put in them.
no invented ranks. the slots are wired; the season fills them.
06 / build queue
what’s actually in the queue.
progress is a note, not a promise. the bars are how finished a thing feels from the inside, which is the only honest metric i have.
07 / contact
say something interesting.
ctf teams, weird protocol questions, or anyone who has also decided their window manager was wrong. not a job board. no resume attached.
note the zero. p0mx2, not pomx2, in the address.
m2