@hotmeshio/long-tail 0.31.0 → 0.31.1

package/build/scripts/bambu-boat.d.ts

@@ -6,10 +6,12 @@
  *   npm run bambu:boat
  *
  * 1. Download the model once into files/.
- * 2. Scale it (BAMBU_BOAT_SCALE, 0.5 by default: about ten minutes on a P1S).
+ * 2. Scale it (BAMBU_BOAT_SCALE, 0.5 by default).
  * 3. Slice it with the printer, process and filament presets. Each is an
  *    OrcaSlicer system preset name or a path to a preset JSON, which may
- *    inherit a system preset by name.
+ *    inherit a system preset by name. Unset, a P1S with a 0.4 nozzle and PLA;
+ *    the presets in examples/workflows/bambu-printer/boat/presets slice the
+ *    example's boat (0.8 nozzle, TPU, about 11 minutes).
  *
  * Env: BAMBU_BOAT_PRINTER, BAMBU_BOAT_PROCESS, BAMBU_BOAT_FILAMENT, BAMBU_BOAT_SCALE,
  * ORCA_SLICER (the OrcaSlicer executable) and ORCA_PROFILES (its BBL profiles directory).

package/build/scripts/bambu-boat.js

@@ -7,10 +7,12 @@
  *   npm run bambu:boat
  *
  * 1. Download the model once into files/.
- * 2. Scale it (BAMBU_BOAT_SCALE, 0.5 by default: about ten minutes on a P1S).
+ * 2. Scale it (BAMBU_BOAT_SCALE, 0.5 by default).
  * 3. Slice it with the printer, process and filament presets. Each is an
  *    OrcaSlicer system preset name or a path to a preset JSON, which may
- *    inherit a system preset by name.
+ *    inherit a system preset by name. Unset, a P1S with a 0.4 nozzle and PLA;
+ *    the presets in examples/workflows/bambu-printer/boat/presets slice the
+ *    example's boat (0.8 nozzle, TPU, about 11 minutes).
  *
  * Env: BAMBU_BOAT_PRINTER, BAMBU_BOAT_PROCESS, BAMBU_BOAT_FILAMENT, BAMBU_BOAT_SCALE,
  * ORCA_SLICER (the OrcaSlicer executable) and ORCA_PROFILES (its BBL profiles directory).

package/build/scripts/bambu-print.d.ts

@@ -10,7 +10,8 @@
  * 1. Put the file on the printer (it prints only files on its own storage) and hash it: the unit's artifact.
  * 2. Start the unit route: one print step at the station, then a person unloads.
  * 3. Print the route's rows and their lifecycle items as they change, until the
