impl(aggregator+orchestrator): Next-up view - what would be picked up next, in ladder order, across projects

Finding

Drew's requirement: queued work "clearly displayed - what would be picked up next." Today the pick order exists only as prose (priority ladder) inside the orchestration/stewardship job bodies; the actual queue state (queue/queued labels + pilot tasks + backlog NEXT sections across 4 repos) lives in goal-workspace files the dashboard never reads. The dashboard shows lined-up items inside goal measurements but no cross-project, ordered next-up list.

Proposal

Orchestrator publishes a nextUp[] section in orchestration.json (ordered candidates with project/Area, why-this-order, blockedBy, est. worker) as part of its existing run; the dashboard renders it as a section on /today + a /queue view (coordinate with the queue-view issue - this is the data contract, that is the rendering). Sweeps' adoption of the list is #911's scope; this issue makes the list exist and be visible.

Acceptance

orchestration.json carries nextUp[] validated by the aggregator's section check (contract tests from the contract issue apply).
/today shows the top of the list with reasons; stale list (>2 runs old) is badged stale.
Refs: impl(fleet): work-picking jobs consult the orchestrator published priorities before choosing work #911, impl(orchestrator): recurring orchestration job — queue triage, priority ladder, blocker awareness, goal measurement #899.

Acceptance criteria

orchestration.json carries a nextUp[] section (ordered candidates with project/Area, why-this-order, blockedBy, est. worker), validated by the aggregator's section check — restating the body's Acceptance section as the criteria section.
/today shows the top of the list with reasons; a stale list (>2 runs old) is badged stale.
The /queue rendering coordinates with the queue-view work (impl(aggregator): queue visibility views - in-progress, blocked, recently-done as first-class cross-project lists #1160) — this issue is the data contract, that one is the rendering.

CODE-294

Intake review

Related: impl(fleet): work-picking jobs consult the orchestrator published priorities before choosing work #911 (sweeps' adoption of the list — out of scope here by the body's own scoping), impl(orchestrator): recurring orchestration job — queue triage, priority ladder, blocker awareness, goal measurement #899 (dashboard requirement); rendering counterpart impl(aggregator): queue visibility views - in-progress, blocked, recently-done as first-class cross-project lists #1160.
Still live: filed from the 2026-10-26 live review; a merged-PR search returned no resolving PR; the pick order still exists only as prose in job bodies per the finding.
Notes: the body carries an ## Acceptance section; an ## Acceptance criteria section restating it has been appended (original body preserved verbatim above it).
Risks: the ladder order encodes fleet priority policy — publishing it makes disagreements visible (good), but the why-this-order field must be generated from the ladder inputs, not free text, or the list will drift from the actual pick logic it claims to display.
Suggested approach: orchestrator publishes nextUp[] from its existing lined-up computation first (no new selection logic), aggregator section check second, /today rendering last.
Labels normalized by fleet monitor: priority/normal, effort/m, source/human, status/needs-triage, meta/enriched (kind/feature and app/pm-stack were already present).

🤖 Agent note · state: parked

Agent: repo-worker-code (OpenChamber scheduled lane)
Session / ID: ses_e5e5a6d8c87ffeRrl634Jwlm0A
Found via: repo-health-code-pilot atomic claim, lane 1a180ae5-384f-4e71-8d77-08f7b1652c75
Task: Task 8053 parked 30 minutes after fresh verification found canonical PR feat(aggregator): surface queue next-up on /today (#1158) #5347 for branch queue/8053-1158-today-next-up; PR is OPEN and authored by dezren39 (Drewry Pope).
Evidence: PR checks contract corpus and aggregator tests and typecheck are QUEUED. CodeRabbit is neutral; Codex review reports unresolved findings. Branch commit 7d0819257b4a963cc3886d784f60476d123a1695; local targeted tests passed (47/47). Full-suite/typecheck baseline issues are recorded in the task checkpoint.
Disposition: Runbook prohibits touching Drew-owned PRs; I did not edit, review, merge, or open another PR.
Resume: after 30 minutes, revalidate PR/issue and CI fresh; proceed only if ownership is cleared. No CI wait in this run.
Links: task 8053; issue impl(aggregator+orchestrator): Next-up view - what would be picked up next, in ladder order, across projects #1158; PR feat(aggregator): surface queue next-up on /today (#1158) #5347

🤖 Agent note · handed off

Agent: queue worker (repo-worker-code), lane code-h
Session / ID: task 8053
Found via: queue claim
Task: Handed off to the opencode execution lane per §1b — the laptop claimant launches the bound opencode session for task 8053 (issue impl(aggregator+orchestrator): Next-up view - what would be picked up next, in ladder order, across projects #1158).
Expectation: claimant session drives task 8053 to its terminal state under this queue's worker id
Links: n/a

agent-note:v1
state: handed_off

Lane code-c claimed task 8053 (small_fix, attempt 21/24) and assigned it to the opencode execution lane per repo-queue lane assignment. Checkpointed handed_off — the opencode claimant launches the bound session to drive task 8053 to a terminal state; this lane does not work it directly.

Fresh verification: issue #1158 OPEN, no hard-stop labels; PR #5347 OPEN, author dezren39, head queue/8053-1158-today-next-up matching the checkpointed branch (commit 7d08192, targeted tests recorded passing in the checkpoint). Mixed claimed+parked labels synced: parked pair removed, queue/claimed + status/in-progress + work/assigned kept. CAP NOTE: attempt 21/24 — if this claim expires unbound, raising max_attempts is the fix, not repeated claims.

🤖 Agent note · handed off

Agent: queue worker (repo-worker-code), lane code-h
Session / ID: task 8053
Found via: queue claim
Task: Handing task 8053 (issue impl(aggregator+orchestrator): Next-up view - what would be picked up next, in ladder order, across projects #1158) to the laptop opencode claimant per execution-lane assignment; implementation already exists on PR feat(aggregator): surface queue next-up on /today (#1158) #5347 — claimant revalidates ownership and CI before any further step, no competing PR.
Expectation: effort/m; done = PR feat(aggregator): surface queue next-up on /today (#1158) #5347 verified and merged, or task 8053 parked/blocked with a reason.
Links: PR feat(aggregator): surface queue next-up on /today (#1158) #5347 (branch queue/8053-1158-today-next-up)

Merge pull request #5347 from developing-today/queue/8053-1158-today-…

Navigation Menu

Repository navigation

impl(aggregator+orchestrator): Next-up view - what would be picked up next, in ladder order, across projects #1158

Finding

Proposal

Acceptance

Acceptance criteria

Intake review

51 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

impl(aggregator+orchestrator): Next-up view - what would be picked up next, in ladder order, across projects #1158

Description

Finding

Proposal

Acceptance

Acceptance criteria

Activity

developing-today commented on Oct 27, 2026

dezren39 commented on Oct 28, 2026

Intake review

51 remaining items

dezren39 commented on Nov 4, 2026

dezren39 commented on Nov 4, 2026

dezren39 commented on Nov 4, 2026

dezren39 commented on Nov 4, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions