GraphReFly Blog
Legacy TypeScript website content. Shared public website, blog, protocol, guide, and language-neutral docs ownership now lives in
~/src/graphreflyunder D563. This page is retained here only as migration/reference material while the TS API generator still lives inwebsite/.
Engineering essays from the GraphReFly project — what it takes to build a reactive harness around probabilistic models: deterministic structure you can describe, trace, and improve, with room for people and LLMs in the loop.
The GraphReFly Chronicle
Section titled “The GraphReFly Chronicle”An evolving collection of posts on that harness — the reactive graph engine, the protocol, and the product-shaped layers on top — not a closed syllabus, but themes we revisit as the spec and implementations move.
Where it started — Motivation, the limits of plain signals, and why protocol-first thinking is load-bearing for anything you want to inspect or govern.
How the graph behaves — Push and pull phases, fan-in and diamonds, memoization, and the lifecycle of a node once the topology gets honest enough to serve as execution substrate.
Speed, safety, and the surrounding system — Performance experiments, correctness tradeoffs, and the orchestration, policy, and platform questions — stores, streaming, tooling — that show up once the core model has to carry real agent workflows.
New pieces land here over time. For one continuous story of the reboot, see From callbag-recharge to GraphReFly: Why We Started Over. To read from the earliest essay, start with The Road to GraphReFly. Browse the sidebar for the full archive.