I build a lot of things. Lately I’ve been finishing more of them, and I wanted somewhere to write that down honestly. This is that place.
why a chronicle
Most project pages read like sales decks. The part worth reading is the middle, the rough edges and the pitfalls, the rewrite I put off three months too long, the moment the architecture finally clicked. That middle part is what goes on this site.
The tower(site) itself follows one rule. Every page is a single HTTP request, carries no JavaScript, and fits in a couple of KB. Build small, build sturdy.
what’s on the shelves
There’s a build log for running commentary and a projects page for the works themselves: the completed, the in-progress, and the still-imagined. Each gets its own page with the full story and every related entry from the log.
The current roster:
- SepulchrynScan — a multithreaded service-discovery and port scanner in Go. The scrying tool I reach for first when I need to map a network.
- Detectsmith — a smithy for detection wards. Tries to be useful, not Splunk.
- CyberToolbox — a belt of security cantrips bound into a single binary.
- Locket — a warded reliquary for secrets, with a TUI worth opening daily.
- Shipnote — a chronicler imp that reads my git log and drafts the release notes so I don’t have to.
- Cleanpaste — a clipboard exorcist. Banishes the invisible spirits that ride along in copied text.
- Sigil — wax seals for release artifacts. GPG with the suffering removed.
- TPing — a watchtower for on-call shifts. Sends ravens to every store device and shows who answered.
- PulpDescent and aGrandAdventure — two procedural text dungeons in Godot 4, written without an LLM. No bound spirit does the writing. Every word is set by hand or grown from deterministic grammar.
what happens next
New entries go up as the work does, usually when something breaks, gets fixed, or ships. There’s an RSS feed if that’s how you read. Otherwise check the build log when you re