Files
zeekay 5c067f1791 keys: a member lists the keys they hold in their org
The key collection now authorizes itself.  A person names an org they
belong to: its admin, or a SuperAdmin, reads every key it holds, and
anyone else reads the keys they hold there.  A stranger is refused with
the bytes every stranger gets, and a reserved org's keys stay a
SuperAdmin's alone.  A confidential client still needs key-mint and
still reads only the org it serves, so its credential alone never reads
another tenant's keys.  A named key stays the Guard's.

The allowlist lookup moves to the principal leaf, so a collection that
authentication is built on asks a capability the way the Guard does.

Claude-Session: https://claude.ai/code/session_01HvACxex9ZZTzJCCHgirsGy
2026-10-06 20:14:00 -07:00
..