Use the glossary's words in lead answers 31, so the words test passes

This commit is contained in:
2026-11-16 09:24:19 +01:00
parent 4169ded5cd
commit 91f60c7075
@@ -802,7 +802,7 @@ the principle that settles it, cited as "design 47 G A-n".
among their callers, so its keeper reads the catalog holder's manifest.
- **A-379** (replaces A-376 and A-378 for the start: the indexer's `catalog-revisions` is declared in its manifest's
old `objects` section, which grants creates (records.go objectsOf, assertions.go), while the tool runner reaches an
object store only by a new-form binding (node-tools internal/bus/bindings.go objectStore), so nothing binds it;
object store only by a new-form binding (`node-tools` internal/bus/bindings.go objectStore), so nothing binds it;
principle 7: what exists) The tool runner reaches a module's object store by the binding when one is bound, and
otherwise by the old `objects` entry its membership names, under the bus name grants created for it
(`OBJ_<module>_<name>`); a name neither names stays refused as today.
@@ -817,10 +817,10 @@ the principle that settles it, cited as "design 47 G A-n".
composed with the create rights of A-364.
- **A-382** (widens A-381 to its kind, met a second time: live 00:02, every G bundle with a finding writer exits "no stream
on the bus carries mesh-conditions.findings-asked", because the tool runner's SubscribeNew finds a stream by subject
through `$JS.API.STREAM.NAMES`, which novox.node-tools may not publish, while EVENTS carries `mesh.seat.*.event.>`;
through `$JS.API.STREAM.NAMES`, which `novox.node-tools` may not publish, while EVENTS carries `mesh.seat.*.event.>`;
principles 7 and 6) Every account grants composes carries `$JS.API.STREAM.NAMES`, the read of stream names by subject
that hearing an event starts with; it lists names only.
- **A-383** (completes A-382; live 00:21: list revision 274 loaded, yet novox.node-tools still lacks
- **A-383** (completes A-382; live 00:21: list revision 274 loaded, yet `novox.node-tools` still lacks
`$JS.API.STREAM.NAMES` (1805 publish rights, unchanged), since grants keeps an account it holds "beyond this pass" as
the list in force while the catalog half is unread; principles 7 and 3) A right every account carries (A-382) is added
to every account grants writes, a kept one included: keeping an account in force never withholds what every account
@@ -828,16 +828,16 @@ the principle that settles it, cited as "design 47 G A-n".
- **A-384** (completes A-382/A-383 for the whole hearing path, met a third time: live 00:35 "an ordered consumer of
mesh-conditions.findings-asked on EVENTS: context deadline exceeded", the runner account holds only INFO of named durables
on EVENTS; principles 6 and 7) Every tool runner account carries what the runner's SubscribeNew (an ordered consumer from
the next message, mesh-tools node-tools internal/bus/subscribenew.go) asks of the stream that carries the events its
the next message, mesh-tools `node-tools` internal/bus/subscribenew.go) asks of the stream that carries the events its
bundles hear: the create of an unnamed consumer filtered to those events' subjects, its next-message fetch, its info and
its delete, on EVENTS and on every kept seat stream; the same form for every runner, composed in one place.
- **A-385** (generalizes A-383, met a fourth time: live 01:00 "mesh-delivery-gate's bundle asked mesh/ledger.get and it
failed after 10s", the gate's ledger `records` exists and is bound, and novox.node-tools holds no right on
failed after 10s", the gate's ledger `records` exists and is bound, and `novox.node-tools` holds no right on
KV_mesh-delivery-gate_records_state, since a held runner account is copied whole from the list in force; principles 7
and 3; A-363's union) An account grants keeps beyond a pass, a runner's included, is written as the union of the list
in force and what this pass composes for it (its carried modules' grants from the trunk's manifests and their
bindings), never the list in force alone; a pass that only adds still never takes from a loaded user.
- **A-386** (completes A-385 for runners kept as they run; live 01:31: grants 3c582b1b in, novox.node-tools unchanged
- **A-386** (completes A-385 for runners kept as they run; live 01:31: grants 3c582b1b in, `novox.node-tools` unchanged
(2004 publish rights, none on KV_mesh-delivery-gate_records_state), since `runnerUsersKept` keeps a runner whose running
manifest does not say it is the tool runner whole (ADR 0601 §4); principles 7 and 3) A runner kept as it runs is written
as the union of the list in force and the runner grants its carried modules' bindings and events give (the ledger
@@ -850,7 +850,7 @@ the principle that settles it, cited as "design 47 G A-n".
every verb that the seat definition the runner holds classes `read` and does not mark needs-approval, and judges every
other call as before; the hand-kept list `startReads` goes. The bootstrapped definitions carry every seat the first
take-in reaches: `git` joins them, a byte-for-byte copy of its contracts file with its row in the bootstrap test. The
catalogue seat's contract classes `modules`, `module`, `provides`, `dependents` and `seat-definitions` as `read`, and
catalog seat's contract classes `modules`, `module`, `provides`, `dependents` and `seat-definitions` as `read`, and
its bootstrapped copy follows.
- **A-388** (completes A-387; the developer's question: seatdef callers.go reads a verb with no class as a read, which
would let unclassed acts such as `mesh-delivery-checker.try` and `operator-channel.tell` through before the catalog
@@ -861,12 +861,12 @@ the principle that settles it, cited as "design 47 G A-n".
`mesh-delivery-forge-bridge.bridge_merged_message` is refused "the marks of mesh-delivery-forge-bridge are not read
yet"; a module tool names no class, and its marks live only in the catalog half's entry the take-in has not made yet;
principles 7 and 3) Before the catalog half is read, a module tool whose proven caller is another module's account (never
a session's or the console's) runs unmarked, and the runner logs each such call once per tool with its caller ("run
a session's or the mesh MCP server's) runs unmarked, and the runner logs each such call once per tool with its caller ("run
unmarked before the catalog half is read"); a module tool called otherwise waits and is judged as before. A module
tool's mark is read again, and holds, from the call after the half is read. Today the one marked module tool,
`gitea_branch_protection_loosen`, has no module among its callers.
- **A-390** (live 03:17 on novox: the tool runner's first view of the catalog half is refused "mesh-catalog.revision is
refused to novox.node-tools: the tool answers only mesh-delivery-builder"; node-tools declares `invokes: ["*"]`, and
refused to `novox.node-tools`: the tool answers only mesh-delivery-builder"; `node-tools` declares `invokes: ["*"]`, and
the verb revision's callers rule (ADR 0663 §2) matches `seat:mesh-catalog.revision` by its exact text alone, while the
grants part reads a single `*` as every seat verb; principles 7 and 3) The verb revision's callers are the parts whose
entry in the newest trunk revision declares `seat:mesh-catalog.revision` or a single `*` in invokes, as the grants part
@@ -926,7 +926,7 @@ the principle that settles it, cited as "design 47 G A-n".
assignment graph's requirement resolution and the order waits keep reading holders from the holds alone; the post-G
remarks take that up with the rest of the holders question.
- **A-401** (live, the control-node 2026-11-14 21:5x: the assigner ended every proposal, since f1-circuits (watched on
master), link2pay and photos (watched on nox-mesh) are held in no catalog graph of their branch; the gate writes
`master`), link2pay and photos (watched on nox-mesh) are held in no catalog graph of their branch; the gate writes
`source.<branch>` only on a take-in of a merge on that branch (A-34), so a newly watched branch is never started; the
operator, 2026-11-14 about 22:00: "by doing a git clone"; principles 2, 4 and 7, §15, §430, A-85, A-93) A watched branch
starts from the forge, as a clone does. The gate, at its start and on each `registration-changed` of the seat
@@ -952,16 +952,16 @@ the principle that settles it, cited as "design 47 G A-n".
key or added to a held one, names no group, as A-401's new key does: no group moved it, so nothing times it as a
group's; the key keeps the group a take-in last wrote.
- **A-405** (live, the control-node 2026-11-14 22:34: its node-engine refused every candidate, "nothing provides" postgres-database,
secret, route, s3-bucket, document-server and mcp-endpoint, since its catalogue holds only modules whose wanted build has a
secret, route, s3-bucket, document-server and mcp-endpoint, since its catalog holds only modules whose wanted build has a
catalog entry, and the providers' wants name the builds running from before G, which have none, their new builds waiting
for a pipeline that cannot be placed while the node refuses; the operator, 2026-11-14 about 22:40: "yes, go ahead";
principles 2 and 7, §421) A module the node runs whose wanted build has no catalog entry stays in the node's catalogue as
principles 2 and 7, §421) A module the node runs whose wanted build has no catalog entry stays in the node's catalog as
the build it runs, from the manifest of that build the node keeps: it provides, claims and requires what that manifest
says, so the node resolves around it. Its want stays held with `entry-missing` (§421) and nothing new of it is composed;
when its new build's entry comes, it is composed as any other.
- **A-406** (live, the control-node 2026-11-14 22:34: the pipeline's manifest at its build was refused by the manifest judge on
2026-11-13, and its candidate carried no parts; the operator, as for A-405; principles 5 and 7) The pipeline's manifest is
made to pass the judge, as any module's; its first build is asked of the builder once by hand, the way a run on request
made to pass the validator, as any module's; its first build is asked of the builder once by hand, the way a run on request
asks it, since only a pipeline asks builds and none runs yet.
- **A-407** (A-405; principles 7 and 2: the node keeps no manifest of a build that has no entry, and the running event
carries only a digest) A running module whose wanted build has no entry is described from the catalog entry of the build
@@ -1171,7 +1171,7 @@ the principle that settles it, cited as "design 47 G A-n".
"parts-differ: fetched and not in the want's parts" for the tool runner's program.)
- **A-433** (A-389, §19; principle 6) While its catalog half is unread, a tool runner runs unmarked every call whose proven
caller is a module's account, a seat verb as a module tool, and a module's own call in a runtime of its own; it holds the
console's account (the one sessions and agents call as), a person, the controller and an unproven caller as before.
mesh MCP server's account (the one sessions and agents call as), a person, the controller and an unproven caller as before.
Approval marks are for agent calls; inside the mesh a module may do everything. (novox, 2026-11-16 02:35 CET: the
indexer's runtime of its own refused its own `mesh-catalog.revision`, the very first view it waits on, so every reader
of the catalog waited for ever.)