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
The three build modules no longer give the step runner a callers reader
of the seat list (steprun.SeatListCallers and Puller.Callers go): no seat
definition names callers and every account may call every verb.
Builds: design 47 H §752, §764 (every seat contract: the callers lists); H-A-41, H-A-66, H-A-71 (3)
Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
gate_heads reads the state heads with each head's since and finding;
gate_head_take, recorded in the hand-act log first, names the held head a
source revision as a merge call does, with a call of its own, its record
marked by hand with who and when and its member <repository>@<commit 12>,
and the finding clears.
Builds: design 47 H §742; H-A-24 (hand, by and the time in the trace), H-A-48 (a hand take's member <repository>@<commit 12>)
Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
The gate consumes the forge bridge's head-moved, keeps in its template
state heads each head source.<branch> does not name, and raises
head-untaken (scope delivery, id <repository>.<branch>, warning, the
operator its resolver) once untaken-bound passes, on its one deadline
timer; a later source revision naming the head lets it go and clears the
finding. The stalled conditions, their state and the operator-channel
use go: the watchman's record-open is the one signal.
Builds: design 47 H §740; H-A-27 (head-moved's form, forgemsg), H-A-48 (the stalled conditions go; untaken-bound on the gate's one timer), H-A-81 (warning, resolver operator, no owner)
Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
For every watched branch the registrations name, one source revision at
each registered repository's head read through git.branch, start true, a
call of its own, source-moved said and no record opened; recorded in the
hand-act log first, the counts answered. It refuses to run while a key of
the earlier form is held, naming it (the source bucket is dropped first).
Builds: design 47 H §768; H-A-15, H-A-47 (the seed opens no record; the start pass writes through its path), H-A-76 (Q-G2: numbers from 1, refuses an earlier-form key)
Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
The gate consumes the seat git's merge-called and, per watched branch its
members name, writes source.<branch> once by compare-and-set keyed by the
call, numbered one above the branch's newest; opens that revision's record
keyed <branch>.<source> with the call, by and account in its trace; says
record-opened on record-opened.<call> and source-moved on
source-moved.<branch>.<source>. The take-in.taken writes its movers into
the record read by its key, and a take-in with no mover ends it as nothing
to deliver. The verb groups, the record's pins and pins-stated, forge-made
and the emitted transition go. One commit for both subtasks: the record's
opening is the handler's second half and neither compiles alone against
the contracts.
Builds: design 47 H §737, §738 (a take-in with no movers ends its record), §749 (the pins are the indexer's), §764 (the gate: the source moved on take-in.taken, the verb groups); H-A-13, H-A-19, H-A-24, H-A-25, H-A-28, H-A-29, H-A-33, H-A-47 (the start writes through the seed's path, no record), H-A-48 (pins, pins-stated, transition, members <repository>@<number>), H-A-76 (Q-G1: the say-again carries the value's heads, start false)
Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
Every account may call every verb from H1, so secret-ask answers every caller the runtime
proved and retire every caller whose warrant holds; the manifest's two lists, the config
retire-callers and its file go. The enrolment verbs keep their one list, now a small type
of the vault's own since mesh-sdk's Callers goes.
Builds: design 47 H §752 (ADR 0682 §10's exception for the enrolment caller, H-A-11); H-A-41, H-A-66
Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
mesh-sdk's callers set goes in H1, so the seat list's two tools of claude-code answer
every caller, and mesh-recovery's seat list part is made with its prefix alone.
Builds: design 47 H §752, §764 (every seat contract's callers); H-A-41, H-A-66
Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
#708's six commits are taken onto main (the pull request path and A-490l's sweep go).
manifest-accepted goes in H1, so a retiring value is judged for every module a
catalog-revision names changed, and the resync tool's words no longer name the
indexer's config candidates, which retire too.
Builds: design 47 H §763 (G §654), §764 (mesh-config: its pull request path and A-490l's pull sweep; the indexer's manifest-accepted and config candidates); H-A-49, H-A-61
Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
The timer was rearmed on a write of proposals or retiring only, so a rename window opened after start, with nothing else
waiting on a time, left it blocked and its seven-day held finding never came; a window opened under a later armed deadline
came late. The condition is now armsDeadline (proposals, retiring, renames), and a test shows a written window rearms it.
The comment on Proposal.Pull cites ADR 0681 §5.
Builds: ADR 0681 §1; lead answer A-490l (hq main, 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md: the held finding comes in a quiet mesh too).
Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
The one timer left is set for the earliest of three deadlines: a waiting proposal's end, an unanswered retirement's second
ask, and a rename window's seven-day held finding, which is now judged at its deadline (JudgeHeldWindows) so it comes in a
quiet mesh too. Its floor is the module's setting deadline-floor-seconds (default 60), not a constant.
Tests: an integration test counts asks by key and fails on any `seat:git.*` over the whole run (ADR 0681, How it is checked,
clause 1); a unit test shows an approved proposal records a hand act naming no pull request; another that a stored proposal
naming a pull request is refused on approval, saying why.
Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
The generated client held only the held values' keys and decoder, which the seat no longer has.
Builds: ADR 0681 §1, §6 (the seat keeps no held value, so its generated client goes).
Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
The mesh knows no pull request (design 47 G, G-1 §38-39). Removed:
- the states `pulls` and `kept` and all code that reads or writes them (pulls.go, the held values a proposal holds, the
listing of held values), SweepPulls, settlePull, HeardPull and the forge call;
- the consumes of git.pull-merged and git.pull-closed, the invoke of seat:git.pull;
- the config verb's `pull`, `head`, `declares` and `pulls` arguments and its actions `pull-declares` and `held`;
- the indexer's config candidates, which only that path used: the consume of mesh-delivery-indexer.views.config-candidates
and the invoke of indexer_read_config_candidates (the indexer's state goes in the same group).
A stored proposal that names a pull request is judged not one this module makes, so nothing is set on it.
Builds: ADR 0681 §1 (no pulls or kept, no git events, no seat:git.pull, no `pull` argument, no pull-declares or held), §3, §5, §6;
lead answer A-490l (a stored proposal naming a pull request is refused on its approval).
Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
mesh-config sent about 262 requests a second and received about 1,540 since its start: every sources() call (a
resolution pass, and a `delivered`, `manifest-reads-changed` or `manifest-accepted` event, each of which read the sources
whether or not a window or a retirement was open) read every key of its own states by one get each (pulls 1,176 keys,
resolved 447, declared 168, values 101...: about 1,200 requests for an event, 2,800 for a pass), serialised by one lock, so
a delivery's burst of events kept it asking the bus back to back.
- The module's own states are read from mesh-sdk's WatchedStates (one watch per state, its own writes taken into the copy)
instead of a get per key (ownstates.go, main.go runtimeStore).
- An event judges what it names: `delivered` and `manifest-reads-changed` read no source when no rename window is open,
`manifest-accepted` reads none when every row is already marked or read again (renames.go windowOpen, retiring.go).
- Open windows and retirements are judged again after each pass, since an entry that answers after the judgement was
made moves the pass, not the event; the slow reads had hidden that race.
- No timer polls: the five-minute resolution and sweep of every pull request on the forge, and the minute's read of the
router's record, are gone. The sweep and Decide run once at start (an event said while the module was down is not said
again), then on git.pull-merged/-closed and operator-channel.decided.mesh-config; an ask ended with no choice also
takes the retirements from the router's record. One timer is left, a deadline: for the earliest waiting proposal
(ProposalLasts + 1 h) or unanswered retirement (HeldFinding), set again when either is written (NextDeadline).
Wake-ups kept, each by its record: `delivered` and `manifest-reads-changed` close a rename window (design 32 *A config
value renamed*, ADR 0609 §4); `manifest-accepted` judges one module's retirements (design 32 *A value no longer read*);
`git.pull-merged` and `-closed` settle one pull request's held values (ADR 0502 §7); `decided.mesh-config` takes one ask's
warrant (ADR 0259); a changed view (assignment, want, predefined list, config candidate, catalog revision, entry) moves a
resolution that writes only what moved (ADR 0565 §3).
Builds: ADR 0681 §1 (no polling of the forge: the five-minute look ends); ADR 0580 §1; ADR 0426 §3; design 32 (*A config value renamed*, *A value no longer read*);
lead answer A-490l (hq main, 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md) for the wake-ups and the one deadline timer.
Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
From H1 only a merge call names a source revision, so the gate stops moving source on
take-in.taken and on the forge bridge's merged message, and the start's comparison with
the forge's heads, gate_source_follow, its finding source-uncompared and the forge-made
record opener nobody calls go with them.
Builds: design 47 H §737 (moveSource leaves the take-in.taken handler; ForgeMerged, moveHead, gate_source_follow go), §764 (the gate: the source per merged message, the start's comparison with the forge's heads, the source moved on take-in.taken; forge-made per H-A-25)
Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
A merge call is the delivery's group from H1, so the gate no longer keeps deliveries
and groups from the seat git's pull events, reads no open pull request at its start,
and answers deliveries and show from the records alone. The verb groups stays,
answered from the records, until the seat mesh-delivery's definition drops it.
Builds: design 47 H §764 (the gate: the groups from a branch name, its states deliveries and groups, its consumption of pull-updated, pull-merged and pull-closed, its start reconciliation); H-A-28
Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
The switch to the records ran once at G's delivery; from H1 one model holds, so the
switch, the carried Approve and its finding, the states merges and the old owed, the
ledger's switch key and the checker client nobody imports leave the gate.
Builds: design 47 H §764 (the gate: the switch and the carried approval, the states merges, owed, asks, pulls, turns); H-A-28
Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
The builder's publish again sends version and digest and no parts; the package seats refused it as not one part.
Both registry holders now run the publish conformance cases.
Builds: design 47 G A-73, A-417, A-490
Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
mesh-build-image's steps now carry Node and SayStep (an image has no step, §328, but the kit holds all three). Prior wired in go and image.
Builds: design 47 G §24, §328
Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
A pipeline step ask (the sdk's lib lint and unit steps) was refused with 'this build module says no step's end': its
AskSteps set no SayStep, Node, Lint or Has. They are set as mesh-build-go sets them; lint runs tsc --noEmit over each TypeScript
package; Puller.Prior counts only runs that started toward poison.
Builds: design 47 G §328 (Lint per language), §22, §24, §25
Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
mesh-build-go and mesh-build-image follow the seat list as mesh-build-node does, so each consumes mesh-catalog.seat-definition-changed and
-removed, and all three invoke seat:mesh-catalog.seat-definitions, which the reader calls.
Builds: design 47 G A-488a, A-488b (hq 57c14047)
Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
Its runtime follows the seat list (seatlist.Start subscribes to mesh-catalog.seat-definition-changed and -removed); with no consumes
there was no consumer shanks_mesh-build-node_tools, the seat list was never read and the asks of a named asker were given back.
Builds: design 47 G A-488a (hq 25df48ad)
Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
Its processes run as the operator account, so its own secrets are owned by it (design 20 "Whose a process's own secrets are").
Builds: ADR 0680 §1, §4; design 20 "Whose a process's own secrets are"
The single-module proof of design 47 G (the operator, 2026-11-17), after pack49:
one change to one leaf module, followed to delivered on g14 and shanks with no hand act.
The single-module proof of design 47 G (the operator, 2026-11-17): one change to one module,
followed through its pipeline to delivered on g14 and shanks.
The toolchain a build module reports (guard key and toolchain-reported event) names the
language version alone (mesh-delivery-sdk steprun Guard); the build module's own
Toolchain func keeps the installed text. Delivered with or after the sdk change.
Builds: design 47 G A-471 (G-22-lead-answers-2.md)
The level took 67 s locally and 74 s in the pipeline, over IntegrationRun's 60 s. The eight slowest tests share no state and run in
parallel: 31 s locally with the fixture's store and bus. The real-store test makes its work directory under the test temp
directory, not /tmp.
Builds: ADR 0445 §3 (the integration level's 60 s bound)
A pipeline's test step places no repository beside the tree and a module's tests read nothing outside their module (lead answer
A-474), so the test no longer needs MESH_CHECK_BESIDE or the node-engine's tree: it fetches a small program of the composer's
contract (testdata/composer) and still proves the build once, the kept composer on the second ask, and the verdict by case.
Builds: design 47 G lead answer A-474 (principles 10 and 9)
The bridge kept a directory for the pre-G indexer's package publishing; its own commit says it goes once G's indexer runs, and
the test of the delivery SDK's step code refuses it. The unit level took 6.3 s over its bound of 5 s in the take-in's pipeline:
the digest tests ran their go commands one after another; the marker table is a subtest per case in a fixture of its own, the
list half a test of its own, and the six slowest independent tests run in parallel (4.6 s locally).
Builds: design 47 G §464, §680 (the build modules keep no copy of the delivery SDK step code); ADR 0445 §3 (the unit level's 5 s bound)