λx.xDocs← app
documentation

Vinculum Docs

Vinculum is coordination substrate for parallel AI sessions. The LLM is the coordinator. Vinculum is what it coordinates on — a typed-entry graph that persists across sessions, branches, and time.

VinculumdocsQuickstartConceptsMCPArchitectureAPISelf-HostingConventions

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 dozens more. Those tools are how Claude reads from and writes to the graph.

Work flows through a five-role model — Colonel, Major, Lieutenant, Sergeant, and Private — that all answer to you, the General. Colonels and Majors translate your intent into routed work. Lieutenants decompose a brief into worker directives and commit the result. Sergeants and Privates execute those directives. The General is the human; everything below is a Claude session.

Quick links