An honest, in-the-open devlog of building NAOMS — a sovereign, local-first memory & identity system. Every week, what shipped and what broke.
Week 24 — NAOMS Engineering Update
Four things changed this week A quieter week by volume, and several of its largest changes took something away.
Week 23 — NAOMS Engineering Update
Four things changed this week One per area; the first three have their own article or section below.
Week 19 — NAOMS Engineering Update
Four things changed this week One per major area, none touching the same code.
Week 18 — NAOMS Engineering Update
Four things changed this week Nothing was published in these seven days, so this week is read from its own record rather than from companion articles.
Week 17 — NAOMS Engineering Update
Four things changed this week Two of these are surfaces you work on. One is a way a group settles something. The fourth added nothing you can screenshot and is the one the other three depend on.
Week 16 — NAOMS Engineering Update
Four things changed this week Two of these are surfaces you land on. Two are refusals — a screen declining to show you something it cannot stand behind, and a control declining to overstate what it did.
Week 15 — NAOMS Engineering Update
Four things changed this week One per area. Behind last week's new doorways, the work itself moved onto your hardware, and the records that leave your machine got quieter about who you are.
Week 14 — NAOMS Engineering Update
Four things changed this week One per area, and each one is a way in rather than a feature inside. None of them is finished, and the substrate underneath all four is the same governed, local-first daemon it was last week.
Week 13 — NAOMS Engineering Update
Four things changed this week Four threads carried the week, and none of them touches the same code as another. Two had been standing in for themselves for months and became real. The other two are foundations — one for moving large files between your own…
Week 12 — NAOMS Engineering Update
Four things changed this week A loud week, and an uneven one: 628 commits on the Monday, 11 on the Wednesday, then 464 and 356 as the overnight runs came back.
Week 11 — NAOMS Engineering Update
Four things changed this week Four threads carried the week: one boundary landed, one diagnosis was reversed in public, one everyday wait was explained down to its cost in memory, and one uncomfortable question about AI agents got a structural answer.
Week 10 — NAOMS Engineering Update
Four things changed this week One per major area, and a week with an unusual shape: 1,303 commits on the Monday, 100 on the Wednesday, 1,028 on the Saturday.
Week 9 — NAOMS Engineering Update
Four things changed this week One per major area, and the week's shape was front-loaded: busiest on 13 May, tapering toward the weekend.
Week 8 — NAOMS Engineering Update
Four things changed this week Four threads, none of them a new feature on a screen. Three are about the project being honest with itself; the fourth is about what a message has to prove before you believe it.
Week 7 — NAOMS Engineering Update
Four things changed this week Two landings, one architecture set down in writing, and one evening that turned a status report into a standing rule.
Week 6 — NAOMS Engineering Update
Four things changed this week One per major area. Calling is the headline, and three other threads landed beside it — one of them going from a Friday conversation to finished overnight.
Week 5 — NAOMS Engineering Update
Four things changed this week One per major area. There is no marquee demo this time — the week's real work was hardening the things that hold identity and memory, and refusing to let green tests stand in for finished ones. Two of the four below are design…
Week 4 — NAOMS Engineering Update
Four things changed this week One per major area. Almost none of it is visible on screen — this is the week the plumbing got serious and the pixels took a break.
Week 3 — NAOMS Engineering Update
Four things changed this week One per major area. The through-line is proof: proving you own an account, proving one attribute without the rest, proving a file arrived intact, and proving a permission was granted by a community rather than simply assumed…
Week 2 — NAOMS Engineering Update
Four things changed this week Four areas moved at once: encryption, consent, trust, and the network path underneath all three. The database beneath everything was rebuilt in the same seven days.
Week 1 — NAOMS Engineering Update
Four things changed this week One per major area, none touching the same code. This is the first window in the series, so each of them is a beginning rather than an improvement on something described before, and each has a longer account published the same…
Browse by theme
Vision is the big picture · Product is what you can do · Technology is how it works · Process is how we build it — or read everything by date →
Vision
Why this matters and where it's going — for investors, new members, and the curious.
60 postsProduct
What you can do with it, and what comes next — for people who'd build with NAOMS.
100 postsTechnology
How it actually works, in depth — for developers and due diligence.
50 postsProcess
How we build it, honestly — for collaborators who might join.