Memolok Is the Decision Record Platform
Memolok captures what you, your team, or your organization decides, why, and what was expected to happen. It is the system of record for your decisions: permanent and instantly queryable, kept on its own ledger rather than in an AI assistant's memory. It runs inside Claude, whether you use Claude Code, Claude chat, or Cowork.
Who It's For
A person forgets why they made a choice. A team loses the reasoning when the person who made the call moves on. A company brings in an AI agent, has nothing to hand it, and watches it hallucinate the reasoning instead.
If you're bringing AI into how you work at all, start the habit now: record your decisions, not just the outcomes. That's what Memolok is for, whether it's one person keeping their own reasoning straight, a team, or a whole organization keeping everyone, human or AI, consistent on the same Memolok Decision Ledger (MDL). See what that looks like in practice on the Use cases page.
Memolok is industry-agnostic, since decision-making is universal. Memolok is opinionated on how you record decisions and agnostic on how you make them. Consensus, hierarchy, or a single mandate; software, legal, medical, or a hobby project, the way Memolok records it stays the same.
It runs today as a plugin for Claude Code, Claude chat, and Cowork, with more surfaces coming soon. It uses the Model Context Protocol (MCP), so capture and retrieval happen inside the conversations you're already having.
A Decision Is Not Just the Verdict
"We chose X." That's not the decision; that's the verdict part of the decision only.
A Memolok Decision Record (MDR) has a clear, unique architecture: the need, the ruled-out alternatives, the world facts the choice rested on (anything true outside the decision itself: a budget, a regulation, a client's requirement, what the team knows, even the weather), the verdict, what you expected to follow, and what you deliberately left unsettled. See how Memolok works for the full breakdown, and how a record is captured, approved, and turned into an account your team and its AI agents can query.
Why Start a Decision Record?
| Benefit | What it means |
|---|---|
| Nothing gets re-litigated | A decision that already ruled out an option stays ruled out. |
| Every choice is checkable | Write down what you expected at the time of your decision so you can check it later, rather than relying on memory. |
| Every decision carries a clear status | Proposed, accepted, rejected, or superseded, always visible, so you and your AI agents can tell what's current without opening every record. |
| You don't need a finished case to start | A decision doesn't have to be right, finished, or fully argued to belong on the ledger. |
See the full list of reasons to start using Memolok on the Product page.
Part of the Governance Layer of Context Engineering
AI systems increasingly run on context engineering, whether or not anyone names it: giving an AI system the right information at the right time, from the system prompt and the tools it can call to what it retrieves and what it writes down for later. Governance is where an agent's rules come from. Memolok captures and preserves the reasoning behind them, instantly accessible, so a rule is never just an assertion nobody can explain.
Read the full picture on Context engineering, or see why the Decision Record is the foundation of Decision Intelligence, whether a person, a machine, or both made the call, on the Decision Intelligence hub.
Try Memolok Today
Memolok is in early testing, and we're inviting people to try it now. Sign up today and start recording your decisions. Sign-ups are read by a person, not a mailing system, so there's no automatic confirmation email.
Follow Us
Follow our Memolok LinkedIn page for product news, daily posts, and the fastest way to check out what we're up to.
The Decision Record
Our newsletter on decision debt: why organizations forget the reasoning behind their own choices, and what that costs them. Written for people who are new to Memolok.
The same issues go out to three places, so you can read them wherever you're most comfortable:
- LinkedIn: The Decision Record
- Substack: Memolok.substack.com
- Medium: medium.com/the-decision-record
The Memolok Loop
This is for our friends already testing and using Memolok: what we shipped, what broke, and what your notes changed. We launched The Memolok Loop in August 2026 on Substack: TheMemolokLoop.substack.com
What to Read Next
- Product: why teams adopt Memolok, the five steps from decision moment to queryable record, and how it compares to what you use today.
- How it works: see a decision captured mid-conversation, and asked about months later.
- Context engineering: where the Decision Record fits in an AI agent's context, as part of the governance layer.
- Decision Intelligence: why the Decision Record is its foundation, whichever way a decision gets made.
- Decision debt: the compounding cost of choices that were made, often carefully, and never recorded.
- Decision records for AI agents: why an agent starting every session cold needs the reasoning, not just the output.
- What you use today: how this differs from an ADR, a decision log, or a page in Notion or Confluence.
- Use cases: onboarding, turnover, partner companies, and where this fits in your AI stack.
- How to choose a Decision Record platform: the eight criteria that separate a record you can trust from a page someone once wrote.
- Decision Record template: a free template for recording any decision, technical or not.
- Glossary: plain definitions for Memolok's vocabulary, decision record, MDR, MDL, and the rest.
