@jarenjs/flow 0.83.3 → 0.84.3

package/README.md

@@ -269,18 +269,9 @@ timing:
 The full tables, the wedge as a conformance row, and the fairness notes
 are on the [benchmarks page](https://jklarenbeek.github.io/jarenjs/#/benchmarks?suite=flow).
 
-## Authoring with a model
-
-A jaren-fsm or jaren-dag document is JSON published as a schema, so a
-constrained decoder can author one — and because every compile error
-carries a `code` and a `docPath`, a schema-valid but semantically broken
-machine (a transition to an undeclared state, say) repairs in a bounded
-loop rather than flailing. `@jarenjs/ai`'s
-[*Authoring engine documents*](../ai/README.md#authoring-engine-documents-validate-and-compile)
-section shows the `composeChecks(schema, compileGate)` recipe, and
-[*A model as a dataflow node*](../ai/README.md#a-model-as-a-dataflow-node)
-runs a model as an ordinary dag `task`. Neither package imports the
-other — the composition is data.
+## Validating authored documents
+
+A jaren-fsm or jaren-dag document is JSON published as a schema. Validate its shape, then compile it: coded errors identify the offending document path. `composeChecks` from `@jarenjs/core/check` combines these gates. Model-assisted generation is owned by [Tangle’s authoring integration](https://github.com/jklarenbeek/tangleai/blob/main/packages/jaren/docs/AUTHORING.md). A model invocation is an ordinary injected DAG task; the Flow engine has no model dependency.
 
 ## Authoring by code
 

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@jarenjs/flow",
   "private": false,
-  "version": "0.83.3",
+  "version": "0.84.3",
   "type": "module",
   "main": "./src/index.js",
   "types": "./dist/types/index.d.ts",
@@ -49,7 +49,7 @@
     "prepack": "npm run build:types"
   },
   "dependencies": {
-    "@jarenjs/core": "^0.83.3",
-    "@jarenjs/json": "^0.83.3"
+    "@jarenjs/core": "^0.84.3",
+    "@jarenjs/json": "^0.84.3"
   }
 }