Systems and software architecture
Map clients, services, data stores, APIs, queues, models, agents, and infrastructure with connectors that remain attached.
Flexible enough for the rough idea. Structured enough for the diagram that explains it later.
Map clients, services, data stores, APIs, queues, models, agents, and infrastructure with connectors that remain attached.
Show orchestration, tool calls, memory, evaluation, approvals, retries, and failure paths.
Turn requirements into user journeys, onboarding, states, and decision trees.
Document intake, approvals, handoffs, exceptions, escalation, and completion. Use lanes to make ownership visible.
Collect ideas with sticky notes, cluster them, frame themes, and leave with an organized outcome.
Sketch interfaces, connect screens, share for critique, and generate an HTML starting point for engineering review.
Prompts worth trying
The Canvas assistant can turn intent, stages, decisions, and ownership into a first editable structure.
“Create a left-to-right retrieval pipeline grouped into Ingest, Retrieve, Generate, and Observe.”
“Draw an agent loop with planning, tool execution, validation, retry, and human escalation.”
“Map support escalation across Frontline, Specialist, and Engineering, including the return path.”
“Map sign-up through verification, with recovery paths for an expired link or forgotten password.”
Teach and explain
Use labeled connections, visual categories, frames, and a laser pointer to walk people through the model. Send a read-only snapshot when the final state should travel without editing access.