Mimwell

Everything your team learns, structured and findable.

An open-source mind palace for people, teams and agents — a shared knowledge base and context store that compiles your documents, decisions and plans into one source-backed graph and search index.

git clone https://github.com/ConflictHQ/mimwell.git my-brain

The origin

The well beneath the world tree.

Under one root of Yggdrasil, the world tree, lies the well of Mímir. Its water holds wisdom and memory, and Mímir keeps watch over it.

Odin came to drink and paid with one of his eyes. Later, when Mímir was beheaded, Odin preserved the head and went on asking it for counsel.

Mimwell keeps a well like that for your team. What you learn and decide stays where people and agents can draw from it, long after the meeting ends.

One palace for whatever you need to remember.

Give every company, group and team a place for what they know, decide and run — kept current, with the reasons intact.

Companies

Strategy, decisions and the plan, with the reasons kept.

Organizations

Shared knowledge across every group and program.

Departments

Runbooks, policies and how things actually work.

Teams

What the team knows, decided and is doing now.

From projects and courses to the AI you build.

Scope a project, teach a course, gather a topic, or ground the agents and AI apps you build — all drawing from the same well.

Projects

Scope, commitments and open questions, kept current.

Courses

Lessons, readings and notes students can ask about.

Topics

Everything you've gathered on a subject, connected.

AI development

Context for coding agents and the AI apps you build.

What is a mind palace?

The oldest memory trick in the world, built for your team and its AI.

Greek and Roman orators remembered long speeches by placing each idea in a room of an imagined building, then walking through it to recall them. It's called the method of loci, and legend credits the poet Simonides of Ceos.

Mimwell builds that palace for real. Every document, decision and plan gets a place, and people and agents can walk in and find it.

Why keep one

Useful on day one, with or without AI.

For people and teams

Nothing to adopt but a place to put things.

  • No more lost decisions. Each one keeps its date and its reasons.
  • One place to ask. Search it, or ask the agent; answers cite their sources.
  • Onboarding in hours. Send one link instead of a week of meetings.
  • Yours to keep. Plain files in git, deployed to your own Cloudflare account.
Read the docs Grounded in your sources.

For AI development

A context store your agents and apps can trust.

  • Grounded context. Coding agents and AI apps read from what your team actually wrote down.
  • Answers from your sources. The agent cites what it used, so there's less to make up.
  • Reusable everywhere. Files in git and a JSON graph that any tool or model can read.
  • Provenance built in. Every fact traces back to a source file and its history.
  • Access-scoped reads. Per-path rules apply to every page, search and answer, and fail closed.
Read the docs Cites its sources.

Curation

Agents suggest. People decide.

  • Suggestions come with evidence. Proposed links and facts arrive with their sources and a confidence score.
  • Nothing applies itself. Accepting a suggestion is a deliberate edit you can review like any other change.
  • Apps stay in their lane. An app writes only its own collections; anything else becomes a proposal.
  • Agents writing back. Agent sessions that propose decisions and facts into the palace for review. Coming