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 regenerates what the code does say.
They compose: Project Context is the authority layer; a generated wiki is an optional derived view.
authority layer
Project Context
Decisions, learnings, the current handoff — written by hand or by an agent, versioned with the code.
derived view · optional
A generated wiki
Regenerates what the code already says. 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 code-centered repository, where symbol and impact analysis can add value. On a mixed repository it is offered as optional rather than recommended, when there is enough code for structural analysis to be useful. Not proposed for document, research or writing projects. | 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. | When the useful corpus reaches past code — a substantial interlinked document set, cross-source research and evidence, or a large relational manuscript or story world. | A derived index over your material. Rebuildable, and never the thing being cited. |
| OpenWiki | Ongoing generated documentation and navigation for stable projects. | Stable, complex projects with a real audience for derived navigation. Deferred while claims or structure are still moving; suppressed for writing projects. | Regenerated from what already exists — including the record it is generated against. |
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
GitNexus is recommended: the repository is code-centered, so symbol and impact analysis can add value. OpenWiki is deferred until a clear audience and a stable need for generated navigation are established. Graphify is not proposed.
- Documents
Graphify for a substantial interlinked corpus. OpenWiki only when collaborators need a maintained browse layer.
- Research
Graphify for cross-source, data and evidence relationships. OpenWiki is deferred until claims and structure are stable.
- Writing
GitNexus and OpenWiki are suppressed. Graphify only for a large relational manuscript or story world.
- Mixed
Graphify is recommended when the repository spans two or more artifact types that benefit from cross-file relationships. GitNexus is optional, offered when the mixed repository contains enough code for structural analysis to be useful. OpenWiki is deferred until collaborators demonstrate a need for maintained generated navigation.
- General
Nothing is offered until inspection finds a concrete need — the same answer while the type is still 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.