The same construct answers both, but input is permissive behind the denies and output is strict — because a tag in a signed event is an act.
The same construct answers both, but input is permissive behind the denies and output is strict — because a tag in a signed event is an act.
INPUT — may this arriving event reach the subject?
INPUT — may this arriving event reach the subject?
OUTPUT — may the subject sign this event?
OUTPUT — may the subject sign this event?
A curated feed has to be livable: real threads contain strangers. One permitted person, place or thing is enough — denies still come first.
A curated feed has to be livable: real threads contain strangers. One permitted person, place or thing is enough — deniesstill come first.
The subject answers for everything under its signature. Everyone and everything the event names must be covered, and nothing denied is amplified.
The subject answers for everything under its signature. Everyone and everything the event names must be covered, andnothing denied is amplified.
Is it genuine? Its id is recomputed and its signature verified.
Is it genuine?Its id is recomputed and its signature verified.
1
1
DENY unverifiable
DENYunverifiable
The subject-wide gate The global set allows this kind, today, at this hour — e.g. bedtime.
The subject-wide gateThe global set allows this kind, today, at this hour — e.g. bedtime.
2
2
DENY global
DENYglobal
The deny gates Author, arrival relay, the event itself and everything it names — any match blocks.
The deny gatesAuthor, arrival relay, the event itself and everything it names — any matchblocks.
3
3
DENY blocklist
DENYblocklist
One hit admits It arrived from a permitted place, its publisher is a permitted person, it is a permitted thing — or it is the subject's own. Encrypted: only an interact grant on the sender.
One hit admitsIt arrived from a permitted place, its publisher is a permitted person, it is apermitted thing — or it is the subject's own. Encrypted: only an interactgrant on the sender.
4
4
PERMIT shown to the subject
PERMITshown to the subject
Nothing hit No grant admits it.
Nothing hitNo grant admits it.
5
5
DENY unmatched
DENYunmatched
The subject-wide gate The same global set, now for signing.
The subject-wide gateThe same global set, now for signing.
1
1
DENY global
DENYglobal
The deny gates Checked on the request itself, the relays it names included.
The deny gatesChecked on the request itself, the relays it names included.
2
2
DENY blocklist
DENYblocklist
The deny sweep What it references is fetched and deny-checked down the chain, within bounds. What the subject names directly must resolve and verify.
The deny sweepWhat it references is fetched and deny-checked down the chain, withinbounds. What the subject names directly must resolve and verify.
3
3
DENY blocklist · global · unresolved
DENYblocklist · global · unresolved
Full coverage Every person it names needs an interact grant of their own; every event it references is granted, or its author is, or it is the subject's own.
Full coverageEvery person it names needs an interact grant of their own; every event itreferences is granted, or its author is, or it is the subject's own.
4
4
DENY unmatched
DENYunmatched
The destinations Never a denied relay. Once a guardian grants interact/relay: only those relays — or a covered recipient's own inbox.
The destinationsNever a denied relay. Once a guardian grants interact/relay: only thoserelays — or a covered recipient's own inbox.
5
5
DENY destination
DENYdestination
Then rendering walks in: referenced events are fetched and deny-checked one by one. The walk stops at a wall and everything above the wall stays visible. No network is needed for the verdict itself.
Then rendering walks in: referenced events are fetched and deny-checked one by one. The walk stops at a walland everything above the wall stays visible.No network is needed for the verdict itself.
PERMIT signed — with NIP-70's ["-"] tag where a restriction demands it
PERMITsigned — with NIP-70's ["-"] tag where a restriction demands it
Encrypted? The engine first recovers who it involves — and then asks exactly the same.
Encrypted? The engine first recovers whoit involves — and then asks exactly thesame.
One thread, two directions
One thread, two directions
A stranger's note published by X — nobody granted X
A stranger's notepublished by X — nobody granted X
A friend's reply to it published by F — F has interact/npub
A friend's reply to itpublished by F — F has interact/npub
replies to
replies to
Input: the friend's reply arrives F is the publisher → an npub hit → permit. X's note renders beneath it: below the event itself nothing needs a grant, only the deny check. X's profile is legible too, so the subject can see who X is.
Input: the friend's reply arrivesF is the publisher → an npub hit → permit.X's note renders beneath it: below the event itself nothing needs a grant,only the deny check. X's profile is legible too, so the subject can see whoX is.
Output: the subject replies to both The reply tags F and X. F is covered; X is not → deny, unmatched, and the trace names the first uncovered element. The subject can ask a guardian for a grant: every guardian is covered by being one — bedtime still applies.
Output: the subject replies to bothThe reply tags F and X. F is covered; X is not → deny, unmatched, and the tracenames the first uncovered element.The subject can ask a guardian for a grant: every guardian is covered by beingone — bedtime still applies.
A stranger seen inside a trusted context is not a stranger reached: output strictness guarantees that.
A stranger seen inside a trusted context is not a stranger reached: output strictness guaranteesthat.