Expert streaming: the declared token gate G0-CORRECT still FAILS on a shipped FEATURES.md row (replaces dead #1299)
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 423
- Forks
- 53
- Avg merge
- 20h 26m
- Merged PRs (30d)
- 310
Description
Row: ENG-EXPERT-STREAM-DEVICE
Replaces dead #1299, cited on docs/FEATURES.md:67 for the words
"staging device DECODES, token gate FAILS". #1299 no longer resolves. It is
re-filed rather than dropped because the claim it supported is still true,
and it is the correctness gate on a shipped feature row.
What is still true
.agents/specs/expert-stream-device-slots.md:372 records the gate's own state:
G0-CORRECT | FAIL, and it now has a CUDA side to fail on. ... the two
arms already select different EXPERTS in the FIRST MoE block of the FIRST
forward, eight tokens before any emitted token differs, so the near-tie is the
symptom. ... WHAT the cause is remains open under## Owed.
and :174:
G0-CORRECT: FAIL as declared. This bullet read the failure as a near-tie,
So: the staging device decodes, and the declared token gate fails. Both halves of
the FEATURES.md cell are accurate; only its evidence link was unreachable.
Why it needed re-filing rather than delinking
gh issue list --state open --search "G0-CORRECT" and --search "expert stream"
return no open issue tracking this failing gate (checked 2026-09-03; the nearest,
#2824, replaces dead #1124 and owns the ExpertSlotStore virtual-read seam, not
the gate). A shipped feature row that advertises a FAILING correctness gate, with
no reachable evidence and no open tracker, is the worst of the three states
#2825 describes: accurate and unverifiable at the same time.
Scope
This issue owns the citation, not the repair. The cause is open under
.agents/specs/expert-stream-device-slots.md ## Owed, which this row already
carries. Closing it needs G0-CORRECT to pass, or the FEATURES.md row to stop
claiming the capability.
Related
- #2825 -- the 107-of-157 dead-citation measurement on
docs/FEATURES.md - #2824 -- the same re-filing shape, for dead #1124
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with docs/FEATURES.md:67 and the G0-CORRECT entries at .agents/specs/expert-stream-device-slots.md:174 and :372, then read its ## Owed section. Confirm the declared gate and its evidence path before investigating the failing first-forward expert selection. Done means G0-CORRECT passes or the FEATURES.md row no longer claims the capability.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- documentation, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100