Skip to content

textleaks: replace stock phrase in writing #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
creatornader merged 1 commit into from
May 29, 2026
Merged

textleaks: replace stock phrase in writing #2

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/leak-classes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -64,7 +64,7 @@ Each class below: what it is, why it leaks, an example, and the prevention rule

**What it catches**: timestamps like "3:23 AM," day-relative words like "today" / "tonight" / "yesterday."

**Why it leaks**: late-night operator work makes timestamps load-bearing for distinguishing decisions. Day-relative words reveal the writer's frame of reference is the operator's calendar, not the project's history.
**Why it leaks**: late-night operator work makes timestamps decision-critical for distinguishing decisions. Day-relative words reveal the writer's frame of reference is the operator's calendar, not the project's history.

**False positives**: legitimate technical uses ("today's typical client," "the next session of the protocol") will trip the patterns. Override on a case-by-case basis.

Expand All @@ -74,7 +74,7 @@ Each class below: what it is, why it leaks, an example, and the prevention rule

**What it catches**: "the user pushed back," "the user said X" framings.

**Why it leaks**: ADR prose treats the operator's interventions as load-bearing decision context. They are, but in operator-private docs.
**Why it leaks**: ADR prose treats the operator's interventions as decision-critical decision context. They are, but in operator-private docs.

**Prevention**: present decisions on their own merits. "Direction was to ship the corpus immediately" not "the user pushed for shipping the corpus immediately."

Expand Down