From fec5bc42dcaa851b04e4eb0eabf6d9b84510b80f Mon Sep 17 00:00:00 2001 From: jochens Date: Fri, 13 Nov 2026 00:40:17 +0100 Subject: [PATCH] Design 42 zfs-owns-zfs: A-31, the run reads the ledger through its module's tool --- 03-DESIGN/01-to-be/42-milestones/zfs-owns-zfs-lead-answers.md | 3 +++ 1 file changed, 3 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 45d4d170..68fd9f68 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 @@ -104,3 +104,6 @@ settles it (`00-META/principles.md`), cited as "design 42 zfs-owns-zfs A-n". The the operation `taken` with the effect `set-fields` on those four fields, and `removed` with the effect `remove` naming no map, so the instance's state goes while its history keeps both operations; one index `by-dataset-kind` on `dataset` and `kind`, read through `mesh/ledger.query`, the newest `at` among a kind's entries being its last. +- **A-31** (§21, §22, §28, A-20, met in develop; principles 1 and 7) The scheduled run reads the ledger as it writes + it, through its own module's tools: its process bus also invokes `zfs.zfs_snapshots_schedule`, whose answer holds + the ledger's entries (§28), and the run takes a kind's last entry and the entries to prune from that answer.