AgentCanvas / Pages / Developer Guide / Core / Decisions
ADRs are append-only. Decisions that are superseded keep their original file and link forward to the replacement; the legacy ones live under _legacy/ in v1. Use this index when you need to know why something is the way it is, not what it is — for the "what", see glossary or architecture.

Fields

canvas

Decisions about the editor surface: how graphs are laid out, composed, nested, and stored. Covers the transition from a fixed two-layer canvas to a flat ComfyUI-style workspace, the unified editor tha…

3 ADRs · canvas/

components

Decisions about how node authors extend the platform: the universal base class, the auto-discovery contract, the Python-driven UI system (no .tsx per node), the nodeset rename, the layout-component …

10 ADRs · components/

dataflow

Decisions about what flows between nodes, where persistent data lives, and how boundary nodes (PortIn/Out, IterIn/Out, Initialize) shape the graph topology. Wire types and state containers are kept di…

9 ADRs · dataflow/

eval

Decisions about batch evaluation: how eval reuses the canvas execution engine (graph-driven, not bespoke pipelines), worker-pool concurrency for env-side throughput, and the batched-inference tier for…

4 ADRs · eval/

executor

Decisions about the scheduling algorithm: when a node fires, what counts as a seed, how iteration cycles are expressed at runtime, and where graph validity is enforced. Distinct from [dataflow](../dat…

4 ADRs · executor/

observability

Decisions about what the framework reveals at runtime: execution_id routing so concurrent runs don't cross streams, shell hooks for external interception, the two-layer execution log system (automat…

5 ADRs · observability/

platform

Decisions that shape the platform as a whole rather than any one subsystem: the framework's zero-domain-knowledge principle, the single-endpoint run API, layered LLM config resolution, the Python-env …

8 ADRs · platform/

server

Decisions about running nodesets in isolated subprocesses: auto-generating HTTP servers from PortDefs, mounting control-plane routes alongside tool-call routes, and bridging controllers transparentl…

4 ADRs · server/

All ADRs by field

FieldCountMost recent
canvas3adr-canvas-003 · 2026-03-31
components10adr-components-010 · 2026-07-04
dataflow9adr-dataflow-009 · 2026-06-11
eval4adr-eval-004 · 2026-05-15
executor4adr-executor-004 · 2026-05-25
observability5adr-observability-005 · 2026-05-10
platform8adr-platform-008 · 2026-06-11
server4adr-server-004 · 2026-06-15