A-379 replaced A-376 for the start, and the seat mesh-catalog offers neither the states modules and manifests as views
nor verbs of those names, so the validator refused the manifest's two consumes and two invokes.
Builds: design 47 G A-379, A-445 (G-22-lead-answers-2.md)
The operator channel kept at most three asks of one asker offered and held its oldest back behind newer ones, so asks
waited unseen (the pipeline's proposal behind two mailu asks). It keeps no count any more and holds nothing back: every
ask is offered when it is raised, and lapses at its expiry or ends at its answer. An ask held back before the change is
offered again at the router's next tick; ask-again offers one so and holds nothing back in its place.
Builds: design 47 G A-424
The builder's publish again of mesh-delivery-pipeline 0.1.6 sends the version and the digest with no parts, as A-73
has it; the build stored the bundle untagged, and the holder answered 'publish: no parts' unless the tag existed
already. The holder now checks the digest against the store under the name (the artifact store, A-50), asks the
builder's reservation, tags it with the version and says published; a digest it holds none of is refused as not
stored, naming the digest.
Builds: design 47 G A-417, A-73, A-50, §588
The forge's git verbs may serve after the gate does; one pass with every head read refused wrote nothing and was never retried.
Builds: design 47 G A-401
At its start and on each registration-changed of the seat mesh-catalog, the gate writes source.<branch> for every watched
branch the registrations name that no source key holds, each registered repository at its head from the seat git's verb
branch, group empty, then says source-moved; a repository whose head cannot be read is left out and said; a held key is
never rewritten. gate_source_start (branch, why) does it by hand through the hand-act log. The manifest consumes
registration-changed and invokes seat:git.branch and seat:mesh-catalog.registrations.
Builds: design 47 G A-401, §430, §15, A-34
The seed and a registration with no branches read the default branch through the seat git (design 47 G-1 §104) by
calling branch with an empty branch; gitea refused it as no branch for a path, and the seed stopped on novox 2026-11-14.
Live on shanks the bundle exited 39 times on 'an ordered consumer of mesh-conditions.findings-asked: context deadline exceeded', so the seat node-build-go never answered steps and the seed waited.
Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
Before the catalog half's first views are in (a read refused, or none-yet), the keeper reads the manifest on the trunk of the
holder of the seat mesh-catalog from the seat's states modules and manifests (the holder from the seat that places modules)
and makes its kept data as any module's, each entry said as ever; every other module waits as A-367 says.
Builds: design 47 G A-376 (G-22-lead-answers-2.md)
Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
PlanCatalog plans nothing, deletes no plans key and orphans no entry while the
catalog half lists no module before any was seen; the first revision with
entries plans as before.
Builds: design 47 G A-367 (G-22-lead-answers-2.md), W22/Q4 of start-waits.md
Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
mesh/check checking a4bc3d95edef on b1125c02cfe6 | novox/mesh-catalog#678 in group fix/47-G-bridge
The running pre-G indexer publishes mesh-catalog's packages only while every package directory it published before is
in the tree; G removed this one, so mesh-catalog's packages are never published (2026-11-13). An empty package keeps
the directory; it goes once G's indexer runs.
Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
mesh/check failed (2): mesh-delivery-checker: no published of the tagged version of go-meshconditions of me…; and 1 more | 53351dd30df2 on b1125c02cfe6
mesh-conditions keeps G's form: the keeper reads no observer's state (no reads, no Observers list), so main's zfs entry there goes. The zfs follower says its findings through G's findings writer over its keeper: the keeper gains the publish of the writer's three events on the finding stream finding-events and the hear of mesh-conditions.findings-asked on its own durable, nothing else; each pool or device not ONLINE is scope module, id zfs.<pool>.<device> (the device's own name), kind not-online, on the node. The manifest asks its state findings by template in requires (G §529, §577), and gains the finding-events stream and the consumes, and the keeper's bus the three events and the consumes.
Builds: design 47 G §383, §384, §387, §529, §577, A-339, A-340, A-341, A-342; design 42 zfs-owns-zfs §27, A-32, A-37, A-39, A-41
Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
mesh/check being carried to 0041b69d1736 on 32f1566cc879 | from 117f933dacf0, mesh-delivery 7221a1e5cd7f, mesh-host 0193949efe9f, mesh-sdk e42b9491c93…
The validator refused zfs and mesh-conditions: mesh-conditions reads zfs.findings, which zfs had moved to bus state in requires, where the new form has no readers (ADR 0596 section 2). The keeper process's bus.state keeps naming findings. The manifest test holds it.
Builds: design 42 zfs-owns-zfs A-46 (A-32, 26, 27)
In the test's temporary directory, or /tmp when the socket path would pass 100 characters, so a long TMPDIR cannot fail the bind.
Builds: design 42 zfs-owns-zfs §18, A-37
Issue 1979, blocking: a date-bound test. The warrant dated 2026-10-29 fell out of the listing's 14 days on 2026-11-13, failing every mesh-catalog check.
Builds: design 42 zfs-owns-zfs (the group's check)
The group's check failed TestRulesBus/NoCatalogueManifestNamesAnInstallation: 11 values name an installation (the vendor sites in the package's zed-functions.sh, resources[13]).
Builds: design 42 zfs-owns-zfs §14, A-2