@lotics/cli 0.257.2 → 0.258.0

package/docs/building_an_app.md

@@ -39,6 +39,19 @@ way per concept, and no key changes it. `lotics scaffold check` prints each app
 see it, with every value a default supplied marked `(default)` — review the app there, before
 anything exists.
 
+**Work people are assigned is a task list, stated like any other.** Give the child entity a stored
+status select with `closed` options, a member field, and a deadline under `due`, and state
+`"task": true` in its `records`. Every table of its rows — a rows block of the record it belongs to,
+its own register, the rows filed under one of them (its steps) — then draws each row as a task: its
+ring ticks it done by the act of that entity setting a closed option — stamping and recording what
+that act does — else by its own save, unticks it by the act moving it back, and its status moves in
+place. State a second act `of` the child with `on: "rows"` to complete several at once.
+`starts: { "<member>": "me" }` fills the assignee from whoever adds the row. `opens: { "<member>":
+"me" }` opens a register on the reader's own rows, and a reading's `where` takes `"me"` the same
+way — both narrowed on the server. A register over that child — "My tasks" — rings its rows by
+its own acts the same way. `scaffold check` prints each ring's write — a ring no write reaches is
+drawn disabled, and the check notes it.
+
 **Look at it before anything exists.** `lotics app preview <model.json>#<app>` compiles the app
 against the model's own ids, answers every read from the model's `rows` (a few synthesized for an
 entity that states none), renders the register, the record in its door and the add dialog at 1280

package/package.json

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