@lotics/cli 0.295.3 → 0.296.1

package/docs/data_model.md

@@ -186,6 +186,21 @@ backfilled, and null clears it. A select's or a member field's default is an ARR
 field holds one (`["Unread"]`, never `"Unread"`) — option names in `add_fields`, where the keys do
 not exist yet, and option keys (`opt_…`) in `update_fields`.
 
+`default_from` (text, number, date, boolean, select, select_member, select_record_link) copies a
+value onto a NEW record off the row one of its links names: `{ link_field_key, field_key,
+options? }`, the link of cardinality `"one"` and not itself copied, the source a field of the linked
+table of this field's own type, date format and notation (a link one to the same table) — a formula,
+a rollup, or a lookup through a one-row link (or an ordered one) read as the value it holds; several
+values only into a field holding several; never into a date `derive_from` stamps. It is
+copied when the record is made and never re-read, so a later change to the source leaves the record
+alone (a line's price as it was when the line was booked). A value the write states wins, then the
+copy, then `default_value`. A select source's `options` maps its option keys onto this field's
+(`update_fields`, once the keys exist); an option left unmapped is not copied. null clears it. Deleting the link a
+copy reads through, or the field it copies off, is refused even with `force` until the copy is
+cleared; the dependency report lists the copying field as `copy_link` or `copy_source` under
+`requires_manual_action`. Any other schema change that leaves a copy unable to stand — its source
+retyped, its link made to hold many — is refused, naming the copy.
+
 ### Computed fields
 
 Read-only in records. `formula` is one key holding an object; a rollup's and a lookup's properties

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/package.json

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