Restrictions: four regimes, two places
Restrictions: four regimes, two places
A restriction set resolves against the evaluation's tuple — kind, weekday, minute, direction, opacity — to allow or deny. Where the set lives decides what a deny does.
A restriction set resolves against the evaluation's tuple — kind, weekday, minute, direction, opacity — to allow or deny. Where the set lives decides what a deny does.
How a set resolves: the first regime whose condition holds
How a set resolves: the first regime whose condition holds
A restriction set meets a tuple
(kind, weekday, minute, direction, opacity)
A restriction set meets a tuple(kind, weekday, minute, direction, opacity)
Does a deny entry
match?
Does a deny entrymatch?
Does an allow entry
match?
Does an allow entrymatch?
Is there any
allow entry at all?
Is there anyallow entry at all?
DENY — REGIME 1
a matching deny decides first, whoever wrote it
DENY — REGIME 1a matching deny decides first, whoever wrote it
ALLOW — REGIME 2
any matching allow entry, from any contributor
ALLOW — REGIME 2any matching allow entry, from any contributor
ALLOW — REGIME 3
an empty or deny-only set constrains only what it names
ALLOW — REGIME 3an empty or deny-only set constrains only what it names
DENY — REGIME 4
a whitelist closes over everything it does not name — kinds not yet invented included
DENY — REGIME 4a whitelist closes over everything it does not name — kinds notyet invented included
yes
yes
no
no
yes
yes
no
no
no
no
yes
yes
An entry matches
when all five of its fields match the tuple; * matches anything. Polarity only decides which regime it feeds; the demand never matters for matching.
An entry matcheswhen all five of its fields match the tuple; * matches anything.Polarity only decides which regime it feeds; the demand nevermatters for matching.
In the global set: a deny blocks the event
In the global set: a deny blocks the event
What is in it: every guardian's global entries, and the entries of every restriction profile a global entry references — one set, unioned.

• A deny from the global set blocks the event, in both directions, whatever any permission grants — the guardians' own line included.
• Allow entries union across guardians: the widest whitelist anyone references applies.
• A deny entry from any guardian holds against all of them — a “never” is a deny, not an omission.

e.g. a bedtime for everything: {deny, *, *, 21:00-07:00, *, *}
What is in it: every guardian's global entries, and the entries of every restriction profile a global entry references — oneset, unioned.• A deny from the global set blocks the event, in both directions, whatever any permission grants — the guardians' ownline included.• Allow entries union across guardians: the widest whitelist anyone references applies.• A deny entry from any guardian holds against all of them — a “never” is a deny, not an omission.e.g. a bedtime for everything: {deny, *, *, 21:00-07:00, *, *}
On a permission: a deny voids that entry
On a permission: a deny voids that entry
Its sets: the permission's own restrictions and its grant-scoping profile's — and, for a harvested entry, the harvested permission's two as well. Each set must allow.

• A deny makes the entry void for this evaluation: no hit, no coverage, no routing, no demand.
• A void entry never denies by itself: another permission that covers the same person still does.
• So one guardian's narrow grant never poisons another's broader one.

e.g. school friends on school days: {allow, 1,7, 1,2,3,4,5, 07:00-20:00, *, *}
The one exception: a direct interact/relay permission switches the destination whitelist on just by existing.
Its sets: the permission's own restrictions and its grant-scoping profile's — and, for a harvested entry, the harvestedpermission's two as well. Each set must allow.• A deny makes the entry void for this evaluation: no hit, no coverage, no routing, no demand.• A void entry never denies by itself: another permission that covers the same person still does.• So one guardian's narrow grant never poisons another's broader one.e.g. school friends on school days: {allow, 1,7, 1,2,3,4,5, 07:00-20:00, *, *}The one exception: a direct interact/relay permission switches the destination whitelist on just by existing.
Time is local wall-clock
Time is local wall-clock
00:00
00:00
03:00
03:00
06:00
06:00
09:00
09:00
12:00
12:00
15:00
15:00
18:00
18:00
21:00
21:00
24:00
24:00
"time": "21:00-07:00" — a window is half-open, [start, end), and wraps past midnight when its end is earlier than its start.
Weekday and minute are the instant's, in the subject's configured timezone — which never appears on the wire.
"time": "21:00-07:00" — a window is half-open, [start, end), and wraps past midnight when its end is earlier than its start.Weekday and minute are the instant's, in the subject's configured timezone — which never appears on the wire.
An encrypted message is resolved at every layer
A NIP-17 message is a gift wrap (1059) around a seal (13) around a rumor (14). A set is resolved at each layer's kind, and a deny at any one of them denies.
A whitelist naming only 14 therefore closes over the wrap by regime 4 — name 13, 14 and 1059 together.
The opacity axis names the property itself, so it never ages as new kinds are minted.
An encrypted message is resolved at every layerA NIP-17 message is a gift wrap (1059) around a seal (13) around a rumor (14). A set is resolved at each layer's kind, and adeny at any one of them denies.A whitelist naming only 14 therefore closes over the wrap by regime 4 — name 13, 14 and 1059 together.The opacity axis names the property itself, so it never ages as new kinds are minted.
TEPP Zeta · diagram 08 · statements: RESTR-001–RESTR-043, POL-008–POL-018, POL-060, POL-061, CONS-003–CONS-007, CONS-044, PROF-015–PROF-022, TOOL-017
TEPP Zeta · diagram 08 · statements: RESTR-001–RESTR-043, POL-008–POL-018, POL-060, POL-061, CONS-003–CONS-007, CONS-044, PROF-015–PROF-022, TOOL-017