STACK~
First-hand engineering essays with receipts: the engine, the box, the store, and the studio.
-
AI as verifier, not author
An agent drove a real image editor and the art was bad. The same kind of agent, pointed at a paywall's test suite, found a bypass the suite had missed. The line between those two results is the whole thesis.
-
"Checkout is not live yet"
A disabled button with a true sentence is a feature. The shop's most important copy is the copy that admits the payment path does not exist yet.
-
Eight subsystems, deleted
The one-pager still says the system keeps learning while it runs. Epoch 2 deleted the machinery that did that — and the honest description got shorter, not sadder.
-
A Forward Pass on the Graph
A forward pass, not a walk — and what had to be deleted before the retrieval design could be explained in one direction.
-
Four machines, one system
A Mac that builds, a laptop that draws and trains, a $23 server that answers, and a GPU that exists only while it is called. The topology is the architecture.
-
Moving the whole thing to a $23 VPS
The cutover took eight minutes: four CNAMEs, one tunnel, a week of preparation. The hard part was not the DNS — it was admitting that the vectors could not travel.
-
One dependency, one third party, zero trackers
The shop loads no analytics, no ad code, no CDN fonts and no third-party JavaScript — except Stripe, on the page where a card is entered. Proving that took a browser, not a grep.
-
Selling tarot through someone else's POD API
The press is rented. Everything that can go wrong on the way to the press is ours — which is why the deck has eight verifiers and no order button.
-
Why the engine uses staged memory
The archaeology cube is the engine's own memory pattern turned on the work of building it. The 231-session corpus gave it value.
-
The 42 KB context audit
The reader was serving a quarter of the context the model was trained for, and the plan said there was nothing above it worth reaching for. One unit error, one constant, and 12 GB of headroom.
-
The engine, on the record
What Metatron is — a store, a pass, a refusal and a writer — and the numbers it gave up when asked.
-
The GPU is rented; the box is not
One $23.37 server owns the bytes. One 48 GB L40S exists only while someone is calling it — and a public URL that starts a GPU is a billing surface before it is an API.
-
The laptop in the closet
Before the rented GPU and the $23 server, the system that answers questions about my own corpus ran on a gaming laptop in a room nobody goes in. That was the right first home, not a compromise.
-
The lightest storefront I could build
One dependency, no build step, no platform subscription — and what Shopify and its peers are really charging for.
-
The night the writer went blind
Thirteen rows on an error dashboard. Twelve were one thirty-five minute outage of one shared dependency. The thirteenth had been there for months, and it was hiding the shape of the incident.
-
The studio that earned its trust
I built a local desk that can edit, commit and deploy this publication, then attacked it twice before letting it touch production. The reviews found the bugs that mattered.
-
We drove GIMP from an AI agent. The art was the failure.
A socket bridge into a real GIMP 3.2.6, a 4,500 × 5,400 print canvas, and a round-trip error of 0.0648/255. The tooling worked. The design did not. Keep the calibration card.
-
You be Sub, I'll Own the STACK
Everyone else rents their publication from a platform that owns the rails. This site doesn't. Here are the receipts — and the complete runbook pack, gated, for whoever wants to build their own.
-
They published an API and hid the door
A developer surface that exists, is priced, and cannot be found — and the traps that only show up after you build against it.