@mindstudio-ai/agent 0.1.85 → 0.1.86

package/llms.txt

@@ -1840,3 +1840,30 @@ return token;
 import { platform } from '@mindstudio-ai/interface';
 const { url } = await platform.upload(token, file, { onProgress });
 ```
+
+#### `dataSources` — searchable document corpora (RAG)
+
+Declare a data source at module scope and import the handle. The platform owns parsing, chunking, embedding, storage and tenant isolation; every hit returns a citation.
+```typescript
+import { dataSources } from '@mindstudio-ai/agent';
+export const Policies = dataSources.defineDataSource('policies');
+
+// search
+const { results } = await Policies.search('what are the payment terms?', { topK: 5 });
+// options: topK (default 5, max 50), scoreThreshold, rerank, hybrid — the last two default on
+const context = results.map((r) => r.text).join(String.fromCharCode(10, 10));
+
+// add a document (background — poll documents() for status)
+await Policies.add(buffer, { filename: 'policy.pdf', contentType: 'application/pdf' });
+const docs = await Policies.documents();
+```
+
+`SearchHit`: `{ score, text, citation: { documentId, filename, pageNumber, headingPath, boundingBox?, url } }`. `citation.url` is a stable on-domain link to the source document — drop it in an `<a href>`.
+
+Supported: pdf, docx, pptx, xlsx, odt, rtf, epub, images, txt, md, json, csv, html.
+
+Adding the same bytes twice is free — documents are content-addressed, so a re-add is a no-op when this source has already processed those exact bytes under its current configuration. Only reconfiguring the source makes a re-add do work again, and that is an explicit owner-triggered migration, never a side effect of a deploy.
+
+`rerank` and `hybrid` are free to change and take effect on the next search. How documents are chunked and embedded is configured on the corpus itself with `mindstudio-prod datasources config` — not in code — and changing it on a populated source is rejected rather than silently rebuilding.
+
+**A data source is live and shared.** Unlike database tables there is no dev copy and no per-release isolation: adding or removing a document changes what the deployed app retrieves, immediately. Scenarios never reset a data source, and re-ingesting a large corpus costs real money.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mindstudio-ai/agent",
-  "version": "0.1.85",
+  "version": "0.1.86",
   "description": "TypeScript SDK for MindStudio direct step execution",
   "type": "module",
   "main": "./dist/index.js",