CLAUDE.md: no AI attribution, and the repo's working rules - #434
Closed
zcsizmadia wants to merge 1 commit into
Closed
zcsizmadia wants to merge 1 commit into
zcsizmadia wants to merge 1 commit into
Conversation
The no-attribution rule has been asked for twice -- after PR #181 on 2026-09-10, and again on 2026-09-19 after it recurred across nine PRs in a single session. It lived only in a per-user memory file, which the harness's own attribution reminder can talk over. CLAUDE.md is the place that reminder explicitly defers to, and it is in the repo rather than in one machine's profile. Also records what this release taught: a green test suite is not evidence a feature works. Three defects shipped in 0.6.0's window with passing tests that exercised a helper instead of the path the product takes -- a security rule that was a hardcoded no-op, an age guard applied only to a log line, and a tray item advertising a shipped feature as unreleased. So: write the test, revert the fix, watch it fail.
Collaborator
Author
|
Wrong home — this belongs in the user's profile so every Claude session honours it, not just work in this repo. |
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.
The no-attribution rule has been asked for twice — after #181 on 2026-09-10, and again today after it recurred across nine PRs in one session. It lived only in a per-user memory file, which the harness's own attribution reminder can talk over.
CLAUDE.mdis the file that reminder explicitly defers to, and it lives in the repo rather than in one machine's profile.Also records what this release taught about testing: three defects shipped in 0.6.0's window with passing tests that exercised a helper rather than the path the product takes —
deny-unattributable-buildsas a hardcoded no-op, the prune age guard applied only to a log line, and the tray advertising a shipped feature as unreleased. So the rule is: write the test, revert the fix, watch it fail.