@tangleai/memory 0.20.1 → 0.24.1

package/src/policy.types.d.ts

@@ -0,0 +1,36 @@
+export interface PolicyContradiction {
+    enabled: boolean;
+    threshold: number;
+    /**
+     * Schema constraints this type cannot express: type="integer", minimum=0
+     */
+    maxPairs: number;
+}
+export interface PolicyRetrieval {
+    /**
+     * Schema constraints this type cannot express: type="integer", minimum=0
+     */
+    k: number;
+    minScore: number;
+}
+export interface PolicyEmbedding {
+    model: string;
+    /**
+     * Schema constraints this type cannot express: type="integer", minimum=0
+     */
+    dims: number;
+    tier: "keyless";
+}
+export interface Policy {
+    novelty: {
+        enabled: boolean;
+        threshold: number;
+    };
+    contradiction: PolicyContradiction;
+    crystallization: {
+        enabled: boolean;
+        threshold: number;
+    };
+    retrieval: PolicyRetrieval;
+    embedding: PolicyEmbedding;
+}

package/src/policy.types.js

@@ -0,0 +1,3 @@
+// Generated by @jarenjs/emit from packages/memory/schemas/policy.schema.json.
+// Do not edit: regenerate instead.
+export {};

package/src/retrieval.d.ts

@@ -2,7 +2,7 @@
  * Embedding-ranked retrieval over memory units.
  *
  * This is Tangle's ranker over its OWN store of full units, beside the
- * @jarenjs/ai ledger's `recall({ near })` (which ranks the mirrored
+ * @tangleai/context ledger's `recall({ near })` (which ranks the mirrored
  * ledger records the same way, through the same kernels). Superseded
  * records never surface — they exist for audit, not for recall. Records
  * without embeddings never surface either, which is a real bias (see

package/src/retrieval.js

@@ -2,7 +2,7 @@
  * Embedding-ranked retrieval over memory units.
  *
  * This is Tangle's ranker over its OWN store of full units, beside the
- * @jarenjs/ai ledger's `recall({ near })` (which ranks the mirrored
+ * @tangleai/context ledger's `recall({ near })` (which ranks the mirrored
  * ledger records the same way, through the same kernels). Superseded
  * records never surface — they exist for audit, not for recall. Records
  * without embeddings never surface either, which is a real bias (see
@@ -21,16 +21,17 @@
  * The metric is `cosineSimilarity` from `@jarenjs/core/vector`: the one
  * the suite ranks by, higher-is-better, 0 for a malformed pair.
  */
+import { DEFAULT_MEMORY_POLICY } from "./policy.js";
 import { cosineSimilarity } from '@jarenjs/core/vector';
-import { sameIdentity } from '@jarenjs/ai';
+import { sameIdentity } from '@tangleai/context/ledger';
 /**
  * Rank the live, comparably-embedded units against a query vector and
  * report what could not be ranked. `queryEmbedding` may be the
  * `Float32Array` an embedder answers or the `number[]` a record stores.
  */
 export function recallByEmbedding(units, queryEmbedding, options = {}) {
-    const k = options.k ?? 5;
-    const minScore = options.minScore ?? 0;
+    const k = options.k ?? DEFAULT_MEMORY_POLICY.retrieval.k;
+    const minScore = options.minScore ?? DEFAULT_MEMORY_POLICY.retrieval.minScore;
     const identity = options.identity;
     const scored = [];
     let skipped = 0;

package/src/store.d.ts

@@ -2,7 +2,7 @@
  * The memory store seam and its default in-memory implementation.
  *
  * The contract is four async methods — `get`, `put`, `delete`, `list` —
- * the same injection shape as the @jarenjs/ai ledger's storage seam, one
+ * the same injection shape as the @tangleai/context ledger's storage seam, one
  * level up: this store holds validated memory UNITS, not raw strings.
  * A host backs it with SQLite, OPFS, a graph database, whatever; the
  * policies in this package only ever see the contract.

package/src/store.js

@@ -2,7 +2,7 @@
  * The memory store seam and its default in-memory implementation.
  *
  * The contract is four async methods — `get`, `put`, `delete`, `list` —
- * the same injection shape as the @jarenjs/ai ledger's storage seam, one
+ * the same injection shape as the @tangleai/context ledger's storage seam, one
  * level up: this store holds validated memory UNITS, not raw strings.
  * A host backs it with SQLite, OPFS, a graph database, whatever; the
  * policies in this package only ever see the contract.