From e1764b4892b657c4d30151845b482370cd8bd6d7 Mon Sep 17 00:00:00 2001 From: jochen Date: Wed, 11 Nov 2026 22:57:23 +0100 Subject: [PATCH] Answer A-66: the seed's steps call, its fetch and its five minutes Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md b/03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md index 8b6d0c99..d0a98fba 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md +++ b/03-DESIGN/01-to-be/47-milestones/G-20-lead-answers.md @@ -257,3 +257,8 @@ names the principle that settles it, and is cited as "design 47 G A-n". - **A-65** (§387, §529; principle 1, a module's data lives on the bus) mesh-knowledge's findings go through the writer like every observer's: it gains the `finding-events` stream and a writer over the `findings` state it already requires, and its findings no longer live in its database. +- **A-66** (§704; principles 7 and 3) The seed's `steps` call names the artifact by the contract's key + `.`, `module` beside it; its `fetch` is composed from the entry (repository, commit, path, the + artifact's paths, and `packages` and `beside` where the entry carries them); the time since a seat first failed to + answer is kept in the indexer's own state, so a restart keeps it, and the finding is written at the next seed attempt + past five minutes.