#stack72
LightNews LightNews
ke0opr.bsky.social
ICAO: #ADFF4F
Owner: #USAF
Flt: #STACK72 #668403 #T38
Time: 2026-09-18 09:12:33 CDT
Min Alt: 17525 ft
Min Dist: 78.51 nm (-122deg WSW)

#adsb #planefence by kx1t sdr-e adsbexchange flightaware faa
September 18, 2026 at 2:24 PM
ke0opr.bsky.social
#PlaneAlert ICAO: #ADFF4F
Owner: #USAF
Flt: #STACK72 #668403 #T38
Time: 2026-09-18 08:45:04 CDT
Min Alt: 15725 ft

#adsb #planefence #planealert by kx1t sdr-e adsbexchange flightaware faa
September 18, 2026 at 1:46 PM
ke0opr.bsky.social
ICAO: #AE003C
Owner: #USAF
Flt: #STACK72 #697080 #T38
Time: 2026-09-10 16:19:16 CDT
Min Alt: 17550 ft
Min Dist: 82.47 nm (-145deg SW)

#adsb #planefence by kx1t sdr-e adsbexchange flightaware faa
September 10, 2026 at 9:51 PM
ke0opr.bsky.social
ICAO: #AE003D
Owner: #USAF
Flt: #STACK72 #701562 #T38
Time: 2026-09-03 15:56:36 CDT
Min Alt: 16200 ft
Min Dist: 80.87 nm (-122deg WSW)

#adsb #planefence by kx1t sdr-e adsbexchange flightaware faa
September 3, 2026 at 9:14 PM
adamhjk.me
Our most recent example is how we replaced our traditional CI pipeline with agent attestation.

Paul writes a great blog about it: stack72.dev/ai-broke-the...
September 1, 2026 at 6:10 PM
ke0opr.bsky.social
ICAO: #AE0036
Owner: #USAF
Flt: #STACK72 #688173 #T38
Time: 2026-07-10 13:25:39 CDT
Min Alt: 17875 ft
Min Dist: 113.93 nm (-134deg SW)
Squawk: #5766
#adsb #planefence by kx1t sdr-e adsbexchange flightaware faa
July 10, 2026 at 6:35 PM
ke0opr.bsky.social
ICAO: #AE0006

Flt: #STACK72 #6413289 #T38
Time: 2026-07-07 09:00:11 CDT
Min Alt: 16750 ft
Min Dist: 77.13 nm (-121deg WSW)

#adsb #planefence by kx1t sdr-e adsbexchange flightaware faa
July 7, 2026 at 2:26 PM
ke0opr.bsky.social
ICAO: #AE000F

Flt: #STACK72 #6510369 #T38
Time: 2026-06-26 08:53:18 CDT
Min Alt: 19200 ft
Min Dist: 118.85 nm (-134deg SW)

#adsb #planefence by kx1t sdr-e adsbexchange flightaware faa
June 26, 2026 at 2:02 PM
stack72.dev
Bug reports that looked like noise turned out to be 3 compounding root causes underneath.

We rearchitected the whole thing in 8 days, multiple agents working together.

If it failed, we lost 8 days. Previously this would've been a 6 month project unprioritised.

stack72.dev/the-rearchit...
The Rearchitecture Your Team Could Never Justify
Every codebase has the rearchitecture that never gets prioritised. We split ours into six parallel workstreams and shipped it in eight days, start to finish. The hard part wasn't speed. It was coordin...
stack72.dev
May 14, 2026 at 11:59 AM
stack72.dev
Your backlog is not a product strategy. When every feature is an afternoon's work, the product that wins is the one where someone had the taste to say no.

And that's not something an agent can help you with.

stack72.dev/when-buildin...
When Building Is Easy, the Danger Is Building Everything
When agents can build anything in an afternoon, the temptation is to build everything. The products that survive are the ones where someone had the discipline to say no.
stack72.dev
May 11, 2026 at 1:02 PM
stack72.dev
I've been writing about how AI agents changed my work. Stopped typing code, started making better decisions, how we are building swamp with agents doing all the implementation.

The fear is real. The shift is real. The difference is structure.
stack72.dev/take-the-lea...
Take the Leap Before You Are Pushed
The fear of AI replacing your work is real. So is the shift. The teams that build structure around agents instead of resisting or rushing find the job gets better, not smaller.
stack72.dev
May 6, 2026 at 3:20 PM
stack72.dev
I haven't written code in months (probably for the best). Five of us build swamp, none of us write code manually.

The job got bigger, not smaller. The code was never the job — the understanding was.

New post up: stack72.dev/the-code-was...
The Code Was Never the Job
Five of us build swamp. None of us write code. Agents write it, review it, test the binary. The work didn't shrink — it shifted to the decisions that were always the most valuable.
stack72.dev
May 4, 2026 at 3:25 PM
stack72.dev
Honest question for OSS maintainers: what percentage of the PRs you review this month were from someone who actually read the code they changed?

GitHub shipped a kill switch for pull requests. That should tell you everything about where this is headed.

stack72.dev/the-communit...
The Community Pull Request Is Dead
The PR-as-contribution model was built for a world where writing code was the bottleneck. AI agents broke that assumption. GitHub shipped a kill switch on PRs. Hashimoto built Vouch. We closed the doo...
stack72.dev
April 27, 2026 at 10:29 AM
lukehedger.dev
after a week wrestling with docker sandboxes this is the exact conclusion I’ve come to. Sandboxing was slowing me down and for very little return beyond filesystem protection. deliberate, destruction-resistant permissions gives you the isolation without the hassle

