Merge pull request 'Design 47 G: the lead's answers A-394 and A-434 to A-444 (the start fixes' review)' (#611) from design/47-G-lead-answers-32 into main
This commit was merged in pull request #611.
This commit is contained in:
@@ -1175,3 +1175,47 @@ the principle that settles it, cited as "design 47 G A-n".
|
||||
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.)
|
||||
- **A-394** (A-392; principle 3) A build seat's finding writer that cannot start is said in the module's journal and in
|
||||
its health, and the module serves its steps on: a step's verdict never waits on a finding being written.
|
||||
- **A-434** (A-433, §19; the operator, 2026-11-15 about 23:15 CET: "I only see 3 accounts, the mesh account, the agent
|
||||
account and the operator account. The mesh accounts should have all the permissions"; "we can always add in gates and
|
||||
guards later") Until the research on the mesh's accounts replaces it, every account the grants part composes but an
|
||||
enrolling node's may publish and subscribe on every subject and put an ask on any seat; a seat verb answered by a
|
||||
process and a tool runner's seat verb admit every caller; no seat loses its holder for every account hearing it.
|
||||
Approval marks stay, for calls that are not a module's (A-435).
|
||||
- **A-435** (A-433, A-434) Approval is the one mark kept: while a verb's seat definition is unread, a call of a verb
|
||||
that may need approval from a caller that is not a module's account (the mesh MCP server's, a person's, an unproven
|
||||
one) is held as before, never run unmarked; a module's account runs it.
|
||||
- **A-436** (A-430b; principle 7) Until every node-engine reads a want by its version, a want for a node whose
|
||||
node-engine reads parts carries the build's parts beside its version, and a module wanted with no passed pipeline
|
||||
names the parts its `build.ended` made until its release is heard. Both forms go in the first change after G is
|
||||
delivered, with A-430b's.
|
||||
- **A-437** (A-428, §16; principle 7) The holder of `mesh-catalog` is wanted with no passed pipeline, as the pipeline
|
||||
runner's own want is: every pipeline runs on a revision it took in, so it cannot wait on one. Every other module still
|
||||
waits.
|
||||
- **A-438** (A-426a; principle 7) For an acting wait, a running have whose node-engine states no health counts as
|
||||
healthy, since an engine from before G states none; and a node that is online runs its node-engine, since online is
|
||||
that engine's own word. Both go when every node-engine states health.
|
||||
- **A-439** (principle 4) The assigner's tool `assigner_why` says why a want is what it is: the step of the pass that
|
||||
decided it and what it read, kept as `why.<node>.<module>` in its state `written`. Until a manifest naming the tool
|
||||
is taken in, `assigner_written` with `why` answers it; that stand-in goes with A-436's forms.
|
||||
- **A-440** (the operator, 2026-11-15 about 18:35 CET) A build seat's queue serves its kinds in turn, so no kind of step
|
||||
waits behind another's backlog.
|
||||
- **A-441** (principles 3, 4 and 7; each a fault met live while G was brought up, fixed where it lives) These stand:
|
||||
an ask's words cut a digest or fingerprint to 12 digits, so the operator channel does not withhold the ask as a
|
||||
secret, and the backup ask names its composition by that prefix; the indexer writes the first registrations from the
|
||||
module graph it holds, with no ask (the operator, 2026-11-14: a module in the module graph is a registration), and a
|
||||
seed asked again writes what its key composed, ends no proposal key, logs each step with its time and prunes nothing
|
||||
on a first registration (completing A-392); a pipeline step fetches a module directory only by its artifact's paths;
|
||||
grants makes each seat's ask stream the bus lacks, from the seat list, with its part's account allowed to; a state is
|
||||
read in pages, never a key at a time, and the indexer's tools keep their view of the trunk while its revision stays
|
||||
the newest (a read over bus state); a get session's object reader lives as long as the session; the forge bridge
|
||||
names each member of a group once and answers open groups or one group, never every ended one; grants reads its
|
||||
loaded list one user per answer, so no answer outgrows one bus message.
|
||||
- **A-442** (A-401; principle 7) The gate's start pass runs once; it asks again only while the registrations cannot be
|
||||
read. A repository it leaves out is said and added at the next registration change or by hand, as A-401 says.
|
||||
- **A-443** (principle 3) Each bus step of a distribution publish is bounded at 10 seconds and logged by name; a step
|
||||
past its bound is given up and said, and its call is cancelled with it, never left running behind.
|
||||
- **A-444** (the seat `git`'s contract; principle 7) The seat `git`'s `branch` with no branch named answers the
|
||||
repository's default branch, as the forge names it; a build seat says each toolchain it reported, not only the ones
|
||||
it could not.
|
||||
|
||||
Reference in New Issue
Block a user