Settle milestone H's last small points: the placement read, a verb's timeout, the enrolment event, the counts
Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
This commit is contained in:
@@ -33,7 +33,8 @@ main file, *Every delivery part wakes on its inputs alone*; §762 here says whic
|
||||
compare-and-set on a newer version, so an older end heard later writes nothing (G §352's state `written` keeps, per
|
||||
module and branch, the newest passed version). A want names a version, never a part's digest (A-430): A-436's
|
||||
stand-in ends, and G §379's digests go. The one exception is a return to an earlier build: the placement's value
|
||||
`build` (G §361), set through the seat `mesh-module-assigner`'s `propose` like any placement change, is read before
|
||||
`build` (G §361), set through the seat `mesh-module-assigner`'s `propose` like any placement change and read through that seat's verb
|
||||
`placement` (A-62), whose answer shows the `build` value beside the branch, is read before
|
||||
the rule and names the want's version (H-A-5; ADR 0682 §8). The want is held for nothing else. These holds end, with
|
||||
their states, findings and tools: the canary and the "at most `step` ahead" rule, every provider healthy, the grant
|
||||
exists (ADR 0429 §6), the served verb, the bus state (rule 8), the acting part's new version first (ADR 0656 §4; G
|
||||
@@ -148,7 +149,8 @@ main file, *Every delivery part wakes on its inputs alone*; §762 here says whic
|
||||
- the seat `mesh-grants`: `user-list-changed` on `mesh.seat.mesh-grants.event.user-list-changed`, body `{revision,
|
||||
users, at}`, consumed by the bus node's agent in place of its watch of the key `user-list`; first view its verb
|
||||
`user-list`;
|
||||
- the enrolment module: `enrolment-changed`, body `{node, state, at}` (its seat is question 1 below).
|
||||
- the enrolment module: `enrolment-changed`, body `{node, state, at}`; its seat and its first-view verb are read
|
||||
from the module's manifest at H4b's prepare, which writes them into this line.
|
||||
The grants part then consumes them, and calls the bus module only through the seat `mesh-broker`'s verbs (`list`,
|
||||
`show`, and `users` and `streams`, which the seat gains in place of the module tools `nats_users` and `nats_streams`
|
||||
the grants part calls today). Built in H4b. How it is checked: unit (the owners' seat definitions); whole (grants
|
||||
@@ -157,8 +159,9 @@ main file, *Every delivery part wakes on its inputs alone*; §762 here says whic
|
||||
gains the read verb `rates`, with `window` (seconds, default 10, from 1 to 60): it reads the bus server's counters of
|
||||
each connection and each stream twice, `window` apart, within the call, and answers per connection (its account's
|
||||
module and node) and per stream the messages and bytes in and out per second, and the slow consumers counted. Its call
|
||||
is bounded at `window` plus 5 seconds, at most 65 seconds, which must sit inside the tool runner's call timeout
|
||||
(question 2 below). Built in H4 (seat definition in mesh-contracts; the bus
|
||||
is bounded at `window` plus 5 seconds, at most 65 seconds. A verb's call timeout is a bound per verb in its seat
|
||||
definition, `timeout`, defaulting to the tool runner's own (principle 11); `rates` names 70 seconds, and the tool
|
||||
runner waits a verb's `timeout` when its definition names one. Built in H4 (seat definition in mesh-contracts; the bus
|
||||
module). How it is checked: whole (bus module): a fixture publishing 100 messages a second reads between 90 and 110.
|
||||
|
||||
### The read tools found missing
|
||||
@@ -189,8 +192,4 @@ main file, *Every delivery part wakes on its inputs alone*; §762 here says whic
|
||||
|
||||
### Questions this file leaves open
|
||||
|
||||
1. **The enrolment module's seat** for `enrolment-changed` and its first view (§773): no record or answer names it.
|
||||
Recommendation: the seat the enrolment module claims in its manifest, read by H4b's prepare and written here then.
|
||||
2. **The tool runner's call timeout for `rates`.** §760's call takes up to 65 seconds; no line says the tool runner's
|
||||
timeout per verb or whether a seat definition can raise it. Recommendation: a verb's definition names its bound and
|
||||
the tool runner waits that bound plus 5 seconds, a seat-definition field the H4 prepare checks exists.
|
||||
None: the enrolment event's seat and first-view verb (§773) are owed to H4b's prepare.
|
||||
|
||||
@@ -112,7 +112,9 @@ One file of milestone H's part of [design 47](../47-delivery-from-commit-to-deli
|
||||
| tool runner | 152, 7 | 1 that starts it whole (H-A-16's gap) | — |
|
||||
|
||||
Every module stays within 50 integration tests; acceptance tests 38, 49, 81, 82, 105 and 106 retire (§764). Before
|
||||
H1's merge its integration tests are run once locally against an embedded bus, and each pull request says so; the
|
||||
chain's live proof (the plan's section 5, step 7) is H1's check, and from H1 on the pipeline makes the check
|
||||
(H-A-16, a rule weighed and said). How it is checked: each pull request of H states its module's counts against the
|
||||
H1's merge its integration tests are run once locally against an embedded bus, as the mesh's instruction
|
||||
*how-work-is-done* allows, and each pull request says so; the chain's live proof (the plan's section 5, step 7) is
|
||||
H1's check, and from H1 on the pipeline makes the check (H-A-16, a rule weighed and said). The counts above are per
|
||||
module; the count per release and the number of tests each retired test frees are each milestone's prepare's, written
|
||||
in its milestone file. How it is checked: each pull request of H states its module's counts against the
|
||||
budget; the review refuses a count over it.
|
||||
|
||||
@@ -378,7 +378,8 @@ next:
|
||||
2. **Merge H1's set to main**, in this order, each reviewed: mesh-contracts #16 and mesh-sdk #200 (held), then
|
||||
mesh-catalog #708 and mesh-delivery #261 (held, mesh-config), mesh-tools #77 (held), and H1's own pull requests
|
||||
(indexer take-in, runner, gate, bridge, assigner, node-engine). mesh-delivery #262 is closed as superseded. The
|
||||
stopped runner starts nothing; the indexer takes the commits in and the gate follows.
|
||||
stopped runner starts nothing; the indexer takes the commits in and the gate follows, as the old programs still
|
||||
running during the freeze do. The new programs take every head in once, at the seed (step 5.9).
|
||||
3. **Build H1's programs from main** with the packs (the g-start phases, one per program), on shanks and novox as
|
||||
before, from main's head after step 2 so that main is what runs.
|
||||
4. **Take the stream snapshot that is the drop's rollback** (design 47 H §765) and test its restore; nothing is
|
||||
|
||||
Reference in New Issue
Block a user