GRAPH.md

Filled from your own map.

You do not type the topic list or the vocabulary. Those are already in your graph, so they get copied across. What you write by hand is only what the store cannot know.

Three ways to generate it

From no effort to full control. Most people start at the first and end up at the second.

Do nothingA connected assistant already gets a default with your topics and vocabulary filled in. Useful on day one, and it costs you nothing.
Generate, then editBuild the file, keep the copied region, and rewrite the prose to suit how you actually think. This is the normal path.
Write it yourselfIgnore the template and write the sections from scratch. Keep the markers and the copied region still refreshes.

In the app

The conventions button in the top bar opens a sheet. Conventions on top, vocabulary waiting for you underneath.

Yours to writeAn editable box: node kinds, how big a concept is, what not to do.
Copied acrossShown in a dashed box, not editable. Not because it is precious, but because the next rebuild would overwrite your edit anyway.
RebuildSaves your edits first, then rewrites only the copied region. Your own lines stay.
The conventions document does not appear in your document list. It is not material, it is the agreement about material, so it stays out of search results too.

On the command line

The same thing, as a command. Writing it to a file is handy if you keep it in a repo or paste it into a chat.

vinc graph-md build --owner you --out GRAPH.md

Hand it an existing file and it becomes an in place refresh: only the copied region is rewritten and the header date is stamped again. Pass --lang ko for a Korean file, or --doc to keep it inside Vinc instead of on disk.

vinc graph-md build --owner you --file GRAPH.md
If the markers are missing it stops rather than guessing where the region was. Put them back and run it again.

Approving vocabulary

When your assistant uses a type outside the vocabulary, it is not thrown away. It is kept as proposed and collects at the bottom of the conventions sheet. The number on the top bar icon is how many are waiting.

Approve one and it becomes your vocabulary, so the next rebuild carries it in the copied region. Your assistant reads that and uses the name from then on. This loop is how the conventions actually stay alive.

ApproveAdds it to the vocabulary. It appears in the file from the next build.
RejectDrops it from the vocabulary. Data already filed under it stays where it is.
RenameFor the ones worth keeping where only the name is off.
An assistant cannot approve its own proposal. Approving is not exposed over MCP and lives only in the app. That asymmetry is deliberate.

Keeping it true

Topics accumulate. Vocabulary changes when you approve. The moment the copied region stops matching the real map, this file becomes a document that lies, and the assistant follows the lie exactly.

Rebuild when your topics have shifted, not on a schedule. Weekly updates are not the point. Validation tells you when it has drifted.