Skip to content
FlowBook

Part III — The Two-Way Contract

Two editable views are only trustworthy when neither view quietly destroys what the other one owns. Part III explains the contract that lets a Flow move between its persisted Board, a typed semantic model, and canonical FlowScript while preserving identity, layout, and runtime meaning.

The current open edition begins this part with the complete round trip: lowering a Board into BoardAst, rendering canonical text, parsing edits, reconciling semantic differences, and applying atomic Board commands. Later chapters in the first-edition plan will continue with identity anchors, safe change, language tools, and run evidence; they will become links here only when substantive chapters are available.

This part is especially useful for developers building editor integrations, reviewers evaluating AI-authored changes, and architects who need to understand which representation owns which facts. It also explains why FlowScript is an authoring language over the executable Flow model—not a parallel runtime with its own hidden semantics.

Part III · Open edition · 2026

Chapters in this part

  1. 14

    Board ⇄ AST ⇄ Text

    Learn how Flow-Like lowers a Board to a typed AST, renders canonical FlowScript, reconciles semantic edits, applies atomic patches, and preserves identity.

See the complete FlowBook plan