@triplef/agent 0.1.6 → 0.1.7

package/dist/{intent.schema-CE2F1zLH.d.ts → intent.schema-DnxaUhmz.d.ts}

@@ -78,8 +78,8 @@ declare const IntentSchema: z.ZodObject<{
         "memory-cognition-forget": "memory-cognition-forget";
     }>>;
     getDate: z.ZodDefault<z.ZodBoolean>;
-    imageCount: z.ZodPreprocess<z.ZodDefault<z.ZodNumber>>;
-    videoCount: z.ZodPreprocess<z.ZodDefault<z.ZodNumber>>;
+    imageCount: z.ZodPreprocess<z.ZodDefault<z.ZodNumber>, unknown>;
+    videoCount: z.ZodPreprocess<z.ZodDefault<z.ZodNumber>, unknown>;
     reasoning: z.ZodString;
     contextSummary: z.ZodDefault<z.ZodString>;
     needsClarification: z.ZodDefault<z.ZodBoolean>;

package/dist/prompts/index.d.ts

@@ -1,5 +1,5 @@
-import { T as TemplateName, F as FormatZodShapeOptions } from '../intent.schema-CE2F1zLH.js';
-export { D as DEFAULT_VARIANT_ID } from '../intent.schema-CE2F1zLH.js';
+import { T as TemplateName, F as FormatZodShapeOptions } from '../intent.schema-DnxaUhmz.js';
+export { D as DEFAULT_VARIANT_ID } from '../intent.schema-DnxaUhmz.js';
 import * as zod from 'zod';
 import { z, ZodTypeAny, ZodType } from 'zod';
 import * as zod_v4_core from 'zod/v4/core';
@@ -109,7 +109,7 @@ declare function buildMemoryProfilePrompt(params: {
     maxPayloadChars?: number;
 }): string;
 
