@lotics/cli 0.316.2 → 0.316.3

package/docs/design.md

@@ -30,6 +30,7 @@ author: state the ones the job needs. A note refuses nothing.
 | A log of what happened | a child List with `layout: "timeline"` | `model/layouts` |
 | Opened to be worked on | the Record's Sections, in the order the work reaches them — `at` where it moves in steps; fields only one kind of row holds (a delay's cause, a safety issue's hours lost) in a Section whose `when` names that kind | `model/section-node` |
 | Rows that each belong to another row | a child List on that row's Record, with `create` and `remove`; a List with `same` or `app` where read-only, for rows another app works | `model/list-node` |
+| A related row's value on the list (the newest contract's end date) | a `lookup` field of the table, ordered, as a column | `model/lookup` |
 | Moving through a status | an Act per move, `status.dates` for the moment of each stage, and the register's Readings | `model/act-node`, `model/status`, `model/reading-node` |
 | 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/tab-node` |
 | Papers a case gathers | a List with `expect`; the papers made, an Act's `templates` | `model/list-node`, `model/act-node` |

package/docs/first_build.md

@@ -80,7 +80,7 @@ Every paper the owner sends is made, one template each. A slot is named after a
 
 ## 3. The app and its acts: `set_app`
 
-**Which apps.** An app is one person's job: the desk they open each day on a list of their own. Does a person open a list the owner names first to do their day's work? An app, that list its register. Part of one record (a vehicle's papers)? A Section or child List of that record's app. Used only while doing another job (the rates a quote is priced from)? A picker on that job's lines, price copied by `default_from`; a book with a keeper or Acts of its own is an app. Same person, another record or rhythm? Another app. Never an app per table; a record passing between people's steps is one app per person over the same table, each register narrowed by `where` to their steps.
+**Which apps.** Shape the apps to the requirement: an app is scoped to a role's work, what that role manages, from the list they open to everything about each row. Where one person runs HR, their app holds the people and, on each person, their contracts, payslips, papers and leave, whatever rhythm each runs at; a business whose payroll, hiring and leave are different people's work may want an app for each. Part of one row (a vehicle's papers)? A Section or child List on that row's page. A value from related rows on the list itself (the newest contract's end date)? A lookup field as a column. Work over many rows at once (a month's payroll)? An Act on the list's rows. Used only while doing another job (the rates a quote is priced from)? A picker on that job's lines, price copied by `default_from`. A role that works several lists holds them in its app; a different role, or work another team does on its own, is another app. Never an app per table.
 
 **The view per kind of row**, chosen before writing the List (a plain register needs none):
 

package/package.json

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