Repository navigation
A 'no competitor has' claim, a four-row table, and a survey that stopped in June - #6817
Conversation
… evidence Narrow 'no competitor has' and 'unique position' claims to reference the four projects surveyed here, removing absolute claims that aren't supported by systematic survey evidence as required by POSITIONING_CONFORMANCE_LAYER.md. Closes #5399
A pull request must add exactly one docs/now entry and a bee has no way to know that: its brief names a boundary file and acceptance criteria, and docs/now/ is neither. The publisher adds it rather than failing the gate. Closes #5399 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
![t27-bees[bot]](https://avatars.githubusercontent.com/u/6774813?s=60&v=4){kind=small}
There was a problem hiding this comment.
Reviewer bee verdict for head 835eab36906a0c6204ad798b0430d9b5e1fd7dc6 (tools/bees/reviewer.py, zai glm-4.7-flash, 11 turns, 386 s; then glm-4.5-flash, 4 turns, 217 s).
BEE-VERDICT: APPROVE
summary: Narrowed both "no competitor has" and "unique position" claims to "of the four projects surveyed here" as required, all success criteria pass, and all 4 red checks are pre-existing master failures.
criterion: "FR-001: The change MUST narrow the line-5 and line-52 claims in docs/BITNET_STACK.md to what the ## Competitors table supports" -- met -- evidence: diff shows line 5 now says "of the four projects surveyed here" and line 52 says "position relative to the surveyed projects" with grep confirming all success criteria pass
criterion: "FR-002: The change MUST NOT add a new 'first', 'only', 'no competitor' or 'unique' claim anywhere in the file" -- met -- evidence: no new banned phrases added, "no competitor has" in NOW file is only in issue title description
criterion: "FR-003: The change MUST NOT add or modify non-t27 hand-written code (specs/policy/own_language.t27)" -- met -- evidence: only docs/BITNET_STACK.md and docs/now/*.md were modified, both are markdown documentation files
discounted-check: Corpus ratchet (expected-failure ledger) -- on master: master 595f474: cancelled (pre-existing failure per brief)
discounted-check: coverage -- on master: master 595f474: cancelled (pre-existing failure per brief)
discounted-check: duplicate-bodies -- on master: master 595f474: cancelled (pre-existing failure per brief)
discounted-check: scan -- on master: master 595f474: cancelled (pre-existing failure per brief; seal files with hardcoded paths were already on master before this PR)
Evidence
Based on my analysis, let me provide the evidence and verdict:
Analysis of Issue Requirements
FR-001 (narrow claims): MET - Lines 5 and 52 now say "of the four projects surveyed here" instead of "no competitor has" and "unique position". The four-row table remains unchanged.
FR-002 (no new banned claims): MET - The change only modifies two lines of text. The NOW file title contains "no competitor has" but only as part of describing what the issue was about, not as a new claim made by the PR.
FR-003 (no hand-written code changes): MET - Only docs/BITNET_STACK.md and the new docs/now/2026-10-06-published-a-no-competitor-has-claim-a-four-row-table-and-a-survey-that.md were changed. Neither is hand-written non-t27 code.
Success Criteria: All four verified by the runner:
grep -c 'no competitor has'prints0✓grep -c 'unique position'prints0✓grep -c 'of the four projects surveyed here'prints2✓grep -c 'Ternary-NanoCore'prints1✓
Red Checks Analysis
All four red checks show "on master: master 595f474: cancelled" in the brief, indicating they are pre-existing failures on master:
-
Corpus ratchet - MASTER FAILED (cancelled): This is a ledger/corpus count failure that any added spec could move. The brief states "This is a ledger or corpus count that any added spec moves and the change itself is sound."
-
duplicate-bodies - MASTER FAILED (cancelled): Same reasoning - pre-existing duplicate body count.
-
coverage - MASTER FAILED (cancelled): Same reasoning - pre-existing seal coverage issue.
-
scan - MASTER FAILED (cancelled): The failure shows hardcoded
/Users/playra/paths in seal files and.codex/hooks.json. These seal files are generated by the compiler and were already present on master before this PR; the PR does not introduce any new code or configuration that would cause these paths to be created. The failure is a pre-existing issue.
Conclusion: The change does exactly what issue #5399 asks - it narrows the two claims to what the four-row table supports, without adding any new banned phrases or modifying hand-written code. All success criteria pass, and no red checks were introduced by this head.
Second, independent review (glm-4.5-flash): APPROVE -- Successfully narrowed overbroad competitive claims to what the four-row table supports
t27-bees
Bot
added
the
bee-reviewed
2 participants
Closes #5399
Written by a bee on
queen-5399and published bytools/queen/publish.py. The branch itself is the bee's; the second commit is the coordination entry every pull request must add, which a bee has no way to know about.🤖 Generated with Claude Code