@lotics/cli 0.321.113 → 0.321.115

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/design.md CHANGED
@@ -422,12 +422,11 @@ stage, `set` the earlier), and without one a row moved on by mistake stays until
422
422
 
423
423
  #### Buttons
424
424
 
425
- An Act is offered everywhere — agents run it, and a row's and a section's ⋯ list it — and draws as a button only where
426
- the tree says a person presses it there. `button: true` on an Act stands it at the foot of its Section: the step a
427
- person takes on the record, typically one or two per stage. A List's `button` names the Act its rows draw, quiet,
428
- where people work row after row from the list (an approval queue, ticking off a pick list) — a list where the row's
429
- next step differs by row, each row drawing the first it offers; most Lists name none. An
430
- Act agents run — an invoice made from delivered orders, a payment matched from a statement — states neither.
425
+ People mostly work through agents, so an app draws no button by default: an Act is offered everywhere, and a record's
426
+ header ⋯ and a row's ⋯ list it. Rows never draw a button: every row act waits in its ⋯, and where many rows are worked,
427
+ tick them and state an act `on: "rows"`. An Act on a record or drawer states `button: true` only for a step a person
428
+ does at that screen (a count received, a signed paper, an approval), never for work an agent does (an invoice made
429
+ from delivered orders, a payment matched from a statement). Every other Act waits in the record's ⋯.
431
430
 
432
431
  #### Stages
433
432
 
@@ -491,7 +490,7 @@ an app (`app_architecture`).
491
490
 
492
491
  #### Sections
493
492
 
494
- A record is a head, its parts and at most one Side. From three parts it shows one part at a time; fewer stack. A part is one area of the record's data a person comes to for its own job, like the tabs of a settings page; its related lists and field groups sit inside it under their headings. A status's stages are not areas: their acts stand at the foot of the rows they move, and a stage that holds something of its own — fields, blocks, acts, a note — is a Section inside `Steps`, one `Steps` to a record. State each
493
+ A record is a head, its parts and at most one Side. Its parts stack, one scroll with each headed; state `parts: "tabs"`, or a `tab` on a Section, to show one part at a time, and Sections stating one `tab` share a tab. A part is one area of the record's data a person comes to for its own job, like the tabs of a settings page; its related lists and field groups sit inside it under their headings. A status's stages are not areas: their acts stand at the foot of the rows they move, and a stage that holds something of its own — fields, blocks, acts, a note — is a Section inside `Steps`, one `Steps` to a record. State each
495
494
  part whole for the work there: a field may stand in any number of parts, and a field an Act requires draws beside it
496
495
  unstated. A stage that holds nothing needs no Section: the path draws it by its name. What a person needs in view at every part (who it is for, how to reach
497
496
  them) goes in a Side: it leaves the head and stays on the rows; what only a stage's Act writes (an invoice's number,
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@lotics/cli",
3
- "version": "0.321.113",
3
+ "version": "0.321.115",
4
4
  "description": "Lotics SDK and CLI for AI agents",
5
5
  "type": "module",
6
6
  "bin": {