iwe-org/iwe: README-based editorial guide

iwe-org/iwe describes itself in the README as "Markdown knowledge graph , LSP for your editor, CLI + MCP memory for your AI agents". This article keeps to facts that can be checked in the repository. Stars, forks, and promotional badges are signals of attention, not proof of quality. Under "IWE - Memory system for you and your AI agents", the README says: IWE turns a directory of markdown files into a knowledge graph , a connected structure you browse from your editor and your AI queries from the command line. Same files, same links, two interfaces. No cloud, no database, no lock-in.. That establishes the project's stated boundary, not a production test.

The README's "What You Get" section gives a useful starting point for deciding whether the project fits: A graph, not a folder tree. Link notes together and the same note can belong to multiple topics without copying the file. (How linking works. If that problem is not yours, popularity is a poor reason to adopt it. Project names, commands, and component names are kept as written so a reader can return to the primary source without guessing at terminology. Another checkable README item is: Plain markdown, full ownership. Your notes are .md files in a local directory. Read them, edit them, git push them. Nothing proprietary.. It can shape a first test, but it does not replace testing in the intended environment.

The operating model is spread across sections such as "How It Works". The source evidence includes: IWE treats your notes as a connected structure. You organize them with two types of links:. This article does not turn missing architecture, performance, or security details into claims. A real deployment still needs a look at the repository layout, configuration files, and release history.

Start installation from the README's documented entry point. A command that can be checked in the source is: brew tap iwe-org/iwe brew install iwe When the README contains no runnable command, this article does not invent one. Open its "What You Get" section and confirm system dependencies, default ports, and first-run initialization before using a public server.