Responsible human¶
CCB permits AI assistance and pull requests opened by automation. Contributors do not have to publish the tool, model, complete prompt, or conversation, but every pull request must name a real Responsible human.
Responsibilities¶
The Responsible human must:
- understand the purpose, implementation, and impact boundary;
- review the final diff, not only the generation process or summary;
- own the test results reported in the pull request;
- verify licenses and attribution for copied, adapted, or ported material;
- record verifiable external sources;
- answer review questions and follow the pull request through merge or closure.
AI output does not prove correctness and does not erase upstream licenses or authorship. If the change cannot be explained or its validation reproduced, investigate further rather than delegating responsibility to the tool.
Review and merge¶
One Responsible human is sufficient for CCB. LYHGLYTX is the currently
confirmed maintainer. A pull request authored by that maintainer does not need
a separate GitHub approval, so the target Ruleset keeps the required approval
count at zero and does not require approval from someone other than the last
pusher. Bots cannot replace the Responsible human or approve their own work.
Pull requests, required checks, resolved review conversations, and the bans on force-pushes and branch deletion remain target protections. Enable them only after the named checks are stable on the default branch and the administrator steps are complete. Automated merging remains disabled.
Bot-created drift pull requests are never auto-merged. A docs pull request must also be refreshed to the final source commit and revalidated after its source pull request merges.