扩展 Foldkit 应用的软件包 向外——代理、服务器、其他设备、网址和设计系统—— 不给它留第二档以保存州。

Foldkit 应用程序是一个状态机：一个 Schema 类型的 Model，一个 消息工会列出所有可能发生的事情，并纯属**update** 将消息转换为下一个模型和一些命令的函数。那个形状 很容易推理、测试和重放。一旦应用发展成 在钩子中缓存，URL中的存储，重新实现工具处理程序 过渡层，或者带有自身缩减器的同步层。

这个仓库里的所有东西都保留一个状态机。代理只能 发送消息update已处理。服务器数据存储在模型中，且 由update对调。副本通过相同的方式重放相同的消息 update。URL和本地存储镜像模型的一部分;它们从不拥有 一。视图从外部样式设计，无需分叉。每个包回答一个 问题，它们之所以会构成，是因为它们在明确的应用边界上相遇。

网站： foldkit-plus.pages.dev 包含每个包的指南和API引用，以及演示，每个都是示例

foldkit-plus

Packages that extend a Foldkit application outward — to agents, servers, other devices, the URL, and design systems — without giving it a second place to keep state.

A Foldkit application is one state machine: a Schema-typed Model, a Message union naming everything that can happen, and one pure update function that turns a Message into the next Model and some Commands. That shape is easy to reason about, test, and replay. It gets lost the moment an app grows a cache in a hook, a store in the URL, a tool handler that re-implements a transition, or a sync layer with its own reducer.

Everything in this repository keeps the one state machine. An agent can only send Messages update already handles. Server data lives in the Model and is reconciled by update. Replicas replay the same Messages through the same update. The URL and local storage mirror a slice of the Model; they never own one. Views are styled from outside without forking. Each package answers one question, and they compose because they meet at explicit application boundaries.

The website: foldkit-plus.pages.dev has each package’s guides and API reference, and the demos, each an example from this repository built as static files. Those with a server run it in your browser, shared by every tab, so nothing you do leaves it:

• A blog studio and its site (examples/cms): Drafts beside the row, revisions, scheduled publishing and a page builder, with the public site rendered at build time.
• Two devices, one registry (examples/registry): Two devices edit 10,000 products in a data grid, offline and in conflict, and agree once both are back.
• Pages two tabs edit at once (examples/pages): Rich text two people edit at the same time, online or not, converging through one journal.
• A rich text playground (examples/richtext-playground): One document with movable blocks, anchored discussions, images, tables, code, toggles and footnotes, every edit a transition of the Model.
• A todo list an agent can use (examples/todo-app): One application definition drives the view, the tools an agent calls, the document replicas share, and the policy the server enforces.
• A Twitter clone, Chirp (examples/chirp): Posts declared once as Entities, guarded on the server, served through Remote, posted and edited through forms built from the same input, and liked in one round trip.