- *    route ends. The unload row is resolved by a person on the dashboard.
+ *    route ends. The unload row is resolved by a person on the dashboard, and
+ *    so is a failed print's decision, on the line's operator role.
  *
  * Env: LT_USERNAME and LT_PASSWORD (a Long Tail login that may invoke the route), BASE_URL
  * (http://localhost:3000), BAMBU_SITE_DIR (deploy/bambu-site), and the printers in .env.

package/build/scripts/bambu-print.js

@@ -11,7 +11,8 @@
  * 1. Put the file on the printer (it prints only files on its own storage) and hash it: the unit's artifact.
  * 2. Start the unit route: one print step at the station, then a person unloads.
  * 3. Print the route's rows and their lifecycle items as they change, until the
- *    route ends. The unload row is resolved by a person on the dashboard.
+ *    route ends. The unload row is resolved by a person on the dashboard, and
+ *    so is a failed print's decision, on the line's operator role.
  *
  * Env: LT_USERNAME and LT_PASSWORD (a Long Tail login that may invoke the route), BASE_URL
  * (http://localhost:3000), BAMBU_SITE_DIR (deploy/bambu-site), and the printers in .env.
@@ -27,6 +28,8 @@ const path_1 = require("path");
 const env_1 = require("../examples/workflows/bambu-printer/env");
 const files_1 = require("../examples/workflows/bambu-printer/files");
 const route_1 = require("../examples/workflows/machine-line/workflows/route");
+const line_1 = require("../lib/machines/line");
+const contracts_1 = require("../services/machines/contracts");
 const env = process.env;
 const BASE_URL = env.BASE_URL || 'http://localhost:3000';
 const SITE_DIR = env.BAMBU_SITE_DIR || 'deploy/bambu-site';
@@ -67,7 +70,8 @@ async function look(orderRef, workflowId, shown) {
     const facets = encodeURIComponent(JSON.stringify({ orderRef }));
     const { escalations } = await api('GET', `/escalations?facets=${facets}&limit=20&sort_by=created_at&order=asc`);
     for (const row of escalations) {
-        const { items = [] } = await api('GET', `/escalations/${row.id}/items`);
+        // Handoff rows hold the lifecycle items; a decision row holds none.
+        const { items = [] } = row.type === contracts_1.ROW_TYPE.HANDOFF ? await api('GET', `/escalations/${row.id}/items`) : {};
         const view = `${row.type}/${row.role} ${row.status}${row.assigned_to ? ' claimed' : ''} [${items.map((i) => i.itemKey).join(', ')}]`;
         if (shown.get(row.id) !== view)
             say(`${row.id.slice(0, 8)} ${view}`);
@@ -100,7 +104,7 @@ async function main() {
         siteId: line.siteId, lineId: line.lineId, routeKey, orderRef: `ORD-${routeKey}`,
         units: [{ unitId: `U-${routeKey}`, carrierId: `PLATE-${routeKey}` }],
         steps: [{ machineId: station, process: env_1.PRINT_PROCESS, recipe: { ...env_1.PRINT_RECIPE } }],
-        artifact: { url, sha256 }, exitRole: env_1.BAMBU_ROLES.UNLOAD, handoffTimeout: env.BAMBU_HANDOFF_TIMEOUT || '6h',
+        artifact: { url, sha256 }, exitRole: (0, line_1.exitRole)(line), operatorRole: (0, line_1.operatorRole)(line), handoffTimeout: env.BAMBU_HANDOFF_TIMEOUT || '6h',
     };
     const workflowId = `bambu-${routeKey}`;
     await api('POST', `/workflows/${route_1.UNIT_ROUTE_WORKFLOW}/invoke`, { data: input, metadata: { source: 'bambu-print' }, workflowId });

package/build/scripts/machine-line.js

@@ -215,7 +215,8 @@ async function startRoutes(artifact) {
         const name = (0, manifests_1.automatedAt)(i, MIX) ? MANIFEST.AUTOMATED : MANIFEST.MANUAL;
         const data = {
             siteId: line.siteId, lineId: line.lineId, routeKey, orderRef: `ORD-${RUN}`, units,
-            steps: (0, manifests_1.manifestSteps)(line, manifests[name]), exitRole: (0, line_1.exitRole)(line), artifact, handoffTimeout: HANDOFF_TIMEOUT,
+            steps: (0, manifests_1.manifestSteps)(line, manifests[name]), exitRole: (0, line_1.exitRole)(line), operatorRole: (0, line_1.operatorRole)(line), qualityRole: (0, line_1.qualityRole)(line),
+            artifact, handoffTimeout: HANDOFF_TIMEOUT,
         };
         const workflowId = `mur-${routeKey}`;
         await api('POST', `/workflows/${route_1.UNIT_ROUTE_WORKFLOW}/invoke`, { workflowId, data, metadata: { source: 'machine-line', manifest: name } });

package/docs/machines.md

@@ -55,7 +55,7 @@ For each line, one replica leads (a Postgres advisory lock held on its own conne
 | `machines[].address` | The physical machine on the wire: its topic level, client id and certificate name, such as a permanent UUID that stays with the machine if it moves. Default `machineId`, which stays the station that rows, roles and routes name |
 | `addressing` | `declared` (default): each address is `machines[].address`, or the station's id. `learned`: a station with no `address` learns it from the machine that claims it. See [Learned addresses](#learned-addresses) |
 | `roles.exit` | The role of the person who receives units at the end of a route. Default `line-exit` |
-| `roles.operator` | The role that gets failed handoffs, stopping alarms, and offline or quiet machines. Default `line-operator` |
+| `roles.operator` | The role that gets failed handoffs, stopping alarms, and offline or quiet machines. Default `line-operator`. A workflow that parks its own failure decisions reads it too: `machineUnitRoute` takes it as `operatorRole` |
 | `roles.quality` | The role that decides units a machine finished on hold: release, rework or scrap. Default `line-quality` |
 | `roles.receivers` | Other roles of people who take units straight from a machine. Machine bots join these roles and the exit role, so they can record their releases on those rows |
 | `machines[].allowedSoftware` | Versions the line accepts. A machine reporting another version is refused before any dispatch |
@@ -336,7 +336,7 @@ The built-in `long-tail-machines` server offers the same surface to agents, gate
 - **Rows are the authority:** an escalation event only tells the gateway which row to look at. It reads the row back as the controller and acts on the stored role, status and metadata. A row on a role the controller does not hold, or an event its stored row contradicts, does nothing.
 - **Roles carry the access:** dispatching to a machine or commanding one means parking a row on that machine's role, so Long Tail's role access decides who can. The gateway acts on a handoff into a machine only on that machine's role, and on a handoff to a person only on a receiver role. A row commands only the machine whose role it is on: cancelling a handoff withdraws the receiver's dispatch, and the sender's job is stopped only by a `cancel` command row on the sender's role.
 - **Rendering:** `Machines.renderSiteConf`, `renderMosquittoConf` and `renderMosquittoAcl(lines, codec)` render the configuration from one line or several on the same broker and site NATS: one bridge identity per line, one gateway user allowed every line's streams, and each line's stations and controller in the ACL. The ACL takes its topics from the codec's channels. Lines on different protocols pass a resolver instead of one codec, `renderMosquittoAcl(lines, (line) => codecOf(line))`, and a `root` resolver to `renderSiteConf` and `renderMosquittoConf`, so each line's bridge, subjects and ACL follow its own codec.
-- **Machines that host their own broker:** the machine broker connects out to each machine's broker with a Mosquitto bridge, carrying the machine's messages in and its commands out under the machine's level of the line's topics, and its codec reads them there. The bridge's notification topic, kept on the machine broker, is the machine's presence. `examples/workflows/bambu-printer` does this for 3D printers.
+- **Machines that host their own broker:** the machine broker connects out to each machine's broker with a Mosquitto bridge, carrying the machine's messages in and its commands out under the machine's level of the line's topics, and its codec reads them there. The bridge's notification topic, kept on the machine broker, is the machine's presence. `examples/workflows/bambu-printer` does this for 3D printers, with a simulated printer (`--profile bambu-sim`) for running it without one.
 
 ### Learned addresses
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hotmeshio/long-tail",
-  "version": "0.31.0",
+  "version": "0.31.1",
   "description": "Long Tail Workflows — Durable AI workflows with human-in-the-loop escalation. Powered by PostgreSQL.",
   "main": "./build/index.js",
   "types": "./build/index.d.ts",