three independent open-source tools
Three optional tools. The record needs none of them.
GitNexus, Graphify and OpenWiki are separate open-source projects, not parts of Project Context. Each is an opt-in add-on: the initializer inspects your project, offers only what fits, and installs or configures nothing until you say yes. With all three absent, the record still works in full.
- independent projects
- opt-in, every time
- derived, never authoritative
How the three add-ons sit around Project Context
authority layer
Project Context
Decisions, learnings and the current handoff, in plain Markdown tracked with your project.
01 authority and derived views
The distinction
Project Context records what the code cannot say — the decisions, the learnings, the current handoff.
A generated wiki synthesizes what your sources already contain — code, documents, or a personal corpus.
They compose on that line: Project Context is the authority layer; a generated wiki is an optional derived view over the material it reads.
authority layer
Project Context
Decisions, learnings, the current handoff — asserted by a person or an agent, because no source contained them, and versioned with the project.
derived view · optional
A generated wiki
Synthesized from sources that already exist, and regenerable from them. Useful, replaceable, and not the source of truth.
02 how an add-on gets offered
Add-ons, only where they earn it
Three independent open-source tools can sit alongside the record. Project Context does not just list them: it inspects the project, recommends only what fits, and installs or configures nothing until you have said yes.
- it inspects the project
- it recommends only what fits
- nothing lands until you opt in
Per tool, the initializer separates two states that look identical from the outside: merely available on your PATH, and actually configured for this repository. Something already installed but unconfigured gets an offer to configure it, not a pointless reinstall. It asks only about unconfigured tools that match the confirmed project type and a need it has actually observed — and it installs only after an explicit answer.
See what it would offer you, before anything is installed
That inspection is its own read-only subcommand. It classifies the repository, reports which of the three tools are on your PATH and which are already configured for it, and prints the resulting guidance — which tool is recommended, which is optional, which is deferred, and which is not proposed at all — without writing a single file.
inspect · read-onlyscroll →
uvx --from git+https://github.com/monomind-ai-lab/project-context project-context inspect --target .
| Tool | What it is | When it fits | Relation to Project Context |
|---|---|---|---|
| GitNexus | Code symbols, their relationships, impact analysis and execution flows. | A repository classified as code. GitNexus is proposed there and nowhere else — a document, research, writing, mixed or general project is never asked about it. | A derived read of the code. The decisions about that code still live in the tracked Markdown. |
| Graphify | Relationships across code, documents, research artifacts and media. | Any project type. Relationships across files are not a property of what those files contain, so a codebase, a document corpus, a research corpus, a manuscript and a mixed tree are all candidates. Recommended when the project is sizable, optional when it is smaller. | A derived index over your material. Rebuildable, and never the thing being cited. |
| OpenWiki | A CLI that writes and maintains a wiki for a codebase or for personal knowledge. A documentation agent reads your sources, synthesizes a linked Markdown wiki you own, and keeps it current as they change — with Grounded Claims tracing facts back to versioned evidence, an interactive visualizer, and OKF v0.2 output. | A code repository, where its code mode applies, or a document or research corpus, where personal mode does. Not asked for a manuscript, which is read in order rather than browsed, or for a mixed or unclassified tree, which has no single body for a wiki to cover. mode applies. Its personal mode genuinely suits a document or research corpus, but the initializer keeps its offers narrow and does not propose it there. mode, or a body of knowledge — a document or research corpus — in personal mode. Offered as an option in both, and in a mixed repository where either applies. Deferred for a manuscript, which is read in order rather than browsed. | Synthesized from sources that already exist, and regenerable from them — including the record it reads. Project Context holds what no source contains. |
03 by project type
What gets offered, by project type
The initializer classifies the repository first. What it may then propose is fixed per type in its own code, not improvised by an agent in the moment.
- Code
All three are recommended. GitNexus for symbols and impact analysis, OpenWiki's code mode to write and maintain the repository's wiki, and Graphify for relationships across files and formats. This is the only project type where every add-on has a case. mode writes and maintains a wiki for a repository this size. Graphify is not proposed.
- Documents
OpenWiki is recommended — a document corpus is the body of knowledge its personal mode is for. Graphify follows size: recommended for a sizable corpus, optional for a smaller one. GitNexus is not proposed. mode is for.
- Research
OpenWiki is recommended — personal mode fits a research corpus, and its grounded claims track a fact back to the source that supports it. Graphify follows size. GitNexus is not proposed. mode fits a research corpus, and its grounded claims track a fact back to the source that supports it.
- Writing
Graphify only, recommended for a sizable manuscript or story world and optional for a smaller one. OpenWiki is not proposed: a manuscript is read in order rather than browsed. GitNexus is not proposed.
- Mixed
Graphify only, on the same size rule as every other non-code type. A mixed tree is not classified as code and has no single body of knowledge for a wiki to cover, so neither GitNexus nor OpenWiki is proposed. for the source, personal for the rest.
- General
Graphify only, and optional unless the project is sizable. Nothing else is offered while the type is uncertain.
04 where the authority stays
Derived, optional, and never the source of truth
Three derived systems and one authored tier are easy to confuse. This is the line between them.
Project Hub is not a fourth add-on. These three are derived views: rebuildable from material you already have, and never the thing being cited. A Hub is another authored tier — records an owner writes in one separate private repository and pushes down into yours, where they arrive read-only and stamped so the doctor can tell an untouched copy from an edited one.
What a Hub authors, and what a push may never send → Project Hub
Project Context stays the authority. The tracked Markdown is what the project is committed to; these three are optional derived systems built from it. None of them becomes the source of truth, and the record works fully with none of them installed.
GitNexus, Graphify and OpenWiki are independent open-source projects, and their names and trademarks belong to their respective owners. Project Context and MonoMind AI Lab are not affiliated with, sponsored by, or endorsed by these projects or their maintainers. They are featured here because they are excellent open-source tools we comfortably recommend when they fit a project's needs.
Official repositories: GitNexus Graphify OpenWiki
independent open-source tools · optional · installed or configured only after you opt in
05 next
Where to go from here
The add-ons are the last thing to think about. The record comes first, and an owner's tier is the only other thing that ever writes into it.