@lotics/cli 0.316.26 → 0.317.0

package/docs/first_build.md

@@ -95,33 +95,36 @@ Every paper the owner sends is made, one template each. A slot is named after a
 | Expected against counted, before against after | a List with `compare: {"before": …, "after": …}` | `reference/list-node` |
 | Ranked by a figure | List `sort: {"field": …, "desc": true}` | `reference/list-node` |
 | Moved through a status (stages) | an Act per move, `status.dates`, Readings | `reference/act-node` |
-| Each belonging to another row | a child List on its Record | `reference/list-node` |
+| Each belonging to another row | a child List on its page | `reference/list-node` |
 | Counted over a period | Tabs over one `period`; Readings | `reference/tab-node` |
 | Papers a case gathers | a List with `expect`; an Act's `template` | `reference/list-node` |
 
 Any other screen: `design/treatments`.
 
-Here one app, the counter's job, naming the tables and the template by the aliases above. The register lists the orders; opening one shows a Section per stage, and each Act sets the next stage. The cakes are a child List of the open order, added in place with `create`. Starting to bake asks for the deposit, readying makes the slip, collecting waits for payment.
+**Start from one root List.** `{"type": "List", "entity": "cake_order"}` in the App's `children` is a whole app: the platform draws the page every row opens (a Section per stage with its moves, the cakes as a child List), the add and the Delete. `set_app` answers with what it drew and what it placed or folded in what you stated; state only the difference. The tree below states this counter's choices.
+
+One app, the counter's job, over the tables and template above. The register lists the orders; its page in `pages` has a Section per stage, and each Act sets the next stage. The cakes are a child List of the open order, added in place with `create`. Starting to bake asks for the deposit, readying makes the slip, collecting waits for payment.
 
 ```json
 {
  "body": {
   "type": "App", "key": "counter", "name": "Counter", "color": "amber",
   "children": [
-   {"type": "List", "entity": "cake_order", "filters": ["customer"], "create": ["customer", "due_on", "pay_by"], "children": [
-    {"type": "Record", "door": "page", "children": [
-     {"type": "Section", "key": "order", "title": "Order", "at": ["taken", "baking"], "children": [
-      "due_on",
-      "pay_by",
-      {"type": "List", "entity": "cake_line", "create": ["item", "quantity"]},
-      {"type": "Act", "key": "start_baking", "label": "Start baking", "when": {"stage": ["taken"]}, "requires": ["due_on"], "asks": ["prepaid"], "set": {"stage": "baking"}},
-      {"type": "Act", "key": "ready", "label": "Ready", "when": {"stage": ["baking"]}, "set": {"stage": "ready"}, "template": "order_slip", "into": "slip"}
-     ]},
-     {"type": "Section", "key": "pickup", "title": "Pickup", "at": ["ready"], "children": [
-      {"field": "balance", "edit": false},
-      {"field": "slip", "edit": false},
-      {"type": "Act", "key": "collect", "label": "Collected", "when": {"stage": ["ready"], "paid": true}, "set": {"stage": "collected"}}
-     ]}
+   {"type": "List", "entity": "cake_order", "filters": ["customer"], "create": ["customer", "due_on", "pay_by"]}
+  ],
+  "pages": [
+   {"type": "Record", "entity": "cake_order", "door": "page", "children": [
+    {"type": "Section", "key": "order", "title": "Order", "at": ["taken", "baking"], "children": [
+     "due_on",
+     "pay_by",
+     {"type": "List", "entity": "cake_line", "create": ["item", "quantity"]},
+     {"type": "Act", "key": "start_baking", "label": "Start baking", "when": {"stage": ["taken"]}, "requires": ["due_on"], "asks": ["prepaid"], "set": {"stage": "baking"}},
+     {"type": "Act", "key": "ready", "label": "Ready", "when": {"stage": ["baking"]}, "set": {"stage": "ready"}, "template": "order_slip", "into": "slip"}
+    ]},
+    {"type": "Section", "key": "pickup", "title": "Pickup", "at": ["ready"], "children": [
+     {"field": "balance", "edit": false},
+     {"field": "slip", "edit": false},
+     {"type": "Act", "key": "collect", "label": "Collected", "when": {"stage": ["ready"], "paid": true}, "set": {"stage": "collected"}}
     ]}
    ]}
   ]
@@ -129,20 +132,14 @@ Here one app, the counter's job, naming the tables and the template by the alias
 }
 ```
 
