Generated from cat-harness/sdlc/processes/saturation-meta-merge.bpmn by gen-processes-viz.ts — do not edit here. All processes · cat-harness processes

Saturation meta-merge: land the ready PRs when the runners are full

Process_SaturationMetaMerge · strict (defaulted) · 8 step(s)

Landing a batch while the runners are full: cancel everything queued, pause new work, consolidate all ready PRs on one meta-merge branch, skip CI and rendering, and merge it, holding the swarm siblings until it is done. It repeats across repositories. Skill saturation-meta-merge holds the steps, the safety rules and the record of its first run. This process bypasses merge:guard on purpose, so the owner’s card, the PR body and a comment on each member PR are the record.

BPMN diagram: Saturation meta-merge: land the ready PRs when the runners are full

How it connects

Lanes — who acts

lanerolewhat it does here
Sibling sessionsibling-sessionEvery other session with a PR in the queue. It acts once: it stops pushing when the hold arrives and names the head it wants merged, so the steward stacks a branch nobody is still moving. It does not choose what lands; the owner does.
Merge stewardmerge-stewardThe merge manager, acting as merge steward for the duration of the drain. It notices the runners are saturated, holds the swarm, dry-runs the meta-merge and asks the owner with every PR named; on a yes it cancels the queued PR runs, builds and lands the meta-merge branch, releases the hold and reports. It never lands anything the owner’s card did not name.
OwneruserThe repository owner, the only lane that decides. A meta-merge lands PRs on main without their own CI, so the choice between the offered options is a person’s, made on a card that names each PR; a PR the card does not name gets no merge.
Build pipelinebuild-pipelineThe CI system, which runs main’s checks once on the merged result. Its verdict is what the steward reports; it is drawn as its own lane because it is a system acting on a fixed program, not a choice anybody makes.

Steps

Every one of the 8 step(s) is documented.

steplaneskill / sub-processwhat it does
Broadcast the hold to siblings
Task_Hold
Merge stewardmerge-manager-watcherMessage every sibling that pushes to the repositories involved: what is about to land, and hold pushes, merges and run cancels until done. Ask the coordinator to pass it on to any thread that cannot be reached.
Hold, and name the heads to merge
Task_SibHold
Sibling sessionsaturation-meta-mergeA sibling that owns a PR in the batch names the head it wants merged.
Dry-run, then ask the owner naming every PR
Task_Ask
Merge stewardask-the-personStack the PRs on a meta-merge branch without pushing. Then post the full question (include, leave out with the reason, merge method, per repository), followed by the card: A go, B also the red ones, C dry run only, D cancel.
Choose A, B, C or D
Task_Owner
Owner—Only the owner’s own tap or words approve the landing. A PR the card does not name gets no merge from it.
Cancel queued PR runs; build, push, merge
Task_Land
Merge stewardsaturation-meta-mergeNever cancel a main push run that has started. Build from fresh main with merge commits, skipping conflicts, .github/workflows/ and subscriptions/. Open one PR per repository, merge it with a merge commit, and comment on each member PR with the link.
Post done to every held sibling
Task_Done
Merge stewardmerge-manager-watcherPost done with what landed and what is still open, also when nothing was merged. A hold with no done is an outage.
Run main’s checks
Task_MainRun
Build pipeline—The merge starts main’s checks. Until tools#1384, a closed PR’s run can cancel them, so the steward re-runs a cancelled main run.
Report what landed and main’s verdict
Task_Report
Merge stewardmerge-to-mainOne message to the owner: what merged, main’s verdict per repository, and any open decision. On red, the fix goes to main as its own PR.

Decisions

1 of 2 decision(s) carry no documentation — gateway-documented lists them.

decisionwhat decides itbranches
Go?
Gw_Go
A or B is yes. C or D is no.Yes → Cancel queued PR runs; build, push, merge
No → Post done to every held sibling
Merged?
Gw_Merged
—Yes → Run main’s checks
No → Hold released, nothing merged

folio-assistant — code under the Apache License 2.0, documentation under CC BY 3.0. Generated schema and API references are rebuilt from source on every push to main.

deployed dev