Drawing from the well.

Mimwell

One knowledge base for your team

Mimwell turns your docs, decisions and plans into one searchable knowledge graph — every answer linked to its source, for your team and your AI agents.

git clone https://github.com/ConflictHQ/mimwell.git
See the story

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.

Frequently asked questions

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.

How it works

Keep knowledge apart. Join it where it helps.

Mimwell keeps knowledge in wells: one for a project, a team, a department, an initiative or just you. Each well decides what it shares upward, so knowledge stays compartmentalized where it should and conjoined where it helps.

  1. Every team keeps its own well. Projects and teams each keep a well, owned by the people who write it.
  2. Closed by default. A well shares nothing until it says so.
  3. Access narrows on the way up. Each well declares what it passes to the well above; the filter runs at the sending well’s edge.
  4. Parent wells conjoin them. What teams share meets and links in one place, without merging their data.
  5. Ask at any level. Every answer points back to the well it came from.

It’s one graph.

Wells link up to parents, sideways to peers and down to children, and records link across wells. Every edge carries its own rule, and the sending well always decides what crosses.

Wells are the nodes of one graph. Teams publish up to their company, a team can enroll in an initiative, a person reads what each company approves, peers link sideways, and the same client can be linked across wells without merging.

Supported topologies

The same graph takes whatever shape your work needs.

Islands, tree, wrapper, peers, many parents and network.

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

FAQ

A few things worth knowing.

Still have questions? Hi@weareconflict.com

What can Mimwell do for our team?

Keep what your team learns in one place, so the next person can find it. Mimwell connects your documents, decisions and plans, making it easier to understand what happened and why. Search your knowledge or ask a question, with answers that point back to your sources. Explore Mimwell ↗

Do we need AI to get value from it?

No. Give your team a shared place to read, search and remember from day one. Add AI when you want to ask questions in plain language and get answers grounded in what your team has written. Chat needs a separately configured AI provider. Learn more ↗

What knowledge should we start with?

Start with the things people keep asking for: project docs, important decisions, meeting notes and plans. Add more as your team grows. You can also bring in wiki pages and prepared exports from other tools, with some setup. Your original material stays yours. See what you can add ↗

How does it help our AI work better?

Give your AI access to the same knowledge your team uses. Coding agents and AI apps can find relevant documents and decisions, so they have your actual context to work from. You choose what they can read; the context connection cannot edit your knowledge. Connect your agents ↗

Who keeps the knowledge trustworthy?

Your team stays in control. People and agents can suggest connections, but a reviewer decides what to accept. Suggestions come with evidence, and accepted changes keep a history. That makes it easier to check a claim, understand a decision and correct something later. How review works ↗

Can we keep it just for our team?

Yes. Run Mimwell in your own Cloudflare account and configure sign-in for your team. You can also set rules so people and agents see only the material they are allowed to read. You decide who gets access. Set up private access ↗

How do we get started?

Start small: one team, one project or one document worth keeping. Follow the guide to set up Mimwell, add your material and preview your first knowledge base. When you're ready, put it online for your team. You can grow it as you go. Build your first Mimwell ↗

Is it really ours to keep?

Yes. Mimwell is open source under Apache 2.0. You can run your own instance, inspect the code and adapt it to your team under the license terms. Your knowledge lives in files you control, with a history you can review. Read the license ↗

Can someone host it for us?

Mimwell is built to run in your own cloud, so your knowledge stays in your accounts. If you would rather not run it, hosting is offered by Calliope Labs, an independent company not affiliated with CONFLICT. See hosted Mimwell at Calliope Labs ↗