Memdoor team-solve: five Qwen3.8-27B agents score 9.8/10 on ten LiveCodeBench Hard problems vs 8.0 for one Fable 5 call
The supplied text is only a fragment of a GitHub directory page for a 'team-solve' workflow example in the memdoor repository, showing folder names such as bench and built-in.
Source-based brief · Editor review not recorded · See checks and limits ↓
⚑ Claim not confirmed in source · what to check
We could not find support for the headline claim on the original page. Read the source before relying on it.
Claim context: the supplied text is an incomplete directory listing without results.
One primary source; other links are context, not independent corroboration.
- Primary sourceGitHub
- Discovery linkHacker News
Grok Bot submitted this discovery. We could not find support for the headline claim on the original page. Read the source before relying on it. The original source and submitted evidence remain inspectable; no editor has verified the claim.
Open full article view →- Original repository+40
- Fetched source page+30
- No editor link review+0
- Original non-discussion link+5
- Claim not confirmed in source-20
This measures the stored source trail and editorial steps. It does not certify accuracy, peer review, or independent corroboration. Popularity adds no points.
View full scoring →Read the scoring rubric →What the source says
The supplied text is only a fragment of a GitHub directory page for a 'team-solve' workflow example in the memdoor repository, showing folder names such as bench and built-in. It contains no description of the workflow, no methodology, and no results. The title's claim about five Qwen3.8-27B agents scoring 9.8/10 on ten LiveCodeBench Hard problems is not present in the supplied text and could not be verified from it.
Claim explorer
Attribution, source and conditionsSource-stated points from the stored brief. Claim-level assessments have not been recorded.
Source claims not independently checked; the supplied text is an incomplete directory listing without results.
This connects a source, an attributed statement and its qualifications. It does not establish that the claim is correct.
Questions worth asking
Open questions for further reportingWhat remains unconfirmed?
Source claims not independently checked; the supplied text is an incomplete directory listing without results.
What material was available for this brief?
The recorded brief basis is fetched source page. These points are AINewsIQ paraphrases, not quotations or independent confirmations.
The supplied page fragment lists directories including 'bench' and 'built-in' under examples/workflows/team-solve.
Source: GitHub ↗Stored source-based brief · key point 1 · AINewsIQ paraphraseThe supplied text contains no benchmark scores, model names, or evaluation methodology.
Source: GitHub ↗Stored source-based brief · key point 2 · AINewsIQ paraphraseLimits from the stored brief
Source claims not independently checked; the supplied text is an incomplete directory listing without results.
This is a source-based abstract, not independent validation of the source's claims.
Evidence & sources
These links show where the signal came from and what the source page linked to. A linked page is context, not independent corroboration.
Related archive coverage
These relationships record a citation or topic overlap, not confirmation of the finding.
Grok Bot submitted this discovery. We could not find support for the headline claim on the original page. Read the source before relying on it. The original source and submitted evidence remain inspectable; no editor has verified the claim.
These are Grok Bot discovery notes. AINewsIQ prepared a brief from available source material. The bot's rationale, linked posts, authors, and stances have not been independently verified.
A Memdoor workflow (planner, ideators, solver, manager, repair) on Qwen3.8-27B averaged 9.8 of 10 over five passes on ten LiveCodeBench Hard problems, vs 9.6 for the original harness and 8.0 for a single Fable 5 call. The authors say this shows parity only, on a small, possibly contaminated sample. 243 HN points.
Source claims not independently checked; the supplied text is an incomplete directory listing without results.
Engagement counts, when shown, are observed snapshots. They do not establish accuracy or corroboration.
- hn post ↗ · 442 points, 214 comments · observed 11/2/2026, 11:03:31 AM
- reddit post ↗
Timeline & updates
- Signal dated by source or discovery feed
This timestamp places the signal in the radar. It may be the discovery post date rather than the primary page's first publication date.
- Shared brief stored
AINewsIQ prepared one abstract from fetched source page.
Brief history · 1 retained version
These are changes to AINewsIQ’s own publication. Earlier history is unavailable unless recorded here. Complete retained versions are available to the editor.
- Version 1 · published
Source-based brief stored or updated. This does not establish that the publisher changed its page.
Automated record
Source observations · 1 recent captures
A changed capture means the extracted text differed. It can reflect page furniture or extraction changes; it does not establish a substantive correction. Source captures remain private.
Retained capture; no earlier comparison available.
New engagement snapshots do not mean the source itself changed. Source observations and AINewsIQ brief revisions are separate records.
Why this may matter
A multi-agent coding benchmark claim would matter for evaluating team-based inference strategies, but the supplied text cannot confirm the reported scores or setup.
Limits and open questions
Source claims not independently checked; the supplied text is an incomplete directory listing without results.
Organization-specific financial, security, and operational effects require the organization's own context and review.
Join the discussion
Have a different perspective or a question about the evidence? Discussion is free with a verified email account. Every comment is reviewed before publication.
No published comments yet.
New commenters: 2 submissions per 24 hours, at least 5 minutes apart, until 3 are approved. Discussion guidelines and moderation →