Review round 1: versionsAnswer's choice of digest per seat had no test.
TestTheVerbsSpeakTheSeatsContract now holds it, with a store whose blob
and manifest digests differ. OCI.Blob refuses a manifest that keeps no
single blob, naming its layers, and versions says that in the journal:
the contract's answer has no field for why.
Notes for H2: OCI.Held (oci.go) compares the tag's manifest digest with
a bundle's or an archive's blob digest, the same kind as this fault;
versions answers kind "" since the tool reads a kind its input does not
take.
Builds: design 47 G A-430a (G-22-lead-answers-2), design 51 *One contract*
The node-engine resolves a want's version to an archive's digest through
oci-artifact-registry's verb versions and fetches /blobs/<digest> by it.
The holder answered the tag's manifest digest, so shanks asked
claude-code/files' manifest as a blob and got 404 (claude-code 0.1.17).
On the artifact seat versions now answers the manifest's one blob, the
digest the reference and the event published carry; the image seat
keeps the manifest digest.
Builds: design 47 G A-430a (G-22-lead-answers-2), design 51 *One contract* (the seats' events carry the digest), the seat's contract Artifact and Listed.artifact
Review round 1. The node build module runs the seat generator's check at its unit level
(steprun.OutOfStep), so its narrowed workspace keeps what H-A-136 and H-A-137 name: every
generated-from directory of the module, and for a root module the seats/ directory and the
paths of every artifact naming generated-from. Narrowed bare, a step of one mesh-contracts
package named the generated files left out as out of step. The fetch and the steps verb now
narrow the same way, and the steps verb reads its narrowed tree as the levels do.
narrowTree and generatedFromDirs are copied from mesh-build-go without its Go part, not moved
into mesh-delivery-sdk's steprun: the move is a change to two more repositories and a group
delivery for some sixty lines, in a fix that unblocks the build steps now; the copy says so.
packageDir and narrowedAway share one path helper.
Builds: design 47 H H-A-136, H-A-137 (hq design/47-H1-answers-59), ADR 0499 clause 4
A step of one TypeScript package of a module with several (mesh-contracts' root:
ts-meshbroker beside ts-meshrecovery, pipeline main.3 of 2026-11-20) fetches a workspace
narrowed to that package's path. The fetch and the lint and test levels read every package
artifact of the manifest, and one whose path the narrowing left out fell back to the
module's directory, which holds no lock: every TypeScript step of mesh-contracts ended
"could not run: the package in . has no package-lock.json". Such a package is now left
out of the fetch's install and of the levels' targets; an unnarrowed tree is read as before.
Builds: design 47 H H-A-136 (a step's workspace holds the artifact's paths; nothing else is fetched), ADR 0499 clause 4
The licence manager says each binding change as binding.changed.<consumer>
(mesh.mod.claude-licence-manager.event.binding.changed.<consumer>), but both
manifests consumed claude-licence-manager.binding.changed, which the grants part
composes into the exact filter mesh.mod.claude-licence-manager.event.binding.changed:
the bus consumer never handed either module one change, and the vault kept only its
first view (2026-11-20: g14 refused a switched licence's token until the first view
was asked again by hand). The consumed pattern now names the further part, `*`.
Builds: design 47 G A-134; design 39 bus-and-switch §17, §19, §22
A login not handed is kept only against a lease that does not succeed it; a lease
of the same account that succeeds it replaces it, said as login superseded. A login
to another account is kept until the manager adopts it.
Builds: ADR 0206, ADR 0209, design 39 §6, H-A-138 (hq design/47-H1-answers-59 175ed320), H-A-139 (hq design/47-H1-answers-59 e359911e), H-A-140 (hq design/47-H1-answers-59 b75d1386)
The manager's refresh keeps the licence's refresh-token expiry, so a grant of the
same lineage with a later access expiry replaces the login; a grant with no
mark, an older lineage or no later access expiry is the older lease and is kept.
Builds: ADR 0206, ADR 0209, design 39 §3 §6, design 14, H-A-138 (hq design/47-H1-answers-59 175ed320), H-A-139 (hq design/47-H1-answers-59 e359911e)
One reason, login kept, on both paths, with a journal line; the not-handed
return skips the binding's generation on purpose.
Builds: ADR 0206, ADR 0209, design 39 §3 §6, design 14, H-A-138 (hq design/47-H1-answers-59 175ed320)
A login made on a node (while the tool runner was stopped, or before the
manager asked claude_code_grant for it) was overwritten by the next apply
of the binding's older grant: Apply took any refresh token in the file as
one already handed, and forced the write. The person's login was lost and
the session asked for a login again.
The node side now keeps the fingerprint of the login claude_code_grant last
sealed (state login-handed, never the token). Apply leaves a file whose
login is not that one untouched (applied false, reason login-not-adopted);
its report makes it the manager's candidate, and the successor the manager
hands back replaces it, as before without a refresh token.
Builds: ADR 0206, ADR 0209; design 39 §6 (the latest login wins, a login
moves its node); design 14 (a node never holds a refresh token).
With the guard gone nothing reads the machines' names, domains and
addresses: remove Machine, the name lookup and the ten-minute timer that
resolved them again, so the tools' table is read only when a followed
state changes. Also remove the now unused cut helper.
The operator asked for the shell guard to go (2026-11-20): the plugin no
longer carries a PreToolUse hook or guard.json, the binary no longer has
a guard verb, and the claude_code_guard tool, its record and the
refusal-ranked order of the instead-of table are gone. The SessionStart
and Stop hooks of the wait list stay, run by the same binary at the same
path, which is also the home-fs helper's. The rendered rule against ssh
to a mesh machine stays as the session's own and no longer claims a
guard enforces it; claude-agent no longer passes the guard's override.
A module at the repository's root naming generated-from "." (mesh-contracts)
kept nothing of it: the narrowing kept "." alone, which prunes everything,
so the seat generator's check of go-meshconfig still found every file out
of step. Such a module now keeps the seats/ directory the generator reads
and the paths of every artifact naming generated-from; nothing else of the
root.
Builds: design 47 H H-A-137
The first pipeline of the clean state (main.3) failed every build of a
mesh-delivery-contracts client: the fetch narrowed the tree to the
artifact's paths (ADR 0499 clause 4), which removed
modules/mesh-delivery-sdk, so its requirement at the zero version found
"no module of that path in the fetched tree". The same narrowing left the
seat generator's out-of-step check without its seat definitions.
The narrowed workspace now also holds every generated-from directory an
artifact of the module names and the directory of every package of the
same repository the artifact's go.mod requires at the zero version, found
by the repository's manifests; the root's manifest and lock files are not
kept when narrowing from the root. The fetch's own Go modules stay those
under the artifact's paths (A-447a), not the added directories.
Builds: design 47 H H-A-136; design 47 G-22 A-447a
Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
The refusal read the keeper's state asked, which holds only a module that
asks for kept data, so a running module keeping no bus data would lose its
live durables. It now reads the keeper's state plans, one key per module of
a watched branch's newest revision; the keeper no longer deletes a plan key
when a module's asked key goes, so plans stays that accepted set.
Builds: design 47 H H-A-126, H-A-127, H-A-128; design 47 G §538
Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
An accepted module's durable (<node>_<module>) is refused on any stream; any
other durable is an orphan and goes, why its warrant, recorded through
mesh-hand-acts. It no longer refuses every consumer of a kept-data stream.
Builds: design 47 H H-A-126, H-A-127
Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
Every open record ends after one hand act naming how many; the answer says
what it ended, counted.
Builds: design 47 H H-A-121 (2), §765 (the gate's open records go at the clean state)
Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
Every account may call every verb; what protects the mail is what the verbs
answer (ADR 0459 §2), not who may call them.
Builds: design 47 H §764 (every callers list, §752); H-A-122
Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
Review round 1, notes: keep-main-rules acts at the token's mint alone since the
ten-minute step went (H-A-100), and the issue tracker's owners named the
checker's path, which a search for the checker must not find (§764).
Builds: design 47 H §764 (the forge module's ten-minute timer; the checker whole); H-A-100
Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
Review round 1, Must 3: the groups and group-ended are retired; the overview
showed the deliveries, another module's state, which the status view owns.
The overview keeps two sources (the tracker, the asks), consumes no merge,
transition or pipeline's end, and the progress verb asks no groups.
Builds: design 47 H §764 (the gate's verb groups; the runner's group-ended); H-A-28; H-A-125
Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
Review round 1, Must 5: the seat lost held-back and ask-again (mesh-contracts
9db2e1d); the holder still offered held-back asks of before, refused choices
on them, listed them in asks and served ask-again.
Builds: design 47 H §764 (The operator channel's limit); H-A-57
Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
Review round 1, Must 2: the want's composed digest left mesh-sdk's motion.Want
(H-A-78); the hold read it and no longer built.
Builds: design 47 H H-A-78 (1)
Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
Review round 1, Must 1: commit 11a22fdf removed the checker's seat package;
the require left the gate unbuildable against the H1 heads.
Builds: design 47 H §764 (the checker whole goes); H-A-57
Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
A Go integration test builds the TypeScript bundle and plays its tool
runner over stdin and stdout against a bus of its own and a fixture
forge: a call stopped after two of three merges says one merge-called at
the start; a failed required step refuses its head; two pull requests in
two repositories merge and say one merge-called; a forge refusing the
second merge says what landed and raises merge-partial, cleared by a
later call.
Builds: design 47 H §774 (forge module: tests 111, 114, 115), §734, §735, §736, §766, §767; H-A-61, H-A-87 (1)
Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
announceHead with its mesh/merge-gate pending, the weighing of trunk and
sibling moves (passPulls, trunksMoved, siblingMoves, GateWriter) and their
files on disk, the pass's pull-passing half with its 60 s retry, and the
10-minute keep-main-rules step go. A pull request's new head is said as
pull.updated from the forge's event alone; the seat's status writes
through the client; pollRepos, pollMerged and readAllAtStart stay.
Builds: design 47 H §764 (the forge module: the merge-check machinery, its poll and timer), §762; H-A-28, H-A-100
Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
The forge module keeps a step's failure at the step-ended body's
fingerprint alone, consumes step-ended on its <module>.<branch>.<commit>
subject, and writes step-unread (scope module, keyed <run>.<module>.<step>,
warning, resolver operator) for a step-ended without its fingerprint,
cleared by the step's later step-ended with it.
Builds: design 47 H §735 (failed-steps from step-ended); G §585; H-A-18, H-A-47 (FORGE-1 builds step-unread), H-A-93
Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
forge_calls answers the kept calls newest first with each member's base,
head and state; forge_call_say_again, with call and why, says a call's
merge-called again once the hand-act log took it.
Builds: design 47 H §766 (its tools); H-A-18
Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
The call stops merging, says merge-called with what landed and refused,
and raises merge-partial (scope delivery, id the call, urgent, resolver
operator) in the module's findings; a later call landing every refused
member clears it, and forge_partial_clear clears one by hand after the
hand-act log took it.
Builds: design 47 H §767; H-A-1, H-A-18, H-A-81
Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
Once its members are merged or refused the call says merge-called on
merge-called.<call> with its landed members (base and merge commit) and
its refused ones, and is kept said; a call that landed none says none. At
the start every call not said says it for what landed.
Builds: design 47 H §736, §766 (said again at the start); H-A-18, H-A-47 (said), H-A-71 (2)
Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
The key call.<call> holds by, the proved account, at, each member with
its base and state (judged, then merged with its commit as it merges, or
refused with why) and said; a call past call-retention (a setting, 30
days) is deleted on a new call's write, oldest first, with no timer.
Builds: design 47 H §766 (the state calls, call-retention); H-A-18, H-A-47 (said, deletion on each new call's write), H-A-71 (2)
Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
merge-pull takes pulls and by, refuses a call with no proved caller,
judges each member (its head, its base a watched branch, not merged
already, no required step failed at its fingerprint) and no branch
protection, merges none when one is refused, else merges in the order
named and answers the call and each member's outcome once. The seat's
branch answers no protection. The seen-expiry test no longer depends on
today's date.
Builds: design 47 H §734, §735, §764 (the single-pull form; merge-pull's protection judgement); ADR 0682 §13; H-A-21, H-A-22, H-A-24, H-A-47
Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
The source key is read with the escaping it is written with, so a merge
call's head on a branch holding a dot is no untaken head. The whole test
raises head-untaken for a head held past the bound, takes a merge call on
release/1.2, holds a push no call delivered, and holds nothing after the seed.
Builds: design 47 H §774 (gate: tests 110, 111), §737, §740, §742, §768; H-A-87 (2)
Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
The record a merge call opened takes the runner's pipeline-started,
pipeline-ended, wait-held and wait-ended, the assigner's wanted and
pipeline-wanted and the node-engine seat's running, read by its key, and
ends on pipeline-wanted (running: every tier runs; tier-late: failed) or
failed on a pipeline that did not pass.
Builds: design 47 H §738 (G §141 to §147); H-A-29, H-A-75, H-A-89 (1) to (5)
Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
The repository's gofmt check refused heads.go, headtools.go and main.go
as written; a stale comment of the stalled conditions goes with them.
Builds: design 47 H §740, §742
Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy