From 70ff0ec9e50bf506cc6d80b929a81e350289f6cc Mon Sep 17 00:00:00 2001 From: tv Date: Sat, 7 Nov 2026 22:35:21 +0100 Subject: access: signed values judged on receipt Inspection gives each operation's kind; under strict every node refuses, at a signed place, anything but an envelope that checks and replaces the one there (deleting first as replacing does), anything within one, and above one anything replacing what holds one. Auth plan M7. --- docs/access.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) (limited to 'docs') diff --git a/docs/access.md b/docs/access.md index fa0b47d..20fa23d 100644 --- a/docs/access.md +++ b/docs/access.md @@ -261,6 +261,9 @@ API changes nothing (`409`). Values there before the policy stay as they are unt replaced: a registry whose entries hold the users' keys turns strict as it is. Without the policy, signed values may be written all the same, and plain ones too. -What it doesn't do yet: **judge signed values on receipt.** Each node checks the -values its users write through it; a member writing to its document directly could -still write there. +Every node judges the changes it receives alike (Changes judged on every node, above), +as their writer saw the registry: at such a place, only a string that is an envelope +that checks, replacing the one there then; nothing within one; and above one, nothing +replacing or deleting what holds one (a map made where there is none yet is fine). So +a member writing to its document directly gets nothing there past the others: the +registry, the policy and the bans change only as a user who may change them signed. -- cgit v1.3.1