chore(acdm): track repo-policy rules (data-protection, publish-readiness, internal-docs-boundary)#30
Merged
Merged
Conversation
…itignore) ACDM rule-distribution principle (PR #18/#20): repo-policy rules describe the repo / are read by repo-tooling and must travel with a clone / CI / contributor (ADR-015 "protection travels with the repo"). They were gitignored under a wholesale .claude/ ignore → not in the repo. Selectively un-ignore the three so they are tracked: - data-protection.md (PII / data-protection policy) - publish-readiness.md (read by /publish-check) - internal-docs-boundary.md (what belongs in the repo) Everything else under .claude/ stays gitignored — process rules, commands, hooks, acdm.json, .mcp.json, CLAUDE.md (local / path-sensitive config, verified via git check-ignore). No config or paths are exposed. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This was referenced Jun 24, 2026
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.
Brings question-forge into the ratified ACDM rule-distribution model (PR #18/#20).
What
The three repo-policy rules were gitignored under a wholesale
.claude/ignore, so they didn't travel with a clone. They describe the repo / are read by repo-tooling and must be present for contributors / CI / the published artifact (ADR-015 "protection travels with the repo"). This selectively un-ignores them so they are tracked:data-protection.md— PII / data-protection policypublish-readiness.md— read by/publish-checkinternal-docs-boundary.md— what belongs in the repoSafety (no config/path leak)
Everything else under
.claude/stays gitignored — process rules, commands, hooks,acdm.json,.mcp.json,CLAUDE.md(local / path-sensitive). Verified withgit check-ignore: the three rules are trackable; all config + the Nextcloudshared_rootpath inacdm.jsonremain ignored. Diff = 3 rule files + the.gitignorechange, nothing else.Note
data-protection.mduses ACDM's canonical "Treat As If Public" title; for a public repo "This Repo Is Public" reads slightly cleaner — a minor wording tweak we can make if preferred (the substance — hard rule, history-scrub, secrets, quasi-identifiers — is the point).Routing config (acdm.json → Nextcloud) is intentionally NOT committed — that's a separate, local-only concern (delspår A routing, doc-model).
🤖 Generated with Claude Code