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)
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
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)
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
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)
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
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
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
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
A directory of a trees listing's files the commit does not hold was
thrown as a plain error and answered with the kind failed, so the
indexer took it for a forge that failed, never ran its one-directory
fallback (issue 1585), and published nothing of the repository.
commitTrees throws DirectoryNotInTree for it, and the seat's failure
answers it with the kind not-found, the error naming the directory.
Builds: design 47 H H-A-232 (2), H-A-234; issue 1585
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
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 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
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.
KEPT gains failed-steps, idle and transfers, so each declared state can be read by
its tools; the force-push refusal's test holds that the refusal names the one tool
that may do it and that it runs on the operator's Approve of that call.
Builds: design 47 G A-287, A-288
Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
The seat mesh-pipeline-runner's step event carries `fingerprint`; gitea read
`fp`, which no event carries, and which the type-check refuses once the Node
fetch places the runner's contracts (design 47 G A-285).
Builds: design 47 G A-285
Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
gitea imports @novox/mesh-delivery-contracts-mesh-pipeline-runner, so its
package.json names it and the Node fetch places the group's (design 47 G A-285);
the catalog view's revision answer is typed with its revision and entries, which
revisionAnswer already refuses loudly when the holder leaves them out.
Builds: design 47 G A-285
Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
The tool is marked in the manifest's needs-approval, so each call runs on the operator's Approve; the manifest
uses operator-channel; set_full keeps refusing a force-push onto a trunk and names the new tool; both clients
gain deleteBranchProtection.
Builds: design 46 approval mark §21 (milestone G)
Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
The delivery repository's contracts and SDK live under modules/ as
mesh-delivery-contracts and mesh-delivery-sdk, their Go module paths
renamed to match the folders (the TypeScript names already did), and
every importer in mesh-delivery, mesh-catalog, mesh-host, mesh-tools
and mesh-sdk follows in the same group: a design as it should be, one
path per module, checked by the group's check building every importer.
Builds: design 47 G §427, §88
Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
sudo and localization expect version 0.1; distribution and gitea read the old objects and state sections; mesh-build-go, mesh-knowledge, mesh-provisioner and mesh-self-check expect the findings asked in requires and the keeper's ask consumed. Each assertion failed against the changed manifest before it was changed.
Builds: design 47 G §368, §529, §584, A-30
Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
transfers, idle (key-ttl), failed-steps (history 1) go from requires entries to the old state section and incoming to the old objects section, as §584 has the forge module keep every state in its old sections.
Builds: design 47 G §584, ADR 0619 §1
Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
mesh-delivery-builder.builder_versions answered no numbered version for any name asked (mesh-sdk go and ts, mesh-host, node-tools, mesh-delivery-builder, mesh-conditions), so every module takes 0.1, the floor §368 gives a module with none published: all 144 manifests (141 from "1", distribution, mesh-provisioner and mesh-provisioner-client from "2", which carries nothing over, §583).
Builds: design 47 G §368, §411, §583, A-46
Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
The held writer reads the keys of its state when it is made, so it is made after Serve answers state calls; the keeper says a finding is not said before it exists.
Builds: design 47 G A-32, A-29, A-37
The writer listens to mesh-conditions.findings-asked, so each also consumes it, as the modules that moved before.
Builds: design 47 G A-30, §383, §686
Claude-Session: https://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZ
WriterConfig.Asked is the generated mesh-conditions contract's SubjectFindingsAsked (A-17), a reader's Findings is the
module's writer itself (A-22, A-26), and mesh-build-go's single manifest ask writes and clears its first-view-unanswered
finding through the writer with the contract's Finding (A-28). mesh-config and mesh-vault's own followers (A-28) are not
yet moved onto a views.Reader: they do not compile at mesh-sdk 24f876a.
Builds: design 47 G §687, §689, A-17, A-22, A-26, A-28
Claude-Session: https://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZ
artifact-store-tools (image-missing, sweep-refused), distribution (program and tools bundle, one writer each over its own
kinds), gitea's package-registry (and the token-refused key the TypeScript bundle watches) and mesh-config keep their
findings open and write and clear them through the generic writer; mesh-vault states its assignments view's. A part of an
id told apart by a ref is in the id (<id>.<ref>), each escaped; the writer starts once Serve has the runtime's channel; the
removed findings helpers and resolved words go.
Builds: design 47 G §686, §687, §689, A-3, A-14, A-16, A-22
Claude-Session: https://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZