@lotics/cli 0.318.4 → 0.318.6
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/src/cli.js +3 -3
- package/docs/agent_surface.md +2 -0
- package/docs/workflows.md +1 -1
- package/package.json +1 -1
package/docs/agent_surface.md
CHANGED
|
@@ -263,6 +263,8 @@ and the runs before it stand. A refused read fails the same way, naming the para
|
|
|
263
263
|
What the business asks an agent in the app again and again, and no screen draws, is stated in the app's tree as Query and Workflow nodes, beside its
|
|
264
264
|
Acts: every figure or list whose definition is the business's own (open orders, what a customer owes, low stock) and every recurring operation (close the month, send to the accounting service, chase overdue invoices), each with a `description` written for an agent. A question asked once stays on `query_records` with `aggregate`. A Workflow gets an Act only where a person presses it; work only an agent does has no button. Both are checked and compiled when the tree is written (`set_app`; `reference/query-node`, `reference/workflow-node`).
|
|
265
265
|
|
|
266
|
+
**What the data decides, the system decides.** Whatever follows from the rows and the rules is stated where it holds for every writer, never left to a caller: a fact of one row in its table (`required`, `unique`, `min` and `max`, `options_where`, a check); a value that follows from others as a formula, a lookup or `default_from`; a step of the work in the status's `stages` and its Acts (`when`, `requires`); who reads which rows in the table's `read_scope` and the app's `rows`; what a write sets off in a table's workflow; and a decision over many rows or papers (which papers a household's facts call for) in a Workflow that computes it and refuses what breaks it, every call the same. A caller's inputs are what only it knows: the facts it read, a judgement it made. An override of what the system computes is an optional input, never the way the work is done.
|
|
267
|
+
|
|
266
268
|
**A query** — the rows of one table, or one figure of them, in the app's own aliases:
|
|
267
269
|
|
|
268
270
|
```jsonc
|
package/docs/workflows.md
CHANGED
|
@@ -381,7 +381,7 @@ follows a dotted path instead, so a key that holds a dot is read with `o[key]`.
|
|
|
381
381
|
|
|
382
382
|
## Writing a field: null and undefined
|
|
383
383
|
|
|
384
|
-
In `update_records`' `set`, `create_records`' `records` and `save_record`'s `set` and line rows:
|
|
384
|
+
In `update_records`' `set`, `create_records`' `records` and the workflow step `save_record`'s `set` and line rows:
|
|
385
385
|
|
|
386
386
|
- `null` clears the field.
|
|
387
387
|
- `undefined`, or leaving the key out, leaves the field as it is.
|