@lotics/cli 0.321.126 → 0.321.128

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/docs/build.md CHANGED
@@ -8,7 +8,7 @@ Before the first table, `set_workspace` states the business's `timezone` (how ev
8
8
 
9
9
  ## 0. The day's work
10
10
 
11
- Before the first table, ask the person who asked for the papers and lists the business keeps, as the files themselves (its sheets, forms, slips), unless they are attached or the person said to go ahead without them: they name the day's work and hold rules no assumption reaches. Then name the jobs done most often and first in the day, the ones the request names and the rest a business of its kind does daily (what comes in, what goes out, what is counted or billed), and the exceptions each meets (the common ones: going back a step, correcting a locked record, work in parts or split, data late or out of order, a cancel, closing only once the work before is done; build those this work meets, not the list). Build every one of those jobs first, each from the screen it starts on, from the papers and, where they are silent, from how this kind of business runs; name each assumption in your report for the owner to change. Who does a job matters where the work says so: a step another person approves, data not everyone may see, and who each app is given to (`get_workspace` kind `member` lists the organization's people, not who does what here). Whether to ask more than the papers is your call; two questions usually settle the rest: what work happens most often, and what must never go wrong.
11
+ Name the jobs done most often and first in the day, the ones the request names and the rest a business of its kind does daily (what comes in, what goes out, what is counted or billed), and the exceptions each meets (the common ones: going back a step, correcting a locked record, work in parts or split, data late or out of order, a cancel, closing only once the work before is done; build those this work meets, not the list). Build those jobs first, each from the screen it starts on, from what you have and, where it is silent, from how this kind of business runs; name each assumption in your report for the owner to change. Who does a job matters where the work says so: a step another person approves, data not everyone may see, and who each app is given to (`get_workspace` kind `member` lists the organization's people, not who does what here). Whether to ask the person who asked is your call; three questions usually settle a workspace: what work happens most often, the papers and lists the business keeps (attached as files), and what must never go wrong.
12
12
 
13
13
  ## 1. Tables and their checks: `set_tables`
14
14
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@lotics/cli",
3
- "version": "0.321.126",
3
+ "version": "0.321.128",
4
4
  "description": "Lotics SDK and CLI for AI agents",
5
5
  "type": "module",
6
6
  "bin": {