@lotics/cli 0.321.79 → 0.321.80
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 +4 -3
- package/docs/design.md +2 -2
- package/package.json +1 -1
package/docs/design.md
CHANGED
|
@@ -430,11 +430,11 @@ A row at a stage leaves it by its owner whatever its `when`; `dropped` names the
|
|
|
430
430
|
that leave the work undone (cancelled, rejected), which whoever holds the row moves it to from any stage. A stage's owner gates who moves a row out of it; who may move a row into a stage ("only a bookkeeper marks an invoice paid") is a check. Late rows, rows due soon, a warning the line draws and rows waiting on the reader stand first in a
|
|
431
431
|
register; a register whose job is a strict order, a first-come queue, states `attention: false`.
|
|
432
432
|
|
|
433
|
-
A status draws one of three ways, by what the author states, never by habit. With nothing `closed` it is a condition a person sets: its select, no steps. With `closed` it is a path: one a person moves by hand (no Act moves it, or its `row` states `status: { edit: true }`) keeps its select alone, and one Acts move draws its stages as a line of steps across the page, each only moving the row on. Where a stage holds something of its own — fields, blocks, an act that asks or files a paper, a note — the Record states it as a Section inside `Steps`, and the path draws down the page, each step holding what its stage holds.
|
|
433
|
+
A status draws one of three ways, by what the author states, never by habit. With nothing `closed` it is a condition a person sets: its select, no steps. With `closed` it is a path: one a person moves by hand (no Act moves it, or its `row` states `status: { edit: true }`) keeps its select alone, and one Acts move draws its stages as a line of steps across the page, each only moving the row on. Where a stage holds something of its own — fields, blocks, an act that asks or files a paper, a note — the Record states it as a Section inside `Steps`, and the path draws down the page, each step holding what its stage holds. A part that is the work at every open stage is no step and states no `at`; `when` shows a part only at some stages.
|
|
434
434
|
|
|
435
435
|
#### Stage dates and history
|
|
436
436
|
|
|
437
|
-
Who changed what and when is the platform's audit trail, never a table and never shown by an app. When a stage's moment matters
|
|
437
|
+
A step reads as done only where the row shows it was reached, by a stamped date or a history move: a finished row with neither ticks none of its earlier steps, so a path whose steps should read states `dates`. Who changed what and when is the platform's audit trail, never a table and never shown by an app. When a stage's moment matters
|
|
438
438
|
to the business — reported, filtered, printed — it is a date on the row that `records.status.dates` stamps as the row
|
|
439
439
|
enters the option, whoever writes: the one way a status is timed, and the moment a stage's `within` runs from (each stage, and
|
|
440
440
|
each open option of a status with stages, naming none gets `<option>_at`). A straight-line process is one select of its steps in order, each dated (a record that states no `Steps` draws it as a line of steps by itself: no date fields or formulas copy it); a move whose
|