aboutsummaryrefslogtreecommitdiffstats
path: root/docs/openapi.yaml
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-15 16:49:31 +0000
committertv <tv@krebsco.de>2026-11-15 16:49:31 +0000
commit5866291a3752342ff954c39d728384dfe7ff02f8 (patch)
treed5a9b905111ad37658f6f56a01d2e340638103ec /docs/openapi.yaml
parent90ad9e632520d3bbc22562c0fd4db2584ef2a92c (diff)
access: what revoking doesn't stop under a strict policy
A change is judged as its writer saw the document, and its writer chooses what it saw. So a capability revoked, a user disabled or a key removed holds against members that weren't members before it, but a member that was can still commit, at a history from before, an envelope the user signed then, and the next, as far as it likes; the highest `seq` is the place's value. A remake ends it. access.md says so where it says what signed values keep out.
Diffstat (limited to 'docs/openapi.yaml')
0 files changed, 0 insertions, 0 deletions