use cases

An agent monitors a codebase via git hooks or CI and maintains an always-current architecture diagram as a persisted scene. On each PR, it scans for new services, endpoints, and database tables, then applies incremental ops to the existing diagram. Reviewers diff revision N vs N-1 to see exactly what changed architecturally.

On every commit that touches database migrations (Prisma, Drizzle, Alembic), a CI step parses migration files and creates or updates an ER diagram with compartmented entity boxes showing columns, types, PK/FK badges, and crow's-foot cardinality from foreign key definitions.

During an incident, an agent generates a focused topology diagram showing affected services and their connections. As the incident evolves, it applies ops to update status - each update creates a new revision. The incident timeline is captured in diagram revisions: "here's what the topology looked like when the DB went down vs after the failover."

An agent researches a company or product idea, then creates a structured lean canvas using frames for the 9 sections (Problem, Solution, Key Metrics, Unique Value Prop, etc.). It populates each section with research findings and uses constraints for automatic layout. The canvas evolves as the agent learns more.

When building multi-agent systems, an orchestration agent creates a BPMN-style workflow diagram showing each agent's role, tools, and data flow. As agents are added or removed, ops update the diagram. Validation ensures the workflow is structurally sound. The diagram serves as both documentation and a runtime artifact.

An agent scans OpenAPI specs across microservices and creates a service topology diagram with edges representing API calls. Labels show endpoint paths and HTTP methods. Auto-layout arranges services hierarchically. On each deploy, the agent updates the diagram with new or removed endpoints.

For regulated industries, an agent generates data flow diagrams showing where PII moves through the system. Edges are labeled with data types. Revision history provides an audit trail - "at this date, this is what the data flow looked like." Validation rules enforce compliance patterns.

An agent reads HR system data and generates structured person cards with name, title, department color accent, and avatar icons. Hierarchical auto-layout positions the tree. Solid edges for direct reports, dashed for matrix relationships. The chart updates automatically as the org changes.

When a new engineer joins, an agent reads the codebase and generates a progressive series of architecture diagrams - starting simple (high-level services) and adding detail (databases, queues, caches). Each diagram is a revision of the same scene, so the engineer steps through complexity levels.

In a PR that changes system architecture, an agent generates a before/after diagram pair using scene diffing. Added nodes in green, removed in red, modified edges in yellow. Posted as a PR comment, reviewers see the architectural impact at a glance.