Optional second round: --revise shows every lane the locked round-1 answers - #65
Merged
Conversation
…nswers (#64) Round 1 stays blind by construction — the packet a lane receives is built from a finished run's transcript, so nothing can leak between live lanes. --revise accepts latest, latest:N, and comma-separated paths, merging the per-lane transcripts --each writes (an answer never loses to a later failure of the same lane) and refusing to mix differing briefs. Each lane sees its own answer marked YOURS and peers anonymised as PANELIST letters — attribution invites the authority-weighting the instructions forbid — and must open HOLD or REVISE with a stated reason. The report banners the round as persuasion rather than independent convergence and tallies who moved; the transcript records round, parents, and the alias map so anonymity is auditable. Calibration is skipped on revision rounds because per-lane packets differ in length. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VmauK5UCYGRYyXoQ36FQ3S
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Team Run ID: Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
…st live use Retrying one failed lane of a revision round with latest:N swept in the siblings' round-2 transcripts. The brief guard cannot catch that — a revision round records the same brief — and the merge would hand the lane its peers' round-2 answers labelled as the round it is trying to redo. Transcripts spanning different rounds now refuse, naming the rounds; retry with the files of one round listed explicitly. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VmauK5UCYGRYyXoQ36FQ3S
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VmauK5UCYGRYyXoQ36FQ3S
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #64.
CJ's ask: a way for the roundtable lanes to have access to each other's answers — with round 1 staying isolated and the second round strictly optional.
What this does
--revise TRANSCRIPTreruns the panel with each lane shown the locked prior answers. Its own is markedYOURS; peers are anonymised asPANELIST A/B/C(attribution invites exactly the authority-weighting the instructions forbid). Lanes must openHOLDorREVISEand move only for a reason they can state.latest,latest:N, and comma-separated paths, and merges them —--eachwrites one transcript per lane, so "the previous round" of a 12-lane run is 12 files. Refuses to mix transcripts whose briefs differ (that is only ever an accident). An answer never loses to a later failure of the same lane.latestresolves to concrete paths in the parent before--eachfans out — a child resolving it for itself would pick up a sibling's round-2 transcript, the exact self-echo this feature must not create.round, parent paths, and the alias map, so anonymity is auditable. Round 3+ works by pointing--reviseat a round-2 transcript.Verification
--reviseagainst the stub server asserting the packet reaches the wire and the banner reaches the report)../roundtable --list— zero network calls, correct routes.🤖 Generated with Claude Code
https://claude.ai/code/session_01VmauK5UCYGRYyXoQ36FQ3S
Proudly Made in Nebraska. Go Big Red! 🌽 https://xkcd.com/2347/