@getenki/ai-darwin-arm64 0.4.0 → 0.5.0

package/README.md

@@ -16,12 +16,18 @@ The package ships prebuilt native binaries for:
 
 ## What It Exports
 
-The current package surface is intentionally small:
+The current package surface is:
 
 - `NativeEnkiAgent`
+- `NativeMultiAgentRuntime`
+- `NativeWorkflowRuntime`
+- `JsAgentStatus`
 - `JsMemoryKind`
 - `JsMemoryModule`
 - `JsMemoryEntry`
+- `JsAgentCard`
+- `JsAgentRunResult`
+- `JsExecutionStep`
 
 `NativeEnkiAgent` is the main entrypoint. It can be created in four modes:
 
@@ -30,6 +36,24 @@ The current package surface is intentionally small:
 - `NativeEnkiAgent.withMemory(...)`
 - `NativeEnkiAgent.withToolsAndMemory(...)`
 
+`NativeMultiAgentRuntime` supports:
+
+- `new(...)`
+- `process(...)`
+- `processWithTrace(...)`
+- `registry(...)`
+- `discover(...)`
+
+`NativeWorkflowRuntime` supports:
+
+- `new(...)`
+- `listWorkflowsJson(...)`
+- `listRunsJson(...)`
+- `inspectJson(...)`
+- `startJson(...)`
+- `resumeJson(...)`
+- `submitInterventionJson(...)`
+
 ## Basic Agent
 
 Use the constructor when you only need a session-based agent backed by the native runtime.
@@ -279,6 +303,107 @@ const recordHandler = (
 }
 ```
 
+## Workflow Runtime
+
+Use `NativeWorkflowRuntime` when you want to register workflow agents plus JSON task and workflow definitions directly from Node.js.
+
+```js
+const { NativeEnkiAgent, NativeWorkflowRuntime } = require('@getenki/ai')
+
+const researcher = new NativeEnkiAgent(
+  'Researcher',
+  'Return short factual notes.',
+  'ollama::qwen3.5:latest',
+  4,
+  './.enki',
+)
+researcher.configureWorkflow('researcher', ['research'])
+
+const writer = new NativeEnkiAgent(
+  'Writer',
+  'Turn notes into a concise summary.',
+  'ollama::qwen3.5:latest',
+  4,
+  './.enki',
+)
+writer.configureWorkflow('writer', ['writing'])
+
+const runtime = new NativeWorkflowRuntime(
+  [researcher, writer],
+  [
+    JSON.stringify({
+      id: 'research_topic',
+      target: { type: 'capabilities', value: ['research'] },
+      prompt: 'Research {{topic}} and return 3 concise bullet points.',
+      input_bindings: { topic: 'input.topic' },
+    }),
+    JSON.stringify({
+      id: 'write_summary',
+      target: { type: 'agent_id', value: 'writer' },
+      prompt: 'Write a short summary for {{topic}} using {{research.content}}',
+      input_bindings: {
+        topic: 'input.topic',
+        research: 'research',
+      },
+    }),
+  ],
+  [
+    JSON.stringify({
+      id: 'research-to-summary',
+      name: 'Research To Summary',
+      nodes: [
+        { id: 'research', kind: 'task', task_id: 'research_topic', output_key: 'research' },
+        { id: 'summary', kind: 'task', task_id: 'write_summary', output_key: 'summary' },
+      ],
+      edges: [{ from: 'research', to: 'summary', transition: { type: 'always' } }],
+    }),
+  ],
+  './.enki',
+)
+
+const response = JSON.parse(
+  await runtime.startJson(
+    JSON.stringify({
+      workflow_id: 'research-to-summary',
+      input: { topic: 'workflow bindings in enki-js' },
+    }),
+  ),
+)
+
+const persisted = JSON.parse(await runtime.inspectJson(response.run_id))
+console.log(persisted.status)
+```
+
+## Human Intervention
+
+Workflow runs persist pending interventions as part of the run state, so approvals and failure escalations can pause and resume without moving state into a separate coordinator service.
+
+Each pending intervention includes:
+
+- `workflow_id`
+- `run_id`
+- `node_id`
+- `prompt`
+- `reason`
+- `response`
+- `created_at` and `resolved_at`
+
+Two built-in patterns are supported:
+
+- `human_gate` nodes pause immediately and wait for a human response
+- task nodes with `failure_policy: "pause_for_intervention"` convert a terminal failure into an intervention asking the human to `retry`, `skip`, `continue`, or `fail`
+
+The runnable TypeScript example is [`example/basic-ts/human-intervention-workflow.ts`](/I:/projects/enki/core-next/example/basic-ts/human-intervention-workflow.ts). It demonstrates:
+
+- a `human_gate` approval flow that pauses, resolves, and resumes to `approval.approved = true`
+- a missing-agent failure that pauses for intervention and resumes after a `skip` response
+
+The runtime interaction loop is:
+
+1. `startJson(...)` returns a paused workflow response
+2. `inspectJson(runId)` exposes `pending_interventions`
+3. `submitInterventionJson(runId, interventionId, response)` resolves the intervention
+4. `resumeJson(runId)` continues the persisted run
 ## Tools And Memory Example
 
 The repository examples in [`example/basic-js/index.js`](/I:/projects/enki/core-next/example/basic-js/index.js) and [`example/basic-ts/index.ts`](/I:/projects/enki/core-next/example/basic-ts/index.ts) use `NativeEnkiAgent.withToolsAndMemory(...)` with:
@@ -448,3 +573,5 @@ Useful scripts:
 - `npm test`: run the AVA test suite
 - `npm run lint`: run `oxlint`
 - `npm run format`: run Prettier, `cargo fmt`, and `taplo format`
+
+

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@getenki/ai-darwin-arm64",
-  "version": "0.4.0",
+  "version": "0.5.0",
   "cpu": [
     "arm64"
   ],
@@ -8,7 +8,7 @@
   "files": [
     "enki-ai.darwin-arm64.node"
   ],
-  "description": "Node.js bindings for Enki AI, a high-performance AI inference engine written in Rust.",
+  "description": "Node.js bindings for Enki's Rust agent runtime.",
   "keywords": [
     "napi-rs",
     "napi-rs",
@@ -23,7 +23,7 @@
     "name": "Enki AI Team",
     "url": "https://getenki.com"
   },
-  "license": " Apache License V2",
+  "license": "Apache-2.0",
   "engines": {
     "node": ">= 12.22.0 < 13 || >= 14.17.0 < 15 || >= 15.12.0 < 16 || >= 16.0.0"
   },