# Project Context

> Small Markdown records, versioned in a project's own repository, that outlive any one person, agent, or chat. Project Context installs into a repository and serves the people building it; Project Hub is its optional other half, one private repository where an owner authors what applies across every project. Markdown and Git are the whole storage contract: no database, no server, no runtime dependency, and no command that reaches the network.

## Start here

- [Project Context — MonoMind](https://projectcontext.monomind.one/): Small Markdown records, versioned in the repo, that outlive any one person, agent, or chat.

## The other half, and what can sit alongside it

- [Project Hub — Project Context](https://projectcontext.monomind.one/project-hub/): The owner's half of the pair, and entirely optional: one private repository where you author the tier that applies everywhere, keep a folder per project, and read what the builders wrote — without giving them a permission on any of it.
- [Add-ons — Project Context](https://projectcontext.monomind.one/add-ons/): Three independent open-source tools — GitNexus, Graphify and OpenWiki — can sit alongside the record as opt-in add-ons. What each one is, how the initializer decides which to offer for your project type, and why none of them ever becomes the source of truth.

## Use cases — what kind of project this suits

- [Use cases — Project Context](https://projectcontext.monomind.one/use-cases/): Two shapes of the same records: Project Context alone inside one project folder, and Project Context plus a private Project Hub above several — for coding, writing, research, planning, or any project you run with agents.

## Docs — for builders working in a repository

- [Docs — Project Context](https://projectcontext.monomind.one/docs/): The record a returning collaborator reads first: a real NOW.md, whether it fits your project, install in 30 seconds, and the session loop.
- [Install — Project Context](https://projectcontext.monomind.one/docs/install/): What installing does to your repo — six safety promises above the command, dry-run first, per-harness setup, the zero-tooling prompt, verifying, and uninstalling.
- [The three records — Project Context](https://projectcontext.monomind.one/docs/records/): An annotated tour of NOW.md, DECISIONS.md, and LEARNINGS.md — the question each answers, what stays out of it, one good and one bad entry side by side, and how each record changes over time.
- [Operating the loop — Project Context](https://projectcontext.monomind.one/docs/operate/): The day-2 page: what agents read before substantial work, what triggers a durable record, what gets updated at the end of a session, when the doctor runs, and the five things worth having written down by day 7.
- [Builder's guide — Project Context](https://projectcontext.monomind.one/docs/builders-guide/): The reference layer: the authority ladder, the six required frontmatter keys, one lifecycle per kind, the reference grammar, capture, packet retrieval, the standing review, the pushed set, the upgrade path, and what is not built yet.

## Docs — for owners overseeing several repositories

- [Owner's guide — Project Hub](https://projectcontext.monomind.one/project-hub/owners-guide/): The complete administrator's reference for a Project Hub: activation step by step, the annotated tree, every command with its real flags, gates and refusals, exactly what reaches a project repository and what never does, the word budgets, and the honest gap list.

## Slide decks

- [Guides & decks — Project Context](https://projectcontext.monomind.one/guide/): Every guide and both slide decks in one place: an ordered path for builders, an ordered path for owners, and a table of all seven written pages with what each one answers.
- [The builder's deck — Project Context](https://projectcontext.monomind.one/guide/builders/): A 19-slide deck for anyone working in a repository: the three records, the session loop, the record model and evidence anchors, installing it, and what the doctor checks afterwards.
- [The owner's deck — Project Hub](https://projectcontext.monomind.one/guide/owners/): A 17-slide deck for anyone overseeing several repositories: scaffold versus instance, the boundary between the two repositories, why a push arrives as a pull request, the budgets, and what a Hub costs.

## Source

- [project-context on GitHub](https://github.com/monomind-ai-lab/project-context): the product installed into a project repository — two skills and one CLI, standard library only.
- [project-hub on GitHub](https://github.com/monomind-ai-lab/project-hub): the scaffold an owner copies into a private repository of their own.