AUTH-5: the auth activation and what a service supplies it.
AUTH-5 — the auth activation: one auth surface in every gated
Plexus hub. Sign in, sign up, who am I, what does this need, and the
admin’s roles and memberships.
NEST-21: a service’s configuration at runtime — settings, the library,
the config activation.
NEST-21 · a service’s configuration at runtime, in three layers.
BIDIR-8 (BIDIR-5’s rule): the gate over a duplex call — open, admit,
re-verify on the gate’s grants generation, answer, audit.
BIDIR-8 (BIDIR-5’s rule, made a library) — the gate over a duplex call.
ForwardPolicyRegistry — per-hub map from callee namespace to the
ForwardPolicy that the framework consults when dispatching across the
boundary into that callee.
BIDIR-6: Input<T>, the input half of a call.
BIDIR-6: the input half of a call. A method declares one parameter
Input<T> and reads what its caller streams into the live call.
RETURNS-40: the IR a service writes of itself — IR 3.0, as synapse builds it.
RETURNS-40 — the service writes its IR. A service answers its
self-description as one document: every type once (irTypes), each
method referring to them (irMethods) — IR 3.1 (ASK-1; 3.0 without the bidir keys) as synapse
defines it (Synapse.IR.Types, Read, Builder) and builds it from the
raw schemas today, so the two are held equal: tests/ir_fixtures.rs
compares this module’s output with the goldens synapse’s ir3-test
writes, byte for byte in synapse’s canonical form.
DYNAUTH-12: tokens a service signs for the peers it forwards calls to.
DYNAUTH-12 (D3, TM-4) · peer tokens: what a service signs for the peer a
call is forwarded to, so the peer can check what it is told rather than
believe who told it.
NEST-15: the service root — a table of peers answered by peer(name).
NEST-15 · the service root is the primitive: a table of peers answered by
peer(name).
PERF-7: the item path — each item encoded once, straight into the frame
its socket writes.
PERF-7: the item path — an item encoded once, by its method’s own event
type, straight into a buffer its socket writes from.
A session’s upper bound (IDENTITY-40): (role or grant, scope) entries,
spelled editor@MENGER-12, tickets.get@*. A check passes a ceiling
when some entry’s scope is in the target’s chain and the entry allows the
grant (the grant itself, or a role listing it).
The one rule in front of every call: the method’s grant, held through a
role on the target’s scope, within the session’s ceiling. Default deny.
Cheap to clone (one Arc); cheap to ask (memory only), so a stream may
ask per event.
Where a call may act: the scopes the caller holds the method’s grant on
(within its ceiling), handed to the method beside auth. A read without a
target (list, watch) answers only from these.
An in-memory Roles: each role an explicit list of grants, where an
entry may also name an earlier role (inclusion, flattened when defined).
ADMIN is built in.
Where a role is held: everywhere (*) or one named scope (MENGER).
What a name means — a shortcode, a tenant, a project — is the service’s;
the gate only compares names and asks Resolve::chain how they nest.
The metadata key a session’s ceiling rides under (IDENTITY-42’s
menger_session sessions write it): either a list of role@SCOPE /
grant@SCOPE strings (one layer) or a list of such lists (layers, every
one of which must allow a check).