Claude Code can work on a client's map in VSTA for you. It reads the map, changes it when you ask, and builds a whole map from a project's files in one import. It does this through a connection that you make on the client's Connect Claude page.

Who can connect

Only a facilitator of the client can make a connection or use one. Editors and readers do not see the Connect Claude page.

A connection belongs to you and to one client. Claude can only see and change that client's map through it. If you work with two clients, make a connection on each.

Make one connection for each computer you use Claude on, so you can remove one without stopping the others. On one computer, Claude Code holds one connection to each client, named vsta-<client address>, such as vsta-ledgerline.

A connection does not expire. VSTA checks on every request that you are still a facilitator of the client, so it stops working when you stop being one.

What Claude can read

Claude Code shows each VSTA tool by name when it uses it. These tools read the map and change nothing:

  • get_organisation reads the client's name and the whole map in summary.
  • get_value_stream reads one value stream with its layers, stages and bands.
  • get_stage reads one stage, its practices and the relations between them.
  • get_practice reads one practice in full.
  • search finds value streams, stages and practices by part of their name.
  • list_items, list_kinds and list_practices list the tools, roles and other items, the kinds of practice, and every practice.

What Claude can change

run_commands changes the map. Claude sends a list of up to 200 changes, such as adding a stage, renaming a practice or adding a relation. VSTA makes them in order and stops at the first one it refuses. Each change is saved as it is made, and each one appears on the Changes page under your email address.

Ask Claude to show you the changes before it sends them.

What an import is

An import builds or updates a map from a project's files in one go. Claude reads the project and writes everything into one import document. Then it uses two tools:

  • preview_import checks the document against the map and reports what an import would add and change. It writes nothing.
  • apply_import makes those changes, all of them or none.

An import never deletes or moves anything, and it never overwrites a change someone made in VSTA. Import a project walks through one.

Stated and inferred relations

When Claude adds a relation between two practices, it marks it as stated (the source says so) or inferred (Claude worked it out). Facilitators and editors see that mark in VSTA, and can change it. Readers see the relation without it. Stated and inferred relations explains more.