Vinc

The book

This is the Vinc Book: thirty-five chapters in five parts and a closing, on why memory has to become a system and whether the system Vinc built was the right one.

Read it in order. Each chapter ends by handing off to the next one by number, and every part builds on the one before it. If a word is new, the chapters do not stop to define it twice: the vocabulary is installed once, on the What Vinc is page, and it is worth ten minutes before Chapter 1.

Who this is for

The reader who has time rather than a task. Nothing here is a procedure, and no chapter asks you to have Vinc installed. If what you want is a working graph in five minutes, this is the wrong page: take the Quickstart instead, and come back when you want to know why it is shaped that way.

Part 0. Why Turn Memory into a System

Why memory has to become a system at all. This is the part with no prerequisites: it argues from how people have carried memory forward, not from how Vinc is built.

Part 1. How Memory Is Stored

What Vinc stores and in what shape: the node kinds, the relations and the pairs they are allowed between, documents and chunks, the vocabulary, and the writing contract.

Part 2. How Memory Is Found and Handed Out

Search, embedding, resolution, the brief, MCP, roles and provenance: the path from a question to material an Agent can act on, and what the system does when it cannot tell.

Part 3. Where Memory Lives: Time and Space

The three time axes, the View, how graph space is made, how causal order becomes position, and what density can and cannot show.

Part 4. Was the Design Actually Right

The part that argues from measurements rather than from principles: the conditions a measurement needs, call efficiency, comparing embedding models, what a rebuild costs, and the failures that looked like successes.

Closing

Memory is a cycle: record, structure, search, interpret, use, measure, decide, record again.