docs(design): genericize target-repo references in success-semantics doc#56
Merged
Conversation
Keep loopy-loop's public design docs self-contained and general-purpose: replace project-specific references (a specific downstream consumer and a prospective `ugm_wp` workflow set) with generic "a target repo that owns a trustworthy contract-test suite" wording, and drop a cross-reference into the analysis notes. No substantive change to either decision. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PN8aFwwxA8FzMy9LgpbQFt
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
Small follow-up to #53. Keeps loopy-loop's public design docs self-contained and general-purpose by replacing project-specific references to a particular downstream consumer (and a prospective
ugm_wpworkflow set) with generic wording — "a target repo that owns a trustworthy contract-test suite" — and dropping a cross-reference into the analysis notes.No substantive change to either recorded decision; wording only.
Why
The design doc for a general-purpose tool reads better when it doesn't couple itself to one specific downstream project. (Both projects referenced are public, so this is a cleanliness/positioning change, not a privacy one.)
🤖 Generated with Claude Code
https://claude.ai/code/session_01PN8aFwwxA8FzMy9LgpbQFt