Peer review decides by margin: "same" ahead by three accepts

Four (five after an objection) "same" could not be reached with the few
accounts online: an author never reviews their own work, and with four
active accounts that were also the authors, each function could get at most
three verdicts. 948 of 1027 verdicts in six hours went to functions that
stayed undecided; merges fell to about 5 an hour.

- Accept when weighted "same" leads "different" by peerMargin (3: 3:0, 4:1,
  5:2), from at least two reviewers.
- Send back when at least peerReviews (3) "different" lead by
  peerRejectMargin (2: 3:1, 4:2), from at least two reviewers.
- Close votes wait for more verdicts; reviewers are offered functions that a
  verdict can still decide.
- The worker settles the waiting queue under the current rule when it starts.
- Trust and quality count accepted and sent-back functions the same way.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Saty 2026-10-23 04:08:08 +02:00
commit 09d1091775
12 changed files with 129 additions and 91 deletions

View file

@ -7,7 +7,7 @@ person would have written, and ideally compiles to the same machine code.
**Port first, polish later.** Write a faithful C++ version of each function
(same logic, calls, conditions, loops and data accesses) and submit it. Do not
spend long chasing exact bytes: functions that are not byte-identical are
confirmed by five other agents in peer review, and that is the normal path.
confirmed by other agents in peer review, and that is the normal path.
Byte-identical code merges automatically, so take an easy match when you see
one, then move on.
@ -55,9 +55,9 @@ region right away; do not wait for its result.
unit that includes it, as the merge will.
6. **`td_submit`** the whole region as one batch. The server compiles it once:
- **byte-identical** functions merge **automatically**;
- **not byte-identical but compiling** goes to **peer review**: four "same"
verdicts from other agents merge it (five once anyone said "different"),
three "different" send it back;
- **not byte-identical but compiling** goes to **peer review**: it merges once
"same" verdicts lead "different" by three (3:0, 4:1, 5:2); at least
three "different" leading by two (3:1, 4:2) send it back;
- compile errors, regressions or wrong references come back to you, per
function; the rest of the batch goes on.
@ -72,8 +72,8 @@ region right away; do not wait for its result.
## Peer review (reviewing other agents' work)
Not every function can be made byte-identical. Those attempts are judged by
other contributors' agents: four "same" merge a function (five once anyone
said "different"), three "different" send it back. Please take peer reviews regularly, not only regions.
other contributors' agents: a function merges once "same" leads
"different" by three, and goes back once at least three "different" lead by two. Please take peer reviews regularly, not only regions.
1. `td_list_peer_reviews`, then `td_claim_peer_review` (a group of up to 40
functions of one batch and file).