Repository navigation
Open
Labels
area/infraInfrastructure, deployment, and operationsInfrastructure, deployment, and operationseffort/mMedium: expected under 1 day of workMedium: expected under 1 day of workkind/featureNew feature or capability requestNew feature or capability requestmeta/enrichedIntake review done: acceptance criteria, links, and normalized labels addedIntake review done: acceptance criteria, links, and normalized labels addedpriority/normalOrdinary priority (the default)Ordinary priority (the default)queue/queuedHas a queued task in the Supabase agent queueHas a queued task in the Supabase agent queuesource/creatorFiled by the new-issue-creator jobFiled by the new-issue-creator jobstatus/needs-triageNot yet triaged; needs a first lookNot yet triaged; needs a first looktask/triageQueue packet kind: verify, reproduce, and route this itemQueue packet kind: verify, reproduce, and route this item
Description
Work (Drew, 2026-10-27)
Pool changes proposed by pool-intelligence flags or the steward's
hunches don't land on vibes — they run a controlled test first. This
issue builds the standing mechanism:
- A test is a small batch of comparable real tasks (same kind/effort
class, drawn from the live queues) run on the candidate
configuration vs the incumbent, in the same window where possible.
Minimum viable batch: 3 tasks per arm for a directional read, 6 for
a config-change recommendation. - Measured per arm: completion, wall-clock, tokens (context-inclusive
input + output), stalls/nudges, rework within 48h (follow-up fixes
on the same issues). - The test harness is a documented procedure + a results template in
the goal workspace; runs are dispatched through the normal queues
with the route pinned by packet (the packet format already carries
routing intent), so tests cost no special infrastructure. - Verdicts are recorded on the flag's issue and in the interpretive
model doc; a passed test hands the steward a PR-ready change, a
failed one retires the flag with its numbers attached.
Acceptance criteria
- Procedure + template exist in the goal workspace.
- First controlled test executed end-to-end (two arms, real
tasks, verdict recorded) — candidate chosen from the first
pool-intelligence flag or the Pilot: Workhorse-first vs Frontier-plan split on comparable effort/m tasks (routing evidence) #1191 routing trial's leftovers. - Pilot: Workhorse-first vs Frontier-plan split on comparable effort/m tasks (routing evidence) #1191's trial results are folded in as the mechanism's first
historical dataset rather than re-run.
Child of the pool & routing intelligence epic. Filed by Muse
(operator) 2026-10-27.
Metadata
Metadata
Assignees
Labels
area/infraInfrastructure, deployment, and operationsInfrastructure, deployment, and operationseffort/mMedium: expected under 1 day of workMedium: expected under 1 day of workkind/featureNew feature or capability requestNew feature or capability requestmeta/enrichedIntake review done: acceptance criteria, links, and normalized labels addedIntake review done: acceptance criteria, links, and normalized labels addedpriority/normalOrdinary priority (the default)Ordinary priority (the default)queue/queuedHas a queued task in the Supabase agent queueHas a queued task in the Supabase agent queuesource/creatorFiled by the new-issue-creator jobFiled by the new-issue-creator jobstatus/needs-triageNot yet triaged; needs a first lookNot yet triaged; needs a first looktask/triageQueue packet kind: verify, reproduce, and route this itemQueue packet kind: verify, reproduce, and route this item
Activity
developing-today commentedon Oct 27, 2026
CODE-446
111 remaining items
dezren39 commentedon Nov 4, 2026
🤖 Agent note · handed off
dezren39 commentedon Nov 4, 2026
🤖 Agent note · handed off
dezren39 commentedon Nov 5, 2026
🤖 Agent note · handed off
dezren39 commentedon Nov 5, 2026
🤖 Agent note · handed off