The company brain is already here.
Memkist is not a folder. It is a governed intelligence over the whole organisation's knowledge: every document parsed and classified, every answer cited, every workflow reviewed by a human, every change provable. This half of the ecosystem runs today.
Governed walls Shipped
Department-scoped on every read surface, one isolated bucket per tenant. An answer can only ever be assembled from what the asker may see.
Cited answers Shipped
Ask in prose; get answers with page-level citations. The AI assistant shows its sources, or it doesn't answer.
Knowledge graph Shipped
People, projects and conventions folded into one wall-scoped picture of who knows what.
Workflows Shipped
Plain-English workflows compiled to validated specs. A manager reviews before activation; every firing is journaled.
Digests and insights Shipped
Weekly catch-ups, manager briefs, flagged-cluster proposals, a monthly tenant report. The brain speaks on a clock.
Tamper-evident audit Shipped
A hash-chained log of every change to people, files, links and settings. A silent edit flips the verdict.
One agent. Two memory systems.
Asa's loop is decision-driven, not hardcoded. Both brains feed it: personal memory and documents from your device, company knowledge and conventions from your workspace — assembled together at prompt time. The vaults never merge.
Personal brain — on your device
The always-on half that lives on your machine. It never needs the cloud to remember who you are.
- A memory that links ideas — notes remember how much they mattered, and connect to the notes they belong with
- Your own files — a private, searchable library on your device, always available
- A full record of every session — replay exactly what happened, step by step
- Bring your own model — connect Asa to the AI service you already use
- It learns your preferences — your corrections become standing instructions, not one-off fixes
Company brain — your Memkist workspace
The shared half: organisational knowledge that every member's agent can recall. A workspace can be a company, a team or a family.
- A shared memory — notes over the workspace's documents and decisions, saved once, recalled by everyone
- Department walls — the wall follows the file: managers see all shared notes, members see their department's plus company-wide ones
- Conventions — the house rules recalled alongside notes, so every agent works the way the team works
- Works with your AI tools — any AI app you connect to Memkist can recall the company brain
- Counted and logged — every AI call is permission-checked and recorded
The rule that keeps them clean: brains meet in the prompt, not in storage. Personal memory is device-local in every tier — the server keeps only the company brain. What flows up is what you explicitly share.
A brain of your own.
Alongside the company brain, every member gets a personal AI brain — a small, private intelligence that knows your projects, your notes, your preferences, your unfinished threads. Not a chat window: a resident. It works when the network doesn't, remembers what you teach it, and goes where you go.
Local-first
Your brain runs on your machine. Answers from your pinned documents and personal memory arrive with the network down — on the train, on a client site, on a plane.
Private by construction
Personal memory lives in your vault. The organisation can neither read it nor ask it questions. Your thinking stays yours.
Yours to keep
When you leave the company, your memory exports with you. The brain you trained is yours — the company keeps its own knowledge, you keep yours.
The personal brain is a concept proposal. See the roadmap at the end of this page.
Where the personal brain lives.
Three placements, no new hardware. The brain module ships inside the Memkist desktop client you already install. Its state roams in a personal namespace in your Memkist account. Every device you sign into becomes a socket it plugs into.
The desktop client
A brain module beside the sync folder: a local runtime plus your memory vault in app storage. No admin rights, no drivers, no dongle. Install Memkist — your brain wakes up.
The roaming profile
Memories, preferences, tasks and drafts travel with your account. The profile is the brain. Devices are where it plugs in.
Every screen you use
Office workstation, home laptop, phone companion. Sign in and the same brain reconstitutes — same memories, same unfinished work. The web UI gets a thin session.
Drafts from pinned docs and personal memory. Nothing leaves the laptop.
Memory updates sync to the roaming profile. A moving brain.
Joins the company network, syncs its profile, collects its briefing — and resumes.
Two brains, one handshake.
The personal brain and the company brain are separate intelligences with a strict contract between them.
Join the network, resume the mind
When your device reaches the company network, your brain reattaches: it syncs its roaming profile, pulls its briefing, and re-opens your working context.
Ask the company brain — through your own permissions
Your brain queries the company brain on your behalf. Answers come back pre-filtered by your access rights. Delegation is never an escalation path.
Org conventions distill into personal memory
The company brain distills how the org works. The slice that matters to you lands in your personal memory, so routine questions can be answered locally.
The company proposes. You decide.
A workflow to activate, a folder to reorganize, a category fix. The company brain proposes; your personal brain surfaces it; a human approves. Agents are never the approver of record.
The company brain works while you're away
Classification, workflows, digests and alerts run around the clock. Come back and the results are queued in your briefing.
Two walls. One rule.
Two intelligences mean two boundaries. The question is always the same: can the personal brain leak the company? The architecture answers before the question is asked.
Company memory
- One isolated bucket per tenant; department walls on every read
- Every answer assembled inside the asker's permissions
- Every access logged content-blind; every change hash-chained
- Workflows only ever run validated, human-activated specs
Personal memory
- A private vault; the organisation cannot read it
- Roams with the person — home, office, phone
- Exports when they leave; deleted when they say so
- Never a query path into company data by itself
The one rule — a brain sees only what its human sees
From company brain to ecosystem.
Everything below the first line is a proposal. Nothing in those phases ships until it has been run end to end.
The company brain, rungs 1–4 Shipped
Searchable corpus with citations, an AI assistant, workflows, webhooks and anomaly alerts, scheduled digests and insights, a knowledge graph, metering, quotas, and a tamper-evident audit.
The brain moves in Proposal
The personal-brain module ships inside the desktop client: a local runtime, a personal memory vault, and a roaming profile in the member's account.
The handshake Proposal
Reattach on network join, delegated queries with asker-scoped answers, offline pinning with queue-and-resume, and proposal surfacing with human approval.
The proactive self Proposal
A personal scheduler for agent runs that start on their own, meeting and document capture companions, and a phone brain sharing the same roaming profile.
The learning organisation Proposal
Personal patterns become org conventions without exposing individuals. The brain reaches rung 5 — anticipatory. Still a proposal.
Dual Brain, straight answers.
Does my personal memory ever go to the cloud?
What happens when I sign out?
Is the company brain just a shared folder?
Can other AI tools use the company brain?
What does "Dual Brain" mean for a family?
Your brain stays yours.
The shared one keeps growing.
Questions about Asa or the Dual Brain architecture? Get in touch.