#Actor state

alepha/actor declares independent default and keyed state from an atom descriptor. Node and Bun use volatile Memory per container. Workerd uses a native Durable Object host. Browser and native client runtimes reject actor execution. Actor snapshots do not synchronize with the local atom store, SSR hydration, browser persistence or React subscriptions. The atom supplies its stable name, schema and default; it is not the actor's live storage.

 1import { $atom, z } from "alepha"; 2import { $actor } from "alepha/actor"; 3  4const counter = $atom({ name: "counter", schema: z.integer(), default: 0 }); 5class CounterService { 6  counter = $actor({ 7    atom: counter, 8    methods: { 9      add: (state, amount: number = 1) => state + amount,10    },11  });12  async increment() {13    await this.counter.add();14    return this.counter.get("alice").add(2);15  }16}

get(key) is synchronous and requires a nonempty string. The default actor and get("default") are separate instances. read() and method calls return detached snapshots. A method resolves to the state committed by that call, even if a later concurrent call has already changed the stored state. read() returns the state observed by that read: for a key with nothing stored, the validated default, and it stores nothing, so reading arbitrary keys never creates state. A method on a missing key starts from the default. Neither returns a method-specific result or a live subscription. A failed transition preserves the previous state; if it was the first call, nothing is stored.

For example, alepha.store.set(counter, 100) leaves service.counter.read() unchanged, and service.counter.add() leaves the ordinary store value unchanged when service is the injected CounterService. Changing the app name or atom name selects new state; it does not migrate or delete previous snapshots. Two distinct actor declarations cannot reuse the same atom name in one container. Method names are own properties and cannot shadow get, read, then, primitive members or object prototype members.

#Nested session state

Keep the schema separate from the service and return a new value from each reducer:

1// sessionState.ts2import { z } from "alepha";3 4export const sessionSchema = z.object({5  names: z.array(z.text()),6  nested: z.object({ count: z.integer() }),7});

 1// SessionService.ts 2import { $atom } from "alepha"; 3import { $actor } from "alepha/actor"; 4  5import { sessionSchema } from "./sessionState.ts"; 6  7const session = $atom({ 8  name: "session", 9  schema: sessionSchema,10  default: { names: [], nested: { count: 0 } },11});12 13class SessionService {14  session = $actor({15    atom: session,16    methods: {17      append: (state, input: { name: string }) => ({18        names: [...state.names, input.name],19        nested: { count: state.nested.count + 1 },20      }),21    },22  });23 24  async join() {25    const actor = this.session.get("party-1");26    const snapshot = await actor.append({ name: "Alice" });27    snapshot.names.push("caller-only"); // does not modify stored actor state28    return actor.read(); // names: ["Alice"], nested: { count: 1 }29  }30}

Arguments are copied synchronously when the call is made. Changing an input while its call waits does not change the reducer's input. Reducer state and arguments are recursively frozen at runtime. Returned snapshots are detached mutable values; changing them cannot modify storage, another result or the atom default.

#Reducer and data contract

Reducers must be deterministic synchronous functions with no I/O, time, randomness, mutable captured dependencies or other side effects. Redis may rerun a reducer on contention, so logging, sending messages and external writes belong outside it. Room callbacks and ordinary services can await actors; the reducer itself cannot. Each reducer returns the complete next state, which is validated before committing. A thrown error, invalid state, attempted mutation or Promise result rejects the call. The per-identity queue remains usable after failure.

Only lossless JSON data is supported: null, booleans, strings, finite numbers, dense arrays and plain objects (including null-prototype objects). Explicit undefined, negative zero, nonfinite numbers, bigint, functions, symbols, symbol keys, hidden properties, accessors, sparse or extended arrays, class instances (including Date, Map and Set) and cycles are rejected. Omit optional properties and trailing arguments instead of passing undefined. Async schemas are unsupported.

A reducer that returns its current state unchanged (canonically equal JSON) commits nothing: no write, no compare-and-set on Redis, and the revision stays where it was. On a missing key that means nothing is created. The revision therefore counts state changes, not calls, and a flood of calls that leave the state alone costs reads only.

Stored envelopes have protocol version 1 or 2 and a nonnegative safe integer revision. Version 2 carries expiresAt and is written only for expiring states (see below). Corrupt data, unknown versions, invalid revisions and schema incompatibility fail closed without resetting state. Stored validation must preserve the JSON value; a changed schema that would strip or transform existing data is incompatible. Revision overflow refuses further transitions. There is no automatic data migration.

#Expiry

