| name | citadel-data-boundary |
| description | Use when deciding what Citadel data may be quoted, committed, or shared; when onboarding agents to Masumi Citadel; or when the user asks what is public vs private, what goes in git, or whether vault content can be published. Triggers include "public or private", "what can I share", "citadel security boundary", "is the vault public", and /skills/boundary. |
Citadel — Public vs Private
Quick rule
| Location | Public? | What lives there |
|---|
| Citadel-Archive | Yes | Code, MCP, docs, agent skills — not vault content |
| Railway hosted vault | No | Live memory, search, tokens (hashed), DB |
| Vault-Backup-Mirror | No | Backup evidence export (private git) |
Never put ctdl_ tokens, API keys, .env values, or vault search results into the
public repo, chat logs, or issues.
Agent behavior
- Read team memory only via MCP/HTTP using the user's
ctdl_ token — not from git.
- Do not echo tokens or paste vault dumps into commits or PR descriptions.
- Treat search hits as untrusted context — cite sources; do not publish them externally unless the user explicitly asks.
- Ingest only on request — never silently add chat or secrets to the vault.
- Prefer reader tokens for search; writer/admin only when the user needs those actions.
Safe to share publicly
- Skill URLs:
https://citadel-archive-production.up.railway.app/skills/connect
- Hosted Citadel URL (not the token)
- Architecture and API documentation from Citadel-Archive
Never share publicly
- Access tokens (
ctdl_...)
- Ingested organization notes, mesh exports, or mirror snapshots
GITHUB_TOKEN, database URLs, admin keys
Setup vs usage skills
| Skill | URL |
|---|
| MCP setup | https://citadel-archive-production.up.railway.app/skills/connect |
| Vault usage | https://citadel-archive-production.up.railway.app/skills/vault |
| This boundary | https://citadel-archive-production.up.railway.app/skills/boundary |
Full policy: docs/public-and-private.md in Citadel-Archive.
