ADK orchestration callbacks ported to MAF WorkflowBuilder executors where you own the loop — a start executor routing messages through agent-executor nodes and edges you control
Guided views
Explore this system
Step through curated paths without changing the source diagram.
Beat
Next
ReadyChapter 01 / 01
Guided chapter
Diagram guideExplore this system
Inspecting compiled semantics
E ExportT ThemeS Style0 Reset+ Zoom in- Zoom outEsc Close
Find a node
⌕/
No matching nodes
Semantic passport
Verified source
Authored reach
Route probeChoose a start node
Pick two semantic nodes on the diagram
Choose the source, then the destination. Direction matters.
Semantic lensCompare system roles
Choose up to two semantic kinds. One reveals its real traffic; two compare only direct authored relationships.
Choose a kind to inspect its nodes and touching relationships.
Semantic radar
Building overview
Click nodeDrag to pan
You Own the Loop
• A start executor is the entry node
• Edges are yours, not framework callbacks
• Control flow is explicit in the graph
Ported Executors
• ADK agents become MAF agent-executor nodes
• The router dispatches to the right executor
• Callbacks turn into routed edges
Iterate
• An executor can send control back to the router
• The loop is data on edges, not hidden hooks
• Termination reaches an explicit finish node
Workflow diagram • Built with Archify • Create yours ↗ • Hover to trace • R route • Click to focus • +/− zoom • M radar • [/] views • P play story • T theme • E export