@lotics/cli 0.311.1 → 0.311.3

package/docs/design.md

@@ -207,6 +207,7 @@ its exception as a formula's yes/no in a `metric`'s `where` (what is late, what
 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`.
 
 #### Funnel
@@ -219,6 +220,16 @@ other, so the second's bars are read over its own first step: they draw on one g
 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.
 
+#### Priced lines
+
+A quote's items, an estimate's works, a repair sheet's damages are lines priced off a book: an entity whose
+`records` names each item, puts the code people type on its line and its price as its `figure`. The line links to
+it, asks the link and its quantities in its block's `create`, and copies the price (`default_from`), so the quote
+keeps what was quoted when the book moves. A line's amount is a formula, the record's total a rollup over the rows
+the block shows — what is not paid for is a second rollup, never a filter on the first, so each group subtotals.
+Group the lines by the parts the record is quoted in (a container, a room, a leg), a field the line asks. The book
+is its keeper's desk, an app of its own.
+
 ### The record
 
 #### Sections

package/package.json

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