Executor — ADRs
Architecture decisions in the executor field.
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 — dataflow is about what moves between nodes and where it lives; executor is about the firing algorithm that moves it.
| ID | Title | Date | Status | Supersedes |
|---|---|---|---|---|
adr-executor-001 |
Dataflow executor with IterIn/IterOut gates | 2026-03-22 |
accepted | — |
adr-executor-002 |
Three-pivot scheduling: seed rule + pairedWith transfer + validate_graph_connectivity |
2026-04-18 |
accepted | — |
adr-executor-003 |
Multi-scope execution — per-scope state, settle isolation, portOut latch propagation | 2026-05-09 |
accepted | — |
adr-executor-004 |
Dynamic Fire-List dispatch — runtime-emitted child firings inside static topology | 2026-05-25 |
accepted | — |
Related
Related: the dataflow-side half of the three-pivot change (boundary-node typology Initialize / iterIn / iterOut and ports_mode="source" / "sink") is dataflow/adr-dataflow-006. The dataflow-side half of the multi-scope change (multiple three-pivot triples in one graph; portIn/portOut as inner-scope IO interface; topology-determined nesting) is dataflow/adr-dataflow-007.