On this page
All Use Cases
Each use case is one job, from the problem to the point it is done. Its page shows the job on the Online store demo workspace, with a video and links to the docs pages it runs on.
Map a system
Use case · Map a system
Generate a software architecture diagram from a codebase
Point the code plugin at a repository and read its architecture as a layered board: the parts, what they depend on, and the contracts between them.
Usually a developer or an architect, for one repository first
Use case · Map a system
Software architecture mapping for enterprise systems
One board for every system you run, buy or integrate. Each system backed by a repository opens into its own board, read from its code.
Usually a head of architecture or a platform team, across many repositories
Document and explain
Plan a change
Use case · Plan a change
Assess the impact of a proposed architecture change
See which other teams' code a change reaches before it is built, read from their repositories, not the diagram. Then decide, hand off and confirm.
Usually an architect or CTO, with the engineering lead and product
Use case · Plan a change
Catch breaking API changes before a release ships
Compare the app as released with the branch about to ship, and see which endpoints, events and tables the release changes for the systems that call them.
Usually the architect or tech lead signing off a release, with the shipping team
Use case · Plan a change
Understand dependencies across multiple repositories
See who calls each endpoint, subscribes to each event and reads each table, found in the callers' own repositories and traced hop by hop.
Usually an architect or a platform engineer, before a contract changes
Use case · Plan a change
Plan and track a software migration
Put the old app beside its replacement, contract by contract, turn what the new side still owes into work items in waves, and see each one land in the code.
Usually an architect or platform engineer, with the team doing the migration
Use case · Plan a change
Plan a new software project from spec to handover
Place a new system's spec on the landscape you already run, write down its rules and decisions, sequence the work and build the first slice.
Usually an architect or an engineering lead, with the developers who build it
Work with AI agents
Use case · Work with AI agents
Architecture decision records for AI coding agents
Accepted decisions land in the repository as skills the coding agent loads, and every sync checks the code it wrote against them.
Usually an architect or a tech lead, for every developer and their agent
Use case · Work with AI agents
Catch architecture drift while coding agents write the code
Every sync checks the boundaries your team agreed against the code, and each week shows which rules broke, the change that broke them and the fix.
Usually an architect or a tech lead, for every app the agents work in
Last updated November 17, 2026