Answer A-363 to A-368: G's first start composes rights from the trunk, builds unpublished packages at the source commit, and waits for nothing only G answers

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
This commit is contained in:
2026-11-13 20:34:47 +01:00
parent f67c788c82
commit 916be3a63c
@@ -746,3 +746,19 @@ the principle that settles it, cited as "design 47 G A-n".
on a cycle, so a call word's edge on a cycle is left out like an invoked verb's.
- **A-362** (completes A-353; principles 3 and 7) The seat list a runner starts with (mesh-sdk's bootstrapped list)
holds `mesh-delivery` beside `mesh-catalog`, so `mesh-delivery.source` is admitted before the seat list is read.
- **A-363** (cycle C7; principles 7 and 2) While its catalog half is unread, grants composes each account from the
manifest the indexer's `modules` first view names for its module (the trunk's), in union with what its want's entry
gives, never from the list in force alone; so the first G parts get their G subjects before any of them serves.
- **A-364** (completes A-363; principle 7) Grants' own account carries the right to create each kept event stream of
the seat list (`SEAT_*`, such as `SEAT_git_branch-moved`) while the catalog half is unread, composed the same way.
- **A-365** (cycle C4, a silence of ADR 0573 §2/§4, which speaks of the latest published version; principle 7) A mesh
Go package no published version holds is built, for its importer, at the commit the gate's `source` names for its
repository, as an import of the same repository is; once a version is published, the latest published applies. The
indexer asks such a build with that commit, not on the version line.
- **A-366** (W5; principles 7 and 3) The indexer takes its own build from `MESH_FINGERPRINT` (mesh-sdk
process.OwnBuild) first, and asks the node-engine's `composition` only when it is unset.
- **A-367** (W22; principle 3) A planner of the catalog half (the bus keeper) treats a `none-yet` trunk as not yet
viewed: it plans nothing, deletes no plan and says no module orphaned until the first revision with entries.
- **A-368** (C6; principle 7) When neither the registrations nor the gate's `source` name a branch (a fresh mesh),
the catalog half counts the trunk as `none-yet`, once in the catalog client's `Ready` for every part, so the approval
gate is ready and `indexer_seed_again` runs. In this release, since G's genesis needs it.