Repository navigation
docs(preallow): order the README by reader task, correct claims the code does not back, and write AGENTS.md as paragraphs - #18
Merged
Conversation
…e code does not back Installing comes first, then what the judge allows and what it leaves to native approval, the settings, what the judge reads, and how a judge decides, with its checks, model calls, verdict, and cache in one place. The log's `judged` fields get a list of their own instead of one sentence. Several statements said more than the code does. The message and input limits count JSON text, not raw characters. A parent's restatement of the task in a subagent's brief cannot supply the explicit words an irreversible effect needs. A file's modification time does not show who made it, the newest FETCH_HEAD does not date the fetch of the ref checked, and the cache is something calls can read, not one they always do. A judge that runs out of time answers review, which the second judge takes up, rather than sending the call to the classifier, and the gitleaks rule behind the `sourcegraph` false positive takes almost any 40-character hex string, not every one. The `/config` descriptions name the other settings by the titles shown beside them.
Each item was a paragraph of rules and their reasons, so the list markup added nothing an agent reads by. preallow's paragraphs now run from the ownership boundary through what reaches the judge, its policy, the user's words, facts, verdicts, and stages to output withholding; no rule, exception, or reason is dropped.
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
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.
The preallow README now opens with installing, then what the judge allows, what it leaves to native approval, the settings, what the judge reads, and how a judge decides, with its checks, model calls, verdict, and cache in one section. The
judgedlog fields get a list of their own instead of one long sentence.Several statements claimed more than the code does. The message and input limits count JSON text, not raw characters. A parent's restatement of the task in a subagent's brief cannot supply the explicit words an irreversible effect needs. A file's modification time does not show who made it, and the newest FETCH_HEAD does not date the fetch of the ref being checked. A judge that runs out of time answers review, which the second judge takes up, instead of sending the call to the classifier. Calls can read the cache, but do not always. The gitleaks rule behind the known
sourcegraphfalse positive has an entropy floor, so it takes almost any 40-character hex string, not every one. The code comments and the 0.0.9 CHANGELOG entry that repeated these claims are corrected too, and the/configdescriptions name the other settings by the titles shown beside them.Both AGENTS.md files are written as paragraphs instead of lists, with no rule, exception, or reason dropped; preallow's run from the ownership boundary to output withholding.
No behavior changes; the policy bullets in the README keep their wording, which follows
JUDGE_SYSTEM.