Verifier revisions discard finding provenance
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 52/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- backend
Research direction
Read the listed locations in src/pipeline/verifier.ts, src/llm/verifier-revision.ts, and src/pipeline/composer.ts to trace how revisions affect provenance and representative selection. The issue suggests forwarding trusted metadata or removing the dormant branch; clarify which behavior is intended before changing code. Done means revised promoted findings retain the intended provenance, or the unused branch is removed consistently.
Written by the indexing model from the issue text.
Description
Problem: Revised findings do not copy provenance. Since every surviving promoted candidate is revised, isPromotedFinding becomes false for all verified promoted findings and the promoted branch of representative selection only runs when verification is disabled.
File:line: src/pipeline/verifier.ts:1284-1301,504-513; src/llm/verifier-revision.ts:32-37; src/pipeline/composer.ts:2059-2074.
Evidence: Code reading by @architect; @lead-dev confirmed revision loses provenance.
Suggested fix size: S (forward trusted metadata) or delete the dormant branch.
Found during #44 (workstream A, challenged by @lead-dev).
- Dominant language
- TypeScript
- Stars
- 8
- Forks
- 1
- Avg merge
- 5m
- Merged PRs (30d)
- 2
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 0xPolygon/codegenie
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
All issues in 0xPolygon/codegenie
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
feature request needs triage
Difficulty 1/5 1-3 hours Newbie friendliness 69/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/symphony#91 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
solidjs/solid-docs#1716 ·
Maintainers usually reply within 1 day