Complete contents
The open 2026 edition currently includes the introduction and Chapters 1–14. Chapters 15–26, the epilogue, and the appendices are planned and are not yet published. Available chapters are marked Read now · Open draft; the remaining chapter briefs live in the editorial blueprint.
- The 3 A.M. Call — Read now · Open draft
- The Manifesto: Constrained Freedom — Read now · Open draft
- One Platform, One Flow Model — Read now · Open draft
- First Flow: Incident Triage in Two Views — Read now · Open draft
- Nodes, Pins, Wires, and Execution — Read now · Open draft
- Anatomy of a FlowScript Document — Read now · Open draft
- Values, Types, Collections, and Interfaces — Read now · Open draft
- Calling the Node Library — Read now · Open draft
- Expressions, Operators, and Readable Sugar — Read now · Open draft
- Branches, Loops, Parallelism, and Return — Read now · Open draft
- State, Configuration, Runtime Values, and Secrets — Read now · Open draft
- Functions, Layers, Handlers, and Caching — Read now · Open draft
- Events, Interfaces, and Complete Apps — Read now · Open draft
- Board ⇄ AST ⇄ Text — Read now · Open draft
- Identity, Anchors, and Safe Change
- The Dual-View Editor and Language Tools
- Runs, Logs, Traces, and Versions
Part IV — Building a Real Application
Section titled “Part IV — Building a Real Application”- Capstone: Build Incident Room
- Files, Tables, SQL, and Data Studio
- FlowPilot and AI-Authored Software
Part V — Extension, Capability, and Trust
Section titled “Part V — Extension, Capability, and Trust”- Build a Custom WASM Node
- The WASM Sandbox: Capabilities, Limits, and Consent
- Packages, Governance, Versions, and Release
Part VI — Runtime, Deployment, and Contribution
Section titled “Part VI — Runtime, Deployment, and Contribution”- From Flow to Compiled Artifact to Rust Runtime
- Deployment Without Rebuilding the Application
- Internals: Protecting the Round Trip
Epilogue — Make the System Explain Itself
Section titled “Epilogue — Make the System Explain Itself”The book returns to the incident room and asks what changes when structure, permissions, data, versions, run history, and the failing operation are available to the people responsible for the system.
The complete subchapter plan, evidence dependencies, and interview requirements are maintained
in STRUCTURE.md at the root of this app.