MonoMind project-context

Guides & decks

Everything written down, in one place.

Two products, two audiences, and nine documents between them. A builder works inside one repository and never sees a Hub; an owner administers several and never opens the code. Start from whichever describes you — the paths below are ordered, not just listed.

  • 2 decks
  • 7 written guides
  • nothing to install
01 start here

Which one are you?

If you are about to change something in a repository, take the first path. If you are deciding what applies across several repositories you do not work in daily, take the second. Each is three steps, and each ends where the reference material begins.

02 the slide decks

To show someone, rather than send them

A deck argues; a guide answers. These are built to be read across a room by someone who has not decided yet — and to hold up afterwards as a reference, since the menu lists every slide by name.

19 slides · project-context

The builder's deck

What the three core summaries and five operational kinds are, the session loop, the record model and evidence anchors, installing it, and what the doctor checks afterwards.

Open the deck 17 slides · project-hub

The owner's deck

Scaffold versus instance, the boundary between the two repositories, why a push arrives as a pull request, the budgets, and what a Hub costs you.

Open the deck

Move through it

Arrow keys, Space, PageUp / PageDown, Home and End. Scroll or swipe works too. On a phone a deck becomes a vertical read rather than a slideshow.

Jump anywhere

The Contents item in the menu lists every slide by name, built from the slides themselves so it cannot drift out of step. Your position is remembered if you close the tab and come back.

Take it with you

The menu will save the deck a copy of itself — one file, no assets folder, opening exactly as it does here. There is a light theme in there too. Both decks are English only; command text and file names would not survive translation anyway.

03 every written page

The whole set, and what each one is for

Seven pages, each answering something the others deliberately leave alone. If two seem to overlap, the narrower one is right and the broader one should be linking to it.

Page What it answers For
Quick guide Will this fit my project, what does a real record look like, and what happens in a session? Builders, first
Install What is written to my repository, what is never touched, and how do I undo it? Builders
Core and operational records What goes in each file, what stays out, and what a good entry looks like beside a bad one. Builders
Operating the loop What do I actually do from now on, and what should exist by the end of week one? Builders, day 2
Builder's guide The reference layer: authority, frontmatter, lifecycles, the reference grammar, capture, retrieval, the pushed set. Builders, month 2
Project Hub What a Hub is, what it is not, what never travels, and whether to run one. Owners, first
Owner's guide Every command, flag, gate, refusal and budget, and an honest list of what is not built. Owners

Use cases sits outside this set on purpose: it is not a guide but an argument that the same three core summaries and five operational kinds work for a manuscript, a research corpus or a client engagement, not only for code.

04 the source

All of it is in the repositories too

Nothing here is generated from something you cannot read. Every page on this site is written against the code it describes, and both products are plain Markdown and Python with no runtime dependency.

github monomind-ai-lab/project-context github monomind-ai-lab/project-hub

Clarity comes with context.