Answer A-66: the seed's steps call, its fetch and its five minutes

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-11 22:57:23 +01:00
parent eb061c7603
commit e1764b4892
1 changed files with 5 additions and 0 deletions
@@ -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>.<artifact>`, `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.