AI is humanized compute
AI isn't a new domain, it's compute grown up enough to act. Treat it like staff: a broad junior, always inside a human accountability tree, carrying its own papers.
Notebook
Field notes, ideas, opinions and the occasional detour — short, practical writing on networking, security, infrastructure, the homelab and whatever else I'm tinkering with.
AI isn't a new domain, it's compute grown up enough to act. Treat it like staff: a broad junior, always inside a human accountability tree, carrying its own papers.
The framework I use to keep infrastructure sane: five pillars on four foundations, every component a CI wired to the rest.
Identity is the control plane for who and what can do what. The trick to keeping it sane: nest accounts into groups and roles, and never pin a permission on a user.
Completing an open-source identity stack with governance and privileged access — and why an AI coding agent finally makes it cheaper than CyberArk.
A private CA as the single SSH trust root: short-lived certs for humans (SSO+MFA), 10-minute ones for machines, and host certs that kill known_hosts TOFU.
Closed software earns its place, but engineer the exit. The line that matters: a moderate lock-in you can leave, a super lock-in that owns you.
Implementing AI isn't buying a tool. It's staffing a team: expert at the task, junior at the call. Why that reshapes hiring, not just headcount.
When an orchestrator agent delegates to a sub-agent, it can quietly hand over a token that does far more than the sub-agent should. Here's the token-chain risk, IBM and Red Hat's Kagenti blueprint, and a zero-trust pattern you can run without re-platforming onto Kubernetes.
Token prices are heading for a real-cost reckoning. The way through is the one we use for compute: own the AI baseline, burst for the bleeding edge.
Defense-in-depth at the homelab edge with CrowdSec: known-bad IPs dropped at the door, then an in-band WAF reads what's left. And why it's deliberately fail-open for now.
Where midPoint plus Authentik can replace the Microsoft identity stack in a hybrid Windows/Linux shop. And where it can't. A thought experiment, not a build.
An internal site that wouldn't load, a resolver that was never asked, and the dead-IP query that proved a 'helpful' gateway was answering DNS behind my back.
I measured uv against our pin-everything dependency policy. It fits. And we're still staying on stdlib venv. The why is more interesting than the verdict.
Wiring our identity agent into a secrets manager without handing it the kingdom: read-only by default, segregation of duties, and writes you have to mean.
From a typed request to a guarded action against a real system, a walk down the stack that turns Claude Code into a fleet of homelab operators: the CLI, the shared agent-core, the agents, their skills, and the actions they perform.
A simple question (do our agents need MCP?) that quietly turned into a clearer picture of skills, MCP servers, and the identity layer sitting underneath both.
Building a DNS skill for our network agent, and the two-layer permission model that hid our zones in plain sight.
Standing up an authoritative internal resolver as code: split-horizon, encrypted upstreams, and the moment the new DNS box couldn't resolve its own installer.
Teaching my agent to update Docker stacks within policy: including the source-built ones that have no image to pull.
Building the cloud-init template every VM clones from. And learning the hard way that UEFI + cloud images + a serial console hides your boot failures.
The first phase changes nothing. It just reads live state and proves how wrong the plan already was. Discovery is the cheapest phase and the most valuable.
Starting a phased, infrastructure-as-code rebuild of the homelab, and pairing with an AI agent that does the typing while I keep the judgement.
The five-minute baseline I apply to every new server before it goes anywhere near a network.
Segmentation isn't just an enterprise checkbox. Here's how I split a single Proxmox node into safe zones.
A critical-auth VLAN so a dead RADIUS server doesn't take a whole floor offline.