State never expires unless its declaration says so. expiresAt is a pure synchronous function of the state returning an epoch-millisecond instant, or undefined for none. Reducers stay pure: the instant is part of the state, usually computed from a now the caller passes in, never read from a clock inside the reducer.

 1import { $atom, $inject, z } from "alepha"; 2import { $actor } from "alepha/actor"; 3import { DateTimeProvider } from "alepha/datetime"; 4  5const window = $atom({ 6  name: "window", 7  schema: z.object({ count: z.integer(), resetAt: z.integer() }), 8  default: { count: 0, resetAt: 0 }, 9});10class Windows {11  dateTime = $inject(DateTimeProvider);12  hits = $actor({13    atom: window,14    methods: {15      hit: (state, now: number, windowMs: number) =>16        state.resetAt <= now17          ? { count: 1, resetAt: now + windowMs }18          : { count: state.count + 1, resetAt: state.resetAt },19    },20    expiresAt: (state) => state.resetAt,21  });22  hit(key: string) {23    return this.hits.get(key).hit(this.dateTime.nowMillis(), 60_000);24  }25}

Once DateTimeProvider reaches expiresAt, the state reads as missing on every provider: read() returns the default and a method starts from it, with the revision restarting at 1. travel() drives this in tests. An expiring state is stored as a version 2 envelope { version, revision, state, expiresAt }; a state whose expiresAt returns undefined, or a declaration without one, keeps writing version 1 byte for byte, so existing data needs no migration. A return that is neither undefined nor a safe integer fails the transition and preserves the state, like an invalid state. An asynchronous expiresAt is refused at declaration.

Expiry is lazy, so reading is always correct, and storage is reclaimed separately: a key touched once and never again would otherwise stay forever.

• Memory keeps each expiresAt beside its snapshot and, on every write, checks at most eight entries from a cursor and deletes the expired ones. The sweep is deterministic, so specs need no probability knob.
• Redis writes an expiring envelope with PXAT expiresAt + expiryGraceMs (Redis 6.2+; expiryGraceMs defaults to one minute in actorRedisOptions), so clock skew never drops a key the app still reads as live. A version 1 write clears the expiry. Until Redis drops it, a transition on an expired key compares and sets against the bytes still present.
• Durable Objects arm the instance's alarm at expiresAt plus one second, only when expiresAt changes: an alarm write is billed as a row written, and a counter's expiry changes once per window, not once per call. The alarm deletes the storage of an expired actor and re-arms one that moved on. It needs no Wrangler configuration and no Durable Object migration.

#Topology: no Redis means one instance

Where actor state lives decides who shares it, and the rule is the provider's:

• Memory (the default on Node and Bun) is one process. It is right for an app that runs a single instance.
• Redis (AlephaActorRedis) is for several instances: every one of them sees the same state.
• Durable Objects on workerd, one per actor identity.

An app without AlephaActorRedis is a single-instance app, and every actor in it assumes so: the login and MFA lockouts of alepha/api/users, every $rateLimit and your own actors. Run two Node instances without Redis and each keeps its own state, so a limit of five becomes five per instance. Nothing falls back to SQL to paper over it.

⚠️ REDIS_URL alone does not select AlephaActorRedis. An app that runs several instances with a Redis cache or queue, but never added the actor module, still keeps actor state per instance. Add alepha.with(AlephaActorRedis) before scaling out.

#Redis on Node and Bun

Select AlephaActorRedis from alepha/actor/redis explicitly with alepha.with(AlephaActorRedis). Every actor identity carries alepha.name: APP_NAME, else the build's app name, else "app". REDIS_URL alone leaves Memory selected. The provider uses the existing runtime Redis variants with a dedicated connection and offline command replay disabled. Start the container before calling actors.

 1import { Alepha } from "alepha"; 2import { AlephaActorRedis } from "alepha/actor/redis"; 3  4const alepha = Alepha.create({ 5  env: { 6    APP_NAME: "my-app-production", 7    REDIS_URL: "redis://localhost:6379", 8  }, 9}).with(AlephaActorRedis);10await alepha.start();

Independent applications share state only when their Redis server, app name, atom name and default-or-key identity agree. Give unrelated applications and environments distinct APP_NAMEs; specs and unbuilt scripts are all "app", so two of them on one Redis share actors. Memory instead owns one container's state; stopping the process or creating a new container loses it.

Each transition validates its candidate locally, then commits one key with an exact observed-byte Lua compare-and-set: one GET and one script call, a missing key included. Only definite conflicts retry, from the value the failed compare-and-set returned (no second GET) and the original detached arguments; a key deleted or evicted meanwhile retries as missing. Between two attempts the provider sleeps a full-jitter exponential backoff, a random delay below min(maxDelayMs, baseDelayMs * 2^attempt) milliseconds, so replicas contending on one hot key do not exhaust their attempts together; the sleep goes through DateTimeProvider. Within one process the per-identity queue already serializes calls, so only replicas contend. actorRedisOptions configures positive maxAttempts (default 32), baseDelayMs (default 1) and maxDelayMs (default 50). Exhaustion throws ActorContentionError.

