From f7d066fb32f99647f586c254bb6ede9d8a161d79 Mon Sep 17 00:00:00 2001 From: jochens Date: Fri, 13 Nov 2026 01:10:06 +0100 Subject: [PATCH] Design 42 zfs-owns-zfs: A-39 and A-40, met in develop --- .../01-to-be/42-milestones/zfs-owns-zfs-lead-answers.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/03-DESIGN/01-to-be/42-milestones/zfs-owns-zfs-lead-answers.md b/03-DESIGN/01-to-be/42-milestones/zfs-owns-zfs-lead-answers.md index b84bd3a5..d5bf7984 100644 --- a/03-DESIGN/01-to-be/42-milestones/zfs-owns-zfs-lead-answers.md +++ b/03-DESIGN/01-to-be/42-milestones/zfs-owns-zfs-lead-answers.md @@ -144,3 +144,8 @@ settles it (`00-META/principles.md`), cited as "design 42 zfs-owns-zfs A-n". The process-bus rule), and the grants (mesh-grants) give the process's account publish on that stream's subjects of its own node and the reads and writes of those states, as they give a module's tools account today. A name its module does not ask for is refused as today. +- **A-39** (A-37, A-17, met in develop; principle 7) The keeper's closed list of calls also reads: `get` one key and + `keys` of the same three states, since the run reads a hand act's key and the apply its state `applied`. +- **A-40** (A-36, met in develop; principle 3) A ledger instance not yet written is the tool runner's answer to + `mesh/ledger.get` with a state `null` and sequence 0 (the tool runner's `internal/ledger/read.go` `Get`, in mesh-tools), never + an error: the module reads it so, and recognises no error by its text.