docs: describe the live review and merge paths - #124
Merged
Conversation
kim-em
force-pushed
the
docs/live-review-state
branch
from
August 26, 2026 02:11
e607a2b to
b979616
Compare
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.
This PR documents the review system's current production paths: contributors generate reviews locally, the newest current-head scoreboard supplies auto-merge's review verdict, and TauCetiData is the separate analytics/provenance archive. It also aligns the security model and internal workflow comments with the deliberate no-author-association scoreboard policy while preserving the narrower rules used when reusing an editable comment.
Tested with
python -m py_compile runner/*.pyand the full committed Python test suite.🤖 Prepared with OpenAI Codex