Skip to main content

Vol. MMXXVINo. 92

Field reports from cloud-security engineering,AI experiments, and a homelab that keeps getting bigger.

Latest writing from William Zujkowski

Security·10 min read·

Nobody Ran It

Ninety agent-assisted posts, audited against source. The defects weren't bad reasoning — they were artifacts nobody had ever executed. Why models produce that, why review can't see it, and what actually catches it.

  1. Security·8 min read·

    The Policy Is the Part That Moves

    A proved gate is only as good as the policy it enforces, and the policy is the part that changes while the agent is running. What OSCAL and the agent-authorization drafts both assume, and what breaks.

  2. Security·14 min read·

    Nobody States Their Denominator

    npm's own replication database says 4,288,093 packages. The aggregator most supply-chain research runs on says 5,732,659. The gap is retained unpublish tombstones, and sampling from the wrong side moves a headline number by sixteen points.

  3. Security·7 min read·

    You Can't Prove the Agent. Prove the Gate.

    Formal verification for AI-agent security. You can't prove a probabilistic model does the right thing — but the deterministic gate in front of it is small enough to prove outright. Dafny proofs, a Rego twin, and differential testing, following the method AWS used for Cedar.

  4. Security·7 min read·

    The Firewall Stays Put. The Agent Improvises.

    Rewriting security controls for probabilistic agents. Static control catalogs assume systems that do what they're told; AI agents don't — so here's how to express agent guardrails (tool allowlists, secret-egress denial, audit) as machine-checkable OSCAL component definitions.

  5. Design·10 min read·

    545 Terminal Themes, and the Rabbit Hole That Produced Them

    A dataset of 545 terminal color schemes, converted to OKLCH and republished as an npm package — and the theme picker in this site's own header that quietly runs on it.