@lotics/cli 0.296.0 → 0.297.0

package/docs/design.md

@@ -237,6 +237,9 @@ captured — and files it as a new row of the record's `timeline` child (`into`)
   reads whole (a `text` block).
 - Every category the job reads is coloured: each select option's `color`, and a `mark` where a brand or a
   glyph names it — on every option of a select read down a column (how it was paid, the channel, the mode).
+- Someone is a face wherever they are read. A person is a member field and a party a row of an entity stating
+  `party`; where a select's options name people or organisations who are neither, every option's `mark` is
+  its face (`{"kind": "avatar", "name": "person"}`), never a colour dot.
 - Every files field is drawn somewhere — a section's `fields`, a `files` block, the `image`, or where the
   act making it stands.
 - The paperwork is the proof of the work, so every paper the job takes in and every document it issues has a

package/docs/workflows.md

@@ -24,6 +24,11 @@ on({ type: "recurring_schedule", cron_expression: "0 9 * * MON" });
 Every source below is typed, so a misspelled member is refused at save rather than read as nothing.
 All three carry `trigger.trigger_id`.
 
+An automation that brings rows in — on a schedule, or a webhook an outside system calls — is marked
+as importing into their table with `imports_into` (a table id) when it is created or edited. Its
+runs are then the imports log of a register over that table that keeps one (`register.imports`);
+on the CLI, `get_automation` and `query_automations` read the mark back.
+
 | trigger | required config | what the body reads |
 |---|---|---|
 | `recurring_schedule` | `cron_expression` | `runtime.timezone`; the current time is `now()` |

package/package.json

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