giles
9cfca1d008
Some checks failed
Test, Build, and Deploy / test-build-deploy (push) Failing after 34s
Completes the host ABI from work-queue to driver loop: the host supplies only a (kind payload) -> answer dispatch fn; flow-drive-host services one tick of pending requests, flow-run-host ticks until quiescent (bounded). Tested via the art-dag render -> human-review -> publish pipeline driven entirely by flow-run-host. The art-dag integration is now: define dispatch, call flow-run-host. 166/166, 11 suites. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
54 lines
3.2 KiB
Markdown
54 lines
3.2 KiB
Markdown
# flow-on-sx Scoreboard
|
|
|
|
**All tests pass: 166 / 166 across 11 suites. Phases 1-8 complete.**
|
|
|
|
`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 |
|
|
| control | 31 | Phase 2: `branch` (6); error model `fail`/`failed?`/`fail-reason` (6); `try-catch` (6); `retry n` (6); `timeout` cooperative step budget (7) |
|
|
| suspend | 17 | Phase 3: suspend/resume/cancel via deterministic replay; multi-step, replay determinism, lifecycle guards, suspend-in-branch |
|
|
| recovery | 8 | Phase 3: crash recovery — store export/import, resumable scan, restart-at-every-step, replay-log survival |
|
|
| distributed | 19 | Phase 4: `remote-node` (7); `remote-failover` (6); replication + handoff across instances (6) |
|
|
| api | 12 | Phase 5: introspection — `flow/status`, `flow/result`, `flow/list`, `flow/pending` |
|
|
| combinators | 17 | Phase 5: `tap`, `recover` (fail-value), `map-flow` fan-over-list, `flow-while`/`flow-until` bounded iteration |
|
|
| railway | 10 | Phase 6: `attempt` — fail-value short-circuiting sequence + recover rejoin |
|
|
| integration | 10 | Phase 7: end-to-end order + onboarding flows composing every phase (suspend, branch, federation, crash recovery, handoff, introspection) |
|
|
| hygiene | 9 | Phase 5: `flow/gc` (prune terminal flows), `flow/forget` (drop one terminal record) |
|
|
| host | 15 | Phase 8: host ABI — `request`/`await-human`/`await-render`, `flow-host-requests` queue, `flow-run-host` reference driver; art-dag-shaped render→review→publish loop |
|
|
|
|
## 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
|
|
|
|
- [x] Phase 1 — Declarative DAG + sequential execution (combinators + 18 tests, `flow/start`)
|
|
- [x] Phase 2 — Control flow + error handling (branch, error model, try-catch, retry, timeout)
|
|
- [x] Phase 3 — Suspend/resume (suspend/resume/cancel + crash recovery via deterministic replay)
|
|
- [x] Phase 4 — Distributed nodes via fed-sx (remote-node, failover, replication + handoff)
|
|
- [x] Phase 5 — Operational API + combinators (introspection, tap, recover, map-flow)
|
|
- [ ] Phase 3 — Suspend / resume (the showcase)
|
|
- [ ] Phase 4 — Distributed nodes via fed-sx
|