Graduates research 086 into its designs (playbook 02): design 47 gains Pipelines per module (registrations, watched branches, steps and policy, what holds a delivery, approval as a step, merges through the seat git's merge-pull, groups, six kinds of edges between artifacts, a publish rebuilds, any size, the runner in the checker's place, callers per verb, health, tools, kept data, build capacity) and folds in milestone G as one milestone with one check; design 46 holds the fourth ask; design 51 numbers a package at publication (package-published on the seat mesh-builds); the glossary gains pipeline, pipeline step, policy, registration, watched branch, run on request, artifact reference, composition step, mesh-pipeline-runner, mesh-builds.
Decisions: ADR 0666 and ADR 0667 (proposed in the knowledge base, each waits for its review and the operator's Approve). Issue 1966 (milestone 47/G).
Review by architectural domain: three rounds, all four domains approve at 40661df (recorded in design 47's Reviewed by architectural domain).
Reviewed-by: review-security-and-upgrade, review-seams-and-tools, review-running-and-testing, review-health-and-events (fix-1965@shanks's reviewers) at 40661df5
Graduates research 086 into its designs (playbook 02): design 47 gains *Pipelines per module* (registrations, watched branches, steps and policy, what holds a delivery, approval as a step, merges through the seat `git`'s `merge-pull`, groups, six kinds of edges between artifacts, a publish rebuilds, any size, the runner in the checker's place, callers per verb, health, tools, kept data, build capacity) and folds in milestone G as one milestone with one check; design 46 holds the fourth ask; design 51 numbers a package at publication (`package-published` on the seat `mesh-builds`); the glossary gains pipeline, pipeline step, policy, registration, watched branch, run on request, artifact reference, composition step, `mesh-pipeline-runner`, `mesh-builds`.
Decisions: ADR 0666 and ADR 0667 (proposed in the knowledge base, each waits for its review and the operator's Approve). Issue 1966 (milestone 47/G).
Review by architectural domain: three rounds, all four domains approve at 40661df (recorded in design 47's *Reviewed by architectural domain*).
Reviewed-by: review-security-and-upgrade, review-seams-and-tools, review-running-and-testing, review-health-and-events (fix-1965@shanks's reviewers) at 40661df5
`go test ./...` at the root passes.
https://claude.ai/code/session_01JG73KK8HD1gufnqyFxMFdW
ADR 0666 and ADR 0667 decide that a change goes from a commit on a watched
branch to the machines through its module's pipeline, with no Approve per
merge and the checker gone, built and delivered as one milestone with
design 47's milestone G. The design now says how: registrations, the
catalog graph per watched branch, pipeline steps and their policy, a
session's own merge through merge-pull reading the head's latest run,
edges between artifacts, values of any size, the tools, the runner's kept
data and the build capacity, and the acceptance tests by level and
repository. Every section the pipelines replace keeps governing G's own
delivery and says so; the recovery merge points to its decision.
Claude-Session: https://claude.ai/code/session_01JG73KK8HD1gufnqyFxMFdW
ADR 0666 §6 has the operator-channel offer a fourth ask instead of refusing
it, never holding the newest back; design 46 now says which ask waits and
how it is offered again. ADR 0666 §9 numbers a package when it is
published and has that publication rebuild its dependents; design 51 now
says how the builder numbers it, says it on the seat mesh-builds, and who
asks a tagged version once the checker goes.
Claude-Session: https://claude.ai/code/session_01JG73KK8HD1gufnqyFxMFdW
Research 086's Domains section names the words its graduation adds and
changes; the designs now use them, so the glossary defines them in the
same set: pipeline, pipeline step, policy, registration, watched branch,
run on request, artifact reference, the seats mesh-pipeline-runner and
mesh-builds, the composition step and the build-input fingerprint, with
Homonyms rows for policy and step. The words that leave (merge check, try,
trunk commit, merge turn, composition check) keep their entries until
milestone G's delivery, since they govern it, and move to Not: lines with
the as-is update after it.
Claude-Session: https://claude.ai/code/session_01JG73KK8HD1gufnqyFxMFdW
The assigner's provider rule read the phase of the bus module's newer want,
so a yes not yet asked held every module asking bus state (issue 1966,
note 150); milestone G reads what runs. Also name the tracker of the
review-author stopgap.
Claude-Session: https://claude.ai/code/session_01JG73KK8HD1gufnqyFxMFdW
The four reviewers asked changes in every domain and fix-1965 ruled on each,
with ADR 0666 and ADR 0667's wording staged to match: foundation parts keep
old sections, merge-pull judges from its own state so a head merges while
the runner is down, a group's wants wait for group-ended, a failed head is
said to its author then the operator, the checker goes only after a first
end-to-end pipeline and a tested backup, and the stores are sized again for
publish rebuilds.
Claude-Session: https://claude.ai/code/session_01JG73KK8HD1gufnqyFxMFdW
Seams and tools and security and upgrade asked seven items, ruled by
fix-1965 with ADR 0666 and ADR 0667 staged to match: the assigner and
merge-pull switch on the first registrations, a branch that lost its
protection starts nothing, a passing rerun clears a failed step, sent
objects are read by a grant derived from the manifests, and the object
store is a small mesh-sdk package so nothing else rebuilds. The staged
record renumbered its clauses, so every citation of ADR 0666 follows the
new numbers.
Claude-Session: https://claude.ai/code/session_01JG73KK8HD1gufnqyFxMFdW
Seams and tools and security and upgrade approved with two fixes: only an
operator's or a healer's rerun clears a failed step for merge-pull, and a
fix before the first registrations is merged by the operator under the
trunk-only want. The review section now records all three rounds.
Claude-Session: https://claude.ai/code/session_01JG73KK8HD1gufnqyFxMFdW
Deliverynovox/hq@43eac215d264 — merged since 2026-11-10T07:20:48Z
Source — source.main moved to novox/hq@38915bbe01. Whether it reached the machines is mesh-delivery-view's, derived from source.main, the wants and the haves.
Transitions
2026-11-10 02:12 (new) → proposed (announced): novox/hq#532's head announced
2026-11-10 02:12 proposed → ready (accepted): a verdict names this commit and the trunk's head as its trunk commit, the gate passed or warned, and the repository's own check did not fail; or the check gates no merge (check-gates-merge false)
2026-11-10 07:20 ready → merged (merged): on the trunk its modules follow: merged there
The commit's note under refs/notes/mesh-plan keeps every transition of this change up to its merge: git log --notes=mesh-plan.
<!-- mesh-delivery:view -->
**Delivery** `novox/hq@43eac215d264` — **merged** since 2026-11-10T07:20:48Z
**Source** — source.main moved to novox/hq@38915bbe0174. Whether it reached the machines is `mesh-delivery-view`'s, derived from `source.main`, the wants and the haves.
**Transitions**
- 2026-11-10 02:12 (new) → proposed (announced): novox/hq#532's head announced
- 2026-11-10 02:12 proposed → ready (accepted): a verdict names this commit and the trunk's head as its trunk commit, the gate passed or warned, and the repository's own check did not fail; or the check gates no merge (check-gates-merge false)
- 2026-11-10 07:20 ready → merged (merged): on the trunk its modules follow: merged there
The commit's note under `refs/notes/mesh-plan` keeps every transition of this change up to its merge: `git log --notes=mesh-plan`.
mesh-delivery: the operator's Approve of this pull request's merge into main is ended: its head 40661df80f is no longer the pull request's head, or the pull request closed. Nothing is merged on it. The operator is asked again once the checks pass at the new head.
mesh-delivery: the operator's Approve of this pull request's merge into main is ended: its head 40661df80ff4 is no longer the pull request's head, or the pull request closed. Nothing is merged on it. The operator is asked again once the checks pass at the new head.
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.
Graduates research 086 into its designs (playbook 02): design 47 gains Pipelines per module (registrations, watched branches, steps and policy, what holds a delivery, approval as a step, merges through the seat
git'smerge-pull, groups, six kinds of edges between artifacts, a publish rebuilds, any size, the runner in the checker's place, callers per verb, health, tools, kept data, build capacity) and folds in milestone G as one milestone with one check; design 46 holds the fourth ask; design 51 numbers a package at publication (package-publishedon the seatmesh-builds); the glossary gains pipeline, pipeline step, policy, registration, watched branch, run on request, artifact reference, composition step,mesh-pipeline-runner,mesh-builds.Decisions: ADR 0666 and ADR 0667 (proposed in the knowledge base, each waits for its review and the operator's Approve). Issue 1966 (milestone 47/G).
Review by architectural domain: three rounds, all four domains approve at
40661df(recorded in design 47's Reviewed by architectural domain).Reviewed-by: review-security-and-upgrade, review-seams-and-tools, review-running-and-testing, review-health-and-events (fix-1965@shanks's reviewers) at 40661df5
go test ./...at the root passes.https://claude.ai/code/session_01JG73KK8HD1gufnqyFxMFdW
Delivery
novox/hq@43eac215d264— merged since 2026-11-10T07:20:48ZSource — source.main moved to novox/hq@38915bbe01. Whether it reached the machines is
mesh-delivery-view's, derived fromsource.main, the wants and the haves.Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition of this change up to its merge:git log --notes=mesh-plan.mesh-delivery: the operator's Approve of this pull request's merge into main is ended: its head
40661df80fis no longer the pull request's head, or the pull request closed. Nothing is merged on it. The operator is asked again once the checks pass at the new head.