docs: add Development provenance section to README - #27
Merged
Conversation
Discloses the AI-assisted, agentic development workflow used on this project up front, near the top of the README rather than buried in CONTRIBUTING.md or left implicit. Points to the Co-Authored-By trailers already present throughout the git history as where that involvement is visible, rather than asserting it abstractly. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
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.
What
Adds a "Development provenance" section to README.md, placed right after the existing security
caveat and before "How it works" — early enough that it's one of the first things a reader sees,
per the maintainer's explicit request.
Why
The maintainer wanted this disclosed up front rather than left implicit or buried in
CONTRIBUTING.md: ContainerBin's implementation and review make extensive use of coding agents,
coordinated by the maintainer, who owns requirements, design, acceptance testing, and releases.
The section points to the
Co-Authored-Bytrailers already present throughout the git historyas where that involvement is concretely visible, rather than just asserting it.
Docs-only change, one file.
🤖 Generated with Claude Code