Smarter agents, same hot path

Scope retrieval by role — before text reaches the model.

Agents keep full access to what their mandate allows. Nothing extra for engineers to configure per query.

One brain, many governed views — memory and identity on the same fabric.

Same question, governed answers

Two agents, one question — depth matches clearance.

Retrieval is scoped by identity tiers before any text reaches the model, not filtered after the fact.

One memory layer, many governed views. Identity and retrieval as one product — not a bolt-on filter on top of a vector database.

Question: "Tell me about customer churn" Analyst tiers: gtm, marketing, public Segment trends, no individual PII Admin tiers: production, pii, customer Latency correlation + named accounts

Try it — pick a question:

Analyst agent

Can access: gtm, marketing, public
Select a question below.

Admin agent

Can access: production, engineering, pii, customer
Select a question below.

Knowledge by data tier

Every document classified once; tiers map to agent permissions.

Retrieval enforces scope structurally — not via post-hoc prompt rules.

public

Docs and FAQs.

All agents.

internal

Company processes.

Authenticated agents.

gtm

Sales and marketing metrics.

GTM-facing agents.

engineering

Architecture and code docs.

Engineering roles.

production

Runbooks and live metrics.

Ops and on-call agents.

pii

Personal customer data.

Restricted roles only.

customer

Account and contract details.

Customer-facing roles.

financial

Revenue and cost data.

Finance and leadership.

regulated

Compliance-critical content.

Legal and compliance roles.

Cortex topology

Institutional knowledge as a living, tier-colored map.

Clusters by meaning — see where sensitive data sits and how agents navigate it.

Drag to rotate, scroll to zoom.

Loading cortex visualization.

Scope held at retrieval

Allows get the same audit trail as denies.

When an Analyst queries churn data, scope is enforced before the model sees text — and the decision is explainable.

SCOPE HELD
Analyst got churn trends — segment data only, no individual PII
analyst-agent → memory retrieve → customer churn · session mem_allow_3847
What happened: Analyst agent asked about customer churn for a quarterly review.
Why allowed: Query matched gtm and marketing tiers. PII and customer tiers were excluded at retrieval — before the model saw any text.
Outcome: Segment-level trends returned (3.2% Q1 churn, mid-market drivers). No individual contact fields. Same audit trail as enforcement denies.
SCOPE HELD TIER OK

Memory guard

Ingestion scans for poisoning before content enters the brain.

Instruction overrides, dormant triggers, credential storage — blocked at ingest.

Compounding moat

Knowledge accumulates across agents over time.

Competitors can copy rules; they cannot copy your institutional graph.

See policy decisions

Memory connects to who the agent is and what actions are allowed.

Review governed decisions on the policy ledger.