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 with the complete round trip: lowering a Board into BoardAst,
rendering canonical text, parsing edits, reconciling semantic differences, and applying atomic
Board commands. It then examines the identity anchors, deterministic corrections, deletion guards,
undo batches, and scoped editing rules that keep those changes bounded. Later chapters in the
first-edition plan will continue with 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 establishes FlowScript as an authoring language over the executable Flow model. The Board remains the runtime program.
Part III · Open edition · 2026
Chapters in this part
- 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.
- 15
Identity, Anchors, and Safe Change
Learn how FlowScript anchors preserve Board identity, how reconciliation repairs deterministic drift, and how deletion guards, atomic Apply, and scoped editing protect existing work.