docs(ready): the ready gate's docs drop the second-look claim — describe the qa → loop → qa mechanism and its policy, cite #1344 for what was measured
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
- Domain
- documentation
Research direction
Read the Ready Gate sections in docs/features/run-ready-gate.md, docs/reference/ready-command.md, and docs/reference/run-command.md, plus founding doc §4 and issue #1344 for the cited measurement. Remove the seven second-look claims and old-anchor links, then describe the qa → loop → qa pass and its policy without claiming a catch rate. Verify the listed grep checks and keep changes within the allowed documentation and changelog files.
Written by the indexing model from the issue text.
Description
Epic: graph-2026-11-simplify Tier: mechanical Execution: sequant_run Blocked by: #1648 (both edit docs/reference/run-command.md)
- Blocked by: #1648
Problem
D-2: the ready gate keeps its loop and drops its second-look claim from the docs. The docs say the gate automates the maintainer's second look and that its value under the ac policy is "the fresh second look". On fixture #34 the gate's final verdict named +0.025 more planted defects than the first verdict, null by #1344's rule; what it did reliably was turn the first verdict's named catch into a fix commit (8 of 8 pairs). The n = 27 study the docs cite found 7 of 10 catches came after the human's "any gaps?", which the gate does not ask. Founding doc §4 lists the seven lines.
Acceptance Criteria
- AC-1: None of the seven claim lines remains. Evidence:
grep -cE 'automating the habitual|already automates exactly|value there is the \*\*fresh second look|reproduce the maintainer.s manual fresh-session|which .sequant ready. automates|post-QA second look' docs/features/run-ready-gate.md docs/reference/ready-command.md docs/reference/run-command.md | awk -F: '{s+=$2} END{print s}'→0 - AC-2: No link points at the old anchor. Evidence:
grep -rn 'ready-gate-post-qa-second-look' README.md docs | grep -v '^docs/internal/' | wc -l | tr -d ' '→0 - AC-3: The feature page says what the gate does and cites the measurement. Evidence:
grep -c '#1344' docs/features/run-ready-gate.md→≥ 1 - AC-4: No code or skill edits. Evidence:
git diff --name-only $(git merge-base origin/main HEAD)..HEAD | grep -vcE '^(docs/|CHANGELOG\.md$)'→0(constraint)
isGateTestEvidence classifies none of these ACs as a gate (parse-check, 2026-11-04).
May touch
docs/features/run-ready-gate.md, docs/reference/ready-command.md, docs/reference/run-command.md (the Ready Gate section and its heading only), CHANGELOG.
Non-Goals
- The gate's behaviour, flags or loop (D-2 keeps them).
docs/investigations/(dated records; left as written).- Skill text that mentions a second look (frozen).
Done when
The ready gate's docs describe a qa → loop → qa pass to a policy and claim no catch rate.
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 1
- Avg merge
- 11h 3m
- Merged PRs (30d)
- 84
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from sequant-io/sequant
-
run: --phases does not suppress the UI-label test phase (determinePhasesForIssue adds it to an explicit list)Possibly taken @admarble claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
sequant-io/sequant#1631 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
sequant-io/sequant#1601 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
sequant-io/sequant#1582 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 76/100
sequant-io/sequant#1381 ·
Maintainers usually reply within 1 day
-
improve(skills): /loop and /fullsolve run affected tests, not the full npm test (#1349 follow-up)Openenhancement
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
sequant-io/sequant#1360 ·
Maintainers usually reply within 1 day
All issues in sequant-io/sequant
Similar issues
-
content triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
tensorflow/tfjs#8754 ·
-
tool-submission
Difficulty 1/5 Under an hour Newbie friendliness 83/100
BraveOPotato/NoSignups#2348 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
code-yeongyu/oh-my-openagent#12784 ·
Maintainers usually reply within 1 day
-
external-issue to-triage
Difficulty 2/5 1-3 hours Newbie friendliness 71/100
Maintainers usually reply within 1 day