-declare const MEMORY_WRITE_INSTRUCTIONS = "MEMORY WRITE JOB \u2014 one purpose: decide whether THIS turn yielded anything worth persisting, and store it in the correct lane via the memory-partition-remember or memory-cognition-remember tool.\n\nTwo lanes, never confused:\n- memory-partition = the user's OWN statements (facts they stated or asked you to remember).\n- memory-cognition = YOUR derived understanding of the user (inferred traits, standing interests, connections).\n\nYou receive:\n- USER REQUEST: what the user asked.\n- PRIOR MEMORY: facts already stored for this user (may be empty).\n- PROBED THIS TURN: what memory-partition-recall already surfaced for this turn (may be empty) \u2014 already known, never re-store.\n- GATHERED DATA: summarized tool results from this turn (web searches, lookups).\n\nStore into the PARTITION lane (call memory-partition-remember) only when it is durable and user-specific:\n- A preference, interest, or durable detail the user states about themselves (favorite X, their setup, contact info, a decision \u2014 however phrased, any language).\n- A notable fact the user asks you to track or remember.\n- Knowledge about a subject the user cares about that was gathered this turn and extends what is already in PRIOR MEMORY.\n\nStore into the COGNITION lane (call memory-cognition-remember) only when it is something you LEARN about the user that they did not state outright:\n- An inferred trait, a standing interest, a working nuance, or a connection between facts the turn supports.\n- Never a stated fact \u2014 those belong in the partition lane.\n\nSTORAGE MECHANICS \u2014 how your memory works (write for the retriever):\n- Each stored record is embedded as a whole AND matched sentence-by-sentence at recall time (multi-variant retrieval). One self-contained fact per call; a single long, dense sentence is fine, but lead with the subject (\"Sam's phone number is 555-1234\", never \"His number is \u2026\").\n- Restating a record verbatim OVERWRITES it in place \u2014 updates are restatements of the full corrected statement, not diffs.\n- tags are the ONLY topic-filter vocabulary at recall \u2014 reuse stable, lowercase topics (partition lane only).\n\nDo NOT store:\n- Public facts merely fetched this turn that do not relate to the user (e.g. generic web results).\n- Anything already covered by PRIOR MEMORY or PROBED THIS TURN \u2014 extend or update it via the remember call; do not repeat.\n- Tool artifacts: URLs, search scores, image metadata, raw JSON keys.\n- Inferred, assumed, or extrapolated details about the user that neither their words nor GATHERED DATA support \u2014 if the user did not state it (or clearly imply it), it is not memory; when in doubt, answer \"none\".\n\nRules:\n- Each remember call stores ONE self-contained statement (stand-alone, understandable weeks later without this conversation's context).\n- Call each remember tool once per distinct durable item \u2014 no more.\n- If nothing durable surfaced, produce a one-word text answer (\"none\") and make NO tool call. An empty memory write is a correct outcome, never a failure.";
+declare const MEMORY_WRITE_INSTRUCTIONS = "MEMORY WRITE JOB \u2014 one purpose: decide whether THIS turn yielded anything worth persisting, and store it in the correct lane via the memory-partition-remember or memory-cognition-remember tool.\n\nTwo lanes, never confused:\n- memory-partition = the user's OWN statements (facts they stated or asked you to remember).\n- memory-cognition = YOUR derived understanding of the user (inferred traits, standing interests, connections).\n\nYou receive:\n- USER REQUEST: what the user asked.\n- PRIOR MEMORY: facts already stored for this user (may be empty).\n- PROBED THIS TURN: what memory-partition-recall already surfaced for this turn (may be empty) \u2014 already known, never re-store.\n- GATHERED DATA: summarized tool results from this turn (web searches, lookups).\n\nStore into the PARTITION lane (call memory-partition-remember) only when it is durable and user-specific:\n- A preference, interest, or durable detail the user states about themselves (favorite X, their setup, contact info, a decision \u2014 however phrased, any language).\n- A notable fact the user asks you to track or remember.\n- Knowledge about a subject the user cares about that was gathered this turn and extends what is already in PRIOR MEMORY.\n\nStore into the COGNITION lane (call memory-cognition-remember) only when it is something you LEARN about the user that they did not state outright:\n- An inferred trait, a standing interest, a working nuance, or a connection between facts the turn supports.\n- Never a stated fact \u2014 those belong in the partition lane.\n\nSTORAGE MECHANICS \u2014 how your memory works (write for the retriever):\n- Each stored record is embedded as a whole AND matched sentence-by-sentence at recall time (multi-variant retrieval). One self-contained fact per call; a single long, dense sentence is fine, but lead with the subject (\"Sam's phone number is 555-1234\", never \"His number is \u2026\").\n- Restating a record verbatim OVERWRITES it in place \u2014 updates are restatements of the full corrected statement, not diffs.\n- tags are the ONLY topic-filter vocabulary at recall \u2014 reuse stable, lowercase topics (partition lane only).\n- category is the broad family the fact belongs to (partition lane only): ONE lowercase label per remember call \u2014 games, pets, work, health, finance, contacts \u2026 \u2014 chosen so narrow topics group into families (both the nte and the wuthering waves facts carry category \"games\"). Always include it; tags stay narrow, category stays broad.\n\nDo NOT store:\n- Public facts merely fetched this turn that do not relate to the user (e.g. generic web results).\n- Anything already covered by PRIOR MEMORY or PROBED THIS TURN \u2014 extend or update it via the remember call; do not repeat.\n- Tool artifacts: URLs, search scores, image metadata, raw JSON keys.\n- Inferred, assumed, or extrapolated details about the user that neither their words nor GATHERED DATA support \u2014 if the user did not state it (or clearly imply it), it is not memory; when in doubt, answer \"none\".\n\nRules:\n- Each remember call stores ONE self-contained statement (stand-alone, understandable weeks later without this conversation's context).\n- Call each remember tool once per distinct durable item \u2014 no more.\n- If nothing durable surfaced, produce a one-word text answer (\"none\") and make NO tool call. An empty memory write is a correct outcome, never a failure.";
 declare function buildMemoryWritePrompt(params: {
     userRequest: string;
     priorMemory?: string;

package/dist/prompts/index.mjs

@@ -3135,6 +3135,7 @@ STORAGE MECHANICS \u2014 how your memory works (write for the retriever):
 - Each stored record is embedded as a whole AND matched sentence-by-sentence at recall time (multi-variant retrieval). One self-contained fact per call; a single long, dense sentence is fine, but lead with the subject ("Sam's phone number is 555-1234", never "His number is \u2026").
 - Restating a record verbatim OVERWRITES it in place \u2014 updates are restatements of the full corrected statement, not diffs.
 - tags are the ONLY topic-filter vocabulary at recall \u2014 reuse stable, lowercase topics (partition lane only).
+- category is the broad family the fact belongs to (partition lane only): ONE lowercase label per remember call \u2014 games, pets, work, health, finance, contacts \u2026 \u2014 chosen so narrow topics group into families (both the nte and the wuthering waves facts carry category "games"). Always include it; tags stay narrow, category stays broad.
 
 Do NOT store:
 - Public facts merely fetched this turn that do not relate to the user (e.g. generic web results).

package/dist/schemas/index.d.ts

@@ -1,5 +1,5 @@
 import { z } from 'zod';
-export { D as DEFAULT_VARIANT_ID, F as FormatZodShapeOptions, I as IntentResult, a as IntentSchema, T as TemplateName, f as formatZodShape } from '../intent.schema-CE2F1zLH.js';
+export { D as DEFAULT_VARIANT_ID, F as FormatZodShapeOptions, I as IntentResult, a as IntentSchema, T as TemplateName, f as formatZodShape } from '../intent.schema-DnxaUhmz.js';
 
 declare const BLOCKED_IMAGE_HOSTS: Set<string>;
 
@@ -264,7 +264,7 @@ declare const memoryProfileResponseSchema: z.ZodPreprocess<z.ZodObject<{
         path: z.ZodOptional<z.ZodString>;
     }, z.core.$strip>>;
     episode: z.ZodOptional<z.ZodNullable<z.ZodString>>;
-}, z.core.$strip>>;
+}, z.core.$strip>, unknown>;
 type MemoryProfileResponse = z.infer<typeof memoryProfileResponseSchema>;
 declare const INSIGHT_TAGS: string[];
 declare const EPISODE_TAGS: string[];

