A living graph of how your company actually works.
Mnemos models the people, processes, systems, customers, and decisions that run your company — and the dependencies that bind them. Not a wiki. Not a CMDB. A reasoning substrate.
Modeled like an operating system, not a knowledge base.
People
Roles, owned scopes, tenure, expertise, and the implicit knowledge that does not appear in any org chart.
Processes
Workflows, SOPs, exception paths, and the decisions that have to happen for the company to operate.
Systems
Tools, accounts, integrations, schemas, and the contracts between them. The CMDB you wish someone had built.
Artifacts
Documents, contracts, decisions, postmortems, and customer records — all linked back to the workflows they support.
The edges are the value.
Anyone can list entities. Mnemos captures the relationships between them — owns, depends-on, escalates-to, supersedes, blocks. Without the edges, you cannot reason about continuity.
- Workflow X depends on system Y, owned by person Z, last verified 12 days ago.
- Customer A escalates through CSM B → AE C → exec sponsor D.
- SOP 142 supersedes SOP 96 — pre-2024 incidents still reference the old version.
- Pricing decision in Q3 cascades to four downstream contracts requiring re-papering.
The graph knows when it is wrong.
Every node carries a freshness score derived from observed activity in source systems, recency of capture, and ownership changes. Stale knowledge is surfaced, not silently served.
Activity-derived
If Slack, the CRM, or git haven't seen the entity move recently, the freshness score decays.
Linked to source
Every node anchors back to the originating transcript, document, or system event it was extracted from.
Permission-aware
Freshness, like the entity itself, is filtered against the asker's access scope before it surfaces.
Give your company a memory.
Bootstrap the graph from your existing tools in under a day. Watch it grow every time the interview agent runs.