Memolok, the Decision Record platform
Today, decisions live in a contract folder, a Jira ticket, a Confluence page nobody has reopened since, a WhatsApp thread, or someone's memory. Rarely anywhere you, your team, or an AI agent can query.
That's why we are developing Memolok, the Decision Record platform: the place your decisions live permanently and are instantly queryable by you, your team, your organization, and the AI agents working for you.
Why adopt Memolok?
| 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. |
| Premises are tracked separately | When a budget, contract, or regulation changes, you find that every decision is affected by it. |
| Every decision carries a clear status | Still being decided, accepted, rejected, or superseded, always visible, so you and your AI agents can tell what's current without opening every record. |
| Who decided travels with the record | The chain of agency, who raised it, who wrote it up, who committed, is part of the record itself, not a git blame or someone's memory. |
| Agent policies trace back to a reason | A rule your AI agents enforce has a Decision Record behind it: who decided it, what else was considered, and what was expected to follow. |
| New hires and new agents ramp up fast | The reasoning is already written down, nobody has to reconstruct it from memory. |
| 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. |
How it works
Memolok turns a decision moment into a permanent, structured record. The key steps of the decision record journey are:
- Always present. Memolok catches the decision moment while you're doing actual work and it's always available to be called.
- Structured record. The AI is the scribe: it drafts the need, the alternatives, and the verdict into shape. It never decides anything.
- Approval schema. The human stays in control: accept it as captured, adjust it, or reject it. Nothing is recorded without you saying so.
- Frozen forever. Once approved, it becomes a Memolok Decision Record, frozen at that moment, never silently rewritten.
- Queryable. Permanent and instantly accessible, by you, your team, and the AI agents working alongside you.
See how Memolok works for the full capture flow, how you ask it later, the Memolok Decision Record (MDR) schema, and what happens after, immutability, supersession, and the wake.
The Decision Record is the third pillar of Decision Intelligence
The Decision Record is what your organization already decided, permanent and queryable, not a system for deciding what's next. See the Decision Intelligence hub for where it sits alongside Decision Automation and Decision Support, or Context engineering for how it fits a second, parallel category.
Compare Memolok to what you use today
Memolok is ADRs on steroids, the Decision Record platform for every decision, not just architecture.
| Local files (Excel, Markdown) | ADRs | Decision logs & trackers | Notion & Confluence | LLM memory | Memolok | |
|---|---|---|---|---|---|---|
| Tracks status: current or superseded | ✗ | ✗ | ✗ | ✗ | ✗ | ✓ |
| Records what was expected, so it's checkable later | ✗ | ✗ | ✗ | ✗ | ✗ | ✓ |
| Queryable by an AI agent as a structured decision record | ✗ | ✗ | ✗ | ✗ | ✗ | ✓ |
See the full breakdown against ADRs, decision logs, Notion, and Confluence on the what you use today page.
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. A person reads that list, so nothing lands in your inbox automatically.
Common questions
What is a decision record?
A decision record is a written account of one decision: what got decided, what else was on the table, what was known going in, and what you expected to happen next. Memolok is the Decision Record platform, the place decisions like this live, permanent and queryable long after they were made. See the glossary for the rest of Memolok's vocabulary, MDR, MDL, and more.
A record is valuable when it is honest, not when it is right
A well-reasoned decision that failed teaches more than one quietly retrofitted to look prescient. The point of recording the alternatives and the premises is that a later reader can tell the difference between bad luck and bad reasoning.
Read about decision debt, the cost this is all about, or why AI agents need decision records.
What to read next
- How it works: the full capture flow, the MDR schema, and what happens after a decision is sealed.
- Decision Intelligence: the three-pillar category the Decision Record sits inside.
- Context engineering: where the Decision Record fits among orchestration, retrieval, and memory.
- What you use today: how this differs from an ADR, a decision log, or a page in Notion or Confluence.
- 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.
