I published a blog post a few hours ago announcing that Sentinel is open source.
The original opening said:
“It took two days to build. It took twenty years to know what to build.”
It was true. It was also wrong.
Not factually wrong. Perceptually wrong. A security architect reading that line maps it to every hackathon toy they’ve ever seen die in production. “Two days” signals prototype. Fragile. Unproven.
So I got a second opinion from a different AI — one I use specifically because it doesn’t agree with me. It came back with a reframe that landed harder:
“The code took two days. The model took twenty years.”
Same fact. Different signal. One sounds like a rush job. The other sounds like compressed execution of a mature mental model.
I changed it. Same evening. Same post. And I’m telling you about it instead of pretending the first version never existed.
Why Show the Edit
There’s a Japanese art form called kintsugi. When pottery breaks, you repair it with gold. The cracks aren’t hidden — they’re illuminated. The piece becomes more valuable for having been broken and repaired with intention.
Most people in tech hide the edits. Ship the polished version. Delete the drafts. Pretend the first take was perfect.
I’m going the other direction.
Sentinel is open source. The code is public. The commits are public. And now the thinking behind the writing is public too. You can watch the reasoning evolve in real time — not because I’m performing transparency, but because hiding the process is more work than showing it, and the showing makes the work better.
How This Post Got Written
This morning I woke up with one goal: test whether a Cloudflare payment upgrade fixed a dashboard I’d been blocked on.
By noon I had:
- Fixed the dashboard
- Designed a phone app
- Invented an active meditation protocol on a Onewheel
- Started building a product vision for a digital neighborhood network
By afternoon I had:
- Open-sourced a security framework
- Scrubbed the entire git history of personal identifiers
- Written and deployed a blog post
- Built an Android app and installed it on my phone
- Generated invite codes for a cycling telemetry platform
By evening I was rewriting the blog post because a second AI told me the opening was perceptually wrong.
None of this was planned. All of it was connected. The meditation informed the app. The app informed the network vision. The network vision informed how I positioned Sentinel. And a sharp critique informed a better opening line.
That’s how the work actually happens. Not in a straight line. In a spiral.
The Commitment
From here forward, Northwoods Sentinel builds in public. Not just the code — the thinking. The edits. The wrong turns. The moments where a second opinion changed the trajectory.
If you want polished, there are plenty of vendors with marketing departments.
If you want real, watch the git log.
Every edit is gold in the seams.