Begin in an outage
Enter the major incident and the question it left behind before learning syntax.
FLOW-LIKE DEVELOPER GUIDE OPEN EDITION · 2026
FlowBook.
A developer's guide to Flow-Like.
A Flow is executable workflow logic. Edit it as FlowScript, Flow-Like's typed text form, or on the canvas as a visual graph. Connect the systems you already run and follow Incident Triage into runtime evidence.
01 INTRODUCTION 02 15 CHAPTERS 03 PDF + WEB
01 / ABOUT THE BOOK INCIDENT-LED EXPLANATION
Learn from a system under pressure
FlowBook begins inside the 3 a.m. outage that raised its central question: why did everyone have to wait for the one person who understood the system? From there, it builds a Flow, or executable workflow, in FlowScript, Flow-Like’s typed text form, and on the canvas.
Open the introductionBuild Incident Triage
Create a deterministic incident classifier with no model, API key, or external service.
Inspect both authoring views
Read the same typed program as compact FlowScript and as a visible graph.
Trace a failure
Follow a bad input to the node and runtime evidence that explain the failure.
02 / THE METHOD FROM PROBLEM TO RUN EVIDENCE
Connect source to the graph it creates
Each construct starts with the problem it solves. The chapter then follows its FlowScript form into the canvas and the evidence left by execution or failure.
SOURCE ↔ GRAPH RUNTIME EVIDENCE
03 / CURRENT EDITION 15 CHAPTERS · 3 PARTS
Follow the current edition from incident to implementation
The current open edition contains the introduction and Chapters 1-15. Read from the founding incident through a complete application path, or jump directly to the language chapters.
See the first-edition plan BEGIN HERE INTRO
One program, two ways to see it
Meet the book’s central question, then follow one Flow from existing systems into governed execution.
PART I 01-04
Software That Explains Itself
Begin with the founding incident, establish the operating principles, and build the first Flow through both authoring views.
PART II 05-13
Thinking and Writing in Flows
Learn the language through the graph it represents: values, operations, control flow, state, and governed runtime boundaries.
PART III 14-15
The Two-Way Contract
Open the machinery that keeps the visual Board and canonical FlowScript aligned through typed meaning and guarded changes.
Next in the first-edition plan: the two-way implementation contract, Incident Room capstone, extensions, governance, runtime, and deployment.
04 / PDF EDITION PRINT EDITION FROM THE WEB SOURCE
Download the print edition
The downloadable edition is built from the same source as this website, with a cover, linked contents, page numbers, running heads, chapter bookmarks, and print-ready A4 pages.
Download the PDFOpen edition · 2026 · 15 chapters · PDF
Flow-Like Open edition · 2026
ONE EXECUTABLE FLOW
FlowBook
A Developer's Guide to Flow-Like
PDF EDITION 15 CHAPTERS
READ THE OPEN EDITION
Choose the edition that fits your reading
Read FlowBook chapter by chapter with web navigation and search, or download the current manuscript as one PDF. Both editions come from the same source.
