@lotics/cli 0.318.47 → 0.318.48

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
@@ -332,9 +332,9 @@ status holds it, `set` to the next), at the foot of the Section whose work it en
332
332
  condition a person sets. A value decided as a row reaches an outcome — why it was lost, refused, voided — is that
333
333
  Act's `asks`, never a field the reader must remember to fill. An Act reaching past the workspace — sending an invoice
334
334
  to a service, a letter by mail — runs its `workflow`, and what the workflow keeps from the answer (an invoice's id,
335
- its link) is named in the Act's `set`. A stage the work only steps aside into from one step
336
- and leaves only back to it — a pause, a repair — is a detour: its option and its Section stand before that step,
337
- entered by its own Act; listed after, it reads as the work's next step. An Act also moves a row back (`when` the later
335
+ its link) is named in the Act's `set`. Work sent back for changes moves back to the earlier
336
+ step; a hold is a yes/no field (and its reason) the step's Acts wait on in their `when`; work only some rows take is a
337
+ stage's `when` (below); an issue to resolve is a row of its own. An Act also moves a row back (`when` the later
338
338
  stage, `set` the earlier): the row draws it beside the way on, and without one a row moved on by mistake stays until an
339
339
  admin edits the table. What a `workflow` or a paper did stands, so a way back there is a correction of its own.
340
340
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@lotics/cli",
3
- "version": "0.318.47",
3
+ "version": "0.318.48",
4
4
  "description": "Lotics SDK and CLI for AI agents",
5
5
  "type": "module",
6
6
  "bin": {