Skip to content

Measure delivery, not dispatch - #4325

Merged
gHashTag merged 1 commit into
masterfrom
fix/measure-delivery
Sep 20, 2026
Merged

gHashTag merged 1 commit into
masterfrom
fix/measure-delivery

Conversation

@gHashTag

Copy link
Copy Markdown
Owner

Closes #4324

nothing-lands counted every merged pull request in the repository, so one
operator merge suppressed it
. Measured today: 17 merged in 24 hours, 0 from
a bee
, while twenty bees ran at 90% utilisation and every instrument reported
a healthy swarm.

And nothing watched the case that actually happened — work that never reaches a
pull request at all. 401 queen-* branches, last bee PR three days old, and no
rule could see it: every number in this file was about dispatch, none about
delivery.

rule fires when
nothing-lands (fixed) no bee pull request merged in 6h while bee PRs are open — prints the repository total beside it
nothing-published (new) bees running, no bee PR open, none merged in 6h
$ python3 tools/queen/pusher.py --self-test
ok: 27 rule shapes, including ten a moving system must NOT fire

Live while writing this — the same reading also caught the next bottleneck:

"bee_merged_last_6h": 1
STOPPED: 2 of 20 lanes are empty while about 12 issue(s) are dispatchable.
STOPPED: About 12 dispatchable issue(s) for 20 lanes ... (122 carry a boundary, 67 claimed, 43 completed)
STOPPED: 67 issues are held by attempts that are not running.
ACTED: `queen-feed-untested.yml` would be dispatched (dry run)

🤖 Generated with Claude Code

`nothing-lands` counted every merged pull request in the repository, so one
operator merge suppressed it. Measured 2026-09-20: seventeen merged in
twenty-four hours, none from a bee, while twenty bees ran at ninety percent
utilisation and every instrument reported health. It now counts only `queen-*`
branches and prints the repository total beside it.

`nothing-published` is new: bees running, no bee pull request open, none merged
in six hours. That is the exact shape of what happened - 401 branches on the
remote, nothing opening a pull request - and no rule could see it, because
every number in this file was about dispatch and none about delivery.

Both report-only; the repair is tools/queen/publish.py.

Twenty-seven rule shapes, ten of them ones a moving system must NOT fire,
including a swarm whose work lands.

Closes #4324

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@gHashTag
gHashTag enabled auto-merge (squash) September 20, 2026 12:07
@github-actions

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-09-20 12:14:47 UTC

Summary

Status Count
Total Open PRs 22
PRs with Failing Checks 18
PRs with All Checks Green 4
READY 2
FAILING 18
PENDING 0
NO CHECKS YET 0

These columns do not partition: 2 + 18 + 0 + 0 = 20, and there are 22 open PRs. A PR is being counted twice or not at all.

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=403499176a5d != manifest seal=87e5cbd3ad94.
    The committed NMSE numbers were certified against an older compiler.rs.
    Run scripts/reseal-check.sh locally for the two-step reseal command (advisory; not a merge gate).

@gHashTag
gHashTag merged commit 2bdcf0c into master Sep 20, 2026
32 of 34 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

📓 NotebookLM Notebook linked to this PR

This notebook contains session context, decisions, and artifacts for this work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

The watchman counts dispatches and never counted deliveries

2 participants