Ampandheaust
d4e8634f67
Amp-Thread-ID: https://ampcode.com/threads/T-019f9d91-77c1-7206-a60f-ed6554ce92ab Co-authored-by: Heaust Azure <heaust.azure@gmail.com>
790 B
790 B
Concepts
For integrators deciding where application responsibilities end and fxnode authority begins. Read in this order:
- Worker authority: locate truth, work, and the asynchronous host boundary.
- Composition: model the application's graph language and live updates.
- Graph state and events: reason about documents, receipts, versions, and observation.
- State and persistence: choose runtime replacement, canonical export, or replayable persistence.
Afterward you should be able to choose the correct API and concurrency domain, predict publication order, and design durable loading without treating fxnode as a graph evaluator. fxnode is an editor and presenter, not an evaluator.