stack72.dev/agent-trust-...
Agent Trust Is a System Design Problem
Most people hit "always allow" within the first hour. Agent trust is a system design problem, not a containment problem. Three layers of permissions, conventions, and context let the agent work autono...
stack72.dev
April 23, 2026 at 9:45 PM
stack72.dev
I sorted every agent tool into two buckets: can git checkout undo it, or does it touch something external?

Eliminated 90% of permission prompts. Kept the ones that matter like gh pr create.

stack72.dev/agent-trust-...
Agent Trust Is a System Design Problem
Most people hit "always allow" within the first hour. Agent trust is a system design problem, not a containment problem. Three layers of permissions, conventions, and context let the agent work autono...
stack72.dev
April 23, 2026 at 3:10 PM
stack72.dev
We test our code but we also test the thing users download.

Separate repo, real compiled binary, CLI tests plus adversarial security and benchmarks. Three potential regressions that were caught in minutes before any user saw them.

The next part of the machine:

stack72.dev/the-gate-bet...
The Gate Between Our Agent Code and Our Users
Every release binary gets dispatched to a separate repo running CLI tests, adversarial security tests, and benchmarks. Three recent bugs — all with full unit test suites passing — never reached a user...
stack72.dev
April 21, 2026 at 5:35 PM
lukehedger.dev
“you're not just shipping code, you're building a system that learns how to ship better code” @stack72.dev

stack72.dev/anatomy-of-a...
lukehedger.dev Luke @lukehedger.dev · Apr 13
Autonomy engineering?
April 15, 2026 at 10:10 PM
stack72.dev
Agents open PRs in our repo. The diff is untrusted input flowing into models with merge authority. This is what dealing with agentic PRs actually looks like — multiple scoped AI reviews, each with a different job, including auditing changes to the pipeline itself.

stack72.dev/anatomy-of-a...
Anatomy of a Swamp PR
Agents open PRs in our repo. Other agents review them. That means untrusted input flowing through models with merge authority — so we built a pipeline with four independent AI reviews, scoped tools, a...
stack72.dev
April 15, 2026 at 7:20 PM
stack72.dev
Vibe coding breaks around PR #200*. Not dramatically — it just drifts. The fix isn't better prompts. It's building a machine that compounds.

The vibes don't scale.

stack72.dev/the-vibes-do...

* There's no science at all to that 200 number - I made it up :D
The Vibes Don't Scale
Vibe coding works great for the first few PRs. Then you do it two hundred more times and the codebase quietly stops making sense. The fix isn't better prompts — it's building a machine that compounds.
stack72.dev
April 13, 2026 at 3:34 PM
stack72.dev
The difference between an AI agent that helps you and one that guesses is context — the knowledge it loads before it does anything.

We package that as skills in swamp, and test them in CI the same way we test code.

stack72.dev/skills-are-c...
Skills Are Context, and Context Needs Tests
Skills are context. They're the thing an agent reads before it decides how to use swamp. If the skills are wrong, everything downstream is wrong — so we test them in CI the same way we test code, using tessl for quality and promptfoo for routing, across every model we care about.
stack72.dev
April 9, 2026 at 3:50 PM
adamhjk.me
The fantastic Paul Stack explains how he built it here: stack72.dev/the-lifecycl...
The Lifecycle of a Swamp Issue
We use swamp to build swamp. That sounds like marketing until you look at how an issue actually moves through our process — not as a GitHub thread with comments piling up, but as a state machine with ...
stack72.dev
April 8, 2026 at 4:57 PM
stack72.dev
GitHub issues aren't a good fit for an agentic process, so we stopped using them. Plan versions, findings, and feedback rounds all collapsed into comment threads.

We moved the lifecycle into swamp itself instead.

stack72.dev/the-lifecycl...
The Lifecycle of a Swamp Issue
We use swamp to build swamp. That sounds like marketing until you look at how an issue actually moves through our process — not as a GitHub thread with comments piling up, but as a state machine with ...
stack72.dev
April 8, 2026 at 12:52 PM
stack72.dev
Deployed Ghost on DigitalOcean with swamp — load balancer, Litestream SQLite replication, Certbot, DNSimple, all of it.

The whole stack written by Claude using swamp as the guardrails. One workflow run to deploy, one to update.

stack72.dev/deploying-gh...
Deploying Ghost on DigitalOcean with Swamp
I asked Claude to build me a blog on DigitalOcean and it worked hand in hand with Swamp to build one!
stack72.dev
April 6, 2026 at 2:29 PM
stack72.dev
Most of my writing has been for work so I haven’t really been thinking out loud in the same way.

Getting back into that in a new blog.

Starting with why I’ve gone all in on AI and how it’s actually affecting how I work day to day.

I’ll share what I’m learning as I go.

stack72.dev/ai-why-im-al...
AI: Why I'm All In
I'm an AI maximalist, and I think operations is about to get left behind: again. This blog is about closing that gap from the inside.
stack72.dev
April 2, 2026 at 8:39 AM
malfunceddie.bsky.social
#cfgmgmtcamp after the SI talk what is the workshop : Hands-On Infrastructure Management with System Initiative going to be about Wednesday ? @stack72.dev
February 2, 2026 at 11:17 AM