docs(agents): explicit solo-maintainer rule#269
Merged
Conversation
Capture an invariant that has been silently shaping recent decisions but was nowhere written down: jackin has exactly one human contributor, and GitHub does not let a PR author approve their own pull request. The previous round of CI hardening (jackin-project/jackin-github-terraform#14) raised `required_approving_review_count` to 1 on the assumption a second reviewer was available — they are not — and the resulting trap needed a follow-up revert (#15). Add a 'Project staffing: solo maintainer' section at the top of AGENTS.md that names the constraint and the four downstream consequences: - Branch protection cannot require an approving review. - 'Get a second pair of eyes' is not available — pre-merge confidence comes from CI, the aggregator status checks, the strict up-to-date branch policy, and the agent following PULL_REQUESTS.md. - Multi-agent review (parallel code-reviewer / comment-analyzer / silent-failure-hunter passes) is the load-bearing substitute for the missing second human, not optional polish. - For irreversible or high-blast-radius changes, prefer asking the operator one more time over assuming green CI is sufficient. The rule retires when the project gains additional human reviewers. Signed-off-by: Alexey Zhokhov <alexey@zhokhov.com> Co-authored-by: Claude <noreply@anthropic.com>
donbeave
added a commit
that referenced
this pull request
May 18, 2026
Capture an invariant that has been silently shaping recent decisions but was nowhere written down: jackin has exactly one human contributor, and GitHub does not let a PR author approve their own pull request. The previous CI hardening round (jackin-project/jackin-github-terraform#14) raised `required_approving_review_count` to 1 on the assumption a second reviewer was available — they are not — and the resulting trap blocked every merge until it was reverted in jackin-project/jackin-github-terraform#15. Add a 'Project staffing: solo maintainer' section at the top of `AGENTS.md` naming the constraint and the four downstream consequences: branch protection cannot require an approving review; "get a second pair of eyes" is not an available pre-merge step (pre-merge confidence comes from CI, the path-aware aggregator status checks, the strict up-to-date branch policy, and the agent following PULL_REQUESTS.md); multi-agent review is the load-bearing substitute for the missing second human, not optional polish; and for irreversible or high-blast-radius changes the agent should prefer asking the operator to confirm one more time over assuming green CI is sufficient. The rule retires when the project gains additional human reviewers. Signed-off-by: Alexey Zhokhov <alexey@zhokhov.com> Co-authored-by: Claude <noreply@anthropic.com>
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.
Summary
Capture an invariant that has been shaping recent decisions but was nowhere written down: jackin has exactly one human contributor, and GitHub does not let a PR author approve their own pull request. The previous CI hardening round (jackin-project/jackin-github-terraform#14) raised
required_approving_review_countto 1 on the assumption a second reviewer was available — they are not — and the resulting trap needed a follow-up revert (jackin-project/jackin-github-terraform#15).Add a "Project staffing: solo maintainer" section at the top of
AGENTS.mdthat names the constraint and the four downstream consequences:PULL_REQUESTS.md.code-reviewer/comment-analyzer/silent-failure-hunter/ etc. passes) is the load-bearing substitute for the missing second human, not optional polish.The rule retires when the project gains additional human reviewers.
Verify locally
export TIRITH=0