create-qpq-app 0.1.14 → 0.1.15

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-qpq-app",
-  "version": "0.1.14",
+  "version": "0.1.15",
   "description": "Scaffold a new quidproquo app: npx create-qpq-app my-app",
   "main": "./lib/commonjs/index.js",
   "module": "./lib/esm/index.js",
@@ -52,7 +52,7 @@
   },
   "devDependencies": {
     "@types/node": "^22.13.13",
-    "quidproquo-tsconfig": "0.1.14"
+    "quidproquo-tsconfig": "0.1.15"
   },
   "bin": {
     "create-qpq-app": "./lib/commonjs/bin/createQpqApp.js"

package/template/docusaurus/docs/actions/core/dynamic-functions/_category_.json

@@ -0,0 +1 @@
+{ "label": "Dynamic Functions", "link": { "type": "generated-index", "description": "Invoke a member of a registered functions object by name from within a story." } }

package/template/docusaurus/docs/actions/core/dynamic-functions/ask-dynamic-function-execute.md

@@ -0,0 +1,89 @@
+---
+title: askDynamicFunctionExecute
+description: Invoke a member of a registered dynamic-functions object by name and return its result, running generator members in-process as a nested story.
+---
+
+# askDynamicFunctionExecute
+
+Invokes one member of a [dynamic functions](../../../config/core/dynamic-functions.md) object by name, passing it positional args, and returns whatever the member resolves to. A **plain or async member** is called and (if needed) awaited directly. A **generator member** — the shape of every qpq story — is instead driven through the runtime as a nested story (one depth deeper), sharing the caller's action processors and session context, and its story result is returned.
+
+- **Action type:** `DynamicFunctionsActionType.Execute`
+
+```typescript
+import { askDynamicFunctionExecute } from 'quidproquo-core';
+
+import { templateEventDoc } from '../eventDocs/templateEventDoc';
+
+export function* foldTemplate(events: unknown[]) {
+  const views = yield* askDynamicFunctionExecute<typeof templateEventDoc>(
+    'templateEventDoc',
+    'foldSnapshotViews',
+    events,
+  );
+
+  return views;
+}
+```
+
+## Signature
+
+```typescript
+function* askDynamicFunctionExecute<TFunctions extends DynamicFunctions, TName extends keyof TFunctions & string>(
+  dynamicFunctionsName: string,
+  functionName: TName,
+  ...args: Parameters<TFunctions[TName]>
+): AskResponse<DynamicFunctionResult<TFunctions[TName]>>;
+```
+
+The `TFunctions` generic is the type of the registered functions object — pass it explicitly (e.g. `askDynamicFunctionExecute<typeof templateEventDoc>(...)`) so `functionName` and `args` are checked against its members and the return type is inferred.
+
+## Parameters
+
+| Parameter | Type | Description |
+| --- | --- | --- |
+| `dynamicFunctionsName` | `string` | Name of the dynamic functions object to invoke — must match the `dynamicFunctionsName` of a surface registered with [defineDynamicFunctions](../../../config/core/dynamic-functions.md). |
+| `functionName` | `TName` | Name of the member to call on the registered object. |
+| `args` | `Parameters<TFunctions[TName]>` | Positional arguments passed to the member, typed from `TFunctions`. |
+
+## Returns
+
+`DynamicFunctionResult<TFunctions[TName]>` — the value the member resolves to:
+
+- A **generator** member (a story) resolves to its story return value.
+- A **promise-returning** member resolves to its awaited value.
+- Any other member resolves to its plain return value.
+
+## Errors
+
+`askDynamicFunctionExecute` fails with `DynamicFunctionsExecuteErrorTypeEnum`:
+
+| Error | Cause |
+| --- | --- |
+| `DynamicFunctionsNotFound` | No `defineDynamicFunctions` setting is registered under `dynamicFunctionsName`. |
+| `ModuleLoadFailed` | The registered module could not be loaded at runtime. |
+| `FunctionNotFound` | `functionName` is not an own enumerable function on the loaded object (inherited/prototype members don't count). |
+| `FunctionThrew` | A plain or async member threw or rejected. |
+
+If the invoked member is a generator and its own story throws, that error propagates to the caller **with its original error type** (not wrapped in one of the above), with the function name added to the error stack. Catch failures with `askCatch`:
+
+```typescript
+const outcome = yield* askCatch(
+  askDynamicFunctionExecute<typeof templateEventDoc>('templateEventDoc', 'foldSnapshotViews', events),
+);
+
+if (outcome.success) {
+  const views = outcome.result;
+} else {
+  // outcome.error.errorType / outcome.error.errorText
+}
+```
+
+## Notes
+
+- The invoked member runs **in the same process** as the caller — a generator member runs nested one level deeper, not as a separate deployed service — dynamic functions add no infrastructure of their own.
+- `createDynamicFunctionCaller` (also exported from `quidproquo-core`) wraps this action in a typed proxy so call sites read like a normal method call instead of a string-keyed action: `const caller = createDynamicFunctionCaller<typeof templateEventDoc>('templateEventDoc'); yield* caller.foldSnapshotViews(events);` yields the exact same action as calling `askDynamicFunctionExecute` directly.
+
+## Related
+
+- [defineDynamicFunctions](../../../config/core/dynamic-functions.md) — registers the functions object this action invokes members on.
+- [askInlineFunctionExecute](../../core/inline-function/ask-inline-function-execute.md) — the single-function predecessor to this action.

package/template/docusaurus/docs/actions/features/event-doc/ask-event-doc-create.md

@@ -57,7 +57,7 @@ A point-in-time snapshot of who produced an event, captured server-side at appen
 
 ## Notes
 
-- The record is validated against `eventDocSummarySchema` before it is written; a schema violation throws (`ErrorTypeEnum` from quidproquo-core).
+- The record is validated against `eventDocSummaryViewSchema` before it is written; a schema violation throws (`ErrorTypeEnum` from quidproquo-core).
 - Not concurrency-safe against duplicate codes on its own. If two callers may create the same `code` at once, prefer [askEventDocGetByCodeOrCreate](./ask-event-doc-get-by-code.md#askeventdocgetbycodeorcreate) and serialise, or add a conditional create.
 
 ---
@@ -91,12 +91,12 @@ Use `askEventDocCreate` unless you are building a custom create flow that needs
 The bare storage write for a summary record — a thin wrapper over the key-value store upsert (with retry). Business rules and validation live in the logic layer (e.g. `askEventDocCreate`, [askEventDocSoftDelete](./ask-event-doc-soft-delete.md)); this just persists whatever record you hand it.
 
 ```typescript
-function* askEventDocUpsert(model: EventDocSummary): AskResponse<void>;
+function* askEventDocUpsert(view: EventDocSummaryView): AskResponse<void>;
 ```
 
 | Parameter | Type | Description |
 | --- | --- | --- |
-| `model` | `EventDocSummary` | The full summary record to write (create or overwrite). |
+| `view` | `EventDocSummaryView` | The summary view to write (create or overwrite) — `type` is resolved from the store context and stamped on internally. |
 
 **Returns** `void`.
 

package/template/docusaurus/docs/actions/features/event-doc/ask-event-doc-event-append.md

@@ -84,7 +84,7 @@ What the client POSTs to append an event. `modelId` and the server-stamped prove
 
 ## Notes
 
-- **No dedup, no version check, and no lifecycle/domain validation at append time.** All three are decided when the log is folded (`foldEventDocLog`), against the accepted events before the one in question: a repeated `clientMessageId` is ignored, an event whose version is older than the log's highest accepted version is ignored, and the collection's `eventValidator` (or `defaultEventDocEventValidator` when none is configured) is run there too. A rejected event is skipped silently — the document reads as though it was never written — rather than causing the append to throw.
+- **No dedup, no version check, and no lifecycle/domain validation at append time.** All three are decided when the log is folded (`foldEventDocLog`), against the accepted events before the one in question: a repeated `clientMessageId` is ignored, an event whose version is older than the log's highest accepted version is ignored, and the collection's `validators` registry (or `defaultEventDocEventValidator` when none is configured) is run there too. A rejected event is skipped silently — the document reads as though it was never written — rather than causing the append to throw.
 - **No read, no retry, no coordination.** The append does not read the tail or the log; it mints a sortable id and writes. Two appends landing in the same millisecond get an arbitrary but stable relative order, which is fine because ordering only has to be stable, not wall-clock-precise.
 - **Write uniqueness** is still enforced by [askEventDocEventWrite](./ask-event-doc-event-write.md)'s conditional (`ifNotExists`) write, but since ids are unique by construction this should never fire in practice — a collision surfaces as `KeyValueStoreUpsertErrorTypeEnum.Conflict` and indicates a bug (two writers minting the same id), not ordinary contention, so there is no retry around it.
 - After writing, it calls `askEventDocSummaryRederive`, which re-folds the whole log and re-derives the document's summary record so the queryable view (identity, version history, timestamps) stays in sync — this is the one piece of read-model maintenance still on the write path, until a stream projector replaces it.

package/template/docusaurus/docs/actions/features/event-doc/ask-event-doc-event-list.md

@@ -46,6 +46,8 @@ function* askEventDocEventList(
 | `limit` | `number` | (store default) | Max number of events to return in the page. |
 | `nextPageKey` | `string` | — | Continuation token from a previous page's `nextPageKey`. |
 | `afterEventId` | `string` | — | Return only events whose event id sorts after this one (exclusive). A sort-key range condition on the events store's primary key — no GSI involved. |
+| `upToEventId` | `string` | — | Return only events whose event id sorts at or before this one (inclusive) — the log prefix up to a known event, for folding a document as of that event (a snapshot). Not combinable with `afterEventId`: a key condition holds one sort-key range. |
+| `sortDescending` | `boolean` | `false` | Newest first, for a display read that walks backwards in time (e.g. a history panel's latest-page-then-load-older). Folding reads never set this — a fold consumes the log in order. |
 | `consistentRead` | `boolean` | `false` | Strongly consistent read. Needed by a caller that just appended and is now folding to decide something — the default eventually-consistent read can otherwise miss that caller's own most recent event. Costs roughly double the read capacity, so leave it off for ordinary reads. |
 
 ### Returns
@@ -69,7 +71,7 @@ export function* fullHistory(docId: string) {
 ```typescript
 function* askEventDocEventListAll(
   modelId: string,
-  options?: { consistentRead?: boolean },
+  options?: { consistentRead?: boolean; upToEventId?: string },
 ): AskResponse<EventDocEvent[]>;
 ```
 
@@ -79,6 +81,7 @@ function* askEventDocEventListAll(
 | --- | --- | --- |
 | `modelId` | `string` | The document id to read the full log for. |
 | `options.consistentRead` | `boolean` | Optional, default `false`. Strongly consistent read — for a caller that just appended and is now folding to decide something, so it does not miss its own most recent event. Leave off for ordinary reads; it doubles the read cost. |
+| `options.upToEventId` | `string` | Optional. Return only the log prefix up to and including this event id — for folding a document as of a known event (a snapshot). |
 
 ### Returns
 

package/template/docusaurus/docs/actions/features/event-doc/ask-event-doc-get-by-id.md

@@ -29,7 +29,7 @@ An event document is never stored as a mutable blob. Its authoritative state is
 - **Draft vs published** — the tail (highest) version with no `publishedAt` is the **draft**; a `PUBLISH` event freezes it and starts the next draft. Each version pointer records the `eventId` (a sortable id) of its last event (its head), so folding events whose `eventId` sorts at or before that head reconstructs the version's content as it was. `publishedAt` is when a version was published; `effectiveFrom` is when that publish takes effect (used for as-of time-travel).
 - **Code** — the caller-chosen, stable business key set at create (via `INIT_STATE`) and editable with `SET_CODE`. It stays constant across versions and is expected unique within the collection (and any owner scope), so you can address a document by `code` instead of its generated `id`.
 
-The version-pointer reads ([askEventDocGetDraft, askEventDocGetLatestPublished, askEventDocGetPublishedAsOf, askEventDocPublishedEventsAsOf](./ask-event-doc-get-draft.md)) resolve entries in this model.
+The version-pointer reads ([askEventDocGetDraft, askEventDocGetLatestPublished, askEventDocGetPublishedAsOf, askEventDocPublishedVersionAsOf](./ask-event-doc-get-draft.md)) resolve entries in this model.
 
 ### The summary record
 

package/template/docusaurus/docs/actions/features/event-doc/ask-event-doc-get-draft.md

@@ -83,15 +83,15 @@ function* askEventDocGetPublishedAsOf(
 
 **Returns** `EventDocVersion | null` — the highest version with `publishedAt <= clock`, or `null`.
 
-## askEventDocPublishedEventsAsOf
+## askEventDocPublishedVersionAsOf
 
-Returns the **events** that make up the version published and *effective* at `clock` — the log truncated at that version's head. It resolves the version from the summary via `effectiveFrom` (when the publish takes effect, so a publish scheduled for the future stays invisible until then), then returns every event whose `eventId` sorts at or before `version.eventId`. Fold the returned events to get the published, as-of-`clock` content — the generic backbone of a "render published" flow. (This mirrors `askEventDocGetPublishedAsOf`, which returns the version pointer rather than its events, and keys on `publishedAt` rather than `effectiveFrom`.)
+Returns the version published and *effective* at `clock`, together with the document **state** at that version's head — folded snapshot-seeded (via `askEventDocDocumentStateAsOf`), so cost tracks the gap since the nearest snapshot rather than the whole log. It resolves the version from the summary via `effectiveFrom` (when the publish takes effect, so a publish scheduled for the future stays invisible until then), then folds the state as of `version.eventId`. Use `state` directly to render the published, as-of-`clock` content, and `version.publishedAt` to pin the doc's own linked assets to the moment it was published — the generic backbone of a "render published" flow. (This mirrors `askEventDocGetPublishedAsOf`, which returns only the version pointer, and keys on `publishedAt` rather than `effectiveFrom`.)
 
 ```typescript
-function* askEventDocPublishedEventsAsOf(
+function* askEventDocPublishedVersionAsOf(
   id: string,
   clock: QpqIsoDateTime,
-): AskResponse<Nullable<EventDocEvent[]>>;
+): AskResponse<Nullable<EventDocVersionState>>;
 ```
 
 | Parameter | Type | Description |
@@ -99,7 +99,7 @@ function* askEventDocPublishedEventsAsOf(
 | `id` | `string` | Id of the document. |
 | `clock` | `QpqIsoDateTime` | ISO-8601 timestamp to resolve the effective version as-of. |
 
-**Returns** `EventDocEvent[] | null` — the truncated event log for the effective version, or `null` when the document is missing/deleted or nothing is effective yet. Reads the full log via `askEventDocEventListAll` (quidproquo-features).
+**Returns** `EventDocVersionState | null` — `{ version, state }` for the effective version, or `null` when the document is missing/deleted, nothing is effective yet, or the version's events are gone (a rewritten log).
 
 ## Related
 

package/template/docusaurus/docs/actions/features/event-doc/ask-event-doc-provide-store.md

@@ -17,10 +17,11 @@ This is the same pattern as [askContextProvideValue](../../core/context/ask-cont
 | `eventsStoreName` | `string` | The events-log store name — by convention `` `${storeName}Events` ``. |
 | `type` | `string` | Pins the document type within a store that can hold several. |
 | `storageDriveName` | `string` | The collection's blob bucket (assets + runtime artifacts), keyed per-doc. |
-| `eventValidator` | `string` (optional) | The collection's append-time validator inline-function name, if configured. |
-| `eventRenderer` | `string` (optional) | The collection's render inline-function name, if configured (powers `GET .../render`). |
+| `onPublish` | `string` (optional) | The collection's on-publish inline-function name, if configured. Invoked after a Publish event is durably appended. |
+| `onAppend` | `string` (optional) | The collection's on-append inline-function name, if configured. Invoked after every successful append. |
 | `scopeResolver` | `string` (optional) | The collection's ambient storage scope resolver inline-function name, if configured (e.g. per-tenant). |
-| `referenceResolver` | `string` (optional) | The collection's reference-collector inline-function name, if configured (powers `GET .../references` and the transfer feature's manifest walk). |
+
+Render, references, and snapshot behaviour are no longer carried on the store binding — they come from the collection's registered `EventDocFunctions` object, addressed by `storeName`/`type` via `eventDocFunctionsName(storeName, type)` (see [defineEventDoc](../../../config/features/event-doc.md)).
 
 There are two ways to establish the context — one for custom routes, one for the built-in routes — plus the raw provide/read primitives and a resolver that throws when the binding is missing.
 
@@ -64,12 +65,9 @@ function* askEventDocProvideStore<T>(
 | --- | --- | --- |
 | `storeName` | `string` | The collection's record store name; the events-table and blob-drive names are derived from it. |
 | `type` | `string` | The document type pinned within the store. |
-| `eventValidator` | `string` (optional) | Append-time validator inline-function name. |
-| `eventRenderer` | `string` (optional) | Render inline-function name. |
 | `onPublish` | `string` (optional) | Inline-function name invoked after a Publish append. |
 | `onAppend` | `string` (optional) | Inline-function name invoked after every append. |
 | `scopeResolver` | `string` (optional) | Ambient storage scope resolver inline-function name. |
-| `referenceResolver` | `string` (optional) | Reference-collector inline-function name (powers `GET .../references`). |
 
 ### Returns
 
@@ -77,7 +75,7 @@ function* askEventDocProvideStore<T>(
 
 ## askEventDocProvideStoreFromGlobals
 
-The built-in-routes counterpart: bridges the per-route **globals** that `defineEventDocRoutes` sets (store name, events-store name, type, storage drive, and the optional validator/renderer) into the store context, then runs the controller sub-story. Reads each global with [askConfigGetGlobal](../../core/config/ask-config-get-global.md), which throws if a route forgot to set them.
+The built-in-routes counterpart: bridges the per-route **globals** that `defineEventDocRoutes` sets (store name, events-store name, type, storage drive, and the optional onPublish/onAppend/scopeResolver hooks) into the store context, then runs the controller sub-story. Reads each global with [askConfigGetGlobal](../../core/config/ask-config-get-global.md), which throws if a route forgot to set them.
 
 ```typescript
 import { askEventDocProvideStoreFromGlobals } from 'quidproquo-features';
@@ -123,7 +121,7 @@ function* askEventDocStoreProvide<T>(
 
 ## askEventDocStoreRead
 
-The raw context **reader**: returns the currently bound [`EventDocStore`](#eventdocstore--the-binding). Built with `createContextReader`. Outside a provider it returns the **empty default** (blank `storeName` / `type`) rather than throwing — so most callers should prefer [askEventDocResolveStore](#askeventdocresolvestore). Internal data stories that only need one field (e.g. `eventValidator`) read it directly.
+The raw context **reader**: returns the currently bound [`EventDocStore`](#eventdocstore--the-binding). Built with `createContextReader`. Outside a provider it returns the **empty default** (blank `storeName` / `type`) rather than throwing — so most callers should prefer [askEventDocResolveStore](#askeventdocresolvestore). Internal data stories that only need one field (e.g. `scopeResolver`) read it directly.
 
 ### Signature
 

package/template/docusaurus/docs/actions/features/event-doc/ask-event-doc-references-from-state.md

@@ -0,0 +1,50 @@
+---
+title: askEventDocReferencesFromState
+description: The other docs the CURRENT document depends on, one hop out, folded snapshot-seeded rather than walking the log.
+---
+
+# askEventDocReferencesFromState
+
+Reads the `EventDocLink`s the **current** document state depends on, one hop out. Folds the document snapshot-seeded (via [askEventDocDocumentStateLatest](./ask-event-doc-get-by-id.md)) and hands the folded state to the `collectReferencesFromState` member of the collection's registered `EventDocFunctions` object (looked up as `eventDocFunctionsName(storeName, type)`, see [defineEventDoc](../../../config/features/event-doc.md)). No log walk — this is the references ROUTE's read: what the document references now, at the cost of the gap since the nearest snapshot rather than the whole log.
+
+A collection with no registered functions object is a leaf: this returns `[]`. So does a document with no events.
+
+- **Built from:** [askEventDocResolveStore](./ask-event-doc-provide-store.md#askeventdocresolvestore) (to read the collection's `storeName`/`type`, which address its functions registration) and `askEventDocDocumentStateLatest` (the folded state `collectReferencesFromState` walks). Requires the store context — call it inside `askEventDocProvideStore({ storeName, type }, ...)`, or from a built-in route where the context is already provided.
+
+```typescript
+import { askEventDocReferencesFromState } from 'quidproquo-features';
+
+export function* readTemplateDependencies(templateId: string) {
+  const links = yield* askEventDocReferencesFromState(templateId);
+
+  return links; // EventDocLink[] — e.g. the template's layout, styles, and content
+}
+```
+
+## Signature
+
+```typescript
+function* askEventDocReferencesFromState(docId: string): AskResponse<EventDocLink[]>;
+```
+
+## Parameters
+
+| Parameter | Type | Description |
+| --- | --- | --- |
+| `docId` | `string` | The document to read outbound references for. |
+
+## Returns
+
+`EventDocLink[]` — the doc's outbound links, one hop out, as of the current state. Empty when the collection has no registered `EventDocFunctions` object, that object's `collectReferencesFromState` returns none, or the document has no events.
+
+## Notes
+
+- This is a **one-hop, current-state** read — the full-history equivalent (every link ANY historical state ever held) is [askEventDocReferences](./ask-event-doc-references.md), used by the transfer export instead.
+- `GET {basePath}/{id}/references`, mounted by [defineEventDocRoutes](../../../config/features/event-doc-routes.md), calls this for one document; the route is always mounted, resolving to `[]` when no functions object is registered.
+
+## Related
+
+- [defineEventDoc](../../../config/features/event-doc.md) — registers the `EventDocFunctions` object (`collectReferencesFromState`) this reads.
+- [askEventDocReferences](./ask-event-doc-references.md) — the full-history sibling read, used by the transfer export.
+- [askEventDocRenderForCollection](./ask-event-doc-render-for-collection.md) — the sibling read (`render`) on the same registered object.
+- [askEventDocGetByIdOrThrow](./ask-event-doc-get-by-id.md) — read the document's own summary alongside its references.

package/template/docusaurus/docs/actions/features/event-doc/ask-event-doc-references.md

@@ -1,13 +1,15 @@
 ---
 title: askEventDocReferences
-description: The other docs one document depends on, one hop out, via its collection's referenceResolver.
+description: Every doc one document has ever depended on, across its whole history, via its collection's registered EventDocFunctions object.
 ---
 
 # askEventDocReferences
 
-Reads the `EventDocLink`s a document depends on, one hop out. Hands the collection's `referenceResolver` inline function (see [defineEventDocRoutes](../../../config/features/event-doc-routes.md#parameters)) the document's whole event log and lets it fold + walk it. A collection with no resolver configured is a leaf: this returns `[]` without reading the log at all.
+Reads the `EventDocLink`s a document has **ever** depended on, one hop out, across its whole history. Hands the document's whole event log to the `collectReferences` member of the collection's registered `EventDocFunctions` object (looked up as `eventDocFunctionsName(storeName, type)`, see [defineEventDoc](../../../config/features/event-doc.md)) and lets it fold + walk it, so a link that existed only in an older version is still found. A collection with no registered functions object is a leaf: this returns `[]`.
 
-- **Built from:** [askEventDocResolveStore](./ask-event-doc-provide-store.md#askeventdocresolvestore) (to read the collection's `referenceResolver` name) and `askEventDocEventListAll` (the full log the resolver folds). Requires the store context — call it inside `askEventDocProvideStore({ storeName, type }, ...)`, or from a built-in route where the context is already provided.
+This is the **transfer export's** read — it exports the whole history and must chase links from all of it. `GET {basePath}/{id}/references` uses [askEventDocReferencesFromState](./ask-event-doc-references-from-state.md) instead (the CURRENT document only, folded snapshot-seeded rather than walking the log).
+
+- **Built from:** [askEventDocResolveStore](./ask-event-doc-provide-store.md#askeventdocresolvestore) (to read the collection's `storeName`/`type`, which address its functions registration) and `askEventDocEventListAll` (the full log `collectReferences` folds). Requires the store context — call it inside `askEventDocProvideStore({ storeName, type }, ...)`, or from a built-in route where the context is already provided.
 
 ```typescript
 import { askEventDocReferences } from 'quidproquo-features';
@@ -33,15 +35,17 @@ function* askEventDocReferences(docId: string): AskResponse<EventDocLink[]>;
 
 ## Returns
 
-`EventDocLink[]` — the doc's outbound links, one hop out. Empty when the collection has no `referenceResolver` configured.
+`EventDocLink[]` — the doc's outbound links, one hop out. Empty when the collection has no registered `EventDocFunctions` object, or that object's `collectReferences` returns none.
 
 ## Notes
 
-- This is a **one-hop** read. The recursive walk over these edges (following a template into its content, then that content's own references, and so on) is the transfer feature's job — see [askEventDocManifest](../event-doc-transfer/ask-event-doc-manifest.md).
-- `GET {basePath}/{id}/references`, mounted by [defineEventDocRoutes](../../../config/features/event-doc-routes.md), calls this for one document; the route is always mounted, resolving to `[]` when no `referenceResolver` is configured.
+- This is a **one-hop** read, over the **whole log**. The recursive walk over these edges (following a template into its content, then that content's own references, and so on) is the transfer feature's job — see [askEventDocManifest](../event-doc-transfer/ask-event-doc-manifest.md).
+- `GET {basePath}/{id}/references`, mounted by [defineEventDocRoutes](../../../config/features/event-doc-routes.md), calls [askEventDocReferencesFromState](./ask-event-doc-references-from-state.md) instead of this — the route only ever needs the CURRENT document's references.
 
 ## Related
 
-- [defineEventDocRoutes](../../../config/features/event-doc-routes.md) — declares the `referenceResolver` this reads.
+- [defineEventDoc](../../../config/features/event-doc.md) — registers the `EventDocFunctions` object (`collectReferences`) this reads.
+- [askEventDocReferencesFromState](./ask-event-doc-references-from-state.md) — the sibling, current-state-only read backing the references route.
+- [askEventDocRenderForCollection](./ask-event-doc-render-for-collection.md) — the sibling read (`render`) on the same registered object.
 - [askEventDocManifest](../event-doc-transfer/ask-event-doc-manifest.md) — the recursive walk built on top of this, one collection at a time.
 - [askEventDocGetByIdOrThrow](./ask-event-doc-get-by-id.md) — read the document's own summary alongside its references.

package/template/docusaurus/docs/actions/features/event-doc/ask-event-doc-render-for-collection.md

@@ -0,0 +1,54 @@
+---
+title: askEventDocRenderForCollection
+description: Render a document from another collection in-process, addressed by identity alone.
+---
+
+# askEventDocRenderForCollection
+
+Renders a document of **another** collection in-process — the in-lambda twin of the `GET {basePath}/{id}/render` route, for cross-collection composition (a template resolving its layout or content links as HTML). Provides the target collection's store context so the renderer's own reads (blob-drive assets, linked docs) resolve against the right stores, then invokes the `render` member of that collection's registered `EventDocFunctions` object with the caller-supplied `input`.
+
+Unlike the render route, nothing here is soft: the caller names a specific collection expecting a renderer, so a missing registration or a functions object with no `render` member propagates as its dynamic-functions error rather than a 404.
+
+- **Built from:** `askEventDocProvideStore` (to bind the target collection's store context) and `createDynamicFunctionCaller<EventDocInvokableFunctions>` (to invoke `render` on `eventDocFunctionsName(storeName, type)`, see [defineEventDoc](../../../config/features/event-doc.md)). The caller resolves WHICH state to render first — this only renders the input it's handed.
+
+```typescript
+import { askEventDocRenderForCollection } from 'quidproquo-features';
+
+export function* renderTemplateLayout(state: unknown, docId: string) {
+  const result = yield* askEventDocRenderForCollection('layouts', 'layout', { state, docId });
+
+  return result.html;
+}
+```
+
+## Signature
+
+```typescript
+function* askEventDocRenderForCollection(
+  storeName: string,
+  type: string,
+  input: EventDocRenderInput,
+): AskResponse<EventDocRenderResult>;
+```
+
+## Parameters
+
+| Parameter | Type | Description |
+| --- | --- | --- |
+| `storeName` | `string` | The target collection's store name (not necessarily the caller's own). |
+| `type` | `string` | The target collection's document type. |
+| `input` | `EventDocRenderInput` | `{ state, docId, version?, renderMode?, effectiveAt? }` — the already-folded document state to render, exactly as the render route builds it. |
+
+## Returns
+
+`AskResponse<EventDocRenderResult>` — the rendered result (e.g. `{ kind: 'html', html }`).
+
+## Notes
+
+- Requires the target collection to have a `render` member on its registered `EventDocFunctions` object; a collection with none throws the dynamic-functions "not found" error rather than resolving to an empty result.
+- The caller is responsible for resolving `renderMode`/`effectiveAt` into a concrete, already-folded `state` before calling this — it renders exactly what it's handed, the same contract the render route's controller follows.
+
+## Related
+
+- [defineEventDoc](../../../config/features/event-doc.md) — registers the `EventDocFunctions` object (`render`) this invokes.
+- [askEventDocReferences](./ask-event-doc-references.md) — the sibling one-hop read (`collectReferences`) on the same registered object.

package/template/docusaurus/docs/actions/features/event-doc-transfer/ask-event-doc-manifest.md

@@ -5,7 +5,7 @@ description: Walk one or more docs' references outward to find everything that h
 
 # askEventDocManifest
 
-Finds every doc that has to travel with a list of starting docs, by following each doc's `referenceResolver` links outward — breadth-first, across collections, with a visited set so a stylesheet three templates share is walked once and lands in the result once. Also the source of a cycle's termination: a link cycle (template → content → template) stops on the visited check instead of recursing forever.
+Finds every doc that has to travel with a list of starting docs, by following each doc's `collectReferences` links outward — breadth-first, across collections, with a visited set so a stylesheet three templates share is walked once and lands in the result once. Also the source of a cycle's termination: a link cycle (template → content → template) stops on the visited check instead of recursing forever.
 
 Takes a **list** of roots so selecting several documents produces one merged manifest, rather than one per selection. A soft-deleted doc is reported (`deleted: true`) but not walked into — it will never be bundled, so its own dependencies are moot.
 

package/template/docusaurus/docs/config/core/dynamic-functions.md

@@ -0,0 +1,65 @@
+---
+title: defineDynamicFunctions
+description: Register a module's exported object of functions as a named dynamic-functions surface that other stories can invoke by member name with askDynamicFunctionExecute.
+---
+
+# defineDynamicFunctions
+
+Registers a module export — an **object whose properties are functions** — under a name, so any story can invoke one of its members by name with [askDynamicFunctionExecute](../../actions/core/dynamic-functions/ask-dynamic-function-execute.md) without a per-function registration. It is the successor to [defineInlineFunction](./inline-function.md): one setting addresses a whole surface (name + member) instead of one function per entry.
+
+- **On AWS:** deploys **no dedicated infrastructure** of its own. The referenced module is loaded and its member is invoked inside whatever Lambda is already running the calling story, sharing its action processors and session context. Registration simply makes the surface resolvable by name.
+
+```typescript
+import { defineDynamicFunctions } from 'quidproquo-core';
+
+export default [
+  defineDynamicFunctions('templateEventDoc', '/entry/eventDocs::templateEventDoc'),
+];
+```
+
+## Signature
+
+```typescript
+function defineDynamicFunctions(
+  dynamicFunctionsName: string,
+  runtime: QpqFunctionRuntime,
+  options?: QPQConfigAdvancedDynamicFunctionsSettings,
+): DynamicFunctionsQPQConfigSetting;
+```
+
+## Parameters
+
+### `dynamicFunctionsName` — `string` (required)
+
+The name callers pass to [askDynamicFunctionExecute](../../actions/core/dynamic-functions/ask-dynamic-function-execute.md). This is the config's `uniqueKey`.
+
+### `runtime` — `QpqFunctionRuntime` (required)
+
+A reference to the module to register, usually a relative path string of the form `'/path/to/file::exportedObjectName'`. The exported value must be an object whose own enumerable properties are functions — that object's members are the callable surface.
+
+### `options` — `QPQConfigAdvancedDynamicFunctionsSettings` (optional)
+
+| Property | Type | Default | Description |
+| --- | --- | --- | --- |
+| `owner` | `CrossModuleOwner<'dynamicFunctionsName'>` | – | Declares that the functions object is owned by **another** module/service, so it can be resolved/invoked across modules. `{ module, application, feature, environment, dynamicFunctionsName }` — all optional; unset parts default to the current service. |
+| `deprecated` | `boolean` | `false` | Marks the setting as deprecated in the config. |
+
+## Examples
+
+```typescript
+import { defineDynamicFunctions } from 'quidproquo-core';
+
+export default [
+  defineDynamicFunctions('templateEventDoc', '/entry/eventDocs::templateEventDoc'),
+
+  // Owned by another module
+  defineDynamicFunctions('billingHelpers', '/entry/functions/billing::billingHelpers', {
+    owner: { module: 'billing' },
+  }),
+];
+```
+
+## Related
+
+- [askDynamicFunctionExecute](../../actions/core/dynamic-functions/ask-dynamic-function-execute.md) — invokes a member of a registered dynamic-functions object by name and returns its result.
+- [defineInlineFunction](./inline-function.md) — registers a single story as a callable function; use this instead when the surface is one exported object with several members.

package/template/docusaurus/docs/config/features/admin-session-event-doc.md

@@ -7,7 +7,7 @@ description: Declare the event document that records one audited session per adm
 
 Declares the **admin session event document** — the audit record behind the admin dashboard. It creates one event doc per admin login, appending every user-intent event for that session so operator activity in the dashboard is fully auditable.
 
-It is built on the quidproquo **eventDoc** feature (`defineEventDoc`): an event document is an append-only, per-instance record backed by storage, routes, and a WebSocket feed. This define fixes that eventDoc's store name, type, base path, and auth directory to the admin conventions, so you don't configure them yourself.
+It is built on the quidproquo **eventDoc** feature — an event document is an append-only, per-instance record backed by storage, routes, and a WebSocket feed — composed directly from [defineEventDocSummary](./event-doc-summary.md) and [defineEventDocRoutes](./event-doc-routes.md) rather than [defineEventDoc](./event-doc.md), since the session collection registers no functions object (no render, no references, no snapshots). This define fixes the store name, type, base path, and auth directory to the admin conventions, so you don't configure them yourself.
 
 `defineAdminSessionEventDoc` returns a `QPQConfig` array. It is spread in automatically by [defineAdminSettings](./admin-settings.md), so you rarely call it directly — but it is exported for services that assemble the admin feature piece by piece.
 

package/template/docusaurus/docs/config/features/event-doc-routes.md

@@ -5,7 +5,7 @@ description: Mount the built-in HTTP routes for an event-sourced document collec
 
 # defineEventDocRoutes
 
-Mounts the built-in REST **routes** for one document `type` in an event-document collection. It returns a `QPQConfig` (an array of route settings). The route controllers ship inside `quidproquo-features` and resolve the store, type, user directory, validator, and renderer from per-route globals — so a service needs no controller wiring of its own: declare the store, add these routes, and the collection is fully served.
+Mounts the built-in REST **routes** for one document `type` in an event-document collection. It returns a `QPQConfig` (an array of route settings). The route controllers ship inside `quidproquo-features` and resolve the store, type, and user directory from per-route globals, invoking the collection's registered `EventDocFunctions` object (looked up by convention as `eventDocFunctionsName(storeName, type)`, see [defineEventDoc](./event-doc.md)) for render/references/snapshot behaviour — so a service needs no controller wiring of its own: declare the store, register the functions object, add these routes, and the collection is fully served.
 
 `defineEventDocRoutes` defines **only** the routes; it assumes the store already exists (declared with [defineEventDocSummary](./event-doc-summary.md)). Use it directly when **several document types share one store** — call `defineEventDocSummary` once, then `defineEventDocRoutes` per type. For the single-type case, [defineEventDoc](./event-doc.md) does both in one call.
 
@@ -33,9 +33,9 @@ All paths are prefixed with the version segment `/v{version}` (default `/v1`):
 | --- | --- | --- |
 | `GET` | `{basePath}` | List one page of the collection's documents (newest first). Accepts `?limit=` and `?nextPageKey=` and returns `QpqPagedData`. |
 | `GET` | `{basePath}/{id}` | Get one document's summary record. |
-| `GET` | `{basePath}/{id}/events` | List a document's event log. |
-| `GET` | `{basePath}/{id}/render` | Render the document to HTML. **Only mounted when `eventRenderer` is set.** |
-| `GET` | `{basePath}/{id}/references` | List the `EventDocLink`s this document depends on. |
+| `GET` | `{basePath}/{id}/events` | List a document's event log. Accepts `?limit=`, `?nextPageKey=`, `?afterEventId=` (exclusive — the tail since a known event), and `?newestFirst=true` (walk the log backwards — the history panel's latest-page-then-load-older read). With `?includeBase=true` the response becomes the bootstrap shape: `{ base, items, nextPageKey }`, where `base` is the newest usable document-view snapshot (`{ eventId, state }`, era-pinned) and `items` starts after it — or `base: null` with the log from event zero when no usable snapshot exists, so the fallback needs no second request shape. The base rides the first page only; page the rest with `?afterEventId=base.eventId`. |
+| `GET` | `{basePath}/{id}/render` | Render the document. Resolves the target state snapshot-seeded (draft = the log's head, `?renderMode=published` = the version effective at `?effectiveAt=`/now) and hands the registered `render` member `{ state, docId, version?, ... }` — a render never replays a whole log. 404s as "no renderer configured" when the collection's registered functions object has no `render` member. |
+| `GET` | `{basePath}/{id}/references` | List the `EventDocLink`s the CURRENT document state depends on (walks the folded state, not the log; the transfer export keeps the full-history walk). Resolves to `[]` when the collection has no registered functions object. |
 | `POST` | `{basePath}` | Create a document. |
 | `POST` | `{basePath}/{id}/events` | Append an event to a document. |
 | `POST` | `{basePath}/{id}/assets` | Request an asset upload URL. |
@@ -60,14 +60,13 @@ The single `options` argument is an `EventDocRoutesOptions`:
 | `basePath` | `` `/${string}` `` | – (required) | URL prefix the routes mount under. Must start with `/`, e.g. `/articles`. |
 | `routeAuthSettings` | `RouteAuthSettings` | – | Auth settings applied to every mounted route (from quidproquo-webserver — see [route](../webserver/route.md)). When it carries a `userDirectoryName`, that directory is exposed to the controllers so mutations can attribute the acting user. **Omit to leave the routes open** — mutations then have no user to attribute. |
 | `version` | `number` | `1` | Version number for the `/v{version}` path prefix on every route. |
-| `eventValidator` | `string` | – | Name of a registered inline function (see `defineInlineFunction`). When set, every append invokes it with `{ event, events }` to reject lifecycle- or payload-invalid events before they reach the log. The frontend editor runs the same rule for instant feedback. |
-| `eventRenderer` | `string` | – | Name of a registered inline function. When set, a `GET {basePath}/{id}/render` route is mounted; it invokes the renderer with the document's full `{ events }` log, which folds + renders to HTML. |
-| `onPublish` | `string` | – | Name of a registered inline function. When set, every successful append of a Publish event invokes it with `{ docId, event, summary }`, after the event is durably written and the summary re-derived. This is the seam for syncing a folded document into a materialized read model. Errors propagate to the caller: the event has landed but the side effect did not, so the caller learns the read model may be stale. |
-| `onAppend` | `string` | – | Name of a registered inline function. When set, EVERY successful append (domain events and lifecycle events alike) invokes it with `{ docId, event, summary, events }`, after the event is durably written and the summary re-derived. This is the seam for reacting to any mutation (e.g. broadcasting the doc's fresh fold). Runs after `onPublish` when both fire on the same Publish event. Errors propagate to the caller: the event has landed but the side effect did not. |
+| `onPublish` | `string` | – | Name of a registered inline function. When set, every successful append of a Publish event invokes it with `{ docId, event, summary, state, previousState }` — the FOLDED document as of the publish event and as of the event before it (latest-shaped, snapshot-seeded, so hook cost tracks the burst since the last snapshot, never the log) — after the event is durably written. This is the seam for syncing a folded document into a materialized read model: use `state`, never re-fold. Errors propagate to the caller: the event has landed but the side effect did not, so the caller learns the read model may be stale. |
+| `onAppend` | `string` | – | Name of a registered inline function. When set, EVERY successful append (domain events and lifecycle events alike) invokes it with `{ docId, event, summary, state, previousState }` — the FOLDED document as of the event and as of its predecessor (latest-shaped, snapshot-seeded) — after the event is durably written. This is the seam for reacting to any mutation (e.g. broadcasting the doc's fresh fold, or diffing `previousState` vs `state` to detect a transition). Runs after `onPublish` when both fire on the same Publish event. Errors propagate to the caller: the event has landed but the side effect did not. |
 | `scopeResolver` | `string` | – | Name of a registered inline function. When set, every route invokes it with `{ event }` before running; a non-null result becomes the ambient storage scope for the whole request, transparently partitioning the collection's stores and assets (e.g. per-tenant). Null means unscoped. Omit for collections that never partition. |
-| `referenceResolver` | `string` | – | Name of a registered inline function. When set, `GET {basePath}/{id}/references` invokes it with the document's `{ events, docId }` log, which folds and returns the `EventDocLink`s that view depends on (e.g. a template's layout/style/content links). The transfer feature's manifest walk follows those links recursively. Omit for a leaf collection (a stylesheet, a layout) — the route is still mounted but always resolves to `[]`. |
 | `excludeRoutes` | `EventDocRouteName[]` | `[]` | Route names to leave unmounted (`'list' \| 'get' \| 'listEvents' \| 'render' \| 'references' \| 'create' \| 'appendEvent' \| 'createAsset' \| 'getAsset' \| 'listAssets' \| 'remove'`). For a collection that must own one of these itself instead of using the stock behavior — e.g. a `create` that must also perform some side effect the stock controller doesn't know about. |
 
+Append-time validation, rendering, references, and snapshotting are no longer per-route options: they come from the collection's registered `EventDocFunctions` object (`collectReferences`, `render`, `foldSnapshotViews`, and the doc type's own fold-gate `validators`), addressed by `eventDocFunctionsName(storeName, type)`. Register it with [defineDynamicFunctions](../core/dynamic-functions.md) directly (a multi-type store calling `defineEventDocRoutes` per type) or let [defineEventDoc](./event-doc.md) do it for the single-type case.
+
 ### `RouteAuthSettings`
 
 `routeAuthSettings` is the standard quidproquo-webserver route auth object (the same one [defineRoute](../webserver/route.md) accepts). Its `userDirectoryName` names the [user directory](../core/key-value-store.md) callers authenticate against; the controllers read it to resolve the acting user for event attribution.
@@ -75,19 +74,20 @@ The single `options` argument is an `EventDocRoutesOptions`:
 ## Examples
 
 ```typescript
-import { defineEventDocSummary, defineEventDocRoutes } from 'quidproquo-features';
+import { defineDynamicFunctions } from 'quidproquo-core';
+import { defineEventDocSummary, defineEventDocRoutes, eventDocFunctionsName } from 'quidproquo-features';
 
 export default [
   // One store, two types, each on its own path and route version.
-  ...defineEventDocSummary('content'),
+  ...defineEventDocSummary('content', { snapshotFunctions: { article: eventDocFunctionsName('content', 'article') } }),
+
+  defineDynamicFunctions(eventDocFunctionsName('content', 'article'), '/entry/eventDocs::articleDefinition'),
 
   ...defineEventDocRoutes({
     storeName: 'content',
     type: 'article',
     basePath: '/articles',
     routeAuthSettings: { userDirectoryName: 'editors' },
-    eventValidator: 'validateArticleEvent',
-    eventRenderer: 'renderArticle',
   }),
 
   ...defineEventDocRoutes({
@@ -102,7 +102,8 @@ export default [
 ## Related
 
 - [defineEventDocSummary](./event-doc-summary.md) — declares the store these routes serve (required before mounting routes).
-- [defineEventDoc](./event-doc.md) — declares the store *and* these routes in one call for the single-type case.
-- [defineEventDocTransfer](./event-doc-transfer.md) — mounts the export/import routes that read every registered collection's `referenceResolver` to build a transfer manifest.
+- [defineEventDoc](./event-doc.md) — declares the store, registers the functions object, *and* mounts these routes in one call for the single-type case.
+- [defineDynamicFunctions](../core/dynamic-functions.md) — registers the `EventDocFunctions` object these routes invoke for render/references/snapshot behaviour.
+- [defineEventDocTransfer](./event-doc-transfer.md) — mounts the export/import routes that read every registered collection's functions object (`collectReferences`) to build a transfer manifest.
 - [defineRoute](../webserver/route.md) — the underlying webserver route config (source of `RouteAuthSettings`).
 - **Custom routes over the same store:** wrap your controllers in `askEventDocProvideStore({ storeName, type }, ...)` (from quidproquo-features) so the generic [reads](../../actions/features/event-doc/ask-event-doc-get-by-id.md) resolve the collection, then compose actions like [askEventDocCreate](../../actions/features/event-doc/ask-event-doc-create.md).

package/template/docusaurus/docs/config/features/event-doc-summary.md

@@ -5,16 +5,17 @@ description: Declare the stores for an event-sourced document collection — its
 
 # defineEventDocSummary
 
-Declares the **stores** that back an event-document collection, without any routes. It returns a `QPQConfig` (an array of config settings) that expands to four underlying core stores:
+Declares the **stores** that back an event-document collection, without any routes. It returns a `QPQConfig` (an array of config settings) that expands to five underlying core stores:
 
 1. A **summary key-value store** (partition key `type`, sort key `id`) — the queryable record for each document, derived by folding the identity/lifecycle events of its log. Rows are the [`EventDocSummary`](../../actions/features/event-doc/ask-event-doc-get-by-id.md) shape and carry the version history. A secondary index on `(type, updatedAt)` supports the recently-updated ordering [askEventDocList](../../actions/features/event-doc/ask-event-doc-list.md) returns. It is a pure projection: nothing on the append path writes it directly. The events store below declares an [`onStream`](../core/key-value-store.md#change-data-capture-onstream) handler that rebuilds a document's summary row from its log whenever an event is appended, so the summary is eventually (not immediately) consistent with the log.
 2. An **append-only events store** (`<storeName>EventLog`, partition key `pk`, string sort key `sk`) — the live ordered log every document is folded from, keyed on a sortable event id (UUIDv7). It has **no** secondary index on purpose: the local dev-server query processor can't target one, so all event reads go through the main table.
-3. A **legacy events store** (`<storeName>Events`, partition key `pk`, numeric sort key `sk`) — the pre-sortable-id log, kept declared but unread/unwritten at runtime so its data stays reachable until it is migrated into the events store above.
-4. A **storage drive** (`<storeName>edocs`, lower-cased) — the collection's blob bucket, holding each document's immutable uploaded assets (and later its derived runtime artifacts) under per-document prefixes.
+3. A **snapshots store** (`<storeName>SS`, partition key `pk`, sort key `sk`) — per-view folded states at points along the log (`pk = docId#view`, `sk` the same sortable event id the log is ordered by). Populated only for the document types you enable via `options.snapshotFunctions`; a type with no entry there simply is not snapshotted. For a type with a registered functions object, the `onStream` handler runs ONE incremental fold per delivery — resuming from the newest usable snapshot and folding only the gap since it — and persists both the snapshot set and the summary row from that same fold (the fold's `summary` view IS the queryable record). The whole-log summary re-derivation remains only as the fallback: types with no registered functions, Remove stream records (a transfer rewrote the log, so snapshots can't seed), and folds that decline.
+4. A **legacy events store** (`<storeName>Events`, partition key `pk`, numeric sort key `sk`) — the pre-sortable-id log, kept declared but unread/unwritten at runtime so its data stays reachable until it is migrated into the events store above.
+5. A **storage drive** (`<storeName>edocs`, lower-cased) — the collection's blob bucket, holding each document's immutable uploaded assets (and later its derived runtime artifacts) under per-document prefixes.
 
-Point-in-time recovery is enabled on all three tables.
+Point-in-time recovery is enabled on all tables.
 
-- **On AWS:** deploys three DynamoDB tables (via [defineKeyValueStore](../core/key-value-store.md)) and one S3 bucket (via [defineStorageDrive](../core/storage-drive.md)). All physical names are derived from `keyValueStoreName`, so a collection needs only that one name.
+- **On AWS:** deploys four DynamoDB tables (via [defineKeyValueStore](../core/key-value-store.md)) and one S3 bucket (via [defineStorageDrive](../core/storage-drive.md)). All physical names are derived from `keyValueStoreName`, so a collection needs only that one name.
 
 ```typescript
 import { defineEventDocSummary } from 'quidproquo-features';
@@ -29,7 +30,7 @@ Use `defineEventDocSummary` when you want to define the store separately from th
 ## Signature
 
 ```typescript
-function defineEventDocSummary(keyValueStoreName: string): QPQConfig;
+function defineEventDocSummary(keyValueStoreName: string, options?: EventDocSummaryOptions): QPQConfig;
 ```
 
 ## Parameters
@@ -38,6 +39,12 @@ function defineEventDocSummary(keyValueStoreName: string): QPQConfig;
 
 The collection's base store name. It is used directly as the summary store name and as the `storeName` that route definitions and store-context calls reference. The events table name (`` `${name}Events` ``) and asset bucket name (`` `${name}edocs`.toLowerCase() ``) are both derived from it, so the whole collection is addressed by this single name. It must match the `storeName` passed to any [defineEventDocRoutes](./event-doc-routes.md) (or [askEventDocProvideStore](#related)) for the same collection.
 
+### `options` — `EventDocSummaryOptions` (optional)
+
+| Property | Type | Default | Description |
+| --- | --- | --- | --- |
+| `snapshotFunctions` | `Record<string, string>` | `{}` | Registered dynamic-functions names (see [defineDynamicFunctions](../core/dynamic-functions.md)) of each collection's `EventDocFunctions` object, keyed by document `type` — keyed because one events table can host several collections and its one stream serves them all. When a row's type has an entry, the stream projector invokes that object's `foldSnapshotViews` with the doc's log prefix (or, once a usable snapshot exists, just the gap since it, plus that snapshot's per-view state as `seedViews`) and writes the folded views to the snapshots store; a type with no entry is not snapshotted. [defineEventDoc](./event-doc.md) threads the single-type case through automatically — call this directly only for a multi-type store. |
+
 ## Examples
 
 ```typescript
@@ -52,6 +59,19 @@ export default [
 ];
 ```
 
+```typescript
+import { defineDynamicFunctions } from 'quidproquo-core';
+import { defineEventDocRoutes, defineEventDocSummary, eventDocFunctionsName } from 'quidproquo-features';
+
+// A shared store where "article" documents are snapshotted and "page" documents are not.
+export default [
+  ...defineEventDocSummary('content', { snapshotFunctions: { article: eventDocFunctionsName('content', 'article') } }),
+  defineDynamicFunctions(eventDocFunctionsName('content', 'article'), '/entry/eventDocs::articleDefinition'),
+  ...defineEventDocRoutes({ storeName: 'content', type: 'article', basePath: '/articles' }),
+  ...defineEventDocRoutes({ storeName: 'content', type: 'page', basePath: '/pages' }),
+];
+```
+
 ## Related
 
 - [defineEventDocRoutes](./event-doc-routes.md) — mounts the HTTP routes against a store declared here (one per type).

package/template/docusaurus/docs/config/features/event-doc-transfer.md

@@ -7,7 +7,7 @@ description: Mount export/import routes that move event-doc collections between
 
 Mounts the export/import **routes** for a service's event-doc collections: a staging storage drive plus five routes that build, stage, plan, and apply portable bundles of one or more documents (and everything they reference). It returns a `QPQConfig` (an array of config settings) that you spread into a service's infrastructure default export, alongside its `defineEventDoc` calls.
 
-An export walks a doc's `referenceResolver` (see [defineEventDocRoutes](./event-doc-routes.md#parameters)) to pull in every doc it depends on — a template's layout, styles, and content — so a bundle is self-contained. An import replays that bundle's event log against the target's own collections, either as a fresh doc or appended onto one that already exists there, and reports what it would do (or did) per document.
+An export walks a doc's registered functions object `collectReferences` (see [defineEventDoc](./event-doc.md)) to pull in every doc it depends on — a template's layout, styles, and content — so a bundle is self-contained. An import replays that bundle's event log against the target's own collections, either as a fresh doc or appended onto one that already exists there, and reports what it would do (or did) per document.
 
 The route controllers ship inside `quidproquo-features` and read the collection registry from per-route globals, so a service needs no controller wiring of its own.
 
@@ -15,15 +15,14 @@ The route controllers ship inside `quidproquo-features` and read the collection
 
 ```typescript
 import { defineEventDoc, defineEventDocTransfer } from 'quidproquo-features';
+import { articleDefinition } from './articleDefinition';
+import { templateDefinition } from './templateDefinition';
 
-const collections = [
-  { storeName: 'templates', type: 'template', referenceResolver: 'collectTemplateReferences' },
-  { storeName: 'content', type: 'article' },
-];
+const collections = [templateDefinition, articleDefinition];
 
 export default [
-  ...defineEventDoc({ storeName: 'templates', type: 'template', basePath: '/templates', referenceResolver: 'collectTemplateReferences' }),
-  ...defineEventDoc({ storeName: 'content', type: 'article', basePath: '/articles' }),
+  ...defineEventDoc(templateDefinition, '/entry/eventDocs::templateDefinition', { basePath: '/templates' }),
+  ...defineEventDoc(articleDefinition, '/entry/eventDocs::articleDefinition', { basePath: '/articles' }),
 
   ...defineEventDocTransfer({
     service: 'cms',
@@ -39,7 +38,7 @@ All paths are prefixed with the version segment `/v{version}` (default `/v1`):
 
 | Method | Path | Purpose |
 | --- | --- | --- |
-| `POST` | `/transfer/manifest` | Every doc that would travel with a given `{ docs: [{ service, type, id }, ...] }` selection, merged and deduped across all of them (follows `referenceResolver` links), without building anything. Feeds an export UI's "these will be included" preview. |
+| `POST` | `/transfer/manifest` | Every doc that would travel with a given `{ docs: [{ service, type, id }, ...] }` selection, merged and deduped across all of them (follows each collection's `collectReferences` links), without building anything. Feeds an export UI's "these will be included" preview. |
 | `POST` | `/transfer/export` | Stage one bundle for `{ docs: [...] }` and return its download url. |
 | `POST` | `/transfer/upload` | A presigned PUT url for uploading a bundle file, plus the id used to plan/import it. |
 | `POST` | `/transfer/plan` | What importing an uploaded bundle (`{ transferId }`) would do to each of its docs (`new`, `fastForward`, `same`, or a blocking `diverged`/`codeConflict`) without writing anything. |
@@ -58,24 +57,22 @@ The single `options` argument is an `EventDocTransferOptions`:
 | Property | Type | Default | Description |
 | --- | --- | --- | --- |
 | `service` | `string` | – (required) | The service name `EventDocLink`s use to address this service's collections (`link.eventDocService`). Transfers never leave it: the stores live here, so a reference into another service throws rather than being silently dropped from a manifest. |
-| `collections` | `EventDocTransferCollection[]` | – (required) | The collections a transfer may read and write. Feed this the same array the service maps over for its `defineEventDoc` calls, so the two cannot drift; the extra fields on a routes-options object (`basePath`, auth, `version`) are simply unused here. |
+| `collections` | `EventDocTransferCollectionSource[]` | – (required) | The collections a transfer may read and write. Feed this the same array the service maps into its `defineEventDoc` calls (each entry's functions object carries the identity), so the two cannot drift — see `EventDocTransferCollectionSource` below. |
 | `scopeResolver` | `string` | – | Name of a registered inline function. Establishes the ambient storage scope for the whole request, exactly like a collection's own `scopeResolver`. Needed separately because a transfer spans collections, so there is no single store to read the resolver name from. Omit only if none of the collections partition. |
 | `routeAuthSettings` | `RouteAuthSettings` | – | Auth settings applied to every mounted route (from quidproquo-webserver — see [route](../webserver/route.md)). Import writes unvalidated history and export reads across every registered collection, so gate these harder than the collections' own routes. |
 | `version` | `number` | `1` | Version number for the `/v{version}` path prefix on every route. |
 
-### `EventDocTransferCollection`
+### `EventDocTransferCollectionSource`
 
-A subset of a collection's own `EventDocRoutesOptions`, so a service can declare its collections once and feed the same array to both `defineEventDoc` and `defineEventDocTransfer`:
+Each `collections` entry can be any of:
 
-| Property | Type | Description |
-| --- | --- | --- |
-| `storeName` | `string` | Must match the collection's own `storeName`. |
-| `type` | `string` | Must match the collection's own `type`. |
-| `onPublish` | `string` | Carried so an imported publish behaves exactly as it does on the collection's own routes. |
-| `onAppend` | `string` | Carried so an imported append fires the same reaction as it does on the collection's own routes. |
-| `referenceResolver` | `string` | Carried so the manifest walk can follow this collection's links. `eventValidator` is deliberately **not** carried — replayed history was already validated at its origin, so imports skip it. |
+- An `EventDocFunctions` object — the same value passed as `defineEventDoc`'s `functions` argument. Its `collectReferences` drives the manifest walk; `storeName`/`type` are read off it.
+- A collection-list entry carrying its functions object under `functions` (`{ functions, ... }`) — so the exact array a service maps over for its `defineEventDoc` calls passes straight through, unmapped.
+- A bare `EventDocTransferCollection` registry entry (`{ storeName, type, onPublish?, onAppend? }`), for a collection that needs the import hooks carried explicitly without passing a live functions object.
+
+`onPublish`/`onAppend` are carried so an imported publish/append behaves exactly as it does on the collection's own routes. Fold-gate validation is deliberately **not** applied to imported events — replayed history was already validated at its origin.
 
 ## Related
 
-- [defineEventDoc](./event-doc.md) / [defineEventDocRoutes](./event-doc-routes.md) — declare the collections a transfer reads and writes, including the `referenceResolver` the manifest walk follows.
+- [defineEventDoc](./event-doc.md) / [defineEventDocRoutes](./event-doc-routes.md) — declare the collections a transfer reads and writes, including the functions object (`collectReferences`) the manifest walk follows.
 - [defineTenantedEventDocTransfer](./tenanted-event-doc-transfer.md) — the same routes with the tenant scope resolver pre-wired, so export/import never cross tenant partitions.

package/template/docusaurus/docs/config/features/event-doc.md

@@ -1,71 +1,85 @@
 ---
 title: defineEventDoc
-description: Define an event-sourced document collection — its stores plus its HTTP routes — in one call.
+description: Register an event-sourced document collection's functions object, declare its stores, and mount its HTTP routes, in one call.
 ---
 
 # defineEventDoc
 
-Defines a complete **event-document collection**: the data stores that hold it *and* the HTTP routes that serve it, in a single call. This is the all-in-one helper for the common **one-store-one-type** case. It returns a `QPQConfig` (an array of config settings) that you spread into a service's infrastructure default export.
+Registers a document collection's **functions object** (its identity plus its behaviour — fold, references, and optionally render — as a [dynamic-functions](../core/dynamic-functions.md) surface), declares the stores that back it, and mounts the HTTP routes that serve it, all in one call. This is the all-in-one helper for the common **one-store-one-type** case. It returns a `QPQConfig` (an array of config settings) that you spread into a service's infrastructure default export.
 
-An event document is not stored as a mutable row. It is derived by folding an ordered, append-only log of events. `defineEventDoc` provisions that log (plus a queryable summary table and a blob bucket) and mounts the REST routes that create documents, append events, read them back, and resolve their draft/published versions.
+An event document is not stored as a mutable row. It is derived by folding an ordered, append-only log of events. `defineEventDoc` provisions that log (plus a queryable summary table and a blob bucket), registers the collection's functions object so the backend can invoke it by name, and mounts the REST routes that create documents, append events, read them back, and resolve their draft/published versions.
 
-- **On AWS:** deploys everything [defineEventDocSummary](./event-doc-summary.md) deploys (two DynamoDB tables — a summary table and an append-only events table — plus an S3 bucket for assets) and everything [defineEventDocRoutes](./event-doc-routes.md) deploys (the API Gateway routes and their Lambda handlers). It creates no infrastructure of its own; it is exactly `[defineEventDocSummary(options.storeName), defineEventDocRoutes(options)]`.
+- **On AWS:** deploys everything [defineEventDocSummary](./event-doc-summary.md) deploys (DynamoDB tables for the summary, events, and snapshots, plus an S3 bucket for assets), everything [defineEventDocRoutes](./event-doc-routes.md) deploys (the API Gateway routes and their Lambda handlers), and a [defineDynamicFunctions](../core/dynamic-functions.md) registration for `functions` — no infrastructure of its own. It reads `functions`' `storeName`/`type` off the object itself, so `options` carries no identity fields.
 
 ```typescript
 import { defineEventDoc } from 'quidproquo-features';
+import { articleDefinition } from './articleDefinition';
 
 export default [
-  ...defineEventDoc({
-    storeName: 'content',
-    type: 'article',
+  ...defineEventDoc(articleDefinition, '/entry/eventDocs::articleDefinition', {
     basePath: '/articles',
     routeAuthSettings: { userDirectoryName: 'editors' },
   }),
 ];
 ```
 
+## Registering a collection's functions
+
+`functions` is an `EventDocFunctions` object: `{ storeName, type, foldSnapshotViews, collectReferences, render? }`. The object `createEventDocDefinition` returns — given `storeName`/`type` in its config — satisfies this shape directly, so a collection with no service-only render can register its definition verbatim. A collection that needs a render step only service code can perform (resolving linked docs, reading blob-drive assets) layers it on with `extendEventDocFunctions(definition, { render })`, which returns a new object and never mutates the definition itself.
+
+`runtime` is a [`QpqFunctionRuntime`](../core/dynamic-functions.md#runtime--qpqfunctionruntime-required) path to that SAME export — the dynamic-functions pattern: identity is read off the object here at config time, behaviour is loaded from the path by the processors at request time. Both must point at the exact object being registered, or the registration and the runtime will disagree about what the collection can do.
+
 ## When to use `defineEventDoc` vs `defineEventDocSummary` + `defineEventDocRoutes`
 
-`defineEventDoc` defines the store **and** the routes together, so it assumes exactly one document `type` per store. If you want several document types to share one physical store (one summary table, one events table, one bucket), you must not define the store more than once. In that case, call [defineEventDocSummary](./event-doc-summary.md) **once** for the shared store, then [defineEventDocRoutes](./event-doc-routes.md) **per type** — each with the same `storeName` but a different `type` and `basePath`. Use `defineEventDoc` whenever the store backs a single type.
+`defineEventDoc` defines the store, the functions registration, **and** the routes together, so it assumes exactly one document `type` per store. If you want several document types to share one physical store (one summary table, one events table, one bucket), you must not define the store more than once. In that case, call [defineEventDocSummary](./event-doc-summary.md) **once** for the shared store, then [defineDynamicFunctions](../core/dynamic-functions.md) and [defineEventDocRoutes](./event-doc-routes.md) **per type** — each with the same `storeName` but a different `type`, `basePath`, and functions object, passing `defineEventDocSummary` the whole `snapshotFunctions` map. Use `defineEventDoc` whenever the store backs a single type.
+
+A collection with no definition at all (no render, no references, no snapshots) composes the low-level pair directly instead of calling `defineEventDoc`: `[...defineEventDocSummary(storeName), ...defineEventDocRoutes({ storeName, type, ...options })]`.
 
 ## Signature
 
 ```typescript
-function defineEventDoc(options: EventDocRoutesOptions): QPQConfig;
+function defineEventDoc(
+  functions: EventDocFunctions,
+  runtime: QpqFunctionRuntime,
+  options: EventDocCollectionOptions,
+): QPQConfig;
 ```
 
 ## Parameters
 
-`defineEventDoc` takes the same `EventDocRoutesOptions` object as [defineEventDocRoutes](./event-doc-routes.md); `options.storeName` is also passed straight through to [defineEventDocSummary](./event-doc-summary.md). See the [defineEventDocRoutes parameter reference](./event-doc-routes.md#parameters) for every field.
+### `functions` — `EventDocFunctions` (required)
+
+The collection's callable surface, read for its identity (`storeName`, `type`) at config time and registered under `runtime` for invocation at request time.
 
 | Property | Type | Required | Description |
 | --- | --- | --- | --- |
 | `storeName` | `string` | yes | Name of the summary store to create and serve. Also derives the events table and asset bucket names. |
 | `type` | `string` | yes | The document type this collection holds — the store's partition value, so one store can (via the split helpers) hold several types. |
-| `basePath` | `` `/${string}` `` | yes | URL prefix the routes mount under, e.g. `/articles`. |
-| `routeAuthSettings` | `RouteAuthSettings` | no | Auth for the mounted routes. Omit to leave them open — mutations then have no user to attribute. |
-| `version` | `number` | no | Route version prefix (`/v{version}`), default `1`. |
-| `eventValidator` | `string` | no | Inline-function name run on every append to reject invalid events. |
-| `eventRenderer` | `string` | no | Inline-function name that folds + renders the log to HTML; mounting it adds a `GET {basePath}/{id}/render` route. |
-| `onPublish` | `string` | no | Inline-function name invoked with `{ docId, event, summary }` after every successful Publish append: the seam for syncing the folded document into a materialized read model. |
-| `onAppend` | `string` | no | Inline-function name invoked with `{ docId, event, summary, events }` after EVERY successful append (domain events and lifecycle events alike): the seam for reacting to any mutation. Runs after `onPublish` when both fire on the same Publish event. |
-| `scopeResolver` | `string` | no | Inline-function name every route invokes with `{ event }` to resolve the request's ambient storage scope (e.g. per-tenant); null means unscoped. |
-| `referenceResolver` | `string` | no | Inline-function name `GET {basePath}/{id}/references` invokes with the document's `{ events, docId }` log to return the `EventDocLink`s that view depends on. Omit for a leaf collection — the route still resolves, just always to `[]`. |
+| `foldSnapshotViews` | `(events, seedViews?) => Nullable<EventDocSnapshotViews>` | yes | Every view of a log prefix, era-pinned — what a snapshot stores. Invoked by the event store's stream projector (which also writes the summary row from the fold's `summary` view). |
+| `foldDocumentState` | `(events, seedState?) => unknown` | yes | The document view at one point, LATEST-shaped, resumable from a stored snapshot's era-pinned document state. The read side's fold: render, references, as-of reads, and the append hooks' state derivation all go through it. |
+| `collectReferences` | `(events) => EventDocLink[]` | yes | The `EventDocLink`s this doc's whole HISTORY depends on; `[]` for a leaf doc type. Invoked by the transfer manifest walk (it exports the whole history). |
+| `collectReferencesFromState` | `(state) => EventDocLink[]` | yes | The `EventDocLink`s the CURRENT state depends on; `[]` for a leaf doc type. Invoked by the references route against a snapshot-seeded folded state. |
+| `render` | `(input: EventDocRenderInput) => EventDocRenderResult \| AskResponse<EventDocRenderResult>` | no | Render the resolved, already-folded document state (`input.state`, resolved snapshot-seeded by the route). Omit and `GET {basePath}/{id}/render` 404s as "no renderer configured". Plain function or story — the dynamic-functions processor runs either. |
+
+### `runtime` — `QpqFunctionRuntime` (required)
+
+A reference to the module exporting `functions`, usually a relative path string of the form `'/path/to/file::exportedObjectName'` — see [defineDynamicFunctions](../core/dynamic-functions.md#runtime--qpqfunctionruntime-required). Must resolve to the SAME object passed as `functions`.
+
+### `options` — `EventDocCollectionOptions` (required)
+
+The same object [defineEventDocRoutes](./event-doc-routes.md#parameters) takes, minus `storeName`/`type` (read off `functions` instead). See the [defineEventDocRoutes parameter reference](./event-doc-routes.md#parameters) for every field: `basePath`, `routeAuthSettings`, `version`, `onPublish`, `onAppend`, `scopeResolver`, `excludeRoutes`.
 
 ## Examples
 
 ```typescript
 import { defineEventDoc } from 'quidproquo-features';
+import { articleDefinition } from './articleDefinition';
 
 export default [
   // A single "article" collection with authenticated mutations.
-  ...defineEventDoc({
-    storeName: 'content',
-    type: 'article',
+  ...defineEventDoc(articleDefinition, '/entry/eventDocs::articleDefinition', {
     basePath: '/articles',
     routeAuthSettings: { userDirectoryName: 'editors' },
-    eventValidator: 'validateArticleEvent',
-    eventRenderer: 'renderArticle',
   }),
 ];
 ```
@@ -74,6 +88,7 @@ export default [
 
 - [defineEventDocSummary](./event-doc-summary.md) — the store half of this helper; call it directly when several types share one store.
 - [defineEventDocRoutes](./event-doc-routes.md) — the routes half; call it per type in the split setup.
+- [defineDynamicFunctions](../core/dynamic-functions.md) — the registration this threads `functions`/`runtime` through.
 - [defineKeyValueStore](../core/key-value-store.md) / [defineStorageDrive](../core/storage-drive.md) — the underlying core config the summary helper composes.
 - **Reading a document in your own stories:** [askEventDocGetByIdOrThrow](../../actions/features/event-doc/ask-event-doc-get-by-id.md), [askEventDocList](../../actions/features/event-doc/ask-event-doc-list.md), and the [version reads](../../actions/features/event-doc/ask-event-doc-get-draft.md).
 - **Creating a document in your own stories:** [askEventDocCreate](../../actions/features/event-doc/ask-event-doc-create.md).

package/template/docusaurus/docs/config/features/tenanted-event-doc-transfer.md

@@ -11,8 +11,9 @@ The pairing matters: transferring collections declared with [defineTenantedEvent
 
 ```typescript
 import { defineTenant, defineTenantedEventDoc, defineTenantedEventDocTransfer } from 'quidproquo-features';
+import { articleDefinition } from './articleDefinition';
 
-const collections = [{ storeName: 'content', type: 'article' }];
+const collections = [articleDefinition];
 
 export default [
   ...defineTenant({
@@ -21,9 +22,7 @@ export default [
     routeAuthSettings: { userDirectoryName: 'users' },
   }),
 
-  ...defineTenantedEventDoc({
-    storeName: 'content',
-    type: 'article',
+  ...defineTenantedEventDoc(articleDefinition, '/entry/eventDocs::articleDefinition', {
     basePath: '/articles',
     routeAuthSettings: { userDirectoryName: 'users' },
   }),

package/template/docusaurus/docs/config/features/tenanted-event-doc.md

@@ -11,6 +11,7 @@ The deploying service must still register the resolver implementation by calling
 
 ```typescript
 import { defineTenantedEventDoc, defineTenant } from 'quidproquo-features';
+import { articleDefinition } from './articleDefinition';
 
 export default [
   ...defineTenant({
@@ -19,9 +20,7 @@ export default [
     routeAuthSettings: { userDirectoryName: 'users' },
   }),
 
-  ...defineTenantedEventDoc({
-    storeName: 'content',
-    type: 'article',
+  ...defineTenantedEventDoc(articleDefinition, '/entry/eventDocs::articleDefinition', {
     basePath: '/articles',
     routeAuthSettings: { userDirectoryName: 'users' },
   }),
@@ -31,14 +30,18 @@ export default [
 ## Signature
 
 ```typescript
-function defineTenantedEventDoc(options: TenantedEventDocOptions): QPQConfig;
+function defineTenantedEventDoc(
+  functions: EventDocFunctions,
+  runtime: QpqFunctionRuntime,
+  options: TenantedEventDocCollectionOptions,
+): QPQConfig;
 ```
 
-`TenantedEventDocOptions` is `EventDocRoutesOptions` with `scopeResolver` omitted — see [defineEventDoc](./event-doc.md#parameters) for the remaining options.
+`TenantedEventDocCollectionOptions` is `EventDocCollectionOptions` with `scopeResolver` omitted — see [defineEventDoc](./event-doc.md#parameters) for the remaining options.
 
 ## Parameters
 
-Same as [defineEventDoc](./event-doc.md#parameters): `storeName`, `type`, `basePath`, `routeAuthSettings`, `version`, `eventValidator`, `eventRenderer`, `onPublish` (without `scopeResolver`, which this always sets to `TENANT_SCOPE_RESOLVER_FN`).
+Same as [defineEventDoc](./event-doc.md#parameters): `functions`, `runtime`, and `options` (`basePath`, `routeAuthSettings`, `version`, `onPublish`, `onAppend`, without `scopeResolver`, which this always sets to `TENANT_SCOPE_RESOLVER_FN`).
 
 ## Returns