State has no local read cache, and expiry is lazy (see above). Redis persistence and failover configuration determine restart durability; eviction loses state. Keys written with an expiry (expiring actors) are candidates for the volatile-* eviction policies as well as the allkeys-* ones. A transport failure after a commit can leave its outcome unknown. The provider does not retry that invocation, and callers must not assume exactly-once delivery. Blindly retrying a failed increment can apply it twice; resolving an unknown business operation requires an application-level protocol. Corrupt, incompatible or unknown-version stored data fails closed. Changing the app name or atom name selects new state without migrating or deleting old state.

See Redis scripting, Redis persistence and Node Redis production behavior.

#Cloudflare workerd

Workerd selects the shared AlephaActorDurableObject host with the ALEPHA_ACTOR binding. Each encoded namespace/name/default-or-key tuple has its own instance. The identity carries alepha.name, as on every other provider; an APP_NAME binding wins over the built name. A missing binding fails without falling back to Memory.

The host resolves registered pure reducers without starting the full application, so an application start hook can call an actor without recursively starting itself. It serializes reads and transitions and awaits validated protocol-v1 KV writes on SQLite-backed storage before success. A read of a missing actor writes nothing. Restarted hosts read persisted state. Failed transitions retain the previous snapshot; corrupt or incompatible stored state fails closed. Each successful transition awaits storage before returning. This does not make RPC delivery exactly once: a lost response can leave the caller uncertain whether its transition committed. The host's alarm is used only to reclaim expired actors (see Expiry); no native SQL API, alarm or subscription is exposed to applications.

Generic ActorHostRegistry declarations and ActorHostRuntime namespace and startup facilities are runtime-neutral. Native host imports stay workerd-only. WebSocket hosts use the same runtime resolution, namespace lookup and application startup facilities, but keep their existing socket transport and lifecycle. RoomEngine.state and per-connection conn.data remain volatile. Accepted socket attachments retain identity metadata across host recreation; they do not restore room state or data bags. Persist important changes through an actor or repository as they happen. onEmpty is a normal room lifecycle callback, not an eviction recovery guarantee. See stateful rooms. Cloudflare storage documentation describes the underlying storage guarantees. Local workerd recovery evidence does not prove live provisioning or production hibernation.

#Build and namespace provisioning

Generic host declarations drive workerd facades, slice wrappers and Worker exports. The loose build manifest records cloudflare.durableObjects and resources.hasDurableObjects; WebSocket paths remain transport metadata. Node and Bun slices contain no native host exports. Rebuild older prebuilt realtime artifacts that lack host declarations before regenerating deployment configuration.

With no explicit build.cloudflare.config.migrations, the build generates Durable Object exports. Use a Wrangler release with declarative exports support (the repository tests Wrangler 4.147.0). The build rejects a locally installed Wrangler schema without that feature. An external application's Wrangler is not pinned by the framework; check its toolchain before deploying.

An explicit migrations array selects the legacy path. Historical ordered tags and steps are preserved; new host classes are appended under a fresh alepha-hosts-vN tag. Durable Object exports and legacy migrations cannot coexist. Compatible user exports preserve their storage backend. Conflicting local bindings or required-host lifecycle tombstones fail before artifacts are written.

Existing sockets keep AlephaWebSocketDurableObject, ALEPHA_WEBSOCKET and channelPath + ":" + roomId namespace identity. Moving framework-generated SQLite provisioning to exports is a one-way control-plane transition. Applications that need legacy history must configure it explicitly. The framework does not migrate application state or infer deletes, renames or transfers from removed host declarations. See Cloudflare class lifecycle.

The E73 command surface uses alepha/cli/infra for explicit infrastructure configuration and alepha deploy for the full build/migrate/deploy lifecycle. alepha deploy --prebuilt consumes an existing artifact and regenerates its deploy configuration; it needs the manifest and its declared runtime slice. Shared adapters are exported from alepha/cli/infra-lib.

Both Cloudflare deploy adapters read these same manifest declarations. Wrangler receives the complete legacy configuration history. The direct Worker upload forwards local durable_object_namespace bindings and declarative exports. For legacy history it reads the applied migration tag, sends only later steps with old_tag/new_tag, and sends no steps on a repeat deployment. Unknown tags and failed metadata lookups refuse deployment before upload.

An explicit forced Worker deletion also destroys its actor snapshots. Durable Object presence is recorded for actor-only artifacts, and a failed Worker deletion keeps that namespace record. There is no separately deletable namespace resource.

Lore and Bay are separate repositories. Their consumers must upgrade the framework, adopt E73's infra imports/commands if needed, and rebuild older prebuilt realtime artifacts to carry generic host declarations. A framework change does not upgrade those applications, preserve undocumented deployment history or deploy them.