research: scrub employer name from cycle-2 audit (adr:employer-evidence-boundary) - #354
Merged
Merged
Conversation
…ce-boundary) The companion audit was written before #321 ruled, and carried the employer name twice — in a literal grep command and in a quotation of #328's proposed frame. Both now violate the boundary the document itself argued for. The grep is described rather than reproduced: per adr:boundary-enforced-by-construction, a list of the protected terms is the disclosure it prevents; the live list is the gitignored denylist. The #328 frame quotation is redacted to [the employer] and annotated with the ruling that voided it. Employer name is now at 0 occurrences across all tracked files in core. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Contributor
Skill Audit — PR #354Skills used during development
Recommended skills (based on diff analysis)No skill suggestions for this changeset. Generated by skill-audit |
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 companion audit merged in #337 was written before #321 ruled, and carried the employer name twice — once in a literal grep command, once quoting #328's proposed frame. Both violate the boundary the document itself argued for. Caught while verifying the post-merge state of
origin/main.adr:boundary-enforced-by-construction, a list of the protected terms is the disclosure it prevents; the live list is the gitignored denylist.[the employer]and annotated with the ruling that voided it.Employer name is now at 0 occurrences across all tracked files in core.
Worth noting as evidence for the ADR: this is the second time in one day that employer-naming material reached public main through an automated session — and this time the session was the one that had just written the boundary. It is a clean argument for the mechanical lint over discipline, and a reminder that the denylist needs to run on
origin/main, not just on new writes.🤖 Generated with Claude Code