The Node build module judged its levels by the same fixed bounds, and its
integration setup took 40 s against 30 s while three nodes' checks ran.
The rule is the kind's, not the Go module's: its bounds, and the
MESH_TEST_LEVEL_BOUND its scripts get, are now their defaults times the
steps the seat has in hand at the step's start (at least 1), and the
result names them (bound, setup_bound).
Builds: design 47 H2 H-A-488, H-A-488 addendum
On a loaded build node the integration level's setup took 34-37 s against
its 30 s bound three times today: the node-engine twice, the assigner once.
The bounds were judging the node's load, not the tests. A level's bounds,
and the MESH_TEST_LEVEL_BOUND its tests get, are now their defaults times
the steps the seat has in hand at the step's start (at least 1). The step's
result keeps naming the bounds it was judged by (bound, setup_bound).
Builds: design 47 H2 H-A-488
The Node build module kept only the last half of its bound of a failed
command's stderr, so esbuild's error line was pushed out by its Node
launcher's stack trace ("esbuild for code: status 1" with no cause). The
image build module's reason and journal line kept stderr's tail alone too,
and so did the Node module's toolchain install. Each now keeps the head and
the tail within its bound, with "… <n> bytes left out …" between them. The
Go build module keeps a failure's first line, not its tail, and is left as
it is.
Builds: design 47 H2 H-A-475
Held compared the version tag's manifest digest with a bundle's or an
archive's blob digest, so every second publish of such a version was
refused even at the same bytes. It now compares like with like: a bundle's
or an archive's stored layer, an image's manifest. The same digest is
already held (ended, published said, nothing stored), on a repeated ask too;
another digest is refused naming the held one. The fake store keeps a
manifest digest beside the layer's, and a row runs the module's OCI code
over a store in memory.
Builds: design 47 H2 H-A-474, design 47 H H-A-393
Review round 1: a durable whose twin is current was removed without
reading the durable itself, so of the five live pairs where both twins
have pulls waiting either one would have gone. The tool now reads the
named durable too and refuses it while pulls wait on it, both read from
the bus at the call. "Current" is the setting twin-current-hours (24 by
default) of the manifest, read from the configuration at each call, the
field name the grants part's manifest names too.
Builds: design 47 H2 H-A-472 (1) and its third addendum (1), (2); review round 1 findings (1), (2)
An unread or stale view held no entry for a watched repository, so every
member would have merged plainly with the note no delivery: a merge that
reports success and delivers nothing. The registrations holder now keeps
the time of its last read and of the last registration-changed heard; the
merge call refuses every member ("the watched branches are not read yet")
while the view is not read since that change, and a read that fails is
said and asked again with the module's growing wait until it answers.
Builds: design 47 H2 H-A-471 (second addendum); review finding H-A-471 addendum (2)
H2 set finding-events to max-mib 8 on every module that binds it; the
healers' manifest test still expected 16 MiB and failed at main.
Builds: design 47 H2 §783, §812; H-A-411 (1), H-A-430 (3)
The operator wants the merge call to work for a repository of no module,
such as hq. A member whose repository has no watched branch (no entry, or
an empty set, in the registrations' watched branches) is judged against
nothing of the module graph (no failed required step at a fingerprint),
merged in the order named, answered and kept merged with the note "no
delivery: the repository has no watched branch", and left out of
merge-called by that kept note, at the call and at the start's re-say, so
it starts no delivery. A group mixing it with watched members judges and
delivers those as before. A watched repository whose base is unwatched
stays refused. The holder answers at the seat git's form 3.
Builds: design 47 H2 H-A-471 and its addendum (1), (2)
A module that moved into the tool runner left its program's durable
<node>_<module>, and one that runs its own program again left
<node>_<module>_tools: about 110 such orphans the tool refused by name.
It now removes a module's durable when its twin on the same stream has
pulls waiting and a delivery within the day, and names the twin in the
hand act; a module's only durable stays refused.
Builds: design 47 H2 H-A-472 (1), H-A-127, H-A-128, G A-340
The entries whose refusal a record's end must clear were kept in process
memory, so after a restart a refusal of an entry never written (an act's
first write, a mover's) was never cleared. A record-too-large finding now
names its record as its subject (its id stays the refused entry), and the
record's end clears every held one whose subject is the record, read from
the gate's own findings state; the in-memory map goes. A finding raised
before this change names its entry as its subject and clears when that
entry is next written within 64 KiB.
Review finding: record-too-large cleared at the record's end only from
process memory (movers.go:228-233, Records.refused).
Builds: design 47 H2 §809, H-A-455 (3), H-A-460
An act the gate owes the forge is now the entry act/<branch.source.act.id>
(type act, index acts on its record's key in the manifest), removed when
the forge bridge performed it; the head entry holds the record's fields
alone, and the record's acts are joined from their entries when read.
The record type keeps no act operation: a head written before this change
is read for its fields and the acts embedded in it are ignored (they are
notes and views of the few records in flight at the delivery; losing them
changes nothing the operator relies on). A view act's text is the record's
summary, the head's fields and a count of movers per outcome, so it fits
64 KiB for any record; gate_record still shows the whole record. The
64 KiB refusal measures every write, the head's, a mover's and an act's,
raising record-too-large, which the record's end clears for every entry
of it. The gate's whole test gains the step: 126 movers write 127 entries
plus their acts, none over 64 KiB, the head counting 126 and holding no
act; a take-in said again with a why past 64 KiB raises record-too-large
and the record's end clears it.
Builds: design 47 H2 §809, H-A-385, H-A-391, H-A-453 (3), H-A-455, H-A-457, H-A-459
The seat git's whole test configures no token: the bundle mints the tools'
account's token at the fixture forge with the admin's login, writes it
through the vault seat's two-step own-put (sealed to the call's key) and
reads it through get (sealed to the process's key), both answered by the
test, with the mint's lease watched as the runtime delivers it. After the
mint the forge holds exactly one token for the account, mesh-tools-1, the
one the vault keeps at generation 1; the old fixed-name token is gone.
Builds: design 47 H2 §808 (whole: the forge holds one token for the account after), H-A-422, H-A-430 (1), H-A-439, H-A-453 (3)
The review found §810's probe proven only at the unit level (H-A-453 (3)): the whole test now enables the budget
probe, answers gate_times with a core delivery 11 minutes from its merge call, reads over-budget for core naming its
record and longest phase, and a core delivery within its budget at the next run clears it.
Builds: design 47 H2 §810, H-A-453 (3)
test/fakebus.ts imports tweetnacl to seal as the vault does; it came only through mesh-sdk's own dependency, so the
forge module's tests named nothing they import (the review's finding; H-A-453). Pinned as mesh-sdk pins it, an
external package as the rule allows.
Builds: design 47 H2 §808, §822; H-A-407, H-A-453
Read on novox at 2026-11-22 01:35 UTC through the bus module's nats_streams
(the review's finding on H-A-437; H-A-453):
gitea bound 16703 bytes, 28 msgs cap 8 MiB
gitea announced 98 bytes, 1 msg cap 8 MiB
gitea findings 565816 bytes, 2013 msgs cap 8 MiB
gitea first-views 369 bytes, 1 msg cap 8 MiB
gitea transfers 396894 bytes, 2015 msgs cap 8 MiB
gitea idle 376879 bytes, 1041 msgs cap 8 MiB
gitea failed-steps 255007 bytes, 754 msgs cap 8 MiB
gitea calls 36362 bytes, 93 msgs cap 8 MiB
gitea taken no bucket on the bus yet cap 8 MiB
gitea-findings log 0 bytes, 0 msgs cap 8 MiB
Each fill is below a quarter of 8 MiB (2 MiB), the largest 565,816 bytes, so
each cap stays at 8 MiB; none is raised.
Builds: design 47 H2 §812; H-A-411 (2), H-A-437, H-A-453
The review found §810's whole criterion proven only at the unit level (H-A-453 (3)): the whole test now ends its
record through the wants seat's wanted and pipeline-wanted and the node-engine seat's running, over the real bus, and
reads the head's delivery-time and class core from a core mover's catalog entry.
Builds: design 47 H2 §810, H-A-453 (3)
The forge module's internal/seatgit whole test needs the Node build seat, and no Go artifact's from holds it, so
nothing named its need and the Go build seat ran it on a node without the Node toolchain. The manifest now says the
need at its top level, read by the Go build module for such packages; gitea declares node-build-node
(review round 1, mesh-catalog, finding on §800; H-A-453 (2)).
Builds: design 47 H2 §800, H-A-453 (2)
A pull request closed unmerged is a fact of the forge, not a fault of the
act, so the gate no longer keeps a refusal for an act the forge bridge
ends not-needed: the record's acts and gate_record show it ended with
that outcome, and delivery_status says no refusal of it. Every other
outcome other than performed is still said as a refusal.
Builds: design 47 H2 §807; H-A-432 (2), H-A-444
The side branch's manifest rows, gate, forge, packet-filter and
package-manager changes join the build modules' share; no file was
touched by both.
Builds: design 47 H2 (the merged commits' own Builds: lines)
The forge bridge ends an act whose pull request closed unmerged with the
outcome not-needed. The gate keeps it in the record's acts as ended, as it
keeps performed and could not be performed, and no longer counts it as
owed. The gate's code takes any outcome forgemsg reads, so the change is
forgemsg's outcome list at mesh-delivery feat/47-H2-a. The row in the
owed-acts test fails where forgemsg refuses not-needed.
Builds: design 47 H2 §807; H-A-432 (2)
The file beside the token that kept its scopes went with C4, and with it
the re-mint of a token carrying a scope beyond the tools' (write:admin).
The value written through own-put now holds the token and its scopes; a
token minted with other scopes, or a value naming none, is minted again
unasked and the one it replaces deleted at the forge. The Go bundles read
the token out of that value. The lost test is back as a row of the scope
test in test/token.test.ts.
Builds: design 47 H2 §808; H-A-439
A bundle publishes under the version its ask reserved, and the delivery SDK's
publish refuses an empty one loudly; the tests' bundle asks carry a version, a
bundle asked with none is shown refused, and an archive still publishes by its
digest alone.
Builds: design 47 H2 H-A-373, H-A-373 addendum
The gate's owed event carries record, the delivery record's source
revision <branch>.<source> (the record's key), said and kept in the
record's acts alike, so the forge bridge keeps it with the act and
bridge_owed_again finds a record's acts in its own state. Built against
the seat mesh-delivery's Owed.record on mesh-delivery feat/47-H2-a.
Builds: design 47 H2 §807; H-A-432 (1)
Read on novox at 2026-11-22 (the seat mesh-broker's show; the gate's
old-section state source through the bus module's nats_streams, since the
bus module made no entry for it):
mesh-delivery-gate heads 582 bytes, 5 keys cap 8 MiB
mesh-delivery-gate findings 24905 bytes, 27 keys cap 8 MiB
mesh-delivery-gate source 70166 bytes, 68 msgs cap 8 MiB
artifact-store-tools findings 8199 bytes, 8 keys cap 8 MiB
Each fill is below a quarter of 8 MiB (2 MiB), so each cap M1 wrote stays
at 8 MiB; none is raised.
Builds: design 47 H2 §812; H-A-411 (2), H-A-437
The packet filter holder's tools read allowances-max themselves (config at
tools/index.ts); no file places it, so the manifest says "runtime": true
and the judge's placed-nowhere rule holds it as read by the module's code.
Builds: design 47 H2 H-A-430 (4)
The eleven other modules that bind finding-events (claude-code, mesh-healers,
mesh-knowledge, mesh-provisioner, mesh-recovery, mesh-self-check,
mesh-watcher, minio, nfs-server, restic, zfs) set max-mib 8 for 7 days, as
the delivery modules' already do, so the indexer's finding-events rule (I6)
judges every manifest alike.
Builds: design 47 H2 §783; H-A-411 (1), H-A-430 (3)
Two processes that minted at once left the forge two tokens by one name, and a token kept in a file in the
runtime state is a plain state. Both accounts' tokens (mesh-tools, mesh-packages) are now the module's own
secrets in the vault, written through the seat mesh-vault's own-put and read through its get, sealed to the
reading process's key. A refused or expired (token-ttl) token is minted again only by the holder of the lease
mint in the state token-lease (mint-lease); each mint is named <account>-<generation>, and the token it
replaces is deleted by id only after own-put landed. The Go bundles read their tokens through get at start
and at secret-changed; the MESH_GITEA_*_TOKEN_FILE words go. forge_token_lease reads the lease and each
token's age, never the token.
Builds: design 47 H2 §808, §822; H-A-407, H-A-422, H-A-426, H-A-430 (1)
Each of the four is core. Every state that named no cap names one, from its
live fill read 2026-11-22 01:4x CET (mesh-broker show, nats_streams on novox):
mesh-build-go steps 16.0 MiB (16,783,695 bytes) -> 128 MiB; mesh-build-node
steps 2.35 MiB (2,463,833 bytes) -> 16 MiB; every other state under 2 MiB ->
8 MiB (largest: distribution holds 1,844,287 bytes, mesh-build-go
detected-steps 868,554, distribution transfers 846,359, findings 668,161, idle
401,736, mesh-build-go pauses 254,366). The Go build module's finding-events is
8 MiB for 7 days. The objects stores already name their caps; none keeps a log.
The Go and Node build modules prune their state detected-steps (each key an
artifact's steps as detected, detected again when gone) at their own writes,
past prune-mark 70 % down to prune-target 50 %, and serve
<module>_state_prune_now and <module>_state_keep; no other state of the four is
prunable (each is truth: running steps, pauses, keys, toolchains, findings,
holds, transfers, windows, mirrors, taken asks).
Builds: design 47 H2 §812, §820; H-A-411 (1), (2), (3), H-A-437
The Go build module's level answers its text in output (test2json's Output
lines), the Node build module's what its commands wrote; the delivery SDK's step
run keeps it as <node>.<ask> in the module's outputs objects, which each module
asks for in requires (1 GiB, kept 7 days) and reads through the verb output at
form 2. Each module's kit test runs the SDK's SeatVerbs.
Builds: design 47 H2 §791, §820; H-A-412 (1), H-A-412 second addendum (a), H-A-421, H-A-434
The objects template takes max-age-days (absent keeps an object for good): the
keeper plans it as the object store's max age, which the bus applies as the
store's TTL, so a build module's outputs objects go at their seven days.
Builds: design 47 H2 §820 (outputs: 7 days, the store's max-age), §791; H-A-434
An install ask's body runs npm ci from the lock with no install script and no
link, packs the tree alone under modules/<module>/node_modules, publishes it to
the artifact store as the archive <module>:node-modules under the ask's version
and answers its reference, which the step's end carries. The package.json npm
ci needs is written from the lock's root entry, a lock without one refused. The
integration level's setup bound in code goes: half of the level's bound, which
each level's script gets as MESH_TEST_LEVEL_BOUND.
Builds: design 47 H2 §800; H-A-399 (2), H-A-403, H-A-427
The delivery SDK replaced the output chunks with the verb answer over the
steps state's objects and output at form 2: each build module keeps an end
over the steps state's value with KeepAnswerIn, serves AnswerTool and
OutputTool over its steps state, and its steps name their outputs objects.
Builds: design 47 H2 §791, H-A-412 addendum, H-A-412 second addendum (b), H-A-399 (1)
The check counts every test the integration level runs, untagged ones in: the NFS server
module held 51 and the package manager module 121, over the budget of 50. Each folded file's
tests run in order as rows of one test that keeps the first one's name and logs each case
before it runs; the root helper's test sockets are numbered per call, as one test now holds
several listeners, and the case that skips without pacman-conf runs last. Counts now 48 and 42.
Builds: design 47 H2 §819; H-A-349 DQ-14
Each build module's steps read tool listed only `<node>.<id>` keys and so
skipped every ask's step, kept as `<asker>.<node>.<id>`: it now reads every key
of its node, newest id first. The Go build module's test of capacity 0 also
holds the seat's current at form 2: no ask taken, why not capacity 0, then
paused.
Builds: design 47 H2 §801; H-A-399 (1)
The Go build module's level result carries not-run (the SDK reader's NOT RUN
skips), its tests get MESH_TEST_LEVEL_BOUND, the level's bound, from which
mesh-sdk's helpers take the setup bound; a test call naming an install archive
reads it from the artifact store by its reference and unpacks it into the
workspace's tree before go test. check-needs is read from the module's
manifest, on the Go artifact whose path holds the package, and the marker
file goes: the Node build module's manifest declares it on its bundle.
Builds: design 47 H2 §800; H-A-294, H-A-350 DMC-6, H-A-368, H-A-399 (1) (2) (3)
The manifest validator takes no # in consumes, and a key part escapes its
dots (mesh-sdk keys.EscapeName), so the forge module keeps hearing
step-ended.*.*.*: a source-only check's module source.<owner>.<name> is one
escaped subject part, and its body names it whole. The whole test says it so.
Builds: design 47 H2 §815; H-A-408
The runner's step-ended of a source-only check names the registration's key
source.<owner>.<name> as its module and the commit's root tree hash as its
fingerprint, so its subject holds more parts than a module's: the forge
module hears every subject under step-ended and judges it as a module's.
The seat's whole test refuses an hq pull request whose unit step failed.
Builds: design 47 H2 §815; H-A-408
heads is written through the SDK's pruned state, which judges the fill each
put answers and past prune-mark (70 %) prunes the oldest keys to
prune-target (50 %); the gate serves mesh-delivery-gate_state_prune_now and
mesh-delivery-gate_state_keep, each written in the hand-act log.
Builds: design 47 H2 §812; H-A-380, H-A-386, H-A-411 (3)
A module that claims a seat is core, one that claims none a leaf (141
manifests; the build modules and the registry are the other developer's).
The forge module's, the gate's and the sweep's states each name 8 MiB, and
their findings stream 8 MiB for 7 days.
Builds: design 47 H2 §810, §812, §783, §820; H-A-394 (1), H-A-411 (1), (2), H-A-378
The forge module reads ask-taken-bound from MESH_CONFIG_ASK_TAKEN_BOUND, the
word the node-engine composes for every setting a manifest declares; the
check takes MESH_CONFIG_<KEY> of each declared config key as set, and an
undeclared one as set by nothing.
Builds: design 47 H2 §775, §781; H-A-370, H-A-400 (2)
A derived accept rule's one comment says derived <modules> <protocol>/<port>
scope <any|private-network|local-network>, its module list cut with a count
past 128 bytes; allow without a source is refused for a port whose derived
rules name no scope any, read from the comments, never from a rule's shape.
Builds: design 47 H2 §813 (4); H-A-357, H-A-384 (1), H-A-349 DQ-11
From..to inclusive, each read from the forge one by one, with its merge
commit, when it was merged and the merge call that made it when a kept call
names it merged; at most 768 KB, capped with the next number as the cursor.
Builds: design 47 H2 §812, §811; H-A-402
Each act (status, comment, view, note, merge-pull, tag) carrying an ask id is
taken in the state taken, key git.<ask>, for the setting ask-taken-bound
(10m, read from MESH_CONFIG_ASK_TAKEN_BOUND): a repeat while the act runs
joins it; after it ended, the repeat answers what the forge holds of the act,
read afresh (a merge call's pull requests merged with their merge commits),
and the act is never done twice. An act that performed nothing drops its
key, so the kept call's repeat acts.
Builds: design 47 H2 §775, §820; H-A-381, H-A-400, H-A-359a
oci-artifact-registry's list filters by name or module while it reads and
answers at most 768 KB a page with capped, total and the cursor next, in
order of the names; container-image-registry's answers whole as its form
says. The registry takes a removal for retention whoever asks it: the
refusal "not the sweep's" and its read of the sweep seat's holder go. The
sweep reads the list from its cursor until no page is left.
Builds: design 47 H2 §813 (7), §811, §779; H-A-350 DMC-10, H-A-399
A 401, 502, 503 or connection fault is judged by the forge's own
unauthenticated version read: the read failing, or naming the store
unavailable, answers the kind away with part and words, which every caller
reads as a transport fault; the read passing, a 401 (the fresh token refused
too) is the forge refusing the mesh's admin account, never worded as an
account to create.
Builds: design 47 H2 §776; H-A-350 DMC-2, H-A-354