One page per job a team repeats: the problem, how it goes in ProvenMap, what it looks like, what it works with and where it stops.
Usually an architect or CTO, with the engineering lead and product
See what a change reaches before anyone builds it: the systems, the contracts other teams call, who depends on them. Then decide, and let the sync confirm it.
Usually an architect or a tech lead, for every developer and their agent
The conventions compiled into the repository as files the agent loads, the change handed over anchored to its code, and a sync that checks what it built.
Usually an architect or a tech lead, for the whole team
A board drawn from the code and redrawn on a schedule, with the old document's decisions adopted beside it, published as the link people open instead.
Usually an architect or a platform engineer, before a contract changes
Every app's contracts read from its own code and folded into one view: the consumer in the other repository named, traced hop by hop, and told when it changes.
Usually an architect, for a CTO, a product manager or operations
One board drawn for the person who has to understand it, published as a link they open without an account, and a run that ends when they say it landed.
Usually a developer or an architect, for one repository first
Bind one system to its repository and let the code plugin map what is inside: a layered board drawn from the code on your machine, kept current by sync.
Usually a head of architecture or a platform team, across many repositories
One root board for every system you run, buy or integrate, and one app for every repository beneath it, kept in sync both ways and read by every role.
Usually a CTO or an engineering lead, before a reorganisation
Tag each system with its owning team, then roll the architecture up into a team map with every dependency between teams on it, published as a link.
Usually an architect or an engineering lead, with the developers who build it
A written spec turned into a landscape, an app with a target sketch, sequenced work items and compiled skills, and a first slice built in an empty repo.
Start with one system
Open one repository and run the code plugin. No migration, no rollout, no diagramming.
No credit card · Analysis runs locally in your own session · Self-hosted available
See the four commands to your first board →
Or for writing on architecture that stays connected across systems.