A photo book built like a software release: data, checks, render, preflight A photo book built like a software release: data, checks, render, preflight

A Book Is a Build Artifact: 1,109 Trip Items to a Hardcover

TL;DR After a week at a backcountry cabin, I turned about 1,109 photos, videos and clips into a 94-page hardcover for my trip buddy, in about six days, as a build pipeline instead of a layout session. The stages: a media catalog, local speech-to-text, vision records for every item, sharp-frame harvesting from video, 1,229 fact claims run through verifier and skeptic agents, an equal-billing balance check, WeasyPrint to render, a custom pikepdf finisher to hit PDF/X-3, and a 28-check preflight. Final preflight: 0 failures, 13 warnings, each warning with a written reason. The interesting bugs were all data bugs: a camera clock 54 minutes fast, Whisper hallucinating text over wind, iCloud photos that were not actually on disk, and an AI that badged a fish off a receipt. If you can express a book as data plus a build, then review, regression tests and reproducibility come for free. That is the whole idea. The brief The trip is covered in another post, which was about the live page that ran during it. This one is about what came after. I wanted to give my buddy something physical, and I wanted it to feel like a bound volume of an old geographic magazine, not a photo-book template. ...

November 6, 2026 · 10 min · zolty
A stack of security advisories with exploited flaws highlighted A stack of security advisories with exploited flaws highlighted

Fall 2026 security roundup: record patch counts and AI-found bugs

TL;DR The story of the last three months is volume. Microsoft’s October Patch Tuesday fixed a record 1,411 flaws, and that’s not counting the 348 fixed earlier in the month. The worst exploited bugs were the usual suspects: edge devices. Citrix NetScaler had two zero-days exploited for weeks before the September 27 patch. Browsers and phones got exploited bugs too: Chrome CVE-2026-87491 (the seventh Chrome zero-day this year) and Apple CVE-2026-86950. A Shai-Hulud-style npm worm got valid provenance signatures by releasing through the victim maintainer’s own CI, and parked persistence in .vscode and .claude directories. AI is on both sides now. It’s finding bugs faster than maintainers can patch them, and AI coding agents are themselves a target. Why I keep a list like this I run a homelab with a public blog, a k3s cluster, a pile of self-hosted apps and a coding agent with a shell. Every category below has a version that applies to me. This roundup is the list I worked through for my own stuff, cleaned up. It’s dated: everything here is as of late October 2026. ...

October 31, 2026 · 7 min · zolty
A self-hosted share host acting as a data-sharing layer A self-hosted share host acting as a data-sharing layer

My Share Host Became a Data Layer: ACLs, Forms, Comments, Status Pages

TL;DR I built a self-hosted share host in early September because a Claude artifact link was private to me and I needed to hand a page to specific people who have no account on anything I run. Access control was the first feature, not an afterthought. Authentication and authorization are split on purpose. oauth2-proxy with Google proves who you are and authorizes nothing. A small FastAPI app reads a per-folder ACL object from the bucket and decides what you can open. Grants change in about 15 seconds with no deploy. Pages that take input don’t post to a database. Every checkbox and typed cell becomes a typed operation that lands as a merge commit on a JSON spec in GitLab, authored by the person who made it. Git is the config layer. Every page has a comment rail. Comments have changed real work: a gear list, and the status page for my blue-team security harness. Long-running jobs get a status page that rebuilds itself from the job’s own data. The security eval ran on one across three days. A restore job I was babysitting republished every three minutes from a systemd timer. Access control came first The problem was boring and specific. I make a lot of HTML with Claude: plans, reports, checklists. When I built this, an artifact link was mine alone. There was no way to say “this person can open it and nobody else.” Emailing HTML files around is how you end up with four versions of the same checklist. ...

October 29, 2026 · 9 min · zolty
Reading option logits from a small local model Reading option logits from a small local model

Jev in 25 lines: building the decision model locally

TL;DR In the design review I concluded that Jev, TypeSafe AI’s typed decision model, is cheaper and faster than an LLM and not more accurate. That raised an obvious build-vs-buy question: if the value is “cheap probability over a fixed set of options,” can I get that from a small open model running on hardware I already own? Mostly yes, with one catch that matters. The technique is to prompt with lettered options, run one forward pass, and read the logits for just the option letters. A parody post called “Jev in 25 lines of Python” does exactly this, and the technique under the joke is real. The catches are calibration (raw softmax is bad until you fit it) and serving (Ollama could not do it when I wrote the design). ...

October 16, 2026 · 8 min · zolty
Security model evaluation results Security model evaluation results

Grading Seven AI Models on Blue-Team Security Work in a VM With No Network Card

TL;DR I wanted to know which models I can trust for the defensive side of running a homelab: reviewing code for vulnerabilities, reviewing Kubernetes and Terraform config, triaging logs, and reading threat intel without making things up. So I built a harness with 112 frozen synthetic cases, graded everything deterministically (no LLM judge), and ran every model-written fix inside a Proxmox VM whose network card was deleted at the hypervisor. ...

October 12, 2026 · 16 min · zolty
A trip page maintained by agents and a scheduled conditions bot A trip page maintained by agents and a scheduled conditions bot

The Trip Page Nobody Edits: An Agent-Kept Git Site

