@loadbare/app 0.9.0 → 0.11.0

package/docs/comparison.md

@@ -1,16 +1,14 @@
 # Loadbare/app and current front-end frameworks
 
 > LLM-authored, not yet revised by a person.  Drafted by Claude on
-> 2026-09-16 against the working tree of `@loadbare/app` 0.7.3, which
-> includes `lb-show`.  Statements about other frameworks are from general
+> 2026-09-16 and brought up to date with the working tree that follows
+> `@loadbare/app` 0.9.0.  Statements about other frameworks are from general
 > knowledge of those projects as of 2026 and carry no per-claim sources.
 
 This document states how `@loadbare/app` differs from the frameworks and
 libraries most used for front-end development today.  It repeats material
-from [Theory](./theory.md), [TECHREF-1.0](./TECHREF-1.0.md),
-[Prior art](./prior-art.md) and
-[Assessing the accidental complexity claim](./analysis-accidental-complexity.md)
-so that it can be read on its own.  Where this document and
+from [Theory](./theory.md), [TECHREF-1.0](./TECHREF-1.0.md) and
+[Prior art](./prior-art.md) so that it can be read on its own.  Where this document and
 [Theory](./theory.md) disagree, Theory is authoritative.
 
 Loadbare/app has not reached 1.0.  The [Blockers](./TECHREF-1.0.md#blockers)
@@ -50,10 +48,11 @@ Loadbare/app is a framework for server-bound database applications.  The
 browser receives one HTML document containing every page as a `<template>`,
 one script and one stylesheet.  After that, only JSON rows cross the wire.
 HTML attributes bind elements to named server queries, and one attribute,
-`lb-action`, turns a click or a submit into a request.  The server answers
-every request with rows, sets of rows, or patches to sets of rows, and the
-browser-side runtime, called the hub, writes those values into the elements
-bound to them.
+`lb-request`, turns a click, a change or a submit into a request.  The
+server answers every request with response items: one row, a set of rows,
+or a patch to a set of rows, each named by its query.  The browser-side
+runtime, called the hub, lands those values on the elements that name the
+query.
 
 Compared with the client component frameworks (React, Vue, Angular, Svelte,
 Solid), Loadbare/app has no component tree rendered at run time, no
@@ -62,7 +61,8 @@ template expressions.
 
 Compared with the server-integrated meta-frameworks (Next.js, Nuxt,
 SvelteKit, React Router 7, Astro), Loadbare/app has no server rendering and
-no hydration, ships no server of its own, and has no route parameters.
+no hydration, ships no server of its own, and has no route parameters:
+a path names a page, and the query parms carry everything finer.
 
 Compared with the hypermedia libraries (htmx, Hotwire Turbo, Unpoly),
 Loadbare/app sends JSON rather than HTML after the first load, requires a
@@ -131,22 +131,25 @@ The hub holds no application data.  There is no store, no signal, no
 observable, and no client cache of query results.
 
 - A value that has landed exists in the DOM: as `textContent` or `value`, and
-  as the `lb-value` attribute.
-- A list exists as the DOM rows the hub cloned, each stamped with
-  `lb-key-value`.
+  as the `lb-column-value` stamp.
+- The rows of a `rows` query exist as the live rows the hub cloned, each
+  stamped with `lb-row-live` and `lb-key-value`.
+- The URL is a row too: the hub serves the query `lb-url`, whose columns are
+  the path, the page label and the query parms.
 - An element hidden by `lb-show` exists inside a `<template>` standing where
   it stood.
 - The hub keeps two pieces of state of its own: the name of the current page,
-  and, until an insert completes, a record of which controls it read.
+  and, until an insert completes, the form it gathered from.
 
-The server is the source of truth for everything else, including view state.
-A query takes no argument from the browser; its only input is `ctx`, which
-the application builds from the Express request.  Which record a page shows,
-or which step of a wizard is current, is held on the server where `ctx`
-reaches it.  A reload runs the page's queries again and shows the same state.
+The server is the source of truth for everything else.  A query takes no
+argument from the browser; its only input is `ctx`, which the application
+builds with `contextFor` from the Express request and the query parms.
+Which record a page shows, a filter or a date range is a query parm, so a
+reload, a bookmark or a mailed link runs the page's queries again and shows
+the same state.
 
-A URL names a page and nothing finer.  Whether a page URL may carry
-parameters is an open blocker in TECHREF-1.0.
+A URL's path names a page and nothing finer.  Everything finer is a query
+parm.
 
 ### Elsewhere
 
@@ -179,20 +182,22 @@ At run time the hub performs a closed set of operations:
 
 | Trigger                    | Operation                                                                  |
 |----------------------------|----------------------------------------------------------------------------|
-| Navigation                 | Clone the page's `<template>` into `<main>`                                |
-| A value for a native element | Set `textContent`, and set `lb-value`                                    |
-| A value for a form control | Set `value`, and set `lb-value`                                            |
-| A value for a custom element | Set `lb-value`                                                           |
-| A new key in a list        | Clone the row template, stamp `lb-key-value`, fill it, insert it           |
-| A whole list               | Place every row in the order given, remove rows whose keys did not arrive  |
+| Navigation                 | Clone the page's `<template>` into `<main>`, land `lb-url`                 |
+| A value for a control      | Set `value`, and stamp `lb-column-value`                                   |
+| A value for another native element | Set `textContent`, and stamp `lb-column-value`                     |
+| A value for a custom element that is not a control | Stamp `lb-column-value`                            |
+| A `row` with no row template | Land it on the element itself, stamp `lb-key-value`                      |
+| A new key through a row template | Clone the row template, stamp `lb-row-live` and `lb-key-value`, fill it, insert it |
+| All rows                   | Place every row in the order given, remove rows whose keys did not arrive  |
 | A patch                    | Upsert the rows named, remove the keys named, leave other rows in place    |
-| After any list result      | Stamp `lb-row-count`                                                       |
+| After rows land            | Stamp `lb-query-row-count`                                                 |
 | An `lb-show` column        | Move the element into, or out of, a `<template lb-show>`                   |
-| A request starts or ends   | Set or remove `lb-pending` and `aria-busy`; set `lb-error` on failure      |
-| An insert succeeds         | Reset the controls it gathered to their defaults                           |
+| A request starts or ends   | Set or remove `lb-request-pending` and `aria-busy`; set `lb-request-error` on failure |
+| An insert from a form succeeds | Reset the form                                                         |
 
 The hub finds targets with `querySelectorAll` on the attributes written in
-the HTML.  No tree is compared with a previous tree.  A response names what
+the HTML.  Each response item names its query, its kind and its key, so the
+markup names none of the three beyond the query.  No tree is compared with a previous tree.  A response names what
 changed, so the hub does not determine what changed.  Between interactions
 the hub runs no timers, observers or polling loops.
 
@@ -224,7 +229,7 @@ values its queries return, serialized as JSON.
 
 The HTML written in `.html` files is the HTML that ships, after expansion.
 Attribute values in the `lb-` namespace are names: a query name, a column
-name, or an action name.  No attribute value is an expression.
+name, or a request name.  No attribute value is an expression.
 
 There are two kinds of placeholder, and they run at different times.
 
@@ -232,7 +237,7 @@ There are two kinds of placeholder, and they run at different times.
   a whole attribute value or a whole text node.  The tag supplies it with an
   `exp-name` attribute.  An unsupplied placeholder with no default drops the
   attribute.  The value becomes permanent in the shipped HTML.
-- Run time.  Data lands through `lb-cell`, `lb-list` with a keyed
+- Run time.  Data lands through `lb-column`, `lb-query` with a row
   `<template>`, and `lb-show`.  There is no run-time interpolation into
   attribute values or text.
 
@@ -241,8 +246,8 @@ listed as decided against in the [Roadmap](./roadmap.md#decided-against).
 
 | Task              | Loadbare/app                                  | React (JSX)                          | Vue                                  | Angular                               | Svelte                        | Alpine.js                                  |
 |-------------------|-----------------------------------------------|--------------------------------------|--------------------------------------|---------------------------------------|-------------------------------|--------------------------------------------|
-| Show a value      | `<span lb-cell="name">`                       | `{row.name}`                         | `{{ row.name }}`                     | `{{ row.name }}`                      | `{row.name}`                  | `<span x-text="row.name">`                 |
-| Keyed list        | `<template lb-key="id">` inside `lb-list`     | `rows.map(r => <li key={r.id}>)`     | `<li v-for="r in rows" :key="r.id">` | `@for (r of rows; track r.id)`        | `{#each rows as r (r.id)}`    | `<template x-for="r in rows" :key="r.id">` |
+| Show a value      | `<span lb-column="name">`                     | `{row.name}`                         | `{{ row.name }}`                     | `{{ row.name }}`                      | `{row.name}`                  | `<span x-text="row.name">`                 |
+| Keyed list        | `<template>` inside `lb-query`, key from the server | `rows.map(r => <li key={r.id}>)`     | `<li v-for="r in rows" :key="r.id">` | `@for (r of rows; track r.id)`        | `{#each rows as r (r.id)}`    | `<template x-for="r in rows" :key="r.id">` |
 | Condition         | `lb-show="column"`                            | `{cond && <X />}`                    | `v-if`, `v-show`                     | `@if (cond) { }`                      | `{#if cond}`                  | `x-if`, `x-show`                           |
 | Expression in markup | Not supported                              | Any JavaScript expression            | JavaScript expressions               | Template expressions                  | JavaScript expressions        | JavaScript expressions                     |
 | Build-time constant | `exp-label="Name"` into `{{label}}`          | A prop                               | A prop                               | An input                              | A prop                        | Not applicable                             |
@@ -296,20 +301,24 @@ without `.browser` is not bundled, and the build error names it.
 - Light DOM throughout.  Loadbare/app uses no shadow DOM.
 - No base class.  A widget extends `HTMLElement`.
 - No props at run time.  Build-time parameters arrive as `exp-` attributes.
-  Data arrives as the `lb-value` attribute, which the widget observes through
+  Data arrives one of two ways.  A form-associated custom element with a
+  `value` property is a control: the hub sets its `value`, gathers it back
+  like an `<input>`, and commits it on `change`.  Any other custom element
+  receives the `lb-column-value` stamp, which it observes through
   `attributeChangedCallback`.  The browser calls that callback for an
   attribute already present at upgrade, so first render and refresh are one
   code path.
-- Composition at build time.  `lb-slot` marks where authored content goes;
-  `lb-template` names additional destinations filled by
-  `<template lb-template="name">`.  A definition may use other widgets; a
+- Composition at build time.  `lb-exp-slot` marks where authored content
+  goes; `lb-exp-template` names additional destinations filled by
+  `<template lb-exp-template="name">`.  A definition may use other widgets; a
   cycle is a build error.
-- A widget sends a request by dispatching a bubbling `lb-request`
-  `CustomEvent`.  The hub adds the scope (`list` or `row`, `key`, `cell`).  An
-  ancestor may stop the event.
-- A list widget may implement `lbPlaceRow(el, row, template)` to decide where
-  a row goes, and `lbRowsLanded()` to build scaffolding such as group
-  headings.  The hub does the cloning, matching, removal and counting.
+- A widget may send a request by dispatching a bubbling `lb-request`
+  `CustomEvent`.  The hub completes it with `query`, `key` and `values` from
+  where the element sits.  An ancestor may stop the event.
+- A custom element carrying `lb-query` and a row template may implement
+  `lbPlaceRow(el, row, template)` to decide where a row goes, and
+  `lbRowsLanded()` to build scaffolding such as group headings.  The hub does
+  the cloning, matching, removal and counting.
 - Method names beginning with `lb` on a custom element are reserved.
 
 Widget libraries are npm packages listed in `imports.ts`.  The builder scans
@@ -330,14 +339,15 @@ The following follow from the builder and hub code.
 - A `.browser.ts` file is bundled by esbuild and may import any package
   esbuild resolves.  A custom element may mount another framework's component
   tree inside itself.
-- The hub does not turn a click on a hyphenated element into a request.  A
-  third-party element carrying `lb-action` sends nothing unless it dispatches
-  `lb-request` itself.
-- A bound value lands on a third-party element as `lb-value`.  The element
-  displays it only if it observes that attribute.
-- Gathering for `lb-row-insert` and `lb-row-update` reads `<input>`, `<select>`
-  and `<textarea>` elements found with `querySelectorAll`, which does not
-  enter a shadow root.
+- A third-party form-associated custom element with a `value` property that
+  fires `change` is a control, and takes `lb-column` and `lb-request` as an
+  `<input>` does.  Any other third-party element carrying `lb-request`
+  commits on `click`.
+- A value lands on a third-party element that is not a control as the
+  `lb-column-value` stamp.  The element displays it only if it observes that
+  attribute.
+- Gathering reads controls found in the light DOM and through a form's
+  owner, which does not enter a shadow root.
 
 ### Elsewhere
 
@@ -366,27 +376,29 @@ the query string the browser is showing.
 
 - An empty body asks for the page's whole query set.  The server runs the
   page's `onPageEnter`, then every query the page declares.
-- A body with an `action` runs that action and its refresh set.
-- A request without an action answers 400.  A `run` that throws answers 500.
+- A body carrying a request, `{ name, query, key, values }`, runs the handler
+  its name picks and then its refresh set.
+- A request without a name answers 400.  A `run` that throws answers 500.
 
-Every response has one shape: an object keyed by query name.
+Every response has one shape: an array of response items.  Each names its
+query, the kind and key the server declared, and one of these:
 
-| Value            | Means                                               |
-|------------------|-----------------------------------------------------|
-| An object        | One row, for a name declared with `row()`           |
-| An array         | The whole set, and its order, for a `list()`        |
-| `{ rows, drop }` | A patch to a `list()`: upsert these, remove these keys |
+| Member           | Means                                                 |
+|------------------|-------------------------------------------------------|
+| `row`            | One row, for a query declared with `row()`            |
+| `rows`           | All rows, and their order, for a query declared with `rows()` |
+| `patch`          | `{ rows, drop }` for a `rows` query: upsert these, remove these keys |
 
-A cell holds one value.  A set of values is a list of its own.  A row never
-contains rows.  Master-detail is a row and a list answered under two names.
-Many masters with their details is one list of joined rows, grouped for
-display by a widget's `lbPlaceRow`.
+A column holds one value.  A set of values is a query of its own.  A row
+never contains rows.  Master-detail is a row and rows answered under two
+names.  Many masters with their details is one `rows` query of joined rows,
+grouped for display by a custom element's `lbPlaceRow`.
 
 The application designs no endpoints, routes or serialization format.  The
 names in the markup are the keys in the page's `.queries.ts` and
-`.requests.ts` files.  The browser can reach only the queries, actions and
-CRUD operations a page declares; any other name answers `{}` and logs a
-server warning.
+`.requests.ts` files.  The browser can reach only the queries, declared
+requests and `crud` entries a page declares; any other name answers `[]` and
+logs a server warning.
 
 Values are not converted.  The hub hands each value to the browser as the
 query produced it.  Formatting a date or an amount is done in the query.
@@ -411,48 +423,54 @@ Data types are an open blocker in TECHREF-1.0.
 
 ### Loadbare/app
 
-`lb-action` names what an interaction asks for.  A value beginning with `lb-`
-is one of three reserved operations; any other value is an action the page
-declares.
-
-| `lb-action`      | Written on                                  | Carries                         | Server key under `crud` |
-|------------------|---------------------------------------------|---------------------------------|-------------------------|
-| `lb-row-insert`  | A `<form>`, or a button in a `<tr>`, in a list | `list`, `values`             | `rowInsert`             |
-| `lb-row-update`  | A `<form>`, a button in a live row, or a widget cell | `list`, `key`, `values` | `rowUpdate`             |
-| `lb-row-delete`  | Anything inside a live row                  | `list`, `key`                   | `rowDelete`             |
-| Any other name   | Any element                                 | Scope in effect, and a widget's `value` | Under `actions`  |
-
-- Position comes from the document.  `list` or `row` comes from the nearest
-  ancestor scope, `key` from the nearest live row, `cell` from the element's
-  own `lb-cell`.  The author writes the action and not the position.
-- Values are gathered from the nearest `<form>`, `<tr>` or live row around
-  the element, the way a button submits its form owner.  A widget carrying
-  `lb-cell` sends its own cell alone, so one `rowUpdate` answers a form and a
-  per-field edit.
-- A native element sends on click, a form on submit.  A widget sends its own.
-- A declared action carries no argument list.
-- A single-row scope is read-only for the three operations, because each needs
-  a key and a key exists only on a live row in a list.
+`lb-request` names what an interaction asks for.  A name beginning with
+`lb-` is one of three requests Loadbare provides; any other name is a
+request the page declares.
+
+| `lb-request`     | Needs                    | Server key                     |
+|------------------|--------------------------|--------------------------------|
+| `lb-row-insert`  | `query`, `values`        | `crud.<query>.rowInsert`       |
+| `lb-row-update`  | `query`, `key`, `values` | `crud.<query>.rowUpdate`       |
+| `lb-row-delete`  | `query`, `key`           | `crud.<query>.rowDelete`       |
+| Any other name   | Whatever is present      | `handlers.<name>`              |
+
+- An element commits the way HTML says it does: a form on `submit`, a
+  control on `change`, anything else on `click`.  A submit button commits
+  with its form, and its own `lb-request` wins over the form's, the way
+  `formaction` wins over `action`.
+- Position comes from the document.  `query` is the nearest ancestor
+  `lb-query` of what was gathered, and `key` comes from the nearest ancestor
+  row of that query.  The author writes the request name and not the
+  position.
+- Values are gathered from controls: the element alone when it carries
+  `lb-column`, a form's controls, a live row's, or the controls whose form
+  owner is the element's form owner, the HTML `form` attribute included.  A
+  control carrying `lb-column` and `lb-request` sends its own column alone,
+  so one `rowUpdate` answers a form and a per-field edit.
+- Every request has one shape, `{ name, query, key, values }`, and a
+  declared request receives the same fields.
+- The hub does not send a request Loadbare provides that lacks what the
+  table lists, and says why in the console.
 
 On the server, each entry has `run` and `refresh`.  `run` does the work and
-may return results, such as a `patch()`.  `refresh` names queries to run
-again.  What `run` returns is laid over the refreshed results.
+may return results, such as a `patch()`, or a new row for the URL with
+`url()`.  `refresh` names queries to run again.  What `run` returns is laid
+over the refreshed results.
 
-The hub stamps the dispatching element:
+The hub stamps the element that committed:
 
-| Attribute      | Means                                                      |
-|----------------|------------------------------------------------------------|
-| `lb-pending`   | The round trip is in flight; `aria-busy="true"` is set with it |
-| `lb-error`     | The last round trip from this element failed               |
+| Stamp                | Means                                                      |
+|----------------------|------------------------------------------------------------|
+| `lb-request-pending` | The round trip is in flight; `aria-busy="true"` is set with it |
+| `lb-request-error`   | The last round trip from this element failed               |
 
-A native button or form performed again while it carries `lb-pending` is
-ignored.  A widget is not held back.  A round trip has a ten-second deadline,
-after which it is aborted and treated as a failure.  `lb-error` records that
-a round trip failed, and carries no message.
+A commit on an element carrying `lb-request-pending` is ignored.  A round
+trip has a ten-second deadline, after which it is aborted and treated as a
+failure.  `lb-request-error` records that a round trip failed, and carries
+no message.
 
-After a successful `lb-row-insert`, the hub resets each control it gathered
-to its default, as `form.reset()` does, unless the control was edited during
-the round trip.  A failed insert resets nothing.
+After a successful `lb-row-insert` gathered from a form, the hub resets the
+form.  A failed insert resets nothing.
 
 The browser displays only values the server returned.  There is no
 optimistic update.  Per-keystroke validation is an open question in the
@@ -482,24 +500,30 @@ roadmap.
 - The path `/members` names the page `members`.  The path `/` names `index`.
 - There are no route parameters, nested routes or per-page layouts.  The
   chrome, `chrome.html`, is the one document surrounding every page.
-- An anchor carrying `lb-nav-link` navigates inside the application: the hub
-  calls `history.pushState`, clones the page template into `<main>`, then
-  fetches the page's data.  An anchor without the attribute is an ordinary
-  link.  `popstate` navigates back and forward.
+- An anchor carrying `lb-url-link` navigates inside the application on a
+  plain primary click: the hub calls `history.pushState`, clones the page
+  template into `<main>`, then fetches the page's data.  An anchor without
+  the attribute is an ordinary link.  `popstate` navigates back and forward.
 - Navigation fetches no HTML and no code.  Every page's markup is already in
   the document.
 - The server answers every GET with the same `app.html` and status 200.  A
   path that names no page is detected in the browser, which opens a
-  `<dialog lb-unknown-page>` if the chrome has one.
-- The hub publishes its own row, `lb-navigation`, with `page-uri` and
-  `page-label` (the text of the matching `lb-nav-link` anchor), bound like
-  any server row.
-- The hub reads `location.pathname` only.  A query string does not reach the
-  server.
+  `<dialog lb-url-unknown>` if the chrome has one.
+- The hub serves its own query, `lb-url`, of kind `row` and keyed by
+  `lb-path`.  Its columns are `lb-path`, `lb-page-label` (the page file's
+  `<title>`, or its stub), `lb-page-unknown`, and one column per query parm,
+  bound like any server row.
+- A control inside `lb-query="lb-url"` carrying `lb-request="lb-row-update"`
+  writes a query parm.  The hub answers that request itself: it replaces the
+  history entry, or pushes one when the element carries `lb-url-push`, and
+  reloads the page's queries.  A handler moves the URL by returning
+  `url({ ... })`, and the page loads there in the same round trip.
+- The query string rides on every round trip, and the server hands its parms
+  to `contextFor`.
 - The application must be served from the origin root.  The hub reaches
   `/lb`, `/client.js` and `/app.css` by absolute path.
-- The hub does not change `document.title`, move focus, or restore scroll
-  position on navigation.
+- The hub sets `document.title` from `lb-page-label`.  It does not move focus
+  or restore scroll position on navigation.
 
 ### Elsewhere
 
@@ -551,20 +575,25 @@ Checked at build time, as errors:
   containing a capital
 - slot and template errors: two slots, two templates of one name, a template
   naming a missing destination, content in a definition with no slot
-- `lb-cell` outside every scope, `lb-key` on anything but a list's row
-  template, `lb-list` and `lb-row` on one element
-- `lb-show` on a `<template>`, on a row template's root, or with no row
-  around it
-- `lb-unknown-page` on anything but a `<dialog>` inside `<lb-hub>`
+- an `lb-` attribute in markup that is not one a developer writes (`lb-query`,
+  `lb-column`, `lb-show`, `lb-request`, `lb-url-link`, `lb-url-push`,
+  `lb-url-unknown`); the rest are stamps, and script never assigns them
+- an `lb-request` value beginning with `lb-` that is not one of the three
+  requests Loadbare provides
+- `lb-url-link` on anything but an `<a>`, `lb-url-push` without
+  `lb-request`, `lb-url-unknown` on anything but a `<dialog>` inside
+  `<lb-hub>`
+- `lb-show` on a `<template>`, on a row template's root, or with no
+  `lb-query` around it
 - a `.queries.ts` or `.requests.ts` with no matching page
 
-Checked when the server starts: a query or action name beginning with `lb-`.
+Checked when the server starts: a query or declared request name beginning
+with `lb-`.
 
-Not checked at build time: that an `lb-list` or `lb-row` name matches a
-declared query, that an `lb-action` matches a declared action or CRUD entry,
-that an `lb-` attribute is one Loadbare defines, that the chrome contains one
-`<lb-hub>` and one empty `<main>`.  The first two are a roadmap item; the
-last two are listed under the builder blockers.  A language server is a
+Not checked at build time: that an `lb-query` name matches a declared query,
+that an `lb-request` matches a declared request or `crud` entry, that the
+chrome contains one `<lb-hub>` and one empty `<main>`.  The first two are a
+roadmap item; the last is listed under the builder blockers.  A language server is a
 roadmap item.
 
 ### Elsewhere
@@ -598,9 +627,10 @@ Nothing is scoped, renamed, added or removed.
   with a tag is a roadmap item.
 - Light DOM means every selector reaches every element, in the chrome and in
   widgets.
-- The hub stamps attributes a stylesheet can select on: `lb-value`,
-  `lb-pending`, `lb-error`, `lb-row-count`.  An empty list is styled with
-  `[lb-row-count="0"]`.
+- The hub stamps attributes a stylesheet can select on: `lb-column-value`,
+  `lb-key-value`, `lb-row-live`, `lb-request-pending`, `lb-request-error`,
+  `lb-query-row-count`.  An empty `rows` query is styled with
+  `[lb-query-row-count="0"]`.
 
 ### Elsewhere
 
@@ -638,8 +668,9 @@ app.get(/.*/, (_req, res) => res.sendFile(path.join(DIST, "app.html")));
 
 These lines do not change as pages are added.
 
-`contextFor(req)` returns `ctx`, which Loadbare passes to every query and
-request and never reads.  Its type is declared by the application through
+`contextFor(req, parms)` returns `ctx`, which Loadbare passes to every query
+and handler and never reads.  `parms` are the query parms of the URL the
+browser is showing.  Its type is declared by the application through
 TypeScript declaration merging on `HubContext`.  Authentication, sessions,
 logging, database access, and any ORM or business-logic layer are the
 application's, placed in Express middleware and in `ctx`.
@@ -648,12 +679,33 @@ A page's server half:
 
 | File                 | Exports    | Contents                                                     |
 |----------------------|------------|--------------------------------------------------------------|
-| `<name>.queries.ts`  | `queries`  | Named queries, each built with `row()` or `list()`           |
-| `<name>.requests.ts` | `requests` | `onPageEnter`, `actions` by name, `crud` by list name        |
+| `<name>.queries.ts`  | `queries`  | Named queries, each built with `row(key, run)` or `rows(key, run)` |
+| `<name>.requests.ts` | `requests` | `onPageEnter`, `handlers` by request name, `crud` by query name |
 
-A query's signature is `(ctx) => Row` or `(ctx) => Row[]`.  An answer whose
+A query's `run` is `(ctx) => Row` or `(ctx) => Row[]`.  An answer whose
 shape disagrees with its declaration is dropped with a warning.
 
+A page's queries are that page's view model, computed on the server: a
+backend-for-frontend scoped to one page, whose answers are the values the
+page shows.
+
+|                  | Data layer (repository, ORM, API) | Backend-for-frontend | Loadbare/app page files |
+|------------------|-----------------------------------|----------------------|-------------------------|
+| Serves           | Any consumer                      | One client application | One page              |
+| Shaped by        | Entities                          | A client's screens   | One page's elements     |
+| Answers with     | Domain objects, independent of any UI | Data the client still turns into a view | Values as the page shows them, formatted and worded |
+| Client-side work | Mapping, state, view models, components | View models, components | None: the hub lands each column on the element that names it |
+| Keeps the rules  | Yes, in code                      | Usually not          | No: the application keeps them beneath, in its database or in code its handlers share |
+| Reused by        | Many screens                      | One application's screens | No other page      |
+
+A typical stack runs database, ORM or repository, service, API contract,
+client store, view model, component and template.  A Loadbare/app page keeps
+three places: the database with the application's rules, the page files that
+say what one page asks and answers, and the markup that says where each
+answer goes.  Reuse does not happen through a layer.  Two pages showing the
+same data repeat a query's shape or share a database view, and shared
+wording goes in a helper module.
+
 The data channel carries no CSRF token.  Where an options argument for
 hooks, transaction wrapping, error handling and CSRF would go is an open
 blocker.  Serving the static files from a separate origin is a roadmap item.
@@ -729,22 +781,24 @@ TECHREF-1.0 lists every name Loadbare/app owns in one cross-reference.
 
 | Owned                               | Count | Names                                                         |
 |-------------------------------------|-------|---------------------------------------------------------------|
-| `lb-*` HTML attributes              | 16    | `lb-list`, `lb-row`, `lb-cell`, `lb-show`, `lb-key`, `lb-key-value`, `lb-value`, `lb-action`, `lb-nav-link`, `lb-pending`, `lb-error`, `lb-row-count`, `lb-unknown-page`, `lb-slot`, `lb-template`, `lb-page` |
-| Reserved `lb-action` values         | 3     | `lb-row-insert`, `lb-row-update`, `lb-row-delete`             |
+| `lb-*` attributes a developer writes | 7    | `lb-query`, `lb-column`, `lb-show`, `lb-request`, `lb-url-link`, `lb-url-push`, `lb-url-unknown` |
+| `lb-*` stamps                       | 8     | `lb-column-value`, `lb-key-value`, `lb-row-live`, `lb-query-row-count`, `lb-request-pending`, `lb-request-error`, `lb-page`, `lb-page-title` |
+| `lb-*` build-time attributes        | 2     | `lb-exp-slot`, `lb-exp-template`                              |
+| Requests Loadbare provides          | 3     | `lb-row-insert`, `lb-row-update`, `lb-row-delete`             |
 | `lb*` methods on custom elements    | 2     | `lbPlaceRow`, `lbRowsLanded`                                  |
 | Attribute namespace for expansion   | 1     | `exp-*`                                                       |
 | Reserved tags                       | 1     | `<lb-hub>`                                                    |
 | Reserved events                     | 1     | `lb-request`                                                  |
-| Synthetic rows                      | 1     | `lb-navigation`                                               |
+| Queries the hub serves              | 1     | `lb-url`, with columns `lb-path`, `lb-page-label`, `lb-page-unknown` |
 | Builder flags                       | 4     | `--src`, `--out`, `--watch`, `--minify`                       |
 | Reserved file names and patterns    | 8     | `chrome.html`, `imports.ts`, `*.page.html`, `*.queries.ts`, `*.requests.ts`, `<tag>.html`, `<tag>.browser.ts`, `*.css` |
 | Reserved `package.json` keys        | 1     | `loadbare.widgets`                                            |
-| Server functions                    | 5     | `row`, `list`, `patch`, `createHub`, `hubRoutes`              |
-| Browser exports                     | 2     | `applyRow`, `applyData`                                       |
+| Server functions                    | 6     | `row`, `rows`, `patch`, `url`, `createHub`, `hubRoutes`       |
+| Browser exports                     | 2     | `applyRow`, `applyResponse`                                   |
 
 The technical reference, TECHREF-1.0.md, is 1,181 lines.  Theory states that
 the vocabulary fits in an LLM's context window, and discloses that Anthropic
-models writing `.requests.ts` files consistently refresh a list query after
+models writing `.requests.ts` files consistently refresh a `rows` query after
 returning a patch for it.
 
 The other projects in the comparison set do not publish a comparable
@@ -757,12 +811,12 @@ cross-reference, so no count is given for them here.
 - Pages and widgets are native HTML in light DOM.  Loadbare/app adds no ARIA
   roles and no elements of its own except `<lb-hub>`, `<template>` for
   absent branches, and the custom elements an application writes.
-- `aria-busy="true"` is set and removed with `lb-pending`.
+- `aria-busy="true"` is set and removed with `lb-request-pending`.
 - An element hidden by `lb-show` is inside template content, so it is not in
   the accessibility tree.
 - A widget's markup is in the document and in view-source.
-- On navigation the hub does not move focus, announce the new page, or change
-  `document.title`.
+- On navigation the hub sets `document.title` from the page's `<title>`.  It
+  does not move focus or announce the new page.
 - Checkboxes and radio buttons are not implemented for landing or gathering.
 
 ### Elsewhere
@@ -808,7 +862,7 @@ The documentation describes no testing approach for applications.
 
 ### Loadbare/app
 
-Loadbare/app is at 0.7.3 and has not reached 1.0.  TECHREF-1.0 lists items
+Loadbare/app is at 0.9.0 and has not reached 1.0.  TECHREF-1.0 lists items
 to decide before 1.0 because they would be breaking changes afterward.
 Theory states that 1.0 is scoped so that foreseeable features can be added
 without breaking existing code.
@@ -853,14 +907,14 @@ Loadbare's history begins with Andromeda in 2003, whose data layer is now
 Each item is current behavior or an open item named in TECHREF-1.0 or the
 Roadmap.
 
-| Area                          | Status in 0.7.3                                                        |
+| Area                          | Status in the working tree after 0.9.0                                 |
 |-------------------------------|------------------------------------------------------------------------|
 | Nested data                   | A row never holds rows.  Trees are sent as joined rows.                 |
-| Record URLs and view parameters | A URL names a page.  Parameters are an open blocker.                  |
-| Query arguments from the browser | None.  Selection is server state reached through `ctx`.              |
+| Record URLs and view parameters | A path names a page.  A record or a filter is a query parm, `/accounts?acct=23`. |
+| Query arguments from the browser | None.  Query parms reach queries through `contextFor` and `ctx`.     |
 | Checkboxes, radio buttons, file inputs | Not landed and not gathered.  Open blocker.                    |
 | Data types and formatting     | No conversion.  Queries format values.  Open blocker.                  |
-| Error messages                | `lb-error` carries no message.                                         |
+| Error messages                | `lb-request-error` carries no message.                                 |
 | Field validation              | No mechanism.  Per-keystroke validation is a roadmap question.         |
 | Optimistic updates            | None.                                                                  |
 | Concurrent writers            | No version or conflict check.  Roadmap question.                       |
@@ -870,7 +924,7 @@ Roadmap.
 | Subpath hosting               | Not possible.  The hub uses absolute paths.                            |
 | Chrome-level queries          | A widget in the chrome bound to a query requires every page to declare it.  Open blocker. |
 | A widget receiving a whole row | Not available.  Open blocker.                                         |
-| A nested list per outer row   | A nested list receives the same rows in every outer row.  A new outer row's nested list stays empty until its name lands again.  Open blocker. |
+| A nested `rows` query per outer row | A nested query receives the same rows in every outer row.  A new outer row's nested query stays empty until its name lands again.  Open blocker. |
 | Configurable request deadline | Fixed at ten seconds.                                                  |
 | Internationalization          | Roadmap item.                                                          |
 | Lazy page loading             | Roadmap item.                                                          |
@@ -893,14 +947,14 @@ one set of accidental complexity for another, and that the system is
 The table lists requirements an application may have, and whether each
 approach provides them without additional libraries.
 
-| Requirement                                   | Loadbare/app 0.7.3 | Client component + API | Meta-frameworks | Hypermedia | Server-driven stateful |
+| Requirement                                   | Loadbare/app 0.9   | Client component + API | Meta-frameworks | Hypermedia | Server-driven stateful |
 |-----------------------------------------------|--------------------|------------------------|-----------------|------------|------------------------|
 | Pages bound to relational query results       | yes                | application code       | application code | server templates | server templates |
 | No endpoint or route design                   | yes                | no                     | partly (actions, loaders) | no | partly (routes, events) |
 | No client-side state management               | yes                | no                     | no              | yes        | yes                    |
 | No build step                                 | no                 | no                     | no              | yes        | depends on stack       |
 | Server-rendered HTML for crawlers             | no                 | no                     | yes             | yes        | yes                    |
-| Route parameters and record URLs              | no                 | yes                    | yes             | yes        | yes                    |
+| Route parameters and record URLs              | query parms only   | yes                    | yes             | yes        | yes                    |
 | Optimistic updates                            | no                 | yes                    | yes             | no         | partly                 |
 | Offline or local-first operation              | no                 | with libraries         | with libraries  | no         | no                     |
 | Real-time server push                         | no                 | with libraries         | with libraries  | extensions, Turbo Streams over WebSocket | yes |
@@ -921,7 +975,7 @@ approach provides them without additional libraries.
 | Components           | Light-DOM custom elements            | Framework components            | Framework components                    | Server partials; Stimulus controllers | Server components         |
 | Wire                 | One POST endpoint, JSON rows         | Application-designed            | Framework-defined                       | HTML over HTTP                  | WebSocket or snapshot POSTs     |
 | Mutation refresh     | Declared `refresh` names; patches    | Application code or query invalidation | Revalidation                     | Response HTML                   | Re-render                       |
-| Routing              | Flat page names; no parameters       | Router library                  | File-based, with parameters and layouts | Server routes                   | Server routes                   |
+| Routing              | Flat page names; query parms         | Router library                  | File-based, with parameters and layouts | Server routes                   | Server routes                   |
 | Build                | `loadbare-app-build`, esbuild        | Vite and others                 | Vite, Turbopack, others                 | None required                   | Stack-specific                  |
 | CSS                  | Concatenated, unscoped               | Varies                          | Varies, scoped options                  | None                            | None built in                   |
 | Server               | Application's Express app            | Application's API               | Framework server or adapters            | Any                             | Phoenix, Laravel, ASP.NET Core  |
@@ -936,18 +990,19 @@ row, so the invoice is refreshed.
 
 ```html
 <!-- invoice.page.html -->
-<section lb-row="invoice">
-  <h2 lb-cell="number"></h2>
-  <span lb-cell="customer"></span>
+<title>Invoice</title>
+<section lb-query="invoice">
+  <h2 lb-column="number"></h2>
+  <span lb-column="customer"></span>
 </section>
 
 <table>
-  <tbody lb-list="invoiceLines">
-    <template lb-key="id">
+  <tbody lb-query="invoiceLines">
+    <template>
       <tr>
-        <td lb-cell="item"></td>
-        <td lb-cell="amount"></td>
-        <td><button lb-action="lb-row-delete">Remove</button></td>
+        <td lb-column="item"></td>
+        <td lb-column="amount"></td>
+        <td><button lb-request="lb-row-delete">Remove</button></td>
       </tr>
     </template>
   </tbody>
@@ -956,11 +1011,11 @@ row, so the invoice is refreshed.
 
 ```ts
 // invoice.queries.ts
-import { list, row, type Queries } from "@loadbare/app/server";
+import { row, rows, type Queries } from "@loadbare/app/server";
 
 export const queries: Queries = {
-  invoice: row((ctx) => ctx.db.currentInvoice()),
-  invoiceLines: list((ctx) => ctx.db.currentInvoiceLines()),
+  invoice: row("id", (ctx) => ctx.db.invoice(ctx.invoiceId)),
+  invoiceLines: rows("id", (ctx) => ctx.db.invoiceLines(ctx.invoiceId)),
 };
 ```
 
@@ -972,9 +1027,9 @@ export const requests: Requests = {
   crud: {
     invoiceLines: {
       rowDelete: {
-        run: async (ctx, where) => {
-          await ctx.db.deleteLine(where.key);
-          return { invoiceLines: patch({ drop: [where.key] }) };
+        run: async (ctx, { key }) => {
+          await ctx.db.deleteLine(key);
+          return { invoiceLines: patch({ drop: [key] }) };
         },
         refresh: ["invoice"],
       },
@@ -983,11 +1038,13 @@ export const requests: Requests = {
 };
 ```
 
-Which invoice is current is held on the server and reached through `ctx`.
-The button carries `lb-pending` and `aria-busy` while the request is in
-flight.  The request sent is
-`{ "action": "lb-row-delete", "list": "invoiceLines", "key": "42" }`.  The
-response carries the refreshed `invoice` row and a patch dropping key `42`.
+Which invoice is current is a query parm, `/invoice?id=7`, which
+`contextFor` puts on `ctx` as `invoiceId`.  The button carries
+`lb-request-pending` and `aria-busy` while the request is in flight.  The
+request sent is
+`{ "name": "lb-row-delete", "query": "invoiceLines", "key": "42" }`.  The
+response carries two response items: the refreshed `invoice` row and a
+patch dropping key `42`.
 
 ### Next.js (App Router)
 
@@ -1097,28 +1154,29 @@ Each equivalent is approximate.
 | Hub                           | Client runtime; router plus data layer                                           |
 | Chrome (`chrome.html`)        | Root layout (`app/layout.tsx`, `+layout.svelte`); application shell              |
 | Page (`<name>.page.html`)     | Route component; page template                                                   |
-| Query (`row()`, `list()`)     | Loader (React Router 7); load function (SvelteKit); data read in a Server Component |
+| Query (`row()`, `rows()`)     | Loader (React Router 7); load function (SvelteKit); data read in a Server Component |
 | `onPageEnter`                 | LiveView `mount`; code at the top of a loader                                    |
-| Declared action               | Route action (React Router 7); form action (SvelteKit); Server Function; LiveView `handle_event` |
+| Declared request (`handlers`) | Route action (React Router 7); form action (SvelteKit); Server Function; LiveView `handle_event` |
 | `crud` operation              | Resource controller action (Rails); REST verb on a row                           |
 | `refresh`                     | Revalidation; `invalidateQueries`; `revalidatePath`                              |
 | `patch({ rows, drop })`       | Keyed partial update; Turbo Stream `append`/`replace`/`remove`; LiveView `stream_insert`/`stream_delete` |
 | Landing                       | Render and commit; swap; patch                                                   |
-| `lb-list`, `lb-row`, `lb-cell` | IE4 `DATASRC` and `DATAFLD`; `v-for` and `{{ }}`; `x-for` and `x-text`         |
-| `lb-key`                      | `key` (React, Vue); `track` (Angular); keyed `each` (Svelte)                     |
+| `lb-query`, `lb-column`       | IE4 `DATASRC` and `DATAFLD`; `v-for` and `{{ }}`; `x-for` and `x-text`         |
+| Key declared by `row()`/`rows()` | `key` (React, Vue); `track` (Angular); keyed `each` (Svelte)                  |
 | `lb-show`                     | `v-if`, `@if`, `{#if}`, `x-if`                                                   |
-| `lb-value`                    | A prop; an observed attribute                                                    |
-| `lb-action`                   | `hx-post`; `phx-click`; `wire:click`; `<form action>`                            |
+| `lb-column-value`             | A prop; an observed attribute                                                    |
+| `lb-request`                  | `hx-post`; `phx-click`; `wire:click`; `<form action>`                            |
 | `lb-request` event            | `htmx:beforeRequest`; a component `emit`                                         |
-| `lb-pending`                  | `htmx-request` class; `phx-click-loading`; `useFormStatus().pending`; `wire:loading` |
-| `lb-error`                    | `htmx:responseError`; an error boundary                                          |
-| `lb-row-count`                | An empty-state conditional in a template                                         |
-| `lb-nav-link`                 | `<Link>`; `hx-boost`; Turbo Drive                                                |
-| `lb-navigation`               | `useLocation`; `page.url` (SvelteKit); `$route` (Vue Router)                     |
+| `lb-request-pending`          | `htmx-request` class; `phx-click-loading`; `useFormStatus().pending`; `wire:loading` |
+| `lb-request-error`            | `htmx:responseError`; an error boundary                                          |
+| `lb-query-row-count`          | An empty-state conditional in a template                                         |
+| `lb-url-link`                 | `<Link>`; `hx-boost`; Turbo Drive                                                |
+| `lb-url`                      | `useLocation` and `useSearchParams`; `page.url` (SvelteKit); `$route` (Vue Router) |
+| `url()` from a handler        | A redirect after POST; `redirect()` in a Server Function                         |
 | Widget                        | Component; custom element                                                        |
 | Expansion                     | Server-side include; partial; build-time component render (Astro)                |
 | `exp-` parameter              | A prop fixed at build time                                                       |
-| `lb-slot`, `lb-template`      | Default slot and named slots; `ng-content` with `select`                         |
+| `lb-exp-slot`, `lb-exp-template` | Default slot and named slots; `ng-content` with `select`                         |
 | `lbPlaceRow`, `lbRowsLanded`  | Custom list rendering; a render prop                                             |
 | `ctx` / `HubContext`          | `event.locals` (SvelteKit); loader `context` (React Router 7); request-scoped dependency injection |
 | `imports.ts`                  | Installing and registering a component library                                   |