caura-ai / caura

What it does

• Tenant isolation. row-level database separation per tenant; PII auto-detected and flagged on every write (surfaced in memory metadata as contains_pii/pii_types)
• Visibility scopes. every memory is stamped at write time: scope_agent (private), scope_team (fleet-wide, default), or scope_org (cross-fleet). Cross-fleet recall is permissioned, not open
• Agent trust tiers. four levels control cross-fleet reads, writes, and deletes. Agents are either provisioned atomically via POST /admin/agent-keys/provision on the managed platform (caura.ai; a self-hosted core-api has no such route) or au
• Full audit log. every write, delete, and transition logged with tenant and scope context
• Agent activity digests. per-agent digests, generated server-side for opted-in orgs (org setting agent_digest.enabled, off by default) on the org's cadence (agent_digest.cadence: daily by default, or weekly or both; an org on the default ge