heaust/yawn
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: add render graph driven renderer architecture

Browse Source 
Amp-Thread-ID: https://ampcode.com/threads/T-019f9d91-77c1-7206-a60f-ed6554ce92ab

Co-authored-by: Heaust Azure <heaust.azure@gmail.com>
This commit is contained in:
Amp
2026-07-27 02:53:44 +00:00
co-authored by heaust
parent 8a8369706b
commit d4e8634f67
290 changed files with 48804 additions and 1995 deletions
Download Patch File Download Diff File Expand all files Collapse all files
vendor/fxnode/docs/learn/concepts/index.md
Vendored
+10
View File
@@ -0,0 +1,10 @@
# Concepts
For integrators deciding where application responsibilities end and fxnode authority begins. Read in this order:
1. [Worker authority](./worker-authority): locate truth, work, and the asynchronous host boundary.
2. [Composition](./composition): model the application's graph language and live updates.
3. [Graph state and events](./graph-state-and-events): reason about documents, receipts, versions, and observation.
4. [State and persistence](./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.