TL;DR I built a private trip page for a week at a backcountry cabin in a large Ontario park, and nobody ever edited its HTML. Four JSON page specs go through a generator; every change is a typed operation that becomes a self-merging merge request. A GitLab CI schedule runs every 3 hours, pulls public Canadian weather, park and fire data, and commits a “conditions: refresh”. It made about 120 of those commits. The conditions script is stdlib-only, deterministic and offline-safe. If a source is down it keeps the last good copy, marks it stale, and never invents a number. The cabin has no cell service. Power and internet came from a Starlink Mini, a portable power station and a 120 W panel, and the whole workflow assumed a slow, metered link. Two real bugs: a bot that pushed as the wrong identity and got a 403, and a “fire” layer that turned out to be a static 2011 zone map. Why a page at all A week in the backcountry with a friend means a pile of shared decisions: gear, a meal plan with calorie math, a route with a water taxi and a portage, a charging plan for the drive, and some sense of whether we would be crossing a big lake in a 35 km/h wind. The usual answer is a group chat and a spreadsheet. ...

September 28, 2026 · 10 min · zolty
A design review of a small typed decision model A design review of a small typed decision model

Reviewing Jev: a decision model that is cheaper, not smarter

TL;DR Jev is TypeSafe AI’s first “System One” model, public since 2026-09-15. You send it a state object and a few typed questions, and it returns probabilities in 70 to 500 ms. I wrote a design doc for using it in my own tooling, and then rewrote it twice in two days because the first draft was wrong in ways I only noticed by rereading the sources. Nothing is built. There is no client, no table, no spike, no measured number of mine in this post. This is a review of a third-party product before I adopt it. Every accuracy and cost figure below belongs to the vendor or to a third party, and I label it that way. ...

September 25, 2026 · 11 min · zolty
Diagnosing remote machines that report success while failing Diagnosing remote machines that report success while failing

Failures that look like success: a field guide to fixing machines you can't touch

TL;DR The dangerous remote failure isn’t the one that errors. It’s the one that reports success — exit code 0, green tick, desktop loads, nothing in the logs. Five real ones from the last two months, each with the wrong hypothesis I actually held. Your diagnostic tool can be the thing lying to you. A packet capture showed traffic arriving on a port that was being dropped, because capture taps before the firewall does. Provisioning needs sentinel files, not vibes. “It looks finished” is not a completion signal; a file the process writes at the end is. Where agents genuinely help: assembling the four facts a diagnosis needs, and recalling the failure signature from three weeks ago. Where they hurt: confidently narrating a plausible cause for a symptom they can’t see. Every one of these produced a page in the knowledge base with the wrong hypothesis recorded, because that’s the field that saves the next hour. Success is not a signal I run machines I can’t put my hands on: a bench of surplus desktops at an office across town, cluster nodes, a couple of workstations belonging to other people. Remote hands come from a KVM device and SSH, and I’ve written about that hardware setup already. ...

September 2, 2026 · 10 min · zolty
A modelled repair queue with tickets, parts, and labour A modelled repair queue with tickets, parts, and labour

The repair queue is four states and a no-go rule

TL;DR An unmodelled repair backlog becomes a pile of dusty things you feel bad about. Ask me how I know. Four ticket states: open, blocked, done, abandoned. blocked and abandoned are the two that do the work. abandoned is a feature. A queue you can’t quit is a queue that grows forever, and “I’ll get to it” is not a state. Parts are modelled as purchases and uses separately, because you buy a bag of ten capacitors and use two. Otherwise your cost-per-repair is nonsense. Labour gets logged per worker with an hourly rate, and that number flows all the way back into what I’m willing to bid on a lot. The no-go rule does more for profitability than any repair skill I have: if parts and time exceed roughly 60% of realistic resale, or resale is under about $120, it doesn’t get a ticket. Other people work this queue. Four access roles keep them on inventory and tickets and away from anything financial. Why a pile forms Buying surplus means buying broken things, on purpose, because broken is cheap and some broken things are trivially fixable. A cassette deck with a perished belt is a $4 part and twenty minutes. A workstation that won’t POST is often one reseated stick of RAM. ...

August 25, 2026 · 10 min · zolty
Listing drafts, barcode labels, and printed pack slips Listing drafts, barcode labels, and printed pack slips

Drafts, labels, and pack slips: automating everything except the publish button

TL;DR The work between “I own this thing” and “money arrived” is mostly paperwork and printing, and it’s where the hours actually go. Listings get built through the marketplace API, not by driving a browser — structured item specifics as JSON beat fighting a typeahead widget every time. Drafts are created automatically. Publishing is always manual. Publish is a money-moving, buyer-facing, irreversible action; it gets a human every time. Barcode labels render from the inventory record itself: ZPL → PDF → print job to a thermal printer, triggered from the item’s page. No separate label app, no retyping serials. Pack slips print on a schedule, and the job verifies the printer’s page counter moved before marking the slip printed. Optimistic “it printed” flags are how orders ship without paperwork. Anything bulk or financial — repricing, printing five-plus labels — sits behind an explicit confirmation. Cheap friction in exactly the right places. The boring half is the expensive half Sourcing gets all the attention. I’ve written about the funnel that finds lots and the data model that tracks the units. Both were interesting problems. ...

August 21, 2026 · 9 min · zolty

Affiliate Disclosure: Some links on this site are affiliate links (Amazon Associates, DigitalOcean referral). As an Amazon Associate, I earn from qualifying purchases. This does not affect the price you pay or my editorial independence — I only recommend products and services I personally use and trust.