anbaric 1.70.0 → 1.72.0

package/docs/api/cli.md

@@ -52,7 +52,7 @@ anbaric app status link-media-brief     # a different app, from anywhere
 
 | Command | Purpose |
 | --- | --- |
-| `anbaric state-machines` | List registered state machines. |
+| `anbaric state-machines` | List registered state machines, with the version of each and when it last registered. |
 | `anbaric jobs create <sm-id> <start-state> [k=v …]` | Create a job and queue it for processing. |
 | `anbaric jobs list [state-machine-id]` | List jobs, newest first, a page at a time (100 by default — `--page 1` for the next). Narrow with `--state`, `--status`, `--app`; `--oldest` flips the order. Filters apply on the platform, across every job, before paging. |
 | `anbaric jobs stats` | Job counts per state and the queue size. |

package/docs/features/deploying.md

@@ -82,6 +82,22 @@ anbaric app tail <name>       # stream runtime logs
 anbaric app tear-down <name>  # stop and remove the app
 ```
 
+## How work reaches a deployed app
+
+The platform queues each step a job is due and pushes it to the app that owns
+the job, at the address the platform itself gave the app when it placed it.
+Nothing in the app chooses or announces that address, and nothing is lost if
+the platform restarts: the route is the deployment.
+
+When a state machine starts it also **registers** itself: its id, the app it
+belongs to and its definition. That registration is what the console's
+**State machines** page, `anbaric state-machines` and the MCP's
+`anbaric_state_machines` show. The platform keeps it, with when the machine
+last registered and a **version** that advances each time the machine's
+definition changes - the same states, actions and transitions registering
+again, after a restart or a redeploy, keep their version. The console shows
+the latest version.
+
 ## Running your own platform
 
 You don't have to use Anbaric Cloud — `anbaric-hosting` runs the whole platform

package/docs/features/entitlements.md

@@ -65,6 +65,17 @@ Apps can't grant. An administrator opens **Entitlements** in the console, picks
 the user, the entitlement and its scope, and adds a note; the same page revokes
 grants and creates global entitlements. Every grant records who made it.
 
+## Invitations and invite links
+
+Entitlements can be chosen when someone is invited, before they have signed
+in: an invitation by email holds them against that address and grants them the
+first time the person signs in. An **invite link** does the same for whoever
+opens it. An owner or admin creates one on the Users page, choosing how many
+people may use it, the role they join as, and the entitlements they receive;
+each person who opens the link and signs in becomes a member with exactly
+those, and the link counts down until it is used up or revoked. Anyone holding
+the link can join, so it is for sharing with the people you mean to invite.
+
 ## Locally
 
 There's no console on your laptop, so the local implementation is

package/docs/features/skills.md

@@ -30,6 +30,10 @@ can read them. Skills belong to the tenant, not to an app, and deployed apps
 cannot see them: they are for the people and agents working on the tenant, not
 for its runtime.
 
+A skill marked **Managed service** is written by Anbaric for a service your
+tenant has, such as the additional services, and kept current by us. It is
+offered to your agents like any other but is not yours to edit or remove.
+
 ## How an agent sees them
 
 Each skill is offered to the agent as a tool named `anbaric_skill_<id>` (hyphens

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "anbaric",
-  "version": "1.70.0",
+  "version": "1.72.0",
   "description": "Everything needed to write an Anbaric app: state machines, jobs, document and secret stores, local in-memory implementations and the Anbaric Cloud clients",
   "license": "MIT",
   "type": "module",
@@ -24,9 +24,9 @@
     "prepublishOnly": "npm run build"
   },
   "dependencies": {
-    "anbaric-impl-cloud": "^1.70.0",
-    "anbaric-data-store": "^1.70.0",
-    "anbaric-state-machine": "^1.70.0",
-    "anbaric-tsapi": "^1.70.0"
+    "anbaric-impl-cloud": "^1.72.0",
+    "anbaric-data-store": "^1.72.0",
+    "anbaric-state-machine": "^1.72.0",
+    "anbaric-tsapi": "^1.72.0"
   }
 }