Mnemos AI
AI Search

Cited answers, permission-aware by design.

Ask anything across your SOPs, transcripts, and connected systems. Mnemos retrieves only what the asker can see, cites every claim, and stamps a full audit lineage on every response.

How do we offboard a customer on the legacy plan?

Legacy plan offboarding follows a three-stage process. Stage one[1] is a 30-day grace period with an automated data export. Stage two triggers a manual review by your account's assigned AE[2]. Stage three archives the workspace and revokes integration credentials via the integration service[3].

[1] sop:offboarding-legacy · fresh · last updated 6 days ago
[2] transcript:may-2026-cs-allhands · cited by 4 SOPs
[3] runbook:integration-revoke-creds · owner: platform
9 retrieved · 3 filtered (access) · 6 cited · 1.18saudit 0193fb6c
The retrieval pipeline

Hybrid retrieval, then permission, then synthesis.

Stage 1

Plan

The query is decomposed. Graph hops, lexical terms, and semantic embeddings are scheduled in parallel.

Stage 2

Retrieve

Hybrid retrieval over pgvector, trigram, and graph traversal. Top-K candidates from each strand are unioned.

Stage 3

Filter

Each candidate is evaluated against the asker's ACL, derived from source systems and Mnemos roles. Restricted content is dropped before synthesis.

Stage 4

Cite

The model is constrained to cite the retained candidates. Spans, freshness, and audit IDs are rendered into the answer.

Permission-aware by design

Access enforced at retrieval, not at render.

Most AI search products show every user the same vector index and try to filter on the way out. Mnemos applies ACLs before the model ever sees the candidate. If a document is restricted, the model cannot leak it because the model never receives it.

  • ACL inheritance from Google Drive, Notion, SharePoint, and Confluence.
  • Mnemos roles layered on top — department, tenure, project.
  • Tenant boundary enforced by row-level security in Postgres.
  • Full audit lineage: who asked, what was filtered, what was cited.
Retrieval ledger
kept sop:142 · acl:engineering+revops
kept transcript:close-may · acl:revops
kept doc:netsuite-import-runbook
filtered doc:cfo-board-memo · acl:exec
filtered transcript:m&a-prep · acl:strategy
filtered sop:layoff-comms · acl:hr-exec
Built for operators

Search that knows the shape of work.

Workflow-aware

Questions about a workflow surface the live owner, the canonical SOP, and the recent incidents in one response.

Always cited

Every claim renders with a hover preview of the source span. No anonymous AI prose.

Audit on every answer

Each response carries an audit ID linking the question, the retrieved set, the filter decisions, and the model used.

Ask your company anything.

Permission-aware. Cited. Auditable. Available on the web, in Slack, in Teams, and over API.