@lotics/cli 0.315.6 → 0.315.9

package/docs/agent_surface.md

@@ -29,6 +29,7 @@ app has.
 |---|---|---|---|
 | `<entity>_list` | Every row of <entity> the reader may see. | `search`?; `<scope entity>_id` where the app states `scope`; `<filter>_is`? per `register.filters` field holding one value — a select, a one-row link, a member, a yes/no; `<filter>_from`? / `<filter>_to`? per date filter — none for a date holding a span; `<filter>_min`? / `<filter>_max`? per number filter — none over `books`, none for a looked-up link or member, none for a number read in each row's own unit or currency | every entity the app draws; the filter params on the app's own entity alone |
 | `<entity>_list_<tab>` | The <entity> rows of the tab "<tab>". | the list's; `from`? / `to`? on a tab dated `in` a period; `to` on a tab of rows `open` on a day | each of `register.tabs`; none over `books`, none for a tab whose period reads a date holding a span |
+| `<entity>_totals_<tab>` | The <child> rows added per <entity> row, by "<link>", over the period from `from` to `to`, dated by "<date>": . | `from`; `to` | each of `register.tabs` stating `totals` |
 | `<entity>_record` | One row of <entity> by its id. | `<entity>_id` | every entity the app draws |
 | `<child>_by_<link>` | The <child> rows under one <entity>, through "<link>". | `<entity>_id` | each block of child rows on the record; one narrowed by `where` or ordered by `sort` adds `_<field>_<option>` and `_sorted_<field>` to its name |
 | `<child>_by_<link>_days` | The <child> rows of the <entity> rows handed in whose "<day>" falls from one day to another. | `<entity>_ids`; `from`; `to` | `register.roster` |

package/docs/data_model.md

@@ -235,7 +235,7 @@ rollup — `source_field_key`, `aggregate_option: { field_key?, operation }`, `f
 - Over a figure read in each row's own unit or currency (a notation's `per_row`), `sum`,
   `avg`, `median`, `min`, `max` and `range` hold only where that select is a lookup, through the
   link paired with `source_field_key`, of a single select on this table — the total reads in this
-  row's option of it. A lookup of such a field has no unit.
+  row's option of it. A lookup of such a field stands only where its own table also looks up that select through the same one-link, and reads in that lookup: a line looks up the item's unit through its link to the item, then may look up the item's stock through the same link.
 - `filter` aggregates only the linked records it matches: a full group over the LINKED table's
   fields — `{ node_type: "group", logic, children: [{ node_type: "condition", type, field_key,
   operator, value }] }`, a select condition using `has_any_of` with an ARRAY value.

package/docs/design.md

@@ -81,7 +81,7 @@ then check again. A note refuses nothing.
 | Moving through a status | an act per move, `status.history`, and the register's `readings` | `model/acts`, `model/status`, `model/readings` |
 | Steps people drop out of between | a `funnel` block on the record whose child rows count them | `model/reading-blocks` |
 | A record's own numbers nobody keys, read at a glance | a `figures` block of two to eight tiles | `model/reading-blocks` |
-| Counted over a period | the register's `tabs` over one `period`; an `open` tab's `where` reads only what was true at the period's end, never a status the row moves on from | `model/tabs` |
+| Counted over a period | the register's `tabs` over one `period`; a tab's `totals` for a child's sums before, during and through it; an `open` tab's `where` reads only what was true at the period's end, never a status the row moves on from | `model/tabs` |
 | Papers a case gathers | a rows block with `expect`; the papers made, an act's `templates` | `model/blocks`, `model/papers-and-recordings` |
 | Rows that are each a place a record is sent | a rows block with `expect` on the link to those places and `post`: each ticked, the post written there and read as its feed shows it | `model/publish-desk` |
 | Papers an agent reads, where the owner asked for one | an act's `intake` with `fills` | `model/papers-and-recordings` |
@@ -112,7 +112,7 @@ papers is a `files` block, read whole. Worked: `examples/cards`.
 #### A link opens its row
 
 On a record, a link to one row opens its peek: a drawer on a desk, a sheet on a phone, reading the
-row's face — its mark, name, status, the line under it and its figure by its field's name — and nothing to edit. A link read in a
+row's face — mark, name, status, line and its figure by its field's name — and nothing to edit. A link read in a
 row's cell or on its line opens from its name; a link the record keeps as a field rests as its picker, and
 its way out stands at the field's label where the row has somewhere to go. The peek's one act leaves for
 the app whose register is that entity's rows — the first, in the model's order, that the member
@@ -196,20 +196,19 @@ register; a register whose job is a strict order, a first-come queue, states `re
 #### History
 
 `records.<entity>.status.history` names a child the app's own writes append one row to per status move: its
-link to the row, the new status, the moment and who. It keeps when each row entered each status and who
-moved it — what the rail reads. A record's activity shows every move as a change, so `record.history: true` adds
+link to the row, the new status, the moment and who. The rail reads it. A record's activity shows every move as a change, so `record.history: true` adds
 nothing — and beside `record.activity: false`, which shows them nowhere, it is
 refused. Worked: `examples/approval`.
 
 #### Readings
 
 `register.readings` stand above the rows and read the rows in view. Lead with the job's headline number —
-its exception as a formula's yes/no in a `metric`'s `where` (what is late, what is short; the rows draw it where every field of its own row it reads is drawn, at that width), never a stage the
+its exception as a formula's yes/no in a `metric`'s `where` (what is late, what is short), never a stage the
 status chips already count — then at most the mix (`breakdown`) and the movement (`trend`), varied by job.
 A `pivot` reads on a dashboard. A dashboard app (`dashboard`) answers one owner's question across jobs, each
 reading windowed by the period the reader picks, and a `list` reading hands over the rows to act on. A
 dashboard of many readings states `tabs` (2 to 5) and each reading the `tab` it stands under, so one sheet draws at a time. A
-record's `metric`, `breakdown` and `trend` blocks read its own child rows. Worked: `examples/approval`, `examples/dashboard`.
+record's `metric`, `breakdown` and `trend` blocks read its own child rows. Sums of each row's child rows are a tab's `totals`. Worked: `examples/approval`, `examples/dashboard`.
 
 #### Funnel
 
@@ -218,8 +217,7 @@ from impressions to bookings, an order's lines from ordered to shipped. It state
 each later one keeps, the share lost between two neighbours, and the last over the first. State two to eight
 `steps` in one unit; where the path turns — reach, then conversion — state two blocks one straight after the
 other, so the second's bars are read over its own first step: they draw on one grid, every bar starting at one
-edge and every value ending at another, each under its own label. A step no row holds a number in reads as not measured, so leave a count empty
-rather than typing a zero nobody measured.
+edge and every value ending at another, each under its own label. A step no row holds a number in reads as not measured: leave it empty, never a zero nobody measured.
 
 #### Priced lines
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lotics/cli",
-  "version": "0.315.6",
+  "version": "0.315.9",
   "description": "Lotics SDK and CLI for AI agents",
   "type": "module",
   "bin": {