@lotics/cli 0.318.6 → 0.318.8

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.
@@ -263,7 +263,7 @@ 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.
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. A Workflow refuses only what would leave a row invalid or put a false statement on a paper, naming the fact that fixes it; what leaves room for error but is not wrong (a blank printed for handwriting, an unusual choice) it does and reports as a warning in what it returns.
267
267
 
268
268
  **A query** — the rows of one table, or one figure of them, in the app's own aliases:
269
269
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@lotics/cli",
3
- "version": "0.318.6",
3
+ "version": "0.318.8",
4
4
  "description": "Lotics SDK and CLI for AI agents",
5
5
  "type": "module",
6
6
  "bin": {