Platform ConceptsScoped Retrieval · Hybrid Search · Citation Grounding
Knowledge & Memory
Accurate enterprise answers require your organization's own definitions — how you calculate net retention, when your fiscal year closes, and which playbooks govern customer renewals. Nunc indexes documents and semantic memories inside your dedicated tenant stores with strict visibility boundaries.
Four strict visibility scopes
Every knowledge source, vector chunk, and memory node belongs to one of four governed boundaries — enforced natively inside Nunc agents and externally over https://api.nunc.cloud/mcp/memory.
| Scope | Who Can Read & Write | Typical Content |
|---|---|---|
| Public | Readable by all authenticated users and scoped specialist agents; admin-gated for writes | Shared reference corpora, compliance standards, public policy handbooks, and org-wide baseline definitions |
| Company | Readable by all authenticated tenant members; excluded from isolated external/specialist agents unless granted | Company-wide SOPs, fiscal calendar, KPI definitions, and internal operating guidelines |
| Workspace (including Personal) | Strict membership boundary — team project workspaces plus each user's private Personal default workspace (pin via ?workspace=<id>) | Personal preferences and working notes, Finance close SOPs, RevOps territory rules, and project uploads |
| Agent | Dedicated isolated store bound to a specific agent persona (combines its agent:<id> corpus with Public baseline) | Role-specific runbooks, curated specialist knowledge, and distilled operational strategies for that agent |
Zero cross-tenant, cross-workspace, or cross-agent leakage
Upload directly into Public, Company, Workspace, or Agent scopes and run idempotent scope migrations or vector re-syncs anytime in Console → Knowledge → Boundaries or inspect retrieval provenance in Memory → Explorer.