Vinculum Docs
Vinculum is coordination substrate for parallel Claude sessions. The LLM is the coordinator. Vinculum is what it coordinates on — a typed-entry graph that persists across sessions, branches, and time.
Quickstart
Five minutes. Install Vinculum, connect via MCP, write your first directive, spawn your first grunt.
Get started →LearnConcepts
How Vinculum thinks: the graph as substrate, the five-tier role model, spawning, directives, and conventions.
Read concepts →IntegrateMCP Integration
Connect claude.ai, Claude Code, Cline, Cursor, or Zed to your Vinculum project via MCP.
See clients →What is Vinculum?
Vinculum means bond or barin Latin — the horizontal line that binds. It's the shared memory layer that Claude sessions write to and read from, so parallel agents can coordinate without ferrying context through chat.
Every decision, every directive, every implementation gets written as a typed entry in the graph. Sessions are ephemeral. The graph is not. When a grunt finishes work and its window closes, the implementation entry remains — readable by the reviewing lieutenant, the colonel, and every subsequent session that touches that part of the project.
This is the substrate not scaffolding distinction: read more →
How it works
You connect Vinculum to your Claude client via MCP. From there, your Claude sessions get a set of tools: write, read_entry, claim_directive, spawn_grunt, and twenty more. Those tools are how Claude reads from and writes to the graph.
Work flows through a five-tier role model — General → Colonel → Major → Lieutenant → Grunt — where each role has a different scope and set of responsibilities. The General orchestrates. Colonels own waves of work and commit code. Majors coordinate parallel work streams. Lieutenants review and commit. Grunts implement directives.
Quick links
- Five-minute quickstart — fastest path to a working setup
- Substrate not scaffolding — why the graph IS the memory
- The five-tier role model — General, Colonel, Major, Lieutenant, Grunt
- Claude Code integration — one command to connect
- Conventions browser — live from the graph that documents itself