Foldkitアプリケーションを拡張するパッケージ outward — エージェント、サーバー、その他のデバイス、URL、および設計システムへ — 状態を保つために2番目の場所を与えずに。

Foldkit アプリケーションは 1 つのステート マシンです。: Schema-typed Model, a メッセージ union は、起こるすべてのものを命名し、1つの純粋な**[[[T0]** メッセージを次のモデルとコマンドに変える関数。 その形 理由、テスト、再生が簡単です。 アプリが成長する瞬間が失われる ホック、URLのストア、再実装するツールハンドラのキャッシュ 移行、または独自の減速機で同期レイヤー。

このリポジトリのすべてが1つのステートマシンを保持します。 エージェントは、 メッセージ [update]を既に処理します。 サーバのデータはモデルに住んでおり、 [updateで再構成します。 同じメッセージを同じメッセージで再生するレプリカ [update]。 URL とローカル ストレージは、モデルのスライスをミラーリングします。 お問い合わせ フォークを使わずに外から眺める 各パッケージは1つに答えます 質問, 彼らは彼らが明示的なアプリケーション境界で会うので、彼らはコンポーズ.

ウェブサイト: 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.