@visiq/core-wasm 0.1.5 → 0.1.7

package/README.md

@@ -7,28 +7,38 @@ of a parallel TS implementation that can drift.
 
 ```js
 const { evaluate } = require('@visiq/core-wasm');
-const decisionJson = evaluate(JSON.stringify(event), JSON.stringify(bundle));
+// PLAIN OBJECTS IN, PLAIN OBJECT OUT — `evaluate` does the JSON marshalling
+// itself. Do NOT pre-stringify: `evaluate(JSON.stringify(event), …)` double-
+// encodes, the core sees a JSON *string* where an object belongs, and the
+// decision comes back with `allowed: true` for an event policy DENIES.
+const decision = evaluate(event, bundle);
+if (!decision.allowed) {
+  // blocked by policy — do not execute the tool call
+}
 ```
 
 - **Synchronous, no async init.** `--target nodejs` glue instantiates the wasm from bytes
   at `require` time (`new WebAssembly.Module`/`Instance`) — a drop-in for a sync call.
   (Node/server only; a browser build would need `--target web` + async init.)
-- **`evaluate(eventJson, bundleJson) → decisionJson`** is the language-neutral seam
-  (`evaluate_json` in the core). Fail-closed (G001) on malformed input — never throws.
+- **`evaluate(event, bundle) → decision`** takes and returns plain objects; the
+  language-neutral seam underneath is `evaluate_json` (JSON string in, JSON string out),
+  and this package's wrapper is what stringifies/parses around it. Fail-closed (G001) on
+  malformed input — never throws.
 - **Faithful.** `node conformance.mjs` proves it reproduces the frozen golden corpus
   (`sdk-corpus/GOLDEN-oracle-vectors.json`) — the same vectors every other binding
-  reproduces. **85/85, 0 diverge.**
+  reproduces. **118/118, 0 diverge.**
 
 ## Rebuild
 
 `./build.sh` (needs rustup + `wasm32-unknown-unknown` + `wasm-bindgen-cli` **=0.2.100**;
 the crate pins `wasm-bindgen = "=0.2.100"` so CLI/schema versions match).
 
-## Scope / what this is NOT
+## Scope
 
-This emits the **decision tuple** `{decision, allowed, action:{decision,argRedactionRules},
-retrieval:{action,redactionRules}}`. It does **not** emit rule attribution (`ruleCode`,
-`reason` prose, `decisionId`) — those are out-of-core (#25) and still computed in TS. A
-full `@visiq/harness` cutover to this core therefore needs the core extended to return
-matched-rule attribution; until then this package is the proven, corpus-gated binding.
-See `experiments/matrix-v2/visiq-core-rs/PARITY-GAPS.md`.
+`evaluate` returns the full decision object — `{decision, allowed, reason, ruleId,
+ruleCode, enforced, agentMode, action:{decision,argRedactionRules},
+retrieval:{action,redactionRules}}`. Matched-rule attribution (`reason` prose,
+`ruleId`, `ruleCode`) IS emitted in-core; `decisionId` is not — it is minted by the
+caller. `@visiq/runtime` declares this package a REQUIRED dependency and calls it the
+sole decision engine, so the harness cutover is done, not pending. Remaining seams are
+tracked in `experiments/matrix-v2/visiq-core-rs/PARITY-GAPS.md`.

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@visiq/core-wasm",
-  "version": "0.1.5",
-  "description": "VisIQ governance core (visiq-core-rs) compiled to WASM — the ONE Rust evaluation core, bound to JS. Same core the Go/Java/Ruby/Python SDKs use. evaluate(eventJson, bundleJson) -> decisionJson.",
+  "version": "0.1.7",
+  "description": "VisIQ governance core for Node.js — the one compiled Rust rule engine behind every VisIQ SDK, prebuilt to WebAssembly; evaluate(event, bundle) takes plain objects and synchronously returns a decision object.",
   "type": "commonjs",
   "main": "index.js",
   "types": "index.d.ts",