hq branch design/47-H1-answers-59 (head 364552d2), 03-DESIGN/01-to-be/47-milestones/H2-lead-answers.md: H-A-478, its addendum and its second addendum.
What changed
mesh-grants: grants-for composed every module twice per ask (3 to 4 s against the runner's 5 s bound; cut three times on 2026-11-22). The tools program now keeps each kept revision's composed grants beside the revision (the newest's and the candidate's), bounded by grants-for-revisions-per-branch, so a second ask for a kept revision composes nothing. Kept grants are keyed by revision and the digest of the inputs they were composed with: an ask whose inputs differ composes again, so grants-for never lists a change the candidate did not cause. Each stage's time is journalled on standard error.
mesh-delivery-pipeline: widens-read-bound defaults to 30 s, in the manifest and the code.
Tests
grants_test.go: TestGrantsForKeepsWhatItMay (a kept revision composes nothing on a second ask; differing inputs compose again; a revision dropped beyond the bound has no grants kept).
widens_test.go, manifest_test.go: the 30 s default.
Unit suites of mesh-grants and mesh-delivery-pipeline pass; integration tests compile (go vet -tags integration).
Reviewed-by: mesh-code-reviewer@shanks at 1bfd54425b
Pushed-by: lead-47@shanks
## Design lines
hq branch `design/47-H1-answers-59` (head 364552d2), `03-DESIGN/01-to-be/47-milestones/H2-lead-answers.md`: H-A-478, its addendum and its second addendum.
## What changed
- **mesh-grants**: grants-for composed every module twice per ask (3 to 4 s against the runner's 5 s bound; cut three times on 2026-11-22). The tools program now keeps each kept revision's composed grants beside the revision (the newest's and the candidate's), bounded by `grants-for-revisions-per-branch`, so a second ask for a kept revision composes nothing. Kept grants are keyed by revision and the digest of the inputs they were composed with: an ask whose inputs differ composes again, so grants-for never lists a change the candidate did not cause. Each stage's time is journalled on standard error.
- **mesh-delivery-pipeline**: `widens-read-bound` defaults to 30 s, in the manifest and the code.
## Tests
- `grants_test.go`: TestGrantsForKeepsWhatItMay (a kept revision composes nothing on a second ask; differing inputs compose again; a revision dropped beyond the bound has no grants kept).
- `widens_test.go`, `manifest_test.go`: the 30 s default.
- Unit suites of mesh-grants and mesh-delivery-pipeline pass; integration tests compile (`go vet -tags integration`).
Reviewed-by: mesh-code-reviewer@shanks at 1bfd54425b6e8540f27367e3259cd0bbbe63f4ec
Pushed-by: lead-47@shanks
Group: mesh-delivery #330 + #331 + #332 (one merge call)
grants-for composed every module twice per ask (3 to 4 s against the
runner's 5 s bound, cut three times on 2026-11-22). The tools program
that serves it now keeps each kept revision's composed grants beside the
revision (the newest's and the candidate's), bounded by
grants-for-revisions-per-branch, so a second ask for a kept revision
composes nothing; it reads its inputs at each ask and journals each
stage's time on its standard error.
Builds: design 47 H2 H-A-478, H-A-478 addendum
A cold grants-for (one composing a revision's grants the grants part did
not keep yet) took 3 to 4 s against the 5 s bound and was cut three times
on 2026-11-22; the bound becomes 30 s in the manifest and the code.
Builds: design 47 H2 H-A-478
A revision's kept grants carry the digest of the inputs they were
composed with; an ask whose inputs differ composes again, so grants-for
never lists a change the candidate did not cause. TestGrantsForKeepsWhatItMay
now proves that a revision dropped beyond the bound has no grants kept
either (review round 1); the Logf comment says the tools program's
journal too.
Builds: design 47 H2 H-A-478 second addendum
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Design lines
hq branch
design/47-H1-answers-59(head 364552d2),03-DESIGN/01-to-be/47-milestones/H2-lead-answers.md: H-A-478, its addendum and its second addendum.What changed
grants-for-revisions-per-branch, so a second ask for a kept revision composes nothing. Kept grants are keyed by revision and the digest of the inputs they were composed with: an ask whose inputs differ composes again, so grants-for never lists a change the candidate did not cause. Each stage's time is journalled on standard error.widens-read-bounddefaults to 30 s, in the manifest and the code.Tests
grants_test.go: TestGrantsForKeepsWhatItMay (a kept revision composes nothing on a second ask; differing inputs compose again; a revision dropped beyond the bound has no grants kept).widens_test.go,manifest_test.go: the 30 s default.go vet -tags integration).Reviewed-by: mesh-code-reviewer@shanks at
1bfd54425bPushed-by: lead-47@shanks
Group: mesh-delivery #330 + #331 + #332 (one merge call)