NAOMS Devlog

Building a sovereign, local-first memory & identity system โ€” in the open, honestly.

NAOMS engineering update

Week 21

Four articles this week: where things live in the app drawer, why the same desktop app is really two different browsers depending on your OS, what your data export actually contains, and a neural voice that never makes a network call.

๐Ÿ“… Aug 16 โ€“ Aug 22 ยท Process
Commits this week
8,863
(416 merges)
Files changed
2,191
Companion articles
4
(all live and linked below)
Busiest day
2026-08-19
1,886 commits
Quietest day
2026-08-22
305 commits (partial day at the window edge)
Process Dispatch free August 22, 2026ยท3 min readยทmeta

Commits per day โ€” Week 21

Four things changed this week

1

The app drawer stops pretending everything in it is an app

The app drawer open on the canvas after the first step of moving non-app entries out of it, with apps grouped as AI, Money, Work, Knowledge and Social and the owner menu showing behind it. Dark theme, captured on 29 June from a test install during that work, not from this week's build.

Where Should This Thing Live? is a piece of honest housekeeping: the app drawer had quietly filled up with things that aren't apps at all โ€” connection ceremonies, a wallet, raw infrastructure knobs โ€” and sorting them into the places people actually reach for meant admitting, in writing, which part of the fix was still a hack rather than calling it finished.

2

The same desktop app is two different browsers depending on your OS

NAOMS installs natively on macOS and Linux with one click and no terminal, but The Same App On Two Operating Systems Is Two Different Browsers is a reminder that "native install" doesn't mean "identical runtime": the window it opens is a different browser engine on each OS, with different features switched on out of the box, so a feature that wants your microphone has to know which browser it's actually standing on before it asks.

3

Your data export tells you exactly what it contains

The Door You Hope Never To Use covers exporting everything NAOMS holds about you and walking away with it. Worth knowing is how it's built: chains and the relationship graph by default, your files and vault secrets only if you explicitly ask for them, a receipt whose numbers are computed from the export itself rather than asserted separately, and a confirmation step designed so the answer that counts is actually yours.

4

A voice that never leaves the machine

A Voice That Never Leaves The Machine covers local text-to-speech: NAOMS can now speak in a warm neural voice with no network call, no API key, and nothing sent anywhere. The genuinely hard part wasn't producing the speech โ€” it was making a 1.7-billion-parameter model answer fast enough that you'd actually let it talk to you, via a warm resident server with a cold-load and an OS-voice fallback behind it if that server isn't running.

What changed area by area

As in week 20, the largest commit volumes this week are fleet-internal โ€” treasury-settlement work, transport plumbing, coding-agent-policy bookkeeping, CI โ€” and none of them shipped a change a person outside the fleet would see, so none is written up above. The real counts, per-commit file union over the window:

token 233 ยท core/transport 217 ยท scripts 166 ยท browser client 146 ยท core/chain 120 ยท coding-agent-policies 94 ยท repo-pipelines 89 ยท hives 77 ยท chat 74 ยท agents 63 ยท photos 59 ยท calling 56 ยท sdk 43 ยท files-browser 36 ยท plan 36 ยท pkg-manager 31 ยท core/tools 30 ยท core/boot 27 ยท messaging-adapters 27 ยท ai-chat 27.

Three quiet days, honestly unexplained

Three days at the start of this window โ€” 2026-08-16 through 2026-08-18 โ€” carried real commit volume (1,206, 1,041 and 1,628 respectively) with no companion article published against them. Nothing in this session established why, and this dispatch does not guess at a reason or invent a feature to explain it.

โ† more in Process   home โœฆ   all โ†’