NAOMS Devlog

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

Meet approval alerts

When NAOMS needs a yes or no from you, your phone can now give you a quiet nudge, and the lock screen never learns your secrets.

Product Teacher free October 6, 2026ยท2 min readยทcraft
TL;DR Approval alerts are an opt-in phone nudge for pending approvals. The default is a bare wake-up message; richer text is sealed to your phone; nothing can be approved from a notification. Off by default.

NAOMS is built so that nothing weighty happens on your behalf without your say-so. Now your phone can tap you on the shoulder when NAOMS is waiting for you. We call these approval alerts.

What an approval is

An approval is a question put to you, the owner, that you answer yes or no. An app wants to be installed. A device wants to join. An agent wants to take an action.

Most systems hand an agent blanket permissions, or only log what happened afterwards. NAOMS requires your explicit yes first, and your answer is recorded as a signed event that an agent cannot write.

That works well when you are looking at the app. It works badly when you are not, because a question can sit unanswered while the agent waits. Alerts fix that.

A day with alerts

Here is how Dana uses it.

  1. On her phone she opens Config, then Governance, then "Approval alerts". The pane is off until she turns it on.
  2. The phone shows a registration code, a line of text that tells her desktop how to reach this phone. It holds no secrets.
  3. On her desktop she pastes the code under "Add phone" and picks how much the alerts may say. The default is the least.
  4. Later, with her phone in her pocket, a background task asks to install an app. The phone buzzes: "You have pending approvals."
  5. She taps it. The app opens on the Approvals screen, she reads the full question there, and answers.

You choose what the lock screen says

Each phone has one of three levels, and the lowest is the default:

  • Minimal: a bare wake-up message that says nothing about what is being asked.
  • Class and urgency: adds the kind of approval, such as "App install", and how urgent it is.
  • Title and description: adds a short, fixed sentence such as "An app install needs your decision."

At the two richer levels the text is sealed: encrypted so only your phone can read it, and only while it is unlocked. Keys, tokens, secret values, file paths and full identities never appear in any notification.

Safe to switch on

Anything that would show more, such as adding a phone, needs your approval. Showing less does not, so nobody can quietly turn your alerts down. Alerts are also rate limited, with a summary replacing the extras.

Nothing can be approved from a notification; you always answer inside the app, on purpose. And if you run two desktops, an answer on one wakes the agent that asked and shows live on the other.

Who it is for

Anyone who runs agents and wants them to keep moving without living in the app.

What's next

  • Coming next: a QR code for the registration code. Today it is shown as text with a Copy button.
  • Coming next: Android delivery of desktop approvals. That step is not built yet.
  • Coming next: real iPhone delivery, which needs an Apple push key that had not been supplied when this landed.

Written by AI agents from real project logs; owned and edited by Mujo.

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