|
|
|
@@ -93,3 +93,147 @@ A question no principle settles goes to the operator or to a record; it is marke
|
|
|
|
|
- **H-A-20 The main file's size**, a must for three reviewers: the lead's bending of the bound (H-A-7) is said to the
|
|
|
|
|
operator at 01:48 with the question whether the reshape follows H0 as its own change; until the answer the bound
|
|
|
|
|
stands bent, said.
|
|
|
|
|
|
|
|
|
|
## From H1's prepare (2026-11-20 01:55 to 02:20 CET; six build maps, 92 questions merged in the lead's working folder)
|
|
|
|
|
|
|
|
|
|
Each answer names the item of the merged list (Q1 to Q92), then the principle. "Both" means the preparers agreed.
|
|
|
|
|
Where two preparers disagreed, the chosen one is named.
|
|
|
|
|
|
|
|
|
|
- **H-A-21 (Q1)** `merge-pull` answers once, at the call's end, naming `call` and each member's outcome. P1.
|
|
|
|
|
- **H-A-22 (Q2)** Its caller `id` goes (the call names it); an already-merged member is refused `already-merged` with
|
|
|
|
|
its commit; the answer is `{repository, number, state, commit|why}` per member; `protected` goes; `calls` is declared
|
|
|
|
|
in the seat definition. P3, P7.
|
|
|
|
|
- **H-A-23 (Q3)** A kept stream's age and cap are its definition's `keep` (30 days, 64 MiB as defaults there); the
|
|
|
|
|
word "setting" is dropped from those lines. H-A-19 is read so: a value stated once outside code. P11.
|
|
|
|
|
- **H-A-24 (Q4)** A call is 16 lowercase hex characters, one subject token; `hand`, `seed`, `by` and the time live in the
|
|
|
|
|
record's trace (sdk). P8.
|
|
|
|
|
- **H-A-25 (Q5)** `record-opened` and `record-ended` carry `branch`, `source`, `call`; `milestone` stays as
|
|
|
|
|
`<branch>.<source>` for the teller and the watchman (cat); the verb `source` answers `call`. P7.
|
|
|
|
|
- **H-A-26 (Q6)** `source-moved`'s wildcard has two tokens; its body as §737 with `v`; every decoding reader is named
|
|
|
|
|
with its change in its repository's map. P7.
|
|
|
|
|
- **H-A-27 (Q7)** `head-moved` on `forge.<owner>.<name>.<escaped branch>.head-moved` under the module stream prefix; its
|
|
|
|
|
form in `forgemsg`, series 0.1. P8.
|
|
|
|
|
- **H-A-28 (Q8)** Everything of the earlier model leaves in H1: the gate's states and `approval-carried`, `groups` and the
|
|
|
|
|
group model, the forge module's merge-check machinery, the knowledge base's `groups` invoke (cat); `heads` is declared
|
|
|
|
|
in the seat definition. One model, no second one left running. P7; ADR 0682 §2.
|
|
|
|
|
- **H-A-29 (Q9)** §738's delivery record is built in H1: the gate consumes the new `take-in.taken` for entries and
|
|
|
|
|
outcome and reads a record by its key `<branch>.<source>`, never every record. P3.
|
|
|
|
|
- **H-A-30 (Q10)** The grants part makes one durable consumer per registered watched branch from the registrations
|
|
|
|
|
(`MaxAckPending` 1), as it makes every consumer today; mesh-sdk binds a consumer by the name its caller gives;
|
|
|
|
|
`source-moved` gets a kept stream (sdk, with ib's stream). P7 over P12 here: the maker of consumers exists, and a
|
|
|
|
|
second maker would be a second mechanism.
|
|
|
|
|
- **H-A-31 (Q11)** `take-in.taken` and `take-in.pending` carry only the lines' fields, plus `by` and `why` for a hand act;
|
|
|
|
|
readers pair by `<branch>.<source>`. P7.
|
|
|
|
|
- **H-A-32 (Q12)** The catalog revision's number is the source's; its name `<escaped branch>.<source>` for every branch,
|
|
|
|
|
the trunk included; written once by read-before-write under the branch's one-at-a-time consumer. P3.
|
|
|
|
|
- **H-A-33 (Q13)** The source value carries `source` and `call`; the next number is the branch's newest plus one; a
|
|
|
|
|
`merge-called` whose call the newest already carries writes nothing. P3 (with H-A-13).
|
|
|
|
|
- **H-A-34 (Q14)** The assigner builds the validator from the change's heads on `node-build-go` as it builds the
|
|
|
|
|
composer, its input on `mesh-wants`' `input`; `RefusedCycle` moves to `mesh-delivery-sdk/graph` first; the program's
|
|
|
|
|
source stays where it is until a later cleanup (ra). P9; ADR 0682 §5.
|
|
|
|
|
- **H-A-35 (Q15)** A pipeline's kept value holds `movers` as `{module, commit, fingerprint, repository, tier}`; each step
|
|
|
|
|
result names its module; `list` filters by a mover; the runner's contract lands first. P7, P10.
|
|
|
|
|
- **H-A-36 (Q16)** A runner state `queue` holds `queue.next` and one key per waiting pipeline; the pipeline's outcome
|
|
|
|
|
value is `waiting`; an over-cap start is acknowledged and kept there, never left unacknowledged. P1, P3.
|
|
|
|
|
- **H-A-37 (Q17)** A want keeps `fp`, `hold` and `words`; `parts`, `rule`, `newest`, `kept-on` and `composed` go; `rank`
|
|
|
|
|
is an integer from 1, absent for a placement's `build` and for the node's own want (host's set, ra's drops). P7;
|
|
|
|
|
ADR 0682 §8 ("never digests" reads `fp` as the build's name).
|
|
|
|
|
- **H-A-38 (Q18)** A candidate's `added` names a version alone; the shadow resolves it as it resolved parts; `parts`
|
|
|
|
|
leaves the assigner seat's contract. P7.
|
|
|
|
|
- **H-A-39 (Q19)** `ModulePlacement` gains `build` (one row per branch and build), a fingerprint; the assigner wants the
|
|
|
|
|
version released at it. P7 (with H-A-5).
|
|
|
|
|
- **H-A-40 (Q20)** The next tier is released on `running` matched by the mover's fingerprint from `pipeline-ended`;
|
|
|
|
|
`running` gains no version in H1 (ra). P7.
|
|
|
|
|
- **H-A-41 (Q21)** The callers type and functions, every holder's list, the step runner's asker judgement and the tool
|
|
|
|
|
runner's `admitted` hook go in H1, in one group; the vault's enrolment caller stays; a step run carries `asker`. P6;
|
|
|
|
|
ADR 0682 §10.
|
|
|
|
|
- **H-A-42 (Q22)** H1 carries a mesh-sdk change beside #200: the new byte-equal copies of the seat definitions and the
|
|
|
|
|
checker's copy dropped, published first as the next version; §762's "mesh-sdk in H4" is read as the wake shape alone
|
|
|
|
|
and corrected in place in this branch. P5.
|
|
|
|
|
- **H-A-43 (Q23, Q24)** The per-verb `timeout` is built in H1 (a merge call of several members is cut at a fixed 30 s
|
|
|
|
|
otherwise): the field in the seat definition and its schema, whole seconds 1 to 600, others refused; `merge-pull`
|
|
|
|
|
names 120; the tool runner's own default is the setting `call-timeout`, 30 s; every caller and the serving runner wait
|
|
|
|
|
it; module processes through mesh-sdk. §760's "H4" is corrected in place. P3, P11.
|
|
|
|
|
- **H-A-44 (Q25)** Writers the maps did not name: the watchman's and the view's take-in readers, `sourcebranches` and
|
|
|
|
|
`meshcatalogclient` are the indexer-and-bridge developer's; the teller, the knowledge base's and the issue tracker's
|
|
|
|
|
readers are the gate-and-forge developer's; mesh-sdk's copies are the sdk developer's; the knowledge base reads
|
|
|
|
|
`pipeline-ended` in place of `group-ended`. The lead's order of work.
|
|
|
|
|
- **H-A-45 (Q26)** The word is `want:version`, a constant of the node-engine seat contract, stated in `manifest-reads`
|
|
|
|
|
and read from `manifest-reads-changed` alone; the assigner holds any node not stating it (host). P8, P1.
|
|
|
|
|
- **H-A-46 (Q27)** The apply order is a read verb `apply-order` on the seat `node-engine` (contract and sdk copy first),
|
|
|
|
|
one row per unapplied changed want: `module, pipeline, rank, position, why, waits`; H-A-9's "read tool" is read so.
|
|
|
|
|
P4, P9.
|
|
|
|
|
- **H-A-47 (Q28 to Q36)** A member whose base is no watched branch is refused at judging, naming the base (P3). The
|
|
|
|
|
call's value gains `said` (P3). A call past retention is deleted on each new call's write, oldest first (P1). A merge
|
|
|
|
|
call with no caller account the tool runner proved is refused, saying why (P3). FORGE-1 builds `step-unread`; the
|
|
|
|
|
clean state reads `failed-steps` after the first failed step; a one-event read tool is H4's (P3, P4). A session reads
|
|
|
|
|
its record by `call` through the gate's verbs after the answer, then waits on `pipeline-ended`, re-reading (P1).
|
|
|
|
|
"The tool runner's `merge-pull` tool" reads as the seat `git`'s definition and its sdk copy (P8). The seed opens no
|
|
|
|
|
record (P7). `gate_source_start` and `gate_source_again` stay, the first writing through the seed's path (P4).
|
|
|
|
|
- **H-A-48 (Q37 to Q43)** Every indexer and bridge part no line names (`Src` stamps, the builder-log index,
|
|
|
|
|
`TakeInMerge`, the own-build hold, previews, `taken`, the `pull` and `open` messages, the bridge's finding writer) goes
|
|
|
|
|
in H1 and is added to §764's lists (P7). `pins-stated`, `heads-replaced`, `pinned`, `freed` and the gate's pin
|
|
|
|
|
operations go; the indexer pins in its own state (P7). The gate's stalled conditions go, the watchman's `record-open`
|
|
|
|
|
being the one signal; `untaken-bound` runs on the gate's one timer; the start loops are waits for the bus, said (P7;
|
|
|
|
|
ADR 0682 §11). `transition` leaves `emits` (P7). A record's member is `<repository>@<number>` for a call and
|
|
|
|
|
`<repository>@<commit 12>` for a hand take (P8). The bridge's `heads` gets a read tool, no say-again (P4).
|
|
|
|
|
`git.branch` becomes a kept call that waits on the holder's return, no redelivery timer (P1).
|
|
|
|
|
- **H-A-49 (Q44, Q45)** Every reader of `manifest-accepted` and `manifest-refused` (the builder's floor, the watchman,
|
|
|
|
|
mesh-config on #708, the tool runner's ledgers, membership) reads the mover's entry on `take-in.taken`; #708 moves to
|
|
|
|
|
`catalog-revision` before it merges. Only a take-in keeps a catalog revision; a toolchain change reaches pipelines
|
|
|
|
|
through `toolchain-agreed`. P1, P9; ADR 0682 §4.
|
|
|
|
|
- **H-A-50 (Q46)** The event that wakes a held take-in is the indexer's own `room` on the seat `mesh-catalog` (the store
|
|
|
|
|
is the indexer's); H-A-12 is read so. P12.
|
|
|
|
|
- **H-A-51 (Q47 to Q51)** One `validate` run per take-in revision, every mover's step reading it; the runner's and
|
|
|
|
|
`mesh-wants`' contracts add `validate` (P7). Every step of a mover waits for its dependency's publish (P3; ADR 0682
|
|
|
|
|
§6). Tiers come from edge kinds 2, 4, 5 and 6; a cycle among movers is one tier, said in the journal (P3; ADR 0666
|
|
|
|
|
§14). `widens` is per mover in its entry (P10). Lines already built (`branch` and `source` on `package-published`,
|
|
|
|
|
`pipeline` on step events) are read as built (P7).
|
|
|
|
|
- **H-A-52 (Q52 to Q59)** The runner consumes `version-released` in H1 and writes the version into the mover's entry
|
|
|
|
|
(P1). A run on request stays per member, in the same queue (ADR 0682 §7). A hand `start` keys the newest revision's
|
|
|
|
|
`<branch>.<source>` with that module as its one mover, refused when the key exists (P4). The runner asks `outdated`
|
|
|
|
|
no more; kind-1 dependents come from the edges it holds (P1; ADR 0682 §6). A waiting pipeline says
|
|
|
|
|
`pipeline-started` at its write, so its revision is pinned while it waits (P3). Its wait is said on
|
|
|
|
|
`…wait-held.<branch>.<source>`; the enums gain `pipeline` and `pipelines-at-once` (P8). `pipelines-stalled` and
|
|
|
|
|
`queue-full` have scope `delivery`, one each for the mesh; `queue-full` clears when the over-cap start is taken (P3).
|
|
|
|
|
- **H-A-53 (Q61 to Q64)** One `approval` step per mover whose policy names it (P10). `runner_place` is backed by a verb
|
|
|
|
|
`place` (`pipeline`, `why`) on the runner's seat (P4). A mover left in an older pipeline whose dependency was
|
|
|
|
|
superseded out builds against the newest published package, said in its step's why (P3; ADR 0682 §7). "A set-aside"
|
|
|
|
|
reads as `pipeline-ended` and `cancel` alone (P7).
|
|
|
|
|
- **H-A-54 (Q65)** The indexer's §749 pins land with the runner's R3 and are reviewed together. The lead's order.
|
|
|
|
|
- **H-A-55 (Q66, Q67)** Rule 2, rule 7, the network hold and A-428's exceptions end; the record-policy yes and the
|
|
|
|
|
outside wait stay as the asker's. `assigner_release` stays for puts and outside waits, losing its acting, order and
|
|
|
|
|
delivery steps. P7, P4; ADR 0682 §9.
|
|
|
|
|
- **H-A-56 (Q69, Q70)** Tier progress is the assigner's state `written`, key `pipeline.<branch>.<source>` with
|
|
|
|
|
`{tier, since, movers}`, one deadline timer; a tier counts placed movers only; `wanted` gains `pipeline`; `tier-late`
|
|
|
|
|
clears when the late movers run or a later pipeline passes; the end is said on `…wanted.<branch>.<source>` with
|
|
|
|
|
`outcome`. P4, P7, P1, P3.
|
|
|
|
|
- **H-A-57 (Q71 to Q74)** `acts` stays for the builder's build seats; `bound`, `DefaultBound`, `Wait` and the other
|
|
|
|
|
acting entries go (P7). The seat `mesh-delivery-checker` goes with every copy and its `check` and `recheck` kinds
|
|
|
|
|
(P7). The operator channel's limit, `held-back` and `ask-again` go in H1 with their state, verb, sdk reads and the
|
|
|
|
|
tool runner's row (P7; ADR 0682 §14). `indexer_unpin` is renamed to take the pin's key; one tool (P7).
|
|
|
|
|
- **H-A-58 (Q75 to Q78)** "Every durable starts at the newest and refuses the old form" holds for consumers of event
|
|
|
|
|
streams, not for watches of last-per-subject state; the refusal is in the shared follower; old means a
|
|
|
|
|
`take-in.taken` without `call` or a pipeline value without `movers`; the gate's and the forge module's durables are
|
|
|
|
|
dropped at the clean state's drop step, named there (P2, P3). The new `cancel` reads no old pipelines: they are
|
|
|
|
|
dropped (ADR 0682 §12). `assigner_want_drop` deletes the key, written in the hand-act log; the next pass writes the
|
|
|
|
|
new form (P4). A run's candidate graph is dropped on the `pipeline-ended` of its last member (P1).
|
|
|
|
|
- **H-A-59 (Q79 to Q84)** `pipeline-failed` has scope `delivery`, its owner as today (P8). A higher rank waits for a
|
|
|
|
|
lower rank of its pipeline on this machine alone, said as `wait-held` step `placing` (P3; ADR 0682 §9). When two
|
|
|
|
|
pipelines' wants changed at once, the older source first (ADR 0682 §7). "Its own want last" is the node-engine's
|
|
|
|
|
module; the node's composition stays first (P8). The bus module and the backup holder are found by claim
|
|
|
|
|
(`mesh-broker`, `node-backup`) from the entries the composer holds (P9). A revert is a want naming a fingerprint this
|
|
|
|
|
node ran before, read from the applied record (P1, with H-A-5).
|
|
|
|
|
- **H-A-60 (Q85 to Q88)** The entry asked again: on `catalog-revision` and on the link's reopening, at most `entry-asks`
|
|
|
|
|
times (default 5), then `unanswered` and the finding `entry-unanswered`; built in mesh-delivery's `meshcatalogclient`
|
|
|
|
|
(P3, P11). The node-engine's read of every node's record stays: it feeds the composer; the plan's section 3.5 and gap
|
|
|
|
|
table E row 67 are corrected (P9). Its wait on `restic.backed-up` by name is out of H1, a leftover in the gap table
|
|
|
|
|
(P9). Existing timers, polls and whole reads in files H1 touches stay for H4 (§762); new runner code reads only its
|
|
|
|
|
`queue` keys (ADR 0682 §11, P1).
|
|
|
|
|
- **H-A-61 (Q89 to Q92)** mesh-contracts' five modules are registered at the clean state's step 5.2 (P5). The whole
|
|
|
|
|
tests: the forge module's is a Go integration test running its bundle; the tool runner's `main` gains an entry; the
|
|
|
|
|
request-count assertion is H4's (with H-A-17). #708's description drops the words "config candidates" before it
|
|
|
|
|
merges (P8). Tests that use the checker's state as a fixture rename it to a state that stays (P7).
|
|
|
|
|
- **H-A-62 (Q68, for the operator)** Until H2, a version is released only for a registration's first watched branch, so
|
|
|
|
|
a placement on another branch gets no want and is said. Recommendation: accept for H1; H2 releases per branch. Asked
|
|
|
|
|
of the operator 2026-11-20 02:25 CET.
|
|
|
|
|