Files

Test, Build, and Deploy / test-build-deploy (push) Failing after 31s

Details

flow: Phase 1 declarative DAG — sequence/parallel/defflow combinators + 18 tests

Flow combinators as a Scheme prelude loaded onto scheme-standard-env; a flow is a
Scheme procedure input->output, run inside the interpreter (sets up Phase 3 call/cc
suspend). flow/start entry point, conformance runner, scoreboard.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

2026-06-06 16:22:22 +00:00

1.6 KiB

Raw Blame History

flow-on-sx Scoreboard

All tests pass: 18 / 18 across 1 suite.

bash lib/flow/conformance.sh

Per-suite breakdown

Suite	Passing	Covers
basic	18	Phase 1: single nodes, linear sequence, data-flow threading, defflow, parallel fan/join, nested composition, publish-shaped flow

Architecture

Flow combinators are a Scheme prelude (lib/flow/spec.sx) loaded onto scheme-standard-env. A flow is a Scheme procedure input -> output. The whole flow executes inside the Scheme interpreter, so Phase 3's suspend (call/cc) will capture the flow continuation directly.

lib/flow/spec.sx — combinators: flow-node, flow-id, flow-const, sequence, parallel, defflow; flow-load-combinators!.
lib/flow/api.sx — flow/start (Scheme); flow-make-env, flow-run, flow-run-in (SX helpers).
lib/flow/tests/basic.sx — 18 cases.
lib/flow/conformance.sh — loads substrate + flow layer, runs suites.

Semantics notes

node = 1-arg Scheme procedure; the upstream value is the argument. A node ignoring its argument is effectively a thunk.
sequence threads left-to-right; empty sequence = identity.
parallel fans the same input to every branch and joins results into a list. Evaluation is sequential for now; true concurrency arrives in Phase 3.

Phases

[~] Phase 1 — Declarative DAG + sequential execution (combinators + 18 tests done; flow/start done)
Phase 2 — Control flow + error handling
Phase 3 — Suspend / resume (the showcase)
Phase 4 — Distributed nodes via fed-sx

1.6 KiB Raw Blame History