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
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
tags answers items {tag, commit} read from the forge's own tag list, a tag
the forge names no commit for being an error, never a tag without one; tag
writes <directory>/vMAJOR.MINOR.PATCH, the form the Go toolchain's direct
fallback reads, go/v<version> among them.
Builds: design 47 H2 §796, §780; H-A-350 DMC-3; mesh-delivery D5 d2d3ebbf
gate_times answers per class its newest delivery (last) with whether it was
over its budget; the self-check's probe D-budget reads gate_times and raises
over-budget with the class as its id, naming the source revision and its
longest phase, and a newest delivery within its budget clears it.
Builds: design 47 H2 §810; H-A-396
The merge of main's H-A-387/H-A-393 fix gave Store.Held a reference and the
digest another publish holds; a repeat answers ended when the reference is set.
Builds: design 47 H2 §775; H-A-381
The head entry keeps merge-called from its opening and the pipeline's phases
from its end; a record whose every mover runs ends with delivery-time (from
merge-called to the last running of its movers) and class (core when a mover's
catalog entry, read once at its entry's opening, says core). gate_times answers
each class's budget (budget-core 10m, budget-leaf 3m), the last seven days'
median and worst, and every delivery over its budget with its longest phase.
Builds: design 47 H2 §810, §785; H-A-394
Each build module declares again-delays (15s,60s) and gives its puller the
delays steprun.AgainDelays reads from it; a publish's no responders is a
transport fault by steprun.PublishFault with no seat call to learn why, so
the modules no longer invoke the assigner's assignments.
Builds: design 47 H2 §799; H-A-350 DMC-7, H-A-390
The test bus serves the ledger's query the movers index answers, and the
take-in's mover is looked for in its own entry, the head counting it.
Builds: design 47 H2 §809; H-A-391
The gate reads the registrations page by page from the cursor each page
answers, so a source-only registration (no module) past the first page is
watched as any branch; its merge's take-in with no movers ends the record
nothing to deliver as before.
Builds: design 47 H2 §815, §806, §779
A record's head entry record/<branch.source> keeps the record-wide fields and
the count of its movers; each mover, the catalog half's too, has its entry
mover/<branch.source.module> with its pipeline, version and step outcomes per
node, found through the index movers on its record's key. An entry over
64 KiB is refused with record-too-large, cleared when written within it or
at the record's end; the ledger is capped at 1 GiB.
Builds: design 47 H2 §809, §820; H-A-385, H-A-391
While the reserved digest is still empty, a second publish of the same
version with another digest passed the reservation check and the store's
Put moved the version's tag. Publish now refuses it in its held branch,
before the reservation is asked, naming both digests, with the publish's
finding and refused said as any refusal; the same digest is taken as before.
The store's Held answers the digest it holds at the version when it differs.
Builds: design 47 H H-A-393, design 47 G A-490j
deliveries takes module, outcome, since and the cursor next beside state,
repository and group, applies them while it reads, and answers at most
768 KB a page with capped, total and the next page's opaque cursor.
Builds: design 47 H2 §811, §779
The builder records a build's digests only at its end, while the Go build
module publishes during the build step with the reserved version (H-A-373),
so the distribution holder's strict digest check refused every archive-only
publish with "reserved ... for another digest". Recorded now takes an
artifact whose reserved digest is empty, as A-490j decided for every holder,
still refuses a different recorded digest, and its refusal names the case:
the digest reserved and the one published, or no reservation of the version.
Builds: design 47 H H-A-387, design 47 G A-490j
A publish carrying an ask id is kept in the state taken for ask-taken-bound
(10m): a repeat while the act runs joins it, a repeat after it ended answers
the act's state read afresh (the transfer's lacking parts, a held version
ended, a transfer gone refused), never publishing twice.
Builds: design 47 H2 §775, §820; H-A-359, H-A-381
Every delete of a chunk in the incoming object store is followed by the
runtime's purge of what it left (busstate.Objects.Purge), so the store's kept
descriptions equal its live objects; a failed purge is said.
Builds: design 47 H2 §813 (8); H-A-227, H-A-366
Every bundle and archive was published with an empty version, a by-digest
publish, so the builder marked none against its reservation: the same kind
as the Node build module's bundles.
Builds: design 47 H H-A-373
Every bundle was published with an empty version, a by-digest publish, so
the builder never saw package-published and the bundle was not marked
against its reservation.
Builds: design 47 H H-A-372
The builder sends a module's directory with every lane, and an archive is
packed by the Go build seat, so the fetch's refusal of a directory without
go.mod left every archive-only module without Go code unbuildable. Such a
directory is now an empty scope (the empty scope file written); a Go bundle
or package without go.mod still fails at its build step, naming it.
Builds: design 47 H H-A-371
mesh-contracts' K1 regenerated every seat package to answer (value, form, error); the catalog's four
callers take the form.
Builds: design 47 H2 §780; H-A-350 DMC-4
The forge module needs a place for its token that only its own processes read: own-put keeps it as
module/<module>/<name>, named by the caller's account, its newest generation only.
Builds: design 47 H2 §822, §808; H-A-345, H-A-349 DQ-7, H-A-360
Since the toolchain lock pins no SDK (design 47 G §571), only the fetch puts
@novox/mesh-sdk in a module's node_modules. The three tests that build with
the real tsc and esbuild skip the fetch, so they read the SDK from an older
installed toolchain that still carried one. Once a build node installed the
current lock (shanks 19:26, then g14), they failed with TS2307 (main.137,
main.155). The fixture now lays a minimal SDK of its own where the fetch
would, so the tests no longer depend on which toolchains a node still keeps.
Builds: design 47 G §571
Review round 2 (1): the start's wait for the expiries the watch handed over
had no test that failed without it; the start test gains a store whose
deletes wait, and without the wait the key is said expired twice. The note:
a node-engine package naming no verb converged refuses the start loudly
instead of asking seat:node-engine.undefined.
Builds: design 33 control-verbs §10, §11, §14; design 47 H H-A-312
Review round 1 (1)-(3): an until without seconds was accepted, which the
node-engine's RFC 3339 read refuses, withholding every later compose; the
verbs answered before started was said and before the watch's expiries
ended; and the holder kept its own copies of the seat's names, key forms
and value forms, which had drifted from H-A-324. The holder now takes them
from the seat's generated package, the tools' inputs are checked against
its input types, and every seat verb waits for the start's end.
Builds: design 33 control-verbs §2, §3, §11, §12, §14; design 47 H H-A-324, H-A-330
An allowance with no interface never opens an outward link; one named in
interfaces does, and allow now says so: a kept allowance whose interface is
in the outward links of the converged answer asked for the call answers
with outward, that link. The holder reads no shape of the loaded table to
tell an outward link from the tunnel; the event carries no outward.
Builds: design 33 control-verbs §4, §14; design 47 H H-A-324, H-A-325
The holder's ask of the node-engine's converged takes the seat's name, the
verb's name and the answer's form from the node-engine seat's TypeScript
package, as the holder says its own event through its seat's package.
Builds: design 33 control-verbs §10, §12; design 47 H H-A-316, H-A-321
The security and seams reviews of the packet filter's control verbs: the
allowances state is one bucket per machine whose keys carry the node, so a
holder lists and writes its own node's only; allow and disallow refuse an
unproven caller, an adopted node and a converged that does not answer within
10 s, and are written in the hand-act log before the state is; allow refuses a
port the loaded mesh table accepts from given sources only unless a source is
given, and more than the setting allowances-max; allowed answers none on an
adopted node and asks converged again while none answered; rules marks loaded
only on an equal at and lists loaded allowance comments nobody keeps. The event
is said through the seat's generated package; the claim says it, so emits
stays without it.
Builds: design 33 control-verbs §1-§11, §14; ADR 0683; design 47 H H-A-314 (3), (5), (6), H-A-315 (1)-(3), (5), (7), H-A-316, H-A-317, H-A-318, H-A-319
The operator, 2026-11-21 20:35: a firewall module has tools to control the
firewall beside the provisioning from declarations. The holder keeps one
allowance per protocol, port and interface in its state allowances, says every
change as allowances-changed, removes an allowance at its until by a timer on
its own state (and every expired one at its start, before started), and rules
marks each allowance loaded by its comment in the mesh's table. It writes no
rule: the node-engine renders the allowances.
Builds: ADR 0683; design 33 control-verbs §1-§7, §9; design 47 H H-A-304..310, H-A-312 (2)
The Go integration level fetches the forge module's tree without node_modules and
without network, so TestTheSeatGitWholeOverARealBus failed every pipeline carrying
the forge. It now checks its needs first and skips by name, as the Node build
module's realMachine does; with its needs present it runs whole as before.
Issue 1960 (H1).
Builds: design 47 H H-A-294
The test switched the peer's uid in a plain variable the keeper's serving
goroutines read, a data race that fails it under -race; it is an atomic now.
A peer the keeper refuses could also get "broken pipe" instead of the
refusal, when the keeper closed before the request was written: the client
now reads the refusal that waits on the socket. A request larger than the
socket's buffer makes that case happen every time.
Builds: A-37 (only root opens the keeper's socket; a non-root peer is told so); design 47 H section 10 rows 165 and 167 (hq branch design/47-H1-answers-59, 81fa1ee4)
The latest release is placed whatever the range a package.json names
(ADR 0573 §2); one outside that range is now said in the journal, for
the SDK and every other mesh package, so a module built against a
release its range excludes is visible. A range of a form not read is
said as such.
Builds: design 47 H H-A-267, H-A-276
A fetch naming a member's build of a mesh package the registry lacks
lays the build and waits on nothing; without the skip in
placeMeshPackages it waits for the registry's release.
Builds: design 47 H H-A-267
The keeper never marks a first view listing no module as answered
(A-367), so the subtest waited for what cannot come and hid every later
subtest. It waits for the first fill pass and takes it as the first.
Builds: design 47 H H-A-268
A trunk build put only the SDK into a module's node_modules; any other
@novox/mesh-* package its package.json names was left out of the install
and only a group or a member's build brought it, so the forge module's
build failed with "Cannot find module" for its contracts package. Each
such package is now placed at the latest release the registry holds, as
the SDK is; a group's packed package or a member's build still takes
precedence.
Builds: design 47 H H-A-267