Skip to content

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.

  1. The 3 A.M. CallRead now · Open draft
  2. The Manifesto: Constrained FreedomRead now · Open draft
  3. One Platform, One Flow ModelRead now · Open draft
  4. First Flow: Incident Triage in Two ViewsRead now · Open draft
  1. Nodes, Pins, Wires, and ExecutionRead now · Open draft
  2. Anatomy of a FlowScript DocumentRead now · Open draft
  3. Values, Types, Collections, and InterfacesRead now · Open draft
  4. Calling the Node LibraryRead now · Open draft
  5. Expressions, Operators, and Readable SugarRead now · Open draft
  6. Branches, Loops, Parallelism, and ReturnRead now · Open draft
  7. State, Configuration, Runtime Values, and SecretsRead now · Open draft
  8. Functions, Layers, Handlers, and CachingRead now · Open draft
  9. Events, Interfaces, and Complete AppsRead now · Open draft
  1. Board ⇄ AST ⇄ TextRead now · Open draft
  2. Identity, Anchors, and Safe Change
  3. The Dual-View Editor and Language Tools
  4. Runs, Logs, Traces, and Versions
  1. Capstone: Build Incident Room
  2. Files, Tables, SQL, and Data Studio
  3. FlowPilot and AI-Authored Software

Part V — Extension, Capability, and Trust

Section titled “Part V — Extension, Capability, and Trust”
  1. Build a Custom WASM Node
  2. The WASM Sandbox: Capabilities, Limits, and Consent
  3. Packages, Governance, Versions, and Release

Part VI — Runtime, Deployment, and Contribution

Section titled “Part VI — Runtime, Deployment, and Contribution”
  1. From Flow to Compiled Artifact to Rust Runtime
  2. Deployment Without Rebuilding the Application
  3. 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.