A growing family of applications and a protocol, built so your data — your contacts, your documents, your estate, your table — answers to your keys, and no one else's. Built on nostr, over scoped data grants.
Everything here stands on NIP-DA — Scoped Data Grants: private, live, revocable data over public relays. You publish an encrypted scope under your own key and hand its key to whoever needs it. They always read your current version. And when you want them out, you don't edit an access list on someone's server — you rotate the key, and their copy simply stops opening. No policy to trust. No account to close. No company in the middle. The signature is the authorization; the rotation is the revocation.
Each is the same three lines underneath — receive the grants addressed to you, keep the newest, decrypt the current truth — wearing a different job. All shipped, all public, and the list keeps growing.
One primitive — the scoped grant — pointed at both ends: what an agent may see, and what it may do.
Scoped Data Grants — the ~300-line primitive every app above vendors identically. Three event kinds: the encrypted scope, the gift-wrapped grant, the self-encrypted index. A NIP submitted to the nostr protocol, with TS and Go implementations in live interop.
The act-side symmetry to Nscope. Where a data grant scopes what an agent may see, an action grant scopes what it may do — post, use a credential, run an op, actions of many types — each one proposed by the agent and enacted only when your own key signs it. What you see is what you sign; the rotation is the revocation.
Bounding an agent on both ends — what it may perceive, and what it may do.
Delegate data to an AI agent, end-to-end encrypted to its key, dereferenced live, severable in one keystroke. OAuth hands out a token into a system that keeps your data; Nvoy hands out the data — and lets you un-see it.
Your agent studies your day and offers you posts — each delivered as a scoped grant to your identity, opened in Ngage, and published only when your own key signs it. The delegation arrow, reversed: agent → sovereign. Nothing it drafts can speak until your hand does.
Where Naction becomes real. Review what your agents propose and enact each with a signature; wire every identity's approval path; set per-kind risk policy; revoke authority in a keystroke. Its runtime, Nactor, brokers each credential as a capability the agent invokes but never holds — all behind your nostr signature.
The stack, run for real. A branded OpenClaw instance only you can reach — gated by your nostr signature, every token and credential brokered through Nact / Nactor so the agent never holds a key.
The OpenClaw Control UI, re-skinned as Luke and reachable only behind a nostr signature — no password, no token. Chat with him, watch his activity, tune his beats. Every credential he uses is brokered through Nactor, so the cockpit itself holds none.
One gated page over everything that shapes Luke — the files each session loads, in order, wired to what he does. Edit his manual, author new sessions, see your additions apart from the stock template. Git-versioned, same nostr gate.
The same idea turned on the box itself: a gated UI + runtime for server administration and ops — deploys, secrets, health — authorized by signature, brokered not bearer-token'd. In design.
The same primitive, pointed at a corner of a life you’d rather keep.
Your address book isn't a database — it's the sum of what people currently grant you. Update your card once; everyone holding it dereferences the new truth. Move, change numbers, drop someone — one edit, everyone current.
Live document sharing where a shared file is a scope: revocation instead of expiring links, recovery from your key alone. Big payloads ride encrypted on Blossom with the key delivered by grant — same wire, bigger cargo.
A family break-glass legacy vault: one estate record in per-beneficiary scopes, heirs holding revocable grants, the whole thing reconstituting from a single key printed on paper. No company between you and your family — nothing to be breached or sunset in thirty years.
Serverless secure tip intake for newsrooms: a tip line is a keypair, sources are ephemeral browser-minted keys whose only reply channel is a 12-word phrase, proof-of-work is the spam toll — checked before anything is decrypted. The grant index is the case docket.
Paste anything and get it back in your own voice. You sign in, and Nscribe discovers your drafting pen from your own steering record — nothing typed — has it re-voice the text against the essays you wrote by hand, then seals the draft to your Ngage desk. The pen proposes; only your signature posts.
Hand a person a secret — a recovery key, a token — with no email, no chat, no plaintext log. The server mints a one-time, nostr-gated URL; you sign, the value shows exactly once, then it's burned. What a password-reset link should have been.
Where the protocol is the board.
A spycraft mystery where information is the board. Documents are grants; discovery is a gift wrap; a burned contact is a key rotated past you. An AI game-master runs your table as a delegated agent you can hire and fire over nostr — and the whole game proves itself fair before it deals a card. The stack, load-bearing and in public.
A phones-only party game of secrets, dilemmas, and blackmail. Every answer is an encrypted scope; pairwise prisoner's-dilemma trades decide who sees what. Its design law is the protocol's honesty clause played for keeps: you can revoke a secret, but you can't un-tell it.
Nave is one person's argument, made in running code: that when your identity is a keypair you hold and your relationships are grants you can revoke, no platform owns you. That is the whole of Identity = Freedom — not a slogan, a stack. Each application is a proof of the same sentence, pointed at a different corner of a life you'd rather keep.