@maximem/synap-js-sdk 0.4.6 → 0.4.7

package/dist/index.d.cts

@@ -597,6 +597,21 @@ interface CreateMemoryOptions {
     documentCreatedAt?: string | Date | null;
     mode?: IngestMode | string;
     metadata?: Json;
+    /**
+     * The level this memory belongs to, named in full, one entry per level down
+     * to it: `{ customer: "acme", team: "payments", user: "dana" }`.
+     *
+     * Only needed by an account whose scope ladder has a level between its
+     * customer and its user levels. `user_id` and `customer_id` cannot say which
+     * one a write belongs to, so on such a ladder the server refuses the write
+     * rather than guessing: a wrong guess at or above the customer level crosses
+     * a tenant boundary.
+     *
+     * Omit it and nothing changes. Sending one to an account without nested
+     * scoping is an error rather than ignored, because a caller who asks to be
+     * narrowed and is ignored gets widened instead.
+     */
+    scope?: Record<string, string> | null;
 }
 /**
  * Mirrors Python's `CreateMemoryResponse`.
@@ -672,6 +687,21 @@ interface CreateFromFileOptions {
     documentType?: string;
     mode?: IngestMode | string;
     metadata?: Json;
+    /**
+     * The level this memory belongs to, named in full, one entry per level down
+     * to it: `{ customer: "acme", team: "payments", user: "dana" }`.
+     *
+     * Only needed by an account whose scope ladder has a level between its
+     * customer and its user levels. `user_id` and `customer_id` cannot say which
+     * one a write belongs to, so on such a ladder the server refuses the write
+     * rather than guessing: a wrong guess at or above the customer level crosses
+     * a tenant boundary.
+     *
+     * Omit it and nothing changes. Sending one to an account without nested
+     * scoping is an error rather than ignored, because a caller who asks to be
+     * narrowed and is ignored gets widened instead.
+     */
+    scope?: Record<string, string> | null;
 }
 interface UpdateMemoryOptions {
     memory_id?: string;

package/dist/index.d.ts

@@ -597,6 +597,21 @@ interface CreateMemoryOptions {
     documentCreatedAt?: string | Date | null;
     mode?: IngestMode | string;
     metadata?: Json;
+    /**
+     * The level this memory belongs to, named in full, one entry per level down
+     * to it: `{ customer: "acme", team: "payments", user: "dana" }`.
+     *
+     * Only needed by an account whose scope ladder has a level between its
+     * customer and its user levels. `user_id` and `customer_id` cannot say which
+     * one a write belongs to, so on such a ladder the server refuses the write
+     * rather than guessing: a wrong guess at or above the customer level crosses
+     * a tenant boundary.
+     *
+     * Omit it and nothing changes. Sending one to an account without nested
+     * scoping is an error rather than ignored, because a caller who asks to be
+     * narrowed and is ignored gets widened instead.
+     */
+    scope?: Record<string, string> | null;
 }
 /**
  * Mirrors Python's `CreateMemoryResponse`.
@@ -672,6 +687,21 @@ interface CreateFromFileOptions {
     documentType?: string;
     mode?: IngestMode | string;
     metadata?: Json;
+    /**
+     * The level this memory belongs to, named in full, one entry per level down
+     * to it: `{ customer: "acme", team: "payments", user: "dana" }`.
+     *
+     * Only needed by an account whose scope ladder has a level between its
+     * customer and its user levels. `user_id` and `customer_id` cannot say which
+     * one a write belongs to, so on such a ladder the server refuses the write
+     * rather than guessing: a wrong guess at or above the customer level crosses
+     * a tenant boundary.
+     *
+     * Omit it and nothing changes. Sending one to an account without nested
+     * scoping is an error rather than ignored, because a caller who asks to be
+     * narrowed and is ignored gets widened instead.
+     */
+    scope?: Record<string, string> | null;
 }
 interface UpdateMemoryOptions {
     memory_id?: string;

package/dist/index.js

@@ -853,6 +853,10 @@ function buildCreateBody(options) {
     ),
     user_id: either(o2, "user_id", "userId") ?? null,
     customer_id: either(o2, "customer_id", "customerId") ?? null,
+    // null, never `{}`. An empty path is not absence: the server treats one as
+    // an error, because a caller asking to be narrowed and being ignored gets
+    // widened instead.
+    scope: options.scope ?? null,
     mode,
     metadata: options.metadata ?? {}
   };