Skip to content

docs: don't leak private consumers in this public repo - #11

Merged
wavekat-eason merged 1 commit into
mainfrom
docs/private-consumer-guidance
May 16, 2026
Merged

docs: don't leak private consumers in this public repo#11
wavekat-eason merged 1 commit into
mainfrom
docs/private-consumer-guidance

Conversation

@wavekat-eason

@wavekat-eason wavekat-eason commented May 16, 2026

Copy link
Copy Markdown
Contributor

Summary

Adds explicit guidance to CLAUDE.md so future contributions (Claude-authored or otherwise) inherit it: this repo is open source, it has private/closed-source downstream consumers in the WaveKat ecosystem, and cross-references to those private repos need redaction in code, docs, commit messages, and PR text.

Why

There was a real gap — an earlier PR in this repo included identifying details about a private downstream consumer in its description and commit body. The links 404 for anyone outside the org, but the existence and internal layout of the private code became public. Codifying the rule in CLAUDE.md prevents the same leak from sneaking into future commits.

What's in scope

  • Don't name private repos by GitHub path or link to them
  • Don't paste their file paths into commit messages / PR bodies / doc comments / // see ... annotations
  • Don't frame a feature as "for product X's Y page" — frame it for an unknown consumer
  • Do keep generic ecosystem framing ("the WaveKat voice pipeline," "downstream consumers")
  • Do name the open-source sibling crates freely (wavekat-core, wavekat-sip, etc.)

Test plan

  • Documentation-only change; no code paths touched.
  • cargo fmt --check and cargo doc --no-deps -p wavekat-asr --all-features still pass (unchanged from main).

Follow-up

The earlier PR still has leaks in its description and commit body. Once this lands I'll send a follow-up to redact those.

🤖 Generated with Claude Code

Adds explicit guidance to CLAUDE.md (so future AI-assisted contributions
inherit it) that wavekat-asr is open source and has private/closed-source
downstream consumers in the WaveKat ecosystem. Commit messages, PR bodies,
doc comments, and `// see ...` annotations in this repo must not name
private repos by their GitHub paths, link to them, or paste their internal
file paths. Frame features for an unknown consumer instead.

Generic ecosystem framing ("the WaveKat voice pipeline," "downstream
consumers") and the other open-source sibling crates are fine to name.
Only the private repos need redaction.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@wavekat-eason
wavekat-eason force-pushed the docs/private-consumer-guidance branch from af8dc1b to df3b22c Compare May 16, 2026 23:18
@wavekat-eason
wavekat-eason merged commit 02fc5d7 into main May 16, 2026
3 checks passed
@wavekat-eason
wavekat-eason deleted the docs/private-consumer-guidance branch May 16, 2026 23:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant