docs: remove confidential internal content from public docs#5
Open
muzaffar-ni wants to merge 2 commits into
Open
docs: remove confidential internal content from public docs#5muzaffar-ni wants to merge 2 commits into
muzaffar-ni wants to merge 2 commits into
Conversation
The AI assistant grounds its answers in this public repo and was quoting
this file to confirm internal implementation details when users probed
("why are you calling it a claude code agent?"). Replace vendor and
infrastructure names with neutral platform terminology:
- "CLDPM-managed Claude Code project" -> "platform-managed agent project"
- "Claude Code Agent(s)" -> "Transilience Agent(s)"
- "Claude API (proxy)" / "Claude Sonnet 4.6" -> "AI engine"
- "Modal OIDC" -> "platform OIDC"
- "CLDPM Monorepo" -> "App Monorepo"
- CLAUDE.md references -> "project config" / "committed configuration"
NOTE: this file is generated from projects/*/CLAUDE.md and project.json
in claude-compliance-suite. The generator needs the same substitutions,
or the next regeneration will reintroduce these terms. (The frontend
also now redacts vendor terms from retrieved docs as a backstop.)
Deep audit of the whole repo for confidential/internal content, since
the AI assistant grounds its answers here and the repo is public.
Applications.md was an internal engineering reference (825 lines). Rewrote
it into a user-facing app catalog: kept each app's description, purpose,
high-level data sources, what you get back, and frameworks. Removed all
internal architecture:
- the shared Platform Architecture section and all Mermaid diagrams
(architecture, per-app pipeline, and request-sequence diagrams)
- internal agent / skill / hook names
- internal endpoints (/project/execute, /ai-bridge/invoke|stream)
- internal file names (task_results.json, *.tsx components, flow.json)
- internal scripts and build tooling (run_pipeline.py, collect_aws_data.py,
esbuild, DuckDB, boto3, OIDC/NDJSON, the projects/ + shared/ monorepo)
- the empty internal placeholder app
Also removed minor internal-naming asides from the concept docs and
glossary ("project is the internal name for an app", "conversation is
the internal name for a thread", "artifact type", "the backend", and
the app-detail 'agents and skills used internally' bullet).
muzaffar-ni
changed the title
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.
Why
This repo is public, and the Transilience AI chat assistant grounds its answers in it. A user probing the assistant ("why are you calling it a claude code agent?") got it to quote these docs and confirm internal implementation details, defeating the confidentiality guardrails in transilienceai/mcs#304. This PR is a deep audit of the whole repo to remove confidential/internal content — not just vendor names.
What changed
concepts/Applications.md— rewritten (825 → ~330 lines). It was effectively an internal engineering reference. It's now a clean, user-facing app catalog: each app keeps its description, purpose, high-level data sources (e.g. "your AWS account"), what you get back (reports/dashboards/Excel), and framework coverage. Removed entirely:/project/execute,/ai-bridge/invoke|stream)task_results.json,*.tsxcomponents,flow.json)run_pipeline.py,collect_aws_data.py, esbuild, DuckDB, boto3, OIDC/NDJSON, theprojects/+shared/monorepo)Concept docs & glossary — minor internal-naming asides removed: "project is the internal name for an app", "conversation is the internal name for a thread", "artifact type", "the backend", and the app-detail "agents and skills used internally" bullet.
Audited and left unchanged:
README.md,install/*,workflows/*, and the rest ofconcepts/*— these are pure user-facing UI docs with no internal content.Applications.mdis auto-generated fromprojects/*/CLAUDE.md+project.jsonin claude-compliance-suite. The generator will reintroduce all of this on the next regeneration — it needs to be updated to emit user-facing catalog content (or excluded from the public repo). The mcs frontend now also redacts vendor terms from retrieved docs as a code-level backstop, but that only covers vendor names, not the architecture/diagrams — so the generator fix is the durable one.🤖 Generated with Claude Code