@lotics/cli 0.301.0 → 0.302.0

package/docs/design.md

@@ -60,6 +60,7 @@ then check again. A note refuses nothing.
 | Who did what on which day | `layout: "roster"` with `roster` | `model/roster` |
 | A log of what happened | a `timeline` block | `model/timeline-and-agenda` |
 | Opened to be worked on | the record's `sections`, in the order the work reaches them — `at` where it moves in steps | `model/record-page` |
+| A record whose page is its own arrangement of pieces the app already states | `record.compose` | `model/composed-page` |
 | Rows that each belong to another row | a `rows` block on that row's record | `model/blocks` |
 | 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` |
@@ -208,7 +209,8 @@ rather than typing a zero nobody measured.
 
 `record.sections`, in the order the work reaches them: the fields people write, a `files` block per paper the record
 keeps, a block per child, the acts at each one's foot. A register laid out in time (calendar, lanes, roster) opens the
-default record: every field a person writes.
+default record: every field a person writes. `record.compose` is not for a record a standard section order would
+do, and never for behaviour, which belongs in an act.
 
 #### Children
 

package/package.json

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