@xmachines/docs 6.0.0 → 7.0.0

package/guides/state-machines.md

@@ -1,4 +1,4 @@
-# Understanding State Machines in XMachines
+# State Machines in XMachines
 
 XMachines uses XState v5 as its state machine engine. This page explains what finite state machines are, how XMachines extends them with routing and view metadata, and why this design eliminates an entire category of bugs common in traditional frontend architecture.
 
@@ -33,7 +33,6 @@ const authSetup = setup({
 	types: {
 		context: {} as { username: string | null },
 		events: {} as { type: "auth.login"; username: string } | { type: "auth.logout" },
-		input: {} as undefined,
 	},
 });
 
@@ -47,7 +46,8 @@ const authMachine = authSetup.createMachine({
 				"auth.login": {
 					target: "authenticated",
 					actions: authSetup.assign({
-						username: ({ event }) => event.username,
+						username: ({ event }) =>
+							event.type === "auth.login" ? event.username : null,
 					}),
 				},
 			},
@@ -78,6 +78,7 @@ XMachines extends XState's `meta` field on each state node. This is where routin
 
 ```typescript
 import { typedSpec } from "@xmachines/play-view";
+import { setup } from "xstate";
 
 const appMachine = setup({/* ... */}).createMachine({
 	id: "app",
@@ -122,19 +123,90 @@ const appMachine = setup({/* ... */}).createMachine({
 
 `meta.route` is a string path. When the machine enters a state, `actor.currentRoute` (a `ReadonlyAtom`) derives this path and emits it. The router bridge reads it and updates the URL.
 
-`meta.view` is a [`PlaySpec`](../api/@xmachines/play-view/index/interfaces/PlaySpec.md) — a `@xmachines/json-render-core` spec object describing what to render. Use `typedSpec(...)` from [`@xmachines/play-actor`](../api/@xmachines/play-actor/README.md) to type-check the spec literal at the definition site (XState's `meta` is untyped). When the machine enters a state, `actor.currentView` is updated with the derived spec. The renderer reads it and projects it through framework components.
+`meta.view` is a [`ViewMeta`](../api/@xmachines/play-view/index/interfaces/ViewMeta.md) — a `@xmachines/json-render-core` spec object describing what to render. The actor derives a [`PlaySpec`](../api/@xmachines/play-view/index/interfaces/PlaySpec.md) from it, and that derived spec is what a renderer receives. Use `typedSpec(...)` from [`@xmachines/play-view`](../api/@xmachines/play-view/README.md) to type-check the spec literal at the definition site (XState's `meta` is untyped). When the machine enters a state, `actor.currentView` is updated with the derived spec. The renderer reads it and projects it through framework components.
 
 The machine's whole context is available to every view through the **`/context` projection**: the derived spec's `state` carries `context: <machine context>`. Specs read it with ordinary state expressions — `{ $state: "/context/username" }` in props, `visible` conditions, or `repeat.statePath`. The subtree is **read-only**: context changes only through machine events, and a `$bindState`/`setState` write under `/context` throws. URL data lives at its own paths (`/context/params/…`, `/context/query/…`, written into context by `formatPlayRouteTransitions`), so a URL param can never shadow a machine-owned field. When validating specs with tools like `validateSpec`, validate the **derived** view (`actor.currentView.get()`) — its `state` honestly describes the store contents — not the raw `meta.view`. A context change re-emits the view with the same `viewKey`; providers respond by refreshing `/context` in the live store, not by remounting the UI.
 
+**Give each state its own id, and do not use an array index as an id.** XState does not check that the ids of the states are unique, and a repeated id makes a `#id` target name two states. XMachines keys the route, the view and its store on the id of a state, so two states that share an id share one route entry, one store, and one key. An array index is a whole number from 0 to 2³² − 2 with no leading zero, such as `"42"`. JavaScript lists such a key first in every object that is keyed on ids, so the route of its state loses its place in the branch. [`@xmachines/play-xstate`](../api/@xmachines/play-xstate/README.md) writes one warning for each machine that breaks these rules.
+
 **The machine is the single source of truth for both routing and views.** There is no separate route configuration file. There is no switch statement in a component deciding what to render based on the URL. The state machine encodes all of that.
 
+### A layout and its pages: `outlets`
+
+Without outlets, the deepest active state that declares a view wins, and a view on a parent state stays off the screen. Declare `outlets` in the view of the parent to show the parent view AND the view of its active child. Each outlet names an element of the parent view, and the view of the child goes into that element:
+
+```typescript
+import { typedSpec, type ViewMeta } from "@xmachines/play-view";
+import { setup } from "xstate";
+
+declare const menuView: ViewMeta, homeView: ViewMeta, searchView: ViewMeta; // your views
+
+const shell = typedSpec({
+	root: "shell",
+	state: { collapsed: false },
+	elements: {
+		shell: { type: "Shell", props: {}, children: ["title"], slots: { sidebar: [] } },
+		title: { type: "Heading", props: { text: "App" }, children: [] },
+	},
+	outlets: {
+		menu: { element: "shell", slot: "sidebar" }, // the region "menu"
+		"*": { element: "shell" }, //                 every other child
+	},
+});
+
+const appMachine = setup({/* ... */}).createMachine({
+	id: "app",
+	type: "parallel",
+	meta: { view: shell },
+	states: {
+		menu: { initial: "open", states: { open: { meta: { view: menuView } } } },
+		page: {
+			initial: "home",
+			states: {
+				home: { meta: { route: "/", view: homeView } },
+				search: { meta: { route: "/search", view: searchView } },
+			},
+		},
+	},
+});
+```
+
+- **The key of an outlet** is the key of a child state in `states`, or `"*"` for each active child that has no outlet of its own. A child with neither stays off the screen.
+- **A compound state** fills one outlet with its active child. **A parallel state** fills one outlet for each region, in the order of `states`.
+- **`slot`** names a named slot of the element. Omit it to append the child view to the `children` of the element. The component of the element renders the slot, as the renderer of your framework describes.
+- **The view of a child** is the deepest view in its active subtree, and a child view can declare `outlets` of its own for a nested layout. A parallel state without outlets shows the region of the routes when that region has a view, and its first region that has a view otherwise. The region of the routes keeps the screen while it sits in a state without a route of its own.
+
+The derived spec holds the elements of every composed view. The keys of the outer view stay as you wrote them, and each key of a child view gets the id of its state as a prefix, for example `app.page.search/root`, so two views never collide.
+
+The `viewKey` of a composed view is the id of the outermost state that declares `outlets`. A change of the page therefore keeps the store of the layout: the `collapsed` value in the example above does not change. The first time that a page shows, the provider writes the keys of its authored `state` that the store does not hold. A page that comes back finds the values that it left. All the pages of one layout share one store, so two pages that declare the same key share one value: give each page its own keys. When two composed views declare the same state key, the outer view wins. The library writes one warning for each layout that names every key that two of its views declare, also for two pages that are never on the screen together.
+
+An outlet that names an element that its view does not hold throws `InvalidViewOutletError`. The actor reports it through its `onError` option, and it keeps the last good view.
+
+**`handler` decides whether the layout survives a navigation.** Under the default `handler: "root"`, a navigation exits and enters every active state below the root, and a parallel state then puts its other regions back in their `initial` state. Declare `handler: "local"` or `"both"` on a routed state inside a region, as [Re-entry on a navigation](routing.md#re-entry-on-a-navigation) describes.
+
+**The URL comes from the routed region.** In a parallel machine, the URL comes from the first region whose active states declare a `meta.route`, so the `menu` region can come before the `page` region. Keep the routes of one layout in one region. The URL shows the route of the first routed region only, so a navigation to a route of a second routed region never shows in the address bar.
+
+CAUTION: a second routed region moves without its URL. Take a `page` region with `/` and `/search`, and a `drawer` region after it with `/drawer` and `/drawer/settings`:
+
+| Step                        | `page`   | `drawer`   | URL       |
+| --------------------------- | -------- | ---------- | --------- |
+| start                       | `home`   | `closed`   | `/`       |
+| a navigation to `#settings` | `home`   | `settings` | `/`       |
+| a navigation to `#search`   | `search` | `closed`   | `/search` |
+
+- The navigation to `#settings` moves the drawer, and the URL stays `/`. The browser adds no history entry, BACK does not close the drawer, and a reload or a shared link loses the drawer.
+- A deep link to `/drawer/settings` moves the drawer too, but the actor derives the URL `/` from the `page` region, so the address bar does not keep the path of the drawer.
+- The navigation to `#search` puts the drawer back to `closed`, because the default `handler: "root"` exits and enters every region. `handler: "local"` keeps it.
+
+A URL path has one hierarchy, and it cannot hold the branches of two regions. Keep the other regions unrouted. When the position of such a region must survive a reload or a shared link, write it as a query value of the routed region, for example `/search?drawer=settings`. The generated `play.route` transition assigns the query to `context.query`, the URL carries `context.query`, and your machine moves the region to match the value.
+
 ---
 
 ## [`formatPlayRouteTransitions`](../api/@xmachines/play-xstate/with-routing/functions/formatPlayRouteTransitions.md) — automatic route event wiring
 
 For routing to work, the machine must respond to `play.route` events (sent by router bridges when the user navigates). Writing these transitions by hand is mechanical:
 
-```typescript
+```typescript fragment
 // Without formatPlayRouteTransitions — verbose and repetitive
 states: {
   home: {
@@ -154,6 +226,7 @@ states: {
 
 ```typescript
 import { formatPlayRouteTransitions } from "@xmachines/play-xstate/routing";
+import { setup } from "xstate";
 
 const appMachine = setup({/* ... */}).createMachine(
 	formatPlayRouteTransitions({
@@ -170,7 +243,7 @@ const appMachine = setup({/* ... */}).createMachine(
 
 [`formatPlayRouteTransitions`](../api/@xmachines/play-xstate/with-routing/functions/formatPlayRouteTransitions.md) inspects all state nodes with a `meta.route` and generates the corresponding `play.route` guard transitions. The machine's context must include `params` and `query` fields (populated by the router bridge when params or query strings are present):
 
-```typescript
+```typescript fragment
 types: {
   context: {} as {
     params: Record<string, string>;
@@ -188,7 +261,12 @@ types: {
 Guards are the mechanism by which the actor controls whether a transition occurs. They are pure functions of `{ context, event }` that return a boolean.
 
 ```typescript
+import { setup } from "xstate";
+
 const authSetup = setup({
+	types: {
+		context: {} as { isAuthenticated: boolean; role: "user" | "admin" },
+	},
 	guards: {
 		isAuthenticated: ({ context }) => context.isAuthenticated,
 		isAdmin: ({ context }) => context.role === "admin",
@@ -216,7 +294,7 @@ Each combinator resolves a guard NAME against the `guards` of `setup()`, so a na
 
 Context is the machine's persistent data store. It survives transitions and can be read and updated by actions:
 
-```typescript
+```typescript fragment
 // Context is defined in setup({ types })
 types: {
   context: {} as {
@@ -243,22 +321,30 @@ Context is accessed in guards, actions, and when computing routes or views. It i
 A snapshot is a point-in-time serialisation of the machine's current state and context. XState produces snapshots in a JSON-compatible format:
 
 ```typescript
+import { definePlayer } from "@xmachines/play-xstate";
+import type { AnyStateMachine } from "xstate";
+
+declare const machine: AnyStateMachine; // your machine
+
+const createPlayer = definePlayer({ machine });
+const actor = createPlayer();
+actor.start();
+
 const snapshot = actor.getSnapshot();
 // snapshot.value → current state node name, e.g. "dashboard"
 // snapshot.context → current context object
 
-// Stop and serialize
+// Serialize and stop
+const saved = JSON.stringify(actor.getPersistedSnapshot());
 actor.stop();
-const saved = JSON.stringify(snapshot);
 
 // Restore
-const restored = JSON.parse(saved);
-const actor = createPlayer(undefined, { snapshot: restored });
-actor.start();
+const restored = createPlayer(undefined, { snapshot: JSON.parse(saved) });
+restored.start();
 // Actor resumes from where it left off
 ```
 
-[`definePlayer`](../api/@xmachines/play-xstate/index/functions/definePlayer.md) accepts an optional `restore` argument for this purpose. Restoration is useful for server-side rendering (hydrate with the server's snapshot), session persistence (resume after page reload), and testing (start from a known mid-flow state).
+The factory that [`definePlayer`](../api/@xmachines/play-xstate/index/functions/definePlayer.md) returns accepts an optional second argument, `{ snapshot }`, for this purpose. Serialize the result of `getPersistedSnapshot()`, and not of `getSnapshot()`: XState restores from the persisted form. Restoration is useful for server-side rendering (hydrate with the server's snapshot), session persistence (resume after page reload), and testing (start from a known mid-flow state).
 
 ---
 
@@ -276,9 +362,10 @@ actor.start();
 
 ## See also
 
-- [Understanding the Actor Model](actor-model.md) — how the machine definition becomes a live actor
-- [Understanding Atoms](atoms.md) — how the actor's state is observed by infrastructure
+- [The Actor Model](actor-model.md) — how the machine definition becomes a live actor
+- [Atoms](atoms.md) — how the actor's state is observed by infrastructure
 - [Getting Started](getting-started.md) — step-by-step walkthrough building your first machine and actor
+- [Views](views.md) — which state supplies the view, how a layout holds its pages, and when a renderer keeps the UI
 - [Routing Patterns](../examples/routing-patterns.md) — worked examples of `meta.route` and guards
 - [@xmachines/play-xstate](../api/@xmachines/play-xstate/README.md) — full API reference for [`definePlayer`](../api/@xmachines/play-xstate/index/functions/definePlayer.md), [`PlayerActor`](../api/@xmachines/play-xstate/index/classes/PlayerActor.md), and the routing utilities
 - [XState v5 documentation](https://stately.ai/docs/xstate) — upstream state machine library documentation

package/guides/views.md

@@ -0,0 +1,367 @@
+# Views in XMachines
+
+A view of XMachines is a fact about a STATE, and not a fact about a component tree. A state node declares `meta.view`, the actor derives the current view from the active states, and a renderer turns that description into the UI of one framework.
+
+This guide tells which state supplies the view, how a parent view holds the views of its substates, how a view reads the machine context, and when a renderer keeps the UI and when it builds the UI again. It also names the four rules that every one of the five renderers follows.
+
+After you read it, you know where to put a value that the screen shows, why a write to `/context` throws, and why a draft in a form survives one event and not another.
+
+---
+
+## What problem a view spec solves
+
+An application without a machine decides the screen inside its components: `if (user && !loading) return <Dashboard />`. Each such condition is a second copy of a decision, and the copies disagree when one of them changes.
+
+The machine knows the state already. XMachines therefore puts the view ON the state, as data. The component tree holds no condition that selects a screen, and the machine holds no import of a framework.
+
+The data is a spec of `@xmachines/json-render-core`: a flat map of elements, each with a component type, props and children. One spec renders in React, in Vue, in SolidJS, in Svelte and in the plain DOM, because each renderer reads the same grammar.
+
+---
+
+## The three parts of a view
+
+| Part     | Where it lives                                 | What it says                                          |
+| -------- | ---------------------------------------------- | ----------------------------------------------------- |
+| catalog  | `defineCatalog(schema, …)`, one for each app   | the component types and the actions that exist        |
+| spec     | `meta.view` of a state node                    | WHICH components show in that state, with which data  |
+| registry | `defineRegistry(catalog, …)`, one per renderer | HOW each component renders, and what each action does |
+
+The catalog is the vocabulary. It holds Zod schemas and no framework code. The spec uses the vocabulary. The registry binds each word to a component of one framework and to a handler of each action.
+
+A machine and its specs therefore change never when you change the framework. You write a second registry.
+
+---
+
+## Declaring a view
+
+A `meta.view` is a [`ViewMeta`](../api/@xmachines/play-view/index/interfaces/ViewMeta.md). `root` names the first element, and `elements` holds every element by its key:
+
+```ts
+import { setup } from "xstate";
+import { typedSpec } from "@xmachines/play-view";
+
+const machine = setup({}).createMachine({
+	id: "app",
+	initial: "home",
+	states: {
+		home: {
+			meta: {
+				view: typedSpec({
+					root: "page",
+					elements: {
+						page: { type: "Page", props: { title: "Welcome" }, children: ["intro"] },
+						intro: { type: "Text", props: { text: "Choose a task." }, children: [] },
+					},
+				}),
+			},
+		},
+	},
+});
+```
+
+XState types `meta` as `Record<string, unknown>`, so TypeScript checks nothing that you write there. `typedSpec` of [`@xmachines/play-view`](../api/@xmachines/play-view/README.md) gives the literal the type `ViewMeta` where you write it, and it does nothing at run time. The check of an excess property works on an inline literal only. For a spec in a variable, write `satisfies ViewMeta` at the literal.
+
+A `ViewMeta` is what you WRITE. A [`PlaySpec`](../api/@xmachines/play-view/index/interfaces/PlaySpec.md) is what the actor DERIVES from it, and what a renderer receives. The derivation consumes `outlets`, it adds the machine context, and it stamps `viewKey` and `viewParts`.
+
+The view is an OPTIONAL capability of the actor. Compose it with `withView` of [`@xmachines/play-xstate`](../api/@xmachines/play-xstate/README.md), from its `view` subpath:
+
+```ts
+import { definePlayer, compose, PlayerActor } from "@xmachines/play-xstate";
+import { withView } from "@xmachines/play-xstate/view";
+import type { AnyStateMachine } from "xstate";
+
+declare const machine: AnyStateMachine; // your machine
+
+const actor = definePlayer({ machine, actor: compose(PlayerActor, withView) })();
+actor.start();
+```
+
+The actor then holds `currentView`, a `ReadonlyAtom<PlaySpec | null>`. An application that renders no view composes no `withView`, and it installs no json-render.
+
+---
+
+## Which state supplies the view
+
+**The deepest active state that declares a view supplies it**, unless a parent composes it. A state that declares no view shows the view of its nearest ancestor that declares one. An ancestor view without `outlets` does not show, because the view of its descendant replaces it:
+
+```ts fragment
+states: {
+	dashboard: {
+		meta: { view: dashboardView },   // shows in dashboard.overview
+		initial: "overview",
+		states: {
+			overview: {},
+			settings: { meta: { view: settingsView } },   // replaces dashboardView
+		},
+	},
+},
+```
+
+When no active state declares a view, `currentView` holds `null`, and the renderer shows its `fallback` content.
+
+A **parallel** state follows the same region as the route derivation: the first region whose active states declare a `meta.route`, else the first region that declares a route in any state, else the first region. A region that owns the routes therefore keeps the screen while it sits in a state without a route, such as a load. The view on the screen therefore belongs to the region of the URL. When that region holds no view, the view comes from another active region, so one region can own the URL and another region can own the view. Keep the routes in one region: the [State Machines](state-machines.md#a-layout-and-its-pages-outlets) guide shows what a second routed region does to the URL.
+
+### A layout and its pages: `outlets`
+
+A parent view that declares `outlets` shows itself AND the view of its active child. Each outlet names an element of the parent view, and the view of the child goes into that element:
+
+```ts fragment
+const shell = typedSpec({
+	root: "shell",
+	state: { collapsed: false },
+	elements: {
+		shell: { type: "Shell", props: {}, children: ["title"] },
+		title: { type: "Heading", props: { text: "App" }, children: [] },
+	},
+	outlets: { "*": { element: "shell" } },
+});
+
+states: {
+	app: {
+		meta: { view: shell },
+		initial: "home",
+		states: {
+			home: { meta: { route: "/", view: homeView } },
+			search: { meta: { route: "/search", view: searchView } },
+		},
+	},
+},
+```
+
+- The key of an outlet is the key of a child in `states`, or `"*"` for each active child that has no outlet of its own. A child with neither stays off the screen.
+- A compound state fills one outlet with its active child. A parallel state fills one outlet for each region, in the order of `states`.
+- `slot` names a named slot of the element. Omit it, and the renderer appends the child view to the `children` of the element.
+- The view of a child is the deepest view below it. A child view can declare `outlets` of its own, for a nested layout.
+- An outlet that names an element that its view does not hold throws `InvalidViewOutletError`. The actor reports it through `onError`, and it keeps the last valid view.
+- The keys of the outer view carry no prefix, and each key of a child view gets the id of its state and a `/` as a prefix. A key of the outer view such as `"page/root"` equals the key of the element `root` of the child state `page`, and the composition throws `ViewElementKeyCollisionError`. Do not start a key of the outer view with the id of a state and a `/`.
+
+The derived spec is ONE flat spec. The keys of the outer view stay as you wrote them. Each key of a child view gets the id of its state as a prefix: the `root` element of the view of the state `app.search` becomes `app.search/root`. Two views therefore never collide. The [State Machines](state-machines.md#a-layout-and-its-pages-outlets) guide shows a parallel layout with a named slot.
+
+### The view key
+
+The derivation stamps the identity of the view on the spec, as `viewKey`. For a view without outlets, it is the id of the state that declares the view. For a composed view, it is the id of the outermost state that declares `outlets`, and `viewParts` lists the id of each composed state. The [renderer section](#when-the-renderer-keeps-the-ui) tells why the key matters. Never write `viewKey` or `viewParts` yourself: `typedSpec` refuses both, and the derivation overwrites them.
+
+---
+
+## Reading the machine context
+
+Each derived view carries the whole machine context in its `state`, under the key `context`:
+
+```
+derived state = { ...meta.view.state, context: <the machine context> }
+```
+
+A spec reads the context through the ordinary state grammar of json-render. The same path works in a prop, in a `visible` condition, and in `repeat.statePath`:
+
+```ts fragment
+elements: {
+	greeting: { type: "Text", props: { text: { $state: "/context/username" } }, children: [] },
+	tasks: {
+		type: "List",
+		props: {},
+		repeat: { statePath: "/context/tasks", key: "id" },
+		children: ["task"],
+	},
+	task: { type: "Text", props: { text: { $item: "title" } }, children: [] },
+},
+```
+
+The routing capability writes the URL into the context: the params go to `context.params`, and the query goes to `context.query`. A spec therefore reads `/context/params/userId` for a value of the URL and `/context/username` for a value of the machine. The path tells the origin of each value, and a param can hide no field of the machine.
+
+**The `/context` subtree is read-only to the spec.** A `$bindState` write or a `setState` write under `/context` throws `ReadOnlyContextError`, and the message names the path. The context changes through a machine event only. A handler that writes the whole snapshot back, with the `context` key unchanged, does not throw: the store ignores a write of an identical value.
+
+`context` is a reserved key. When `meta.view.state` declares a top-level `context` key of its own, the derivation skips the projection for that view, the authored value wins, and a warning in development names the conflict. Rename the field.
+
+CAUTION: the projection shows the WHOLE context to the client. A debug panel, an inspector and a validator read the view store, and each one is a client-side tool. Keep a secret out of the context.
+
+Validate the DERIVED view, `actor.currentView.get()`, and not the raw `meta.view`. The `state` of the derived view describes the store as it is, so a tool such as `validateSpec` sees a spec that agrees with itself.
+
+---
+
+## Two kinds of state
+
+A view store holds two kinds of state, at two places, with two owners.
+
+| Kind            | Where in the store    | Written by                                                   | Lives for     |
+| --------------- | --------------------- | ------------------------------------------------------------ | ------------- |
+| ephemeral state | the root: `/username` | `spec.state` seeds it; `$bindState` and `setState` change it | one `viewKey` |
+| domain state    | `/context/…`          | the machine, through an event                                | the actor     |
+
+Ephemeral state is the state of the screen: a draft in a field, an open panel, a selected tab. The machine does not need it until the user commits it.
+
+Domain state is the state of the application. Each change of it is an event, so the inspector shows each change with its cause.
+
+This login form uses both. The field binds to `/username`, and the submit sends the value to the machine:
+
+```ts fragment
+view: typedSpec({
+	root: "form",
+	state: { username: "" },
+	elements: {
+		form: {
+			type: "Login",
+			props: { username: { $bindState: "/username" } },
+			children: [],
+			on: {
+				submit: { action: "login", params: { username: { $state: "/username" } } },
+			},
+		},
+	},
+}),
+```
+
+Keep high-frequency data in the ephemeral state or in a child actor, and not in the context. Each change of a top-level field of the context emits the view again. A keystroke is not a fact of the domain.
+
+---
+
+## How an interaction becomes an event
+
+A component emits a named event of json-render, such as `submit` or `press`. The `on` field of its element maps that name to an ACTION, with params that the renderer resolves from the store. The registry holds the handler of each action, and a handler of a domain action sends a machine event:
+
+```ts
+import { defineCatalog } from "@xmachines/json-render-core";
+import { defineRegistry, schema, type ComponentFn } from "@xmachines/play-dom";
+import type { ViewActor } from "@xmachines/play-view";
+import { z } from "zod";
+
+declare const actor: ViewActor<unknown, { type: "auth.login"; username: string }>;
+
+const catalog = defineCatalog(schema, {
+	components: { Login: { props: z.object({ username: z.string() }) } },
+	actions: { login: { params: z.object({ username: z.string() }) } },
+});
+
+declare const Login: ComponentFn<typeof catalog, "Login">; // your component
+
+const registryResult = defineRegistry(catalog, {
+	components: { Login },
+	actions: {
+		login: async (params) => {
+			if (params) actor.send({ type: "auth.login", username: params.username });
+		},
+	},
+});
+```
+
+The guards of the machine then decide. The renderer changes no state of the machine, and it selects no view. It sends, and it shows what the actor derives next.
+
+The renderer implements four built-in actions over the ephemeral state: `setState`, `pushState`, `removeState` and `validateForm`. They need no handler in the registry. An `on` entry can hold an array of bindings, and the renderer runs them in order. For example, it sends the event, and then it clears the draft:
+
+```ts fragment
+on: {
+	press: [
+		{ action: "addTask", params: { title: { $state: "/newTaskTitle" } } },
+		{ action: "setState", params: { statePath: "/newTaskTitle", value: "" } },
+	],
+},
+```
+
+In an action param, `{ $item: "id" }` resolves to the JSON pointer of the item field, such as `/context/tasks/0/id`, and not to its value. The built-ins need the pointer to address the entry. A handler that needs the value reads it from the state that it receives as its third argument.
+
+---
+
+## When the renderer keeps the UI
+
+A renderer holds one view store for each view, and the `viewKey` decides its lifetime.
+
+| The emission                          | What the renderer does                                          |
+| ------------------------------------- | --------------------------------------------------------------- |
+| a new `viewKey`                       | it seeds a NEW store from `spec.state`                          |
+| the same `viewKey`                    | it replaces `/context` in the live store, and it keeps the rest |
+| the same `viewKey`, new `viewParts`   | as above, and it writes each authored key that the store lacks  |
+| no `viewKey`, from a hand-built actor | it seeds a new store for each emission                          |
+| a different actor                     | it discards the store with the actor                            |
+| `null`                                | it shows the fallback, and it resolves no store                 |
+
+With the same `viewKey`, every renderer keeps the DOM nodes, the focus and the ephemeral state. A context change therefore updates a list under a field that has the focus, and the draft in the field stays.
+
+With a new `viewKey`, the ephemeral state starts again from `spec.state`, and every renderer builds the view again. The state that a component keeps for itself, such as the text of an unbound input, goes with the old view. Two sibling states that each declare a view therefore reset a draft on each transition between them, also when their two specs are equal.
+
+A parent keeps the ephemeral state across a move between its children in one of two ways:
+
+- **Declare the view on the parent**, and no view on the children. The `viewKey` stays the id of the parent.
+- **Declare `outlets` on the parent.** The `viewKey` stays the id of the parent, and each child still shows its own view. A change of the page keeps the store of the layout, so the `collapsed` value of the [layout above](#a-layout-and-its-pages-outlets) does not change.
+
+In a composed view, all the views of one layout share ONE store. The first time that a page shows, the renderer writes each key of its authored `state` that the store does not hold. A page that comes back finds the values that it left. Two pages that declare the same key therefore share one value: give each page its own keys. When two composed views declare the same key, the outer view wins. play-xstate reads the states of the machine one time, and it writes one warning for each layout that names every key that two of its views declare.
+
+`currentView` also emits only on a real change of the view on the screen. An event that changes no context field and moves to no other view keeps the previous reference, and no subscriber runs. The gate compares the top-level fields of the context. It does not enter a value, so a new object in a field emits again, also when its contents are equal.
+
+In the **controlled mode**, you give the provider a `store`. The provider then ignores `spec.state`, and you own the seed and the lifetime of that store. The renderer still owns `/context`, and it refreshes the subtree in your store on each emission. The tree lives as long as its store, so a new `viewKey` keeps the tree in the controlled mode, and a new store builds it again.
+
+---
+
+## When a view fails
+
+A failure of the DERIVATION stays inside the actor. `currentView` catches it, it keeps the last valid view, and it reports the error to the `onError` hook of the actor in a microtask. The transition continues for every other observer.
+
+A failure of the RENDER stays inside the provider. When a component throws, when the store does not resolve, or when the root of the view fails, the provider shows its `fallback` and it calls its own `onError` prop:
+
+| Renderer                                                          | The `onError` prop of the provider |
+| ----------------------------------------------------------------- | ---------------------------------- |
+| [`@xmachines/play-react`](../api/@xmachines/play-react/README.md) | `(error, reset, info) => void`     |
+| the four other renderers                                          | `(error, reset) => void`           |
+
+The provider reports one failure one time for one set of inputs — the actor, the view and the store — and not one time for each render. A new emission, or a call of `reset`, makes the next failure report again. Without `onError`, the provider writes the failure to `console.error`, so that no failure is silent. A handler that throws does not break the containment: the provider writes that failure to `console.error` too.
+
+`onRenderError` receives each failure that json-render reports, with `(error, name, info)`, and it replaces every handler of `defineRegistry`. `info.kind` names the failure: a catalog component that throws (`"element"`), a prop or a `visible` condition of a child (`"props"`, `"visible"`), an action chain or a watch chain (`"action"`, `"watch"`), or the root (`"root"`). A failure of the ROOT — its component, a prop, or its `visible` condition — leaves no view on the screen. json-render gives it to no error boundary of the host, so each of the five providers contains it as a failure of the view: it shows its `fallback`, it calls `onError` one time, and the next view renders again. `onRenderError` also receives it, with the kind `"root"`. A failure below the root reaches `onRenderError` alone, and the rest of the view stays. Without a handler of the host, the provider writes one console line for a failure of the root, and not two.
+
+---
+
+## The view invariants
+
+### 1. The machine selects the view. The renderer never does
+
+The renderer reads `currentView` and shows it. No component decides which screen shows. A condition that selects a screen belongs in a state and its guards.
+
+### 2. `/context` is read-only to the spec
+
+A spec reads the machine context, and it writes it never. The store throws `ReadOnlyContextError` for a write, and the machine changes the context through an event. The renderer refreshes the subtree through a store below the guard, so the rule binds the spec and not the machinery.
+
+### 3. The `viewKey` decides the life of the ephemeral state
+
+The same key keeps the store, and a new key seeds a new one. Put a view, or a layout with `outlets`, on the state whose lifetime the ephemeral state must have.
+
+### 4. A renderer reads `currentView` and `send`, and nothing else
+
+A provider takes a `ViewActor`: the actor contract and the `Viewable` capability. It names no engine and no router. The five renderers read no router package, and the routers read no view package. The two halves meet in the application only.
+
+---
+
+## Which renderer to use
+
+| Renderer                                                            | Mount                                          |
+| ------------------------------------------------------------------- | ---------------------------------------------- |
+| [`@xmachines/play-react`](../api/@xmachines/play-react/README.md)   | `<PlayUIProvider>` around `<PlayRenderer />`   |
+| [`@xmachines/play-vue`](../api/@xmachines/play-vue/README.md)       | `<PlayUIProvider>` around `<PlayRenderer />`   |
+| [`@xmachines/play-solid`](../api/@xmachines/play-solid/README.md)   | `<PlayUIProvider>` around `<PlayRenderer />`   |
+| [`@xmachines/play-svelte`](../api/@xmachines/play-svelte/README.md) | `<PlayUIProvider>` around `<PlayRenderer />`   |
+| [`@xmachines/play-dom`](../api/@xmachines/play-dom/README.md)       | `createPlayUI(registryResult)(actor, element)` |
+
+Each one exports `schema` for `defineCatalog`, and `defineRegistry` for its own components. `PlayUIProvider` takes the `actor`, the `registryResult`, and the optional `store`, `fallback`, `onError` and `onRenderError`. The [Getting Started](getting-started.md#connecting-a-view-renderer) guide shows a complete mount for each framework.
+
+[`@xmachines/play-view`](../api/@xmachines/play-view/README.md) holds the part that the five share: the view session, which resolves the store of each view outside a render, the `/context` guard and the report guard. A shared contract suite runs the same scenarios against each renderer, so the five agree on what a viewer sees.
+
+---
+
+## Summary
+
+| Question                                  | Answer                                                              |
+| ----------------------------------------- | ------------------------------------------------------------------- |
+| Where does a view come from?              | `meta.view` of the deepest active state that declares one           |
+| How does a layout show its page?          | The layout declares `outlets`, and the page view goes into one      |
+| What shows when no state declares a view? | The `fallback` of the provider                                      |
+| How does a spec read the machine context? | `{ $state: "/context/…" }`, in a prop, a condition or a repeat      |
+| Can a spec write the context?             | No. Send the actor an event                                         |
+| Where does a draft go?                    | In `spec.state`, at the root of the store, with `$bindState`        |
+| When does a draft reset?                  | When the `viewKey` changes: the outermost state of the view changes |
+| Which side selects the screen?            | The machine, in every renderer                                      |
+| Who reports a failure of a render?        | The provider, one time, through its `onError`                       |
+
+## See also
+
+- [State Machines](state-machines.md) — how `meta.route` and `meta.view` sit on a state node
+- [Routing](routing.md) — the other half, and the same rule of a single active branch
+- [Atoms](atoms.md) — the primitive under `currentView`
+- [The Actor Model](actor-model.md) — why the machine holds no framework import
+- [Form validation](../examples/form-validation.md) — a worked login form, with `$bindState` and a guard
+- [@xmachines/play-view](../api/@xmachines/play-view/README.md) — API reference

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@xmachines/docs",
-  "version": "6.0.0",
+  "version": "7.0.0",
   "description": "Documentation for XMachines",
   "keywords": [
     "documentation",
@@ -56,13 +56,13 @@
   },
   "devDependencies": {
     "@testing-library/jest-dom": "^7.0.1",
-    "@types/node": "^26.6.2",
-    "oxfmt": "^0.70.0",
-    "oxlint": "^1.85.0",
+    "@types/node": "^26.6.4",
+    "oxfmt": "^0.71.0",
+    "oxlint": "^1.86.0",
     "typedoc": "^0.28.20",
     "typedoc-plugin-llms-txt": "^0.1.2",
-    "typedoc-plugin-markdown": "^4.13.0",
-    "vitest": "^5.0.1"
+    "typedoc-plugin-markdown": "^4.13.1",
+    "vitest": "^5.0.3"
   },
   "engines": {
     "node": ">=24.0.0"