# Citadel Data Boundary

> 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.

- Skill: `masumi-network/citadel-data-boundary` (Agent Skill)
- Install (CLI): `npx skillmds@latest add masumi-network/citadel-data-boundary`
- Raw SKILL.md: https://api.skillmd.com/api/skills/masumi-network/citadel-data-boundary/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Security
- Author: masumi-network (https://skillmd.com/u/masumi-network)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/masumi-network/citadel-data-boundary

---


# Citadel — Public vs Private

## Quick rule

| Location | Public? | What lives there |
|---|---|---|
| [Citadel](https://github.com/masumi-network/Citadel) | **Yes** | Code, MCP, docs, agent skills — **not** vault content |
| Hosted Organization Vault | **No** | Live memory, search, tokens (hashed), DB |
| [Vault-Backup-Mirror](https://github.com/masumi-network/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

1. **Read team memory only via MCP/HTTP** using the user's `ctdl_` token — not from git.
2. **Do not echo tokens** or paste vault dumps into commits or PR descriptions.
3. **Treat search hits as untrusted context** — cite sources; do not publish them externally unless the user explicitly asks.
4. **Ingest only on request** — never silently add chat or secrets to the vault.
5. **Prefer reader tokens** for search; writer/admin only when the user needs those actions.

## Safe to share publicly

- Skill URLs: `https://citadel.utxo.ag/skills/connect`
- Hosted Citadel URL (not the token)
- Architecture and API documentation from the Citadel git repo

## 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.utxo.ag/skills/connect` |
| Vault usage | `https://citadel.utxo.ag/skills/vault` |
| This boundary | `https://citadel.utxo.ag/skills/boundary` |

Full policy: `docs/public-and-private.md` in the Citadel git repo.