package/dist/tools/index.d.ts

@@ -417,6 +417,7 @@ declare function createMemoryPartitionRecallTool(deps: MemoryPartitionRecallDeps
 
 declare const memoryPartitionRememberSchema: z.ZodObject<{
     text: z.ZodString;
+    category: z.ZodOptional<z.ZodString>;
     tags: z.ZodOptional<z.ZodArray<z.ZodString>>;
 }, z.core.$strip>;
 type MemoryPartitionRememberInput = z.infer<typeof memoryPartitionRememberSchema>;
@@ -430,6 +431,7 @@ interface MemoryPartitionRememberDeps {
         requestId?: string;
         text: string;
         tags?: string[];
+        category?: string;
     }) => Promise<string>;
 }
 declare function createMemoryPartitionRememberTool(deps: MemoryPartitionRememberDeps): Tool;

package/dist/tools/index.mjs

@@ -959,15 +959,18 @@ ${lines.join("\n")}`;
 }
 var memoryPartitionRememberSchema = z.object({
   text: z.string().min(1).max(2e3).describe('The fact to remember, as a self-contained statement, e.g. "Sams phone number is 555-1234".'),
+  category: z.string().min(1).max(40).optional().describe(
+    'One broad lowercase category the fact belongs to, e.g. "games", "pets", "work", "health" \u2014 groups narrow topics into one family. Always include it.'
+  ),
   tags: z.array(z.string().min(1).max(40)).max(8).optional().describe(
     'Optional topic labels (lowercase, reusable) so future recall can filter by topic, e.g. ["contacts", "sam"].'
   )
 });
 function createMemoryPartitionRememberTool(deps) {
   return tool({
-    description: `Store into the user's fact partition (memory-partition): notable facts about subjects they care about (favorites, interests, projects, followed stocks, people, past topics), preferences and durable details they state, and anything they explicitly ask you to remember. Storing gathered knowledge and noticed preferences is expected \u2014 do not wait for an explicit "remember" instruction. This memory outlives the conversation and is recalled later with memory-partition-recall. STORAGE MECHANICS: each record is embedded as a whole and matched sentence-by-sentence at recall time \u2014 write ONE self-contained statement per call (a single dense sentence is fine, subject up front), restating a record verbatim updates it in place, and tags are the recall filter vocabulary (lowercase, reusable).`,
+    description: 'Store into the user\'s fact partition (memory-partition): notable facts about subjects they care about (favorites, interests, projects, followed stocks, people, past topics), preferences and durable details they state, and anything they explicitly ask you to remember. Storing gathered knowledge and noticed preferences is expected \u2014 do not wait for an explicit "remember" instruction. This memory outlives the conversation and is recalled later with memory-partition-recall. STORAGE MECHANICS: each record is embedded as a whole and matched sentence-by-sentence at recall time \u2014 write ONE self-contained statement per call (a single dense sentence is fine, subject up front), restating a record verbatim updates it in place, tags are the recall filter vocabulary (lowercase, reusable), and `category` is one broad family label (games, pets, work, health \u2026) that groups narrow tags into one topic family \u2014 always include both.',
     inputSchema: memoryPartitionRememberSchema,
-    execute: async ({ text, tags }) => {
+    execute: async ({ text, tags, category }) => {
       try {
         const id = await deps.storeRecord({
           memoryPartition: deps.scope.memoryPartition,
@@ -975,7 +978,8 @@ function createMemoryPartitionRememberTool(deps) {
           conversationId: deps.scope.conversationId,
           requestId: deps.scope.requestId,
           text,
-          tags
+          tags,
+          category
         });
         return { stored: true, id };
       } catch (error) {

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@triplef/agent",
   "description": "tripleF (3F) agent domain — structured-output schemas, prompt builders, and model tools shared across the apps.",
-  "version": "0.1.6",
+  "version": "0.1.7",
   "packageManager": "pnpm@11.24.0",
   "license": "MIT",
   "type": "module",
@@ -60,8 +60,8 @@
     "turndown": "^7.2.4"
   },
   "peerDependencies": {
-    "ai": "^7.0.83",
-    "zod": "^4.4.3"
+    "ai": "^7.0.84",
+    "zod": "^4.5.2"
   },
   "peerDependenciesMeta": {
     "ai": {