-`set_app` answers with a note for what the rows call for that the tree leaves out; these fold with one: a read-only copy of a placed Field, `create`/`remove: false` on a read-only List, its `app` where one app is over its table, a lone text field's `unique`, a patch address unlike the node's `key`. **What the check refuses**, each with its id (`reference/<id>` is its page):
+`set_app` answers with a note for what the rows call for that the tree leaves out. It places what has one fix and stores the placed tree: a reader's `where` moved to `opens`, a `row.subtitle` made `columns`, Acts alike but for their key made one. These fold with one note: a read-only copy of a placed Field, `create`/`remove: false` on a read-only List, its `app` where one app is over its table, a lone text field's `unique`, a patch address unlike the node's `key`. **What the check refuses**, each with its id (`reference/<id>` is its page; some show a wrong → right):
 
-- `record.placed-once`: a Field, child List, Reading, Statement or Act stands once in a Record, whose head draws the title, subtitle, image, status, figure.
+- `record.placed-once`: a Field, child List, Reading, Statement or Act stands once in a Record, whose head draws the title, subtitle, image, status, figure; a read-only repeat is left out and said.
 - `list.filter-unshown`: a `filters` entry (at most 3) is a select, member, link, date, yes/no or number the rows show, or a formula of such; never text, and the status is the chips already.
 - `list.columns-budget`: `columns` fit the room a desk leaves beside the name, status, deadline and figure.
 - `act.requires-drawn`: an Act's `requires` field is drawn in its Section or asked by it.
-- `app.logs`: a further List at the App's root is a log (at most 3) with its own `key`, over another table than the register's.
 - `act.makes-or-runs`: an Act makes a `template` or runs a `workflow`.
-- `reading.list-app`: a List's `app` has its register over that List's table.
-- `list.list-opens`: a read-only child List opens its rows in the drawer, so its table is one a List of the app draws, or its `app` names the app that works it.
-- A Field's `label` or `when` stands only on a gallery or prose Field (files, markdown text, or `block: true`).
-- `entity.unique`: a `unique` set holds two fields or more of one value each (text, number, date, single select, one-row link).
 - `app.names-declared`: each alias a key names exists (a table, field, option, Act `key`, template).
-- A Query's `sort` is `{"field": …, "desc": true}` (`desc` optional) or a list of them, beside `fields`.
 - A workflow writes a link as ids, `[x.id]`; a whole record or bare value is refused.
 
 Then `set_access` gives the app to the people whose job it is: a `principal_type` of `member` (id from `get_workspace`, `kind: "member"`), `member_group` (an admin lists them: `kind: "group"`) or `organization`, a `role` of `user` or `manager`; none loses access.

package/docs/getting_started.md

@@ -5,6 +5,7 @@ A workspace is where one business keeps what it knows and does its daily work. *
 Open the one page for the job. Pages are read with the `docs` tool (`docs path="design"`; `lotics docs design` on the CLI).
 
 - **Build a workspace from a description:** `docs path="first_build"`. Ask the owner once, only what their papers and your defaults cannot settle, usually their papers and lists first, then a whole bakery built call by call: tables with a check, the paper, the app (which apps, a treatment per kind of row, what the check refuses, who gets it), the owner's rows, then pressing it.
+- **An app starts as one root List:** `{"type": "List", "entity": "order"}` in the App's `children` draws the page, the add and the Delete. The write's answer shows what it drew, placed or folded; change only the difference (`first_build`, § 3).
 - **Change an app:** `docs path="reference/changing-an-app"`. `get_app`, then `set_app` with `nodes` and `base_version_id`. A table is changed with `get_table`, then `set_tables` with its `table_id` (`data_model`).
 - **Enforce a rule on a table:** `docs path="workflows/table-checks"`. A condition no create, update or delete may meet, whoever makes it, and the language it is written in.
 - **Make a document:** `docs path="document_templates"`. A template, its slots and loops, and the act that files it on a record.

package/docs/workflows.md

@@ -81,7 +81,7 @@ All three carry `trigger.trigger_id`.
 | wait | `await wait({ duration_in_minutes: 5 });` |
 | wait for an event | `await wait_for_event({ event_type: "webhook", event_ref: <expr>, timeout_in_minutes: 60 });` |
 | wait for an approval | `await wait_for_approval({ approvers: <expr>, prompt: <expr> });` — see **Waiting for an approval** |
-| return | `return({ status: "success" \| "error", message: <expr>, field_errors: { ... }?, data: { ... }? });` — `data` holds the outputs a Workflow node declares |
+| return | `return({ status: "success" \| "error", message: <expr>, field_errors: { ... }?, data: { ... }? });` — `data` holds the outputs a Workflow node declares — a return of `error` undoes no write a step before it made, so every refusal stands before the body's first write |
 | validate | `validate({ checks: [{ fail_when: <expr>, field_key: "...", message: <expr> }, ...] });` |
 
 A delayed run is never cancelled from a workflow: after a `wait`, it reads the row's state and acts only if it still holds.

package/package.json

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