Repository navigation
Plan: artifact events reach the job (pod release on merge, auto-fix on failing checks) - #122
Open
Evanfeenstra wants to merge 6 commits into
Open
Evanfeenstra wants to merge 6 commits into
Evanfeenstra wants to merge 6 commits into
Conversation
…ix on failing checks plans/job-artifact-events.md. An event about an artifact a job reported (first: a pull request merging, closing or failing its checks) becomes a turn on that job with a machine-written prompt, and the agent decides what it means for the pod it holds. One door for every kind of artifact: a kind-agnostic index of reported refs by URL, one `[artifact-event] <kind> <url> <what happened>` line; event sources and card actions are plug-ins. Hive's pool API takes a `?job=` claimant in the column it has. Strut changes nothing; jobs.md's header points at the plan.
…h notes found from control, a busy job queues the event on its index row for the settle handler, the launch as a service the webhook and the Fix route both call, check links, two pool-API one-liners
…low_run not check_suite, the Fix route under continue_job's owner rule, the hold note appended, the reason through both claim functions, the job id threaded to the PR viewer, the normalized URL and one slot per (job, ref); the settle wake kept and told its origin, with one entry at launch
…keyed on the workspace and the webhook's lookup scoped to it, a null claimant releasable (the pods claimed before the steps send a job), the launch-time entry as an assistant row with its own source kind the pending card accepts, hive items branch from master
This was referenced Oct 8, 2026
… hive#5447, hive#5448); the origin row after the dispatch, the job_busy requeue
…acked base, re-opened against master)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A plan only, no code:
plans/job-artifact-events.md, plus a four-line pointer inplans/jobs.md's status header.What it decides
[artifact-event] <kind> <url> <what happened>, specifics below. Event sources (the GitHub webhook) are adapters; card actions (the PR card's "Fix") are per-viewer prompt composers. Neither adds a seam.?job=claimant in theusage_status_marked_bycolumn it already has — no migration — and the drop path checks ownership, which closes a real hole: today a stale release can drop a pod hive has already handed to a task.POST /jobs/:id/events) is named as the later, fully generic door and not taken now.Work order is in §9: hive pool API → mcp pod steps + the
Podpage → hive's door → the Fix action.