Repository navigation
docs: development.md describes how the agent is built, not how it is sold - #84
Merged
Merged
Conversation
…sold The stability check was product validation in a testing document: a week-long comparison of two spool captures on a long-lived cluster, to decide whether a finding is stable enough to show. `docs/` ships with the Apache-2.0 repository, and its reader is looking for how the software is built and tested. `backend-requirements.md` justified the configuration fingerprint by naming that procedure; the obligation stands, its wording is now self-contained. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011YRKuL97KRndaopfpixrhp
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.
docs/ships with the Apache-2.0 repository. Its reader is looking for how thesoftware is built and tested, not for what we intend to sell.
development.md— removed the "stability check" bullet from Testingmethodology (added in docs: the stability check is a named procedure, not an intention #59): a week-long comparison of two spool captures on a
long-lived cluster, to decide whether a finding is stable enough to show. That
is product validation, and it was the only thing in the file that was not a
claim about the software.
backend-requirements.md— the configuration-fingerprint obligationjustified itself by naming that procedure. The obligation is unchanged; its
wording no longer points at something the repository does not define.
Evidence:
go test ./docs/...passes;grep -rn 'stability check' docs/ README.mdreturns nothing.
🤖 Generated with Claude Code
https://claude.ai/code/session_011YRKuL97KRndaopfpixrhp