From 51e3c7b4d8d77e27fbc6911457586e6f2cc30ef4 Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 19 Nov 2026 01:03:21 +0100 Subject: [PATCH] Answer A-487b: the catalog half reads its newest revision from its own objects, never by asking its own seat --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index 92868e81..484a46a4 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -1990,3 +1990,8 @@ the principle that settles it, cited as "design 47 G A-n". 30 s, 1, 2 and then 5 minutes per module, whichever comes first; never on every pass. The backoff of a module starts again from 5 s when an answer comes. (Same recovery: three asks at a time per node, asked again at every pass, kept the catalog choked after each restart.) +- **A-487b** (A-487; principles 7 and 12) The catalog half reads the newest trunk revision from its own objects + `catalog-revisions` when its runtime starts and when it hears `catalog-revision`, never by asking its own seat's verb + `revision` over the bus: a module calling its own seat adds a call through the tool runner that nothing needs, and + waits on itself while it starts. Its manifest invokes no verb of its own seat. (From the develop of A-487: the + follower path the contracts' clients use asks the verb `revision`, which suits a reader of another module.) -- 2.54.0