EARLY ACCESS — DESIGN PARTNERS
Code remembers what.
Mithrandir remembers why.
The decisions behind your code live in Slack threads, meetings, and tickets — and vanish when people leave. Mithrandir permanently connects every piece of code to the reasoning that explains it.
MEMORY
Immutable
ACCESS
Structural
REACH
Every AI tool
scheduler/dst_offset.ts
“We assumed a fixed offset — the real fix touched three services, and launch was 48 hours out.”
CLICK A NODE OR BRIDGE TO EXPLORE · ▪ CODE ● RATIONALE
01 · The problem
Your tools know what changed. None of them know why.
The workaround and the reason it exists live in different worlds. One is versioned forever. The other was archived with the channel.
payments/cache_workaround.ts
GIT BLAME
a41f9e3 maya 2023-03-14 if (tz === FIXED_OFFSET) {
a41f9e3 maya 2023-03-14 return cachedWindow(ts); // workaround
9c02b1d tomas 2023-03-14 }
7e55d20 priya 2022-11-02 const window = schedule(ts);
A diff, a name, a date. Not one word of reasoning.
#incident-payments
ARCHIVED · AUG 2023
maya · 14:02
“The proper fix touches three services. We don't have 48 hours.”
tomas · 14:04
“Ship the cache workaround. We'll document it after launch.”
The entire rationale. Gone when the channel was archived.
Six months later, someone new “cleans up” the workaround — and reintroduces the exact incident it was protecting against. The knowledge wasn't lost in the code. It was lost in an archived channel, a meeting nobody transcribed, a ticket nobody linked.
Every company is quietly forgetting why it made its most important decisions.
THE MEMORY GAP
02 · Architecture
Two brains, one memory
Structure on one side, reasoning on the other, and a bridge that keeps them permanently in sync.
STRUCTURE
Left Brain
Understands your codebase the way a senior engineer does — files, classes, functions, and how they depend on each other. The structural spine.
RATIONALE
Right Brain
A permanent record of every decision that shaped the system: Slack threads, meeting transcripts, tickets, PR reviews. Nothing is ever deleted or overwritten — and at maturity, it extends beyond engineering to finance, sales, legal, and the exec team.
CONNECTION
The Bridge
Automatically connects a specific piece of code to the real conversation that explains why it exists. Anyone looking at that code sees the reasoning — not just the diff.
03 · Demonstration
Same question. Two correct answers.
Access isn't a filter applied to the answer — it decides what the AI can reach at all. Ask the same question at two clearance levels and watch.
QUERY
“Why did this DST bug happen?”
CLEARANCE · DIRECTOR
- 01
The outage traced back to a timezone conversion that assumed a fixed UTC offset.
POSTMORTEM · MAR 2023
- 02
The original incident thread shows the team debated a full refactor vs. a cache-layer workaround.
INCIDENT THREAD · MAR 2023
- 03
They chose the workaround: a major customer launch was 48 hours out, and the proper fix touched 3 services.
DECISION · MAR 2023
- 04
The follow-up ticket to remove the workaround was deprioritized two quarters in a row — that context is why it resurfaced.
TICKET · Q3 2023
The intern's answer isn't a redacted version of the director's — it was assembled without the restricted material ever being touched. There is nothing in the context to leak.
04 · Security · GBAC
Security your CISO can verify, not hope for
The uncomfortable truth about most enterprise AI: it filters answers, not access. Mithrandir is built the other way around.
ENFORCED BY STRUCTURE
Not a rule the AI follows
Most AI tools retrieve everything and then ask the model to be discreet. Prompt-level rules can be argued with. Mithrandir's access control isn't an instruction — it defines what the AI can reach.
NOTHING TO LEAK
Never in the context at all
Restricted information is never assembled into the model's context in the first place. No clever prompt, jailbreak, or paraphrase can extract what was never there.
CORRECT AT EVERY LEVEL
Complete for each clearance
An intern and a director asking the identical question each get an answer that is complete for their access level — not an error, not a redaction, and never a leak.
05 · Platform · MCP
A knowledge layer, not another chat window
Mithrandir isn't a destination your team has to visit. It's a layer any AI tool can query mid-task — your coding assistant asks while it works, and gets back institutional context that is semantically relevant and access-controlled for the person driving.
- Claude Code
- Cursor
- Your internal agents
One integration point. Every agent your company runs gets a memory.
CLAUDE CODE · MID-TASK
“Why does this retry cap exist?”
Capped at three since the June pilot — finance flagged duplicate invoices. The full thread is available at your clearance.
ANSWERED · SCOPED TO THE ASKER
06 · Comparison
A different architecture, not a better index
| Capability | Mithrandir | Glean | Microsoft Copilot | Notion AI |
|---|---|---|---|---|
| Understands code structure (not just text search) | Built on a structural model of the codebase | Document search | Code-aware in IDE, no org-wide structural graph | Not code-focused |
| Permanent decision record | Immutable by design — nothing deleted or overwritten | Indexes live sources; not designed as a permanent record | Bound to M365 retention | Editable workspace pages — built for collaboration, not as a permanent record |
| Links code to the decision behind it | Core function (the Bridge) | Not a design goal | Not a design goal | Not a design goal |
| Access control model | Structural: restricted context is never assembled | Permission-aware search results | Permission-trimmed retrieval | Page-level sharing |
| Serves other AI tools mid-task (MCP) | Native distribution model | Emerging connectors | Oriented to Microsoft's own surfaces | Locked to Notion |
Based on each product's publicly documented architecture as of 2026. This table is about design choices, not marketing — we're happy to be corrected.
v0 — DESIGN PARTNERS
Request early access
We're working with a small number of early design partners while we build. No product tour, no trial — a conversation about whether your team's problem is the one we're solving.