@lotics/cli 0.318.30 → 0.318.31

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.
@@ -33,7 +33,7 @@ coarse, restate a term the heading was carrying.
33
33
 
34
34
  A new doc is **owned by you and private**. `set_access` shares it: `resources[]` with `resource_type` `knowledge_doc`, and `principals[]` (a
35
35
  member, a member group, or `organization` for everyone), each with a `role` of `user` or `manager`; a principal without a `role` has
36
- its access taken away. A doc reaches an agent only when the member can `use` it, an organization admin included.
36
+ its access taken away. A doc reaches an agent when the member can `use` it. An organization admin can use any doc, and their agent searches what they list unless it passes `all: true`.
37
37
 
38
38
  ## How an agent uses a doc
39
39
 
@@ -16,9 +16,11 @@ owner. Everything starts private, and sharing is the only way to widen it. `set_
16
16
  whole organization a role on a resource (`working_in_a_workspace`). Several shares add up, the highest role wins, and
17
17
  there is no deny.
18
18
 
19
+ **Lists are shorter than reach.** A listing shows your own work and what is shared with you. An admin's listing says what it left out (`not_listed`), and `all: true` on `get_workspace` lists it: apps, knowledge docs and templates. An admin's agent lists every table, automation and connection without it. A doc search covers what is listed, so a member's private doc enters an admin's answers only with `all: true`. By id, an admin reaches anything. Sharing an item with yourself through `set_access` lists it from then on.
20
+
19
21
  | Role | Reaches |
20
22
  |---|---|
21
- | Organization owner, admin | Every resource, except the content of a knowledge doc or template not shared with them; `get_workspace` lists those as `unavailable` |
23
+ | Organization owner, admin | Every resource |
22
24
  | Member | What they own and what is shared with them |
23
25
 
24
26
  ## Two doors to data
@@ -49,15 +51,15 @@ and a person who owns the target or an admin can share it with them as viewer.
49
51
 
50
52
  A workflow, app, automation and notification workflow uses its owner's current permissions. Pressing a button, answering
51
53
  a card or filling a form only triggers it. If the owner loses access, the run fails. Only the owner or an admin writes a
52
- body; only its owner replaces a notification workflow or names it on a card.
54
+ body, and that includes a notification workflow and naming it on a card; it still runs as its owner.
53
55
 
54
- Saving a body needs the person saving it and its owner to be able to use every connection, template and knowledge doc it
55
- names. To inspect what a member would get, an admin passes `as_member` with a read or a dry run.
56
+ Saving a body needs its owner to be able to use every connection, template and knowledge doc it names. To inspect what a member would get, an admin passes `as_member` with a read or a dry run.
56
57
 
57
58
  ## Connections
58
59
 
59
60
  A connection belongs to the company. Only an admin connects one, in Lotics under Settings → Connections. Admins and
60
- whoever it is shared with can act through it, and it passes to an admin when its owner leaves.
61
+ whoever it is shared with can act through it, and it passes to an admin when its owner leaves. An app handed from one admin
62
+ to another keeps its shares; any other handover clears them.
61
63
 
62
64
  A workflow step's `connected_account_id` is a literal, a constant bound to one, or a choice among them, so every possible
63
65
  value is judged at save; one read from an input, a record or a call is refused at save and at run. A document template
@@ -4,8 +4,8 @@
4
4
 
5
5
  The steps only a workflow body runs: a connection's (an invoice issuer, a mailbox, …) and the platform's own. Each is
6
6
  called as `await <step>({ ...inputs })` (see `workflows`); a step's inputs and answer are its entry here. A connection
7
- step takes the `connected_account_id` that `get_workspace` lists under kind `connection`, and the app's owner and
8
- whoever saves the body must both be able to use that connection. A step's `connected_account_id` is a literal, a
7
+ step takes the `connected_account_id` that `get_workspace` lists under kind `connection`, and the app's owner must be
8
+ able to use that connection. A step's `connected_account_id` is a literal, a
9
9
  constant bound to one, or a choice among them: every possible value is judged at save, and one read from an input, a
10
10
  record or a call is refused. A template may come from data; a run refuses one its owner cannot use.
11
11
 
@@ -3251,7 +3251,7 @@ above. A provider's refusal carries the provider's own words.
3251
3251
  - Notify workspace members.
3252
3252
  - Lotics shows it to each recipient and emails it to their own address, through no connection; a member who signs in with an identifier an admin issued has no mailbox and sees it in Lotics alone.
3253
3253
  - A member is named by the member_id get_workspace kind member lists. (chat, MCP, CLI)
3254
- - In a workflow body, every member is { type: "organization", id: runtime.organization_id } and the member who started the run { type: "member", id: runtime.triggered_by_member_id }; a run a schedule, a webhook or an email starts was started by no member. blocks draw under the message: text, stat, chart, fields, link, and record (table_id and record_id; the card shows the record's own title, read as the sender can read it). actions are buttons: each runs workflow_id under its owner's access when pressed, and only its owner may name it.
3254
+ - In a workflow body, every member is { type: "organization", id: runtime.organization_id } and the member who started the run { type: "member", id: runtime.triggered_by_member_id }; a run a schedule, a webhook or an email starts was started by no member. blocks draw under the message: text, stat, chart, fields, link, and record (table_id and record_id; the card shows the record's own title, read as the sender can read it). actions are buttons: each runs workflow_id under its owner's access when pressed, and its owner or an admin may name it.
3255
3255
  - A workflow a card can run declares notification inputs. inputs are the values the sender fixes; asks are the values the presser answers, each ask key an input of the workflow that inputs does not fix; every required input of the workflow is fixed or asked as required. decision is "any" (one decision for all recipients: the first press decides it) or "each" (every recipient decides alone); it is required with actions and refused without.
3256
3256
 
3257
3257
  **Inputs**
package/docs/workflows.md CHANGED
@@ -42,7 +42,7 @@ not supply is refused, naming the ones it takes. A rehearsal needs write scope:
42
42
  a step it drops included. `even_if_invoked` and `acknowledge_breaking_api_change` belong to an app workflow and are
43
43
  refused for another kind.
44
44
 
45
- A notification workflow is run by the action of a notification card under its owner's access; the press only triggers it. It declares `inputs` as an app workflow does, reads them as `inputs.<name>` (or `trigger.notification_action.inputs.<name>`), cannot `wait` or `wait_for_event`, and is bound to no table, automation, button or app. Its owner or an admin reads and deletes it; only its owner replaces it or puts it on a card; it has one owner for life and is archived with them when they leave (its open cards close), never handed on. Its writes are judged and attributed as its owner. Its runs are read by its owner and admins, and are never retried: pressing the card again is the retry. A step that sends a card names each action's `workflow_id` as a literal. Only a workflow sends a card; an `agent` step writes the title and body it sends.
45
+ A notification workflow is run by the action of a notification card under its owner's access; the press only triggers it. It declares `inputs` as an app workflow does, reads them as `inputs.<name>` (or `trigger.notification_action.inputs.<name>`), cannot `wait` or `wait_for_event`, and is bound to no table, automation, button or app. Its owner or an admin reads, replaces and deletes it and puts it on a card, and it still runs as its owner; it has one owner for life and is archived with them when they leave (its open cards close), never handed on. Its writes are judged and attributed as its owner. Its runs are read by its owner and admins, and are never retried: pressing the card again is the retry. A step that sends a card names each action's `workflow_id` as a literal. Only a workflow sends a card; an `agent` step writes the title and body it sends.
46
46
 
47
47
  An app workflow reads its call as `trigger.app_workflow.inputs.<name>`, or `inputs.<name>`, which is the same read. A Workflow node receives the inputs it declares;
48
48
  an Act's `workflow` receives `record_id` (`record_ids` on an act over several rows) and what the Act asks.
@@ -91,7 +91,7 @@ A delayed run is never cancelled from a workflow: after a `wait`, it reads the r
91
91
  A tool's inputs and answer are in its own description; the steps only a body runs — a connection's, a mail's — are each
92
92
  an entry of `workflow_steps`. An admin connects a service in Lotics under Settings → Connections; a step names that
93
93
  connection by its `connected_account_id`, which `get_workspace` with `kind: "connection"` lists for the connections the
94
- caller can use. The app's owner and whoever saves the body must both be able to use that connection, so a
94
+ caller can use. The app's owner must be able to use that connection, so a
95
95
  `connected_account_id` is a literal, a constant bound to one, or a choice among them: every possible value is judged at
96
96
  save, and one read from an input, a record or a call is refused. A template may come from data; a run refuses one its
97
97
  owner cannot use.
@@ -21,11 +21,11 @@ Find the means in this order: `get_workspace` maps the workspace; `search` it by
21
21
 
22
22
  ## People
23
23
 
24
- `get_workspace` with kind `member` lists every member's name and id; an admin also sees each one's email, role, `managed` and `sign_in_name`, and a `unavailable` list (kind `knowledge` or `template`) of the docs and templates the admin cannot open, while usable ones carry `access`. An admin also reads the credit limits there.
24
+ `get_workspace` with kind `member` lists every member's name and id; an admin also sees each one's email, role, `managed` and `sign_in_name`, and, on kind `app`, `knowledge` or `template`, `not_listed`: how many more they can reach, which `all: true` lists. Listed docs and templates carry `access`. An admin also reads the credit limits there.
25
25
 
26
26
  `set_members` is an admin's: `members` is a map keyed by an email address, a member id or a managed member's sign-in name, and `groups` a map keyed by a group id or the name of a group to create. In `members`, an email no member holds invites that person (`role` is `member` or `admin`; the invitation email goes out), a current member's entry sets `name` and `role`, a removed member's entry restores them and takes only `name`, and `null` removes a member or cancels the invitation pending to that address. Sign-in names are compared in lowercase. A person adds a managed member and sets its password in Settings → Members. The organization keeps at least one admin: the last one cannot be demoted or removed. In `groups`, an entry sets `name`, `description` and the roster with `member_ids`, or with `add_member_ids` and `remove_member_ids` that leave the rest in place; a roster entry may be a key of `members`, so a person invited in the same call can join; `null` deletes the group. The whole input is checked before anything is written or sent; members are applied before groups, in the order given, and the caller's own step-down last. A member's tool list does not carry `set_members` or `set_workspace`.
27
27
 
28
- `set_access` gives members, groups or the whole organization a role on resources. Role `owner`, on one member, hands every resource listed to that member, whom only the resource's owner or an admin may name; a call cannot share an app and hand it over together, an app handed over loses its sharing, and an automation is turned off until its new owner turns it on. Handovers are applied one resource at a time, and a failure part-way names what was already applied. `set_workspace` takes `credit_limits` (`workspace`, `apps` by app id, `members` by member id; a number is the daily ceiling in credits, `null` removes it and asks for approval).
28
+ `set_access` gives members, groups or the whole organization a role on resources. Role `owner`, on one member, hands every resource listed to that member, whom only the resource's owner or an admin may name; a call cannot share an app and hand it over together, an app handed to or from a member loses its sharing, and an automation is turned off until its new owner turns it on. Handovers are applied one resource at a time, and a failure part-way names what was already applied. `set_workspace` takes `credit_limits` (`workspace`, `apps` by app id, `members` by member id; a number is the daily ceiling in credits, `null` removes it and asks for approval).
29
29
 
30
30
  ## Comments
31
31
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@lotics/cli",
3
- "version": "0.318.30",
3
+ "version": "0.318.31",
4
4
  "description": "Lotics SDK and CLI for AI agents",
5
5
  "type": "module",
6
6
  "bin": {