---
title: "fak issue dispatch status: fleet worker and backlog tracker"
description: "Auto-generated fak issue dispatch status: dispatcher and worker state, open-issue backlog by lane, and closure-honesty rate across the fleet."
---

# Issue dispatch status — 2026-06-29

_Auto-generated by `tools/dispatch_status.py --md`. Do not hand-edit; re-run the tool (or the `FleetDispatchStatusDoc` task) to refresh._

- **dispatcher**: `STALLED` (ok)
- **workers**: 0/2 live (headroom 2); host clean
- **switcher account**: `gem7-netra` (t1, opus), available=True
- **always-on watchdog**: installed (Ready)
- **supervisor**: `PLAN_SURFACE_EMPTY` (alive 0/0)
- **run status source**: `dos status` digests for 6 RID(s), errors=0

## Backlog by lane (issue → lane sync)

Open issues: **142** — routed 126, unrouted 16.

| lane | open issues |
|---|---|
| tools | 25 |
| docs | 22 |
| gateway | 9 |
| metrics | 7 |
| compute | 6 |
| ci | 5 |
| cmd | 5 |
| model | 5 |
| policy | 5 |
| sessionimage | 4 |
| agent | 3 |
| bench | 3 |
| engine | 3 |
| experiments | 3 |
| ggufload | 3 |
| scoreboard | 3 |
| claude | 2 |
| promptmmu | 2 |
| session | 2 |
| ctxplan | 1 |
| devindex | 1 |
| examples | 1 |
| kvmmu | 1 |
| metalgemm | 1 |
| modelroute | 1 |
| recall | 1 |
| swebench | 1 |
| vdso | 1 |

## Closure honesty

`closure_rate` = **0.8484** (TRUE_RESOLVED / (TRUE_RESOLVED + CLAIMED_CLOSED) — strict diff-witness); `honest_close_rate` = **0.8493** (also credits the DATA rung).

| bucket | count |
|---|---|
| TRUE_RESOLVED | 1024 |
| DATA_RESOLVED | 7 |
| CLAIMED_CLOSED | 183 |
| OPEN_WITNESSED (closable now) | 8 |

## Throughput (closed issues per hour)

`verdict` = **ON_TRACK** — **12.33/h** completed over the trailing **6h** window (target **10.0/h**). Graded on the *completed* (resolved, not wontfix/dup) rate.

| window | closed | completed | completed /h | loop-closed | loop /h |
|---|---|---|---|---|---|
| 1h | 4 | 4 | 4.0 | 2 | 2.0 |
| 3h | 13 | 13 | 4.33 | 6 | 2.0 |
| 6h | 74 | 74 | 12.33 | 26 | 4.33 |
| 12h | 148 | 148 | 12.33 | 74 | 6.17 |
| 24h | 229 | 229 | 9.54 | 119 | 4.96 |

Loop's last attributed close: 11.6 min ago. A gh-rate far above the loop-rate means humans/peers are draining the backlog, not the dispatcher.

## Backend health / reallocation

**1** backend(s) are spinning dead (a streak of banner-only / 0-byte worker logs the weekly-cap gate doesn't catch — e.g. a credit-walled codex or a glm worker that prints only its startup banner). The dispatcher holds their spawns and a healthy backend claims the freed lane + budget; one re-probe worker is admitted per interval, so each auto-restores the moment it produces a real turn again.

| backend | dead since | lane reallocated | re-probe (min) |
|---|---|---|---|
| opencode | 2026-06-30T00:27:31.521111Z | docs | 30 |

Backend stub-rate (recent resolve logs):

| backend | lookback | recent logs | productive | stub | stub rate | verdict | evidence |
|---|---:|---:|---:|---:|---:|---|---|
| opencode | 90m | 25 | 0 | 25 | 1.0 | **MAJORITY_STUB** | `resolve-1346-20260629-235906.log`, `resolve-1339-20260629-235857.log`, `resolve-1329-20260629-235849.log` |
| codex | 90m | 4 | 4 | 0 | 0.0 | ok | — |

## Hook health (guard-layer binding)

**1** backend(s) ran **UNHOOKED** by the guard layer over the recent window — every session logged `hook: <name> Failed`, so the fak guard hooks (PreToolUse / PostToolUse / Stop) never bound. `claude` binds the guard hooks natively; a non-claude backend (codex/opencode) runs its own native hook config, and when that config can't reach the dos hook CLI at runtime every lifecycle hook fails. Such a worker stays productive but runs unguarded by the hook backstop — the commit-path / `OFF_TRUNK` guard is what still holds the line (#1277).

| backend | lookback | sessions | sessions w/ hook fail | fail-session rate | hook failures | verdict | evidence |
|---|---:|---:|---:|---:|---:|---|---|
| codex | 90m | 3 | 3 | 1.0 | 452 | **UNHOOKED** | `resolve-10-20260630-041044.log`, `resolve-1199-20260630-041115.log`, `resolve-43-20260630-040939.log` |
| claude | 90m | 26 | 1 | 0.038 | 150 | ok | `resolve-26-20260630-035813.log` |

## Guard coverage (kernel decisions on the dispatch path)

`fak guard` recorded **673** kernel decision(s) across **24** guarded dispatch session(s) (**0** within 90m) — the WITNESS that the concurrent-dispatch path ran THROUGH the kernel, not just got configured to. Each session owns a unique hash-chained journal (`fak audit verify <file>`); the decision mix is the kernel's verdict tally.

- **denied** (DENY + RESULT_DENY): 4
- **quarantined**: 47
- **empty sessions** (booted under guard, no adjudicated tool call): 2

| decision kind | count |
|---|---:|
| DECIDE | 622 |
| QUARANTINE | 47 |
| DENY | 4 |

Recent journals: `sessionimage-claude-35732-11031111.jsonl`, `policy-claude-55308-8f2c7667.jsonl`, `cmd-claude-46072-e0af5ae5.jsonl`, `ci-claude-33728-1f0d8668.jsonl`, `docs-claude-1596-b44fb818.jsonl`.

## Workers that produced nothing

None — every spawned worker either produced output or is still running.

---

Reasons: account 'gem7-netra' weekly-capped — resets ? (holding spawn until 2026-06-30T05:29:07.741657Z); the t2 glm/docs pool is unaffected; always-on watchdog installed (Ready); 1 backend(s) held dead, lane reallocated (opencode->docs) — a healthy backend is covering; auto-restores on recovery; backend stub-rate majority-stub over recent logs (opencode 25/25 stub) — inspect backend output; guard hook layer UNBOUND on 1 backend(s) (codex 452 fail/3 sess (100%)) — productive but running unhooked; the commit-path/OFF_TRUNK guard is the backstop (#1277); fak guard witnessed 673 kernel decision(s) across 24 dispatch session(s) (4 denied, 47 quarantined); throughput ON_TRACK (12.33/h completed over the 6h analysis window, target 10.0/h); run truth from dos status digest for 6 RID(s)
