Files
zeekay f9db4f5737 Publish under the org, not a person
Bylines, paper authorship, correspondence addresses and the founder blurb under
each post named an individual. They name the organisation that published the
work instead: the brand on posts and pages, the research byline on papers, and
research@ in place of a personal address. Both are what these repositories
already used elsewhere — nothing new was coined.

Co-authors are untouched. Where a paper named someone else alongside, they stay
named; only the one byline changed. Bibliography entries, running heads,
PDF metadata and affiliations move with it, so a citation still resolves to
whoever the cited paper names.

Sample and fixture data uses the placeholder name these tests already use
elsewhere, so no assertion changed meaning.
2026-09-01 08:53:13 -07:00

67 lines
3.0 KiB
TeX

% Hanzo Flow: Visual Workflow Builder for AI Agent Orchestration
\documentclass[11pt,twocolumn]{article}
\usepackage{../shared/hanzocover}
\usepackage{amsmath, amssymb, amsthm}
\usepackage{mathtools}
\usepackage{bm}
\usepackage{graphicx}
\usepackage{booktabs}
\usepackage{hyperref}
\usepackage{enumitem}
\usepackage{algorithm}
\usepackage{algpseudocode}
\usepackage{xcolor}
\usepackage{float}
\usepackage{subcaption}
\usepackage{multirow}
\usepackage{listings}
\input{../shared/lstlang}
\usepackage[numbers]{natbib}
\hypersetup{colorlinks=true,linkcolor=black,citecolor=blue,urlcolor=blue}
\newtheorem{theorem}{Theorem}
\newtheorem{lemma}[theorem]{Lemma}
\newtheorem{definition}{Definition}
\newtheorem{proposition}[theorem]{Proposition}
\newtheorem{corollary}[theorem]{Corollary}
\lstset{
basicstyle=\ttfamily\small,
breaklines=true,
frame=single,
numbers=left,
numberstyle=\tiny,
xleftmargin=2em,
}
\title{Hanzo Flow: Visual Workflow Builder for AI Agent Orchestration}
\author{
David Wei \quad
Marcus Chen \quad
Hanzo AI Research \\
\textit{Hanzo AI Research} \\
\texttt{[email protected]}
}
\date{April 2025}
\begin{document}
\hanzocoverpage
\begin{abstract}
We present \textbf{Hanzo Flow}, a visual workflow builder for constructing, debugging, and deploying multi-agent AI systems. While code-based agent frameworks provide flexibility, they impose high barriers to iteration, lack visibility into agent decision-making, and make debugging multi-agent interactions intractable. Hanzo Flow introduces three innovations: (i) a \emph{typed dataflow graph} formalism where nodes represent agent operations (LLM calls, tool invocations, control flow, human-in-the-loop gates) and edges represent typed data channels, enabling static verification of workflow correctness before execution; (ii) a \emph{visual debugger} with execution replay, token-level attribution, and branching exploration that reduces debugging time by 67\% compared to log-based debugging; and (iii) an \emph{adaptive execution engine} that supports parallel branch execution, dynamic subgraph expansion, and automatic retry with model fallback, achieving 94\% end-to-end success rate on complex multi-step tasks. We evaluate Hanzo Flow on the AgentBench suite, a novel visual workflow benchmark (FlowBench-200), and a user study with 48 developers. Results show that visual workflow construction reduces development time by 3.2x compared to code-based frameworks while achieving equivalent or superior task completion rates. Hanzo Flow has been used in production to build 1,200+ workflows processing 8.4 million agent invocations over 10 months.
\end{abstract}
\input{sections/01-introduction}
\input{sections/02-typed-dataflow-graphs}
\input{sections/03-visual-debugger}
\input{sections/04-adaptive-execution-engine}
\input{sections/05-workflow-patterns}
\input{sections/06-evaluation}
\input{sections/07-production-deployment}
\input{sections/08-related-work}
\input{sections/09-discussion}
\input{sections/99-conclusion}
\end{document}