@triplef/agent 0.1.9 → 0.1.11

package/dist/prompts/index.d.ts

@@ -111,15 +111,17 @@ 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- 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 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 topic labels (partition lane only). Tags are NARROW and specific: entity names, product names, game titles (\"amd\", \"stellar blade\", \"stellar blade blood rain\").\n- category is the broad family the fact belongs to (partition lane only): ONE lowercase PLURAL family noun per remember call \u2014 stocks, games, pets, work, health, finance, contacts \u2026 \u2014 chosen so narrow topics group into families. A category is NEVER a specific entity, product, company, or game title: \"amd\" is a tag under the category \"stocks\"; \"stellar blade\" and \"stellar blade blood rain\" are tags under the category \"games\". Always include it; tags stay narrow, category stays broad and plural.\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;
     probedMemory?: string;
     gathered?: string;
+    knownCategories?: string[];
+    knownTags?: string[];
 }): string;
 
-declare function buildExtractionPrompt(): string;
+declare function buildExtractionPrompt(knownCategories?: readonly string[], knownTags?: readonly string[]): string;
 declare function buildExtractionCorrectionPrompt(error: string): string;
 
 declare const COMMONMARK_FORMAT = "MARKDOWN FORMAT (strict CommonMark):\n- Use ASCII asterisks only: *italic* and **bold**.\n- Never put spaces inside the markers: write **bold**, never ** bold **.\n- Never use fullwidth or unicode asterisk characters (\uFF0A or \u2217).\n- Separate paragraphs with a blank line; keep paragraphs short.\n- Use Markdown links for URLs: [label](https://...). Never paste bare URLs.\n- Use emphasis sparingly. Bold only the single most important term in a paragraph \u2014 never a whole sentence or a lead-in clause.\n- Prefer ## or ### headings to introduce sections instead of bolding the lead-in.\n- Use - bullets for parallel items and 1. numbers for ordered steps.";

package/dist/prompts/index.mjs

@@ -644,14 +644,18 @@ var ExtractionSchema = z.object({
   facts: z.array(z.string()),
   /**
    * 2–6 stable, reusable lowercase topic labels describing the text; the open
-   * vocabulary that powers topic-filtered recall.
+   * vocabulary that powers topic-filtered recall. Tags are NARROW and
+   * specific — entity names, product names, game titles (e.g. `amd`,
+   * `stellar blade`, `stellar blade blood rain`).
    */
   tags: z.array(z.string()),
   /**
-   * One broad lowercase family label for the whole turn-side (e.g. `work`,
-   * `pets`, `games`) — groups the narrow tags into one topic family for the
-   * constellation's community tier and the relink job's per-category passes.
-   * Optional: a turn with nothing durable may omit it.
+   * One broad lowercase PLURAL family label for the whole turn-side (e.g.
+   * `stocks`, `pets`, `games`) — groups the narrow tags into one topic family
+   * for the constellation's community tier and the relink job's per-category
+   * passes. Never a specific entity, product, company, or game title: `amd`
+   * belongs under `stocks`; `stellar blade` belongs under `games`. Optional:
+   * a turn with nothing durable may omit it.
    */
   category: z.string().optional()
 });
@@ -3169,8 +3173,8 @@ Store into the COGNITION lane (call memory-cognition-remember) only when it is s
 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.
+- tags are the ONLY topic-filter vocabulary at recall \u2014 reuse stable, lowercase topic labels (partition lane only). Tags are NARROW and specific: entity names, product names, game titles ("amd", "stellar blade", "stellar blade blood rain").
+- category is the broad family the fact belongs to (partition lane only): ONE lowercase PLURAL family noun per remember call \u2014 stocks, games, pets, work, health, finance, contacts \u2026 \u2014 chosen so narrow topics group into families. A category is NEVER a specific entity, product, company, or game title: "amd" is a tag under the category "stocks"; "stellar blade" and "stellar blade blood rain" are tags under the category "games". Always include it; tags stay narrow, category stays broad and plural.
 
 Do NOT store:
 - Public facts merely fetched this turn that do not relate to the user (e.g. generic web results).
@@ -3183,18 +3187,31 @@ Rules:
 - Call each remember tool once per distinct durable item \u2014 no more.
 - 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.`;
 function buildMemoryWritePrompt(params) {
+  const vocabulary = buildVocabularySection(params.knownCategories, params.knownTags);
   return [
     `USER REQUEST: ${params.userRequest}`,
     `PRIOR MEMORY: ${params.priorMemory?.trim() || "(none stored yet)"}`,
     `PROBED THIS TURN: ${params.probedMemory?.trim() || "(nothing probed this turn)"}`,
     `GATHERED DATA: ${params.gathered?.trim() || "(no tools produced data this turn)"}`,
+    vocabulary,
     MEMORY_WRITE_VERDICT
-  ].join("\n\n");
+  ].filter(Boolean).join("\n\n");
+}
+function buildVocabularySection(knownCategories = [], knownTags = []) {
+  if (knownCategories.length === 0 && knownTags.length === 0) return "";
+  const lines = [];
+  if (knownCategories.length > 0) {
+    lines.push(
+      `KNOWN CATEGORIES (reuse one when it fits; only mint a new plural family noun when none applies): ${knownCategories.join(", ")}`
+    );
+  }
+  if (knownTags.length > 0) lines.push(`KNOWN TOPICS (reuse these tag labels when they fit): ${knownTags.join(", ")}`);
+  return lines.join("\n");
 }
 var MEMORY_WRITE_VERDICT = 'Decide: store each durable user-specific fact with one memory-partition-remember call, each derived understanding with one memory-cognition-remember call, or answer "none" if the turn surfaced nothing durable about this user.';
 
 // src/prompts/memory/vectorize-prompt.constant.ts
-function buildExtractionPrompt() {
+function buildExtractionPrompt(knownCategories = [], knownTags = []) {
   return buildStructuredPrompt(ExtractionSchema, {
     before: "OUTPUT FORMAT \u2014 output ONLY valid JSON matching this exact schema:",
     after: `
@@ -3204,10 +3221,10 @@ YOUR TASK \u2014 decide what is worth remembering:
 - Facts must be self-contained \u2014 no "this"/"that" references; write them as third-person statements.
 - Storage mechanics: each fact is embedded as a whole and matched sentence-by-sentence at recall time (multi-variant retrieval). One dense sentence is fine \u2014 put the subject up front ("User prefers single-line if statements", not "They prefer that style").
 - Skip transient content: greetings, small talk, one-off instructions, filler \u2014 anything with no future recall value. When in doubt about whether a detail is durable, keep it: a durable detail is cheaper to store than to lose.
-- Tags: 2 to 6 stable, reusable, lowercase topic labels describing what the text is about (e.g. "work", "rust", "contacts"). They are the vocabulary for topic-filtered recall later.
-- Category: ONE broad lowercase family label for the whole text (e.g. "work", "pets", "games", "health") that groups the narrow tags into one topic family \u2014 always include it when facts are emitted; omit it when nothing durable is found.
+- Tags: 2 to 6 stable, reusable, lowercase topic labels describing what the text is about (e.g. "work", "rust", "contacts", "amd", "stellar blade"). Tags are NARROW and specific \u2014 entity names, product names, game titles. They are the vocabulary for topic-filtered recall later.
+- Category: ONE broad lowercase PLURAL family noun for the whole text (e.g. "stocks", "pets", "games", "health") that groups the narrow tags into one topic family. A category is NEVER a specific entity, product, company, or game title: "amd" belongs under "stocks"; "stellar blade" and "stellar blade blood rain" belong under "games". Always include it when facts are emitted; omit it when nothing durable is found.
 - If nothing durable is found, return an empty facts array; tags may still label the topic when useful.
-
+${buildVocabularySection2(knownCategories, knownTags)}
 PRIOR MEMORY (when the user message ends with an "ALREADY STORED IN MEMORY" section):
 - That section lists facts already stored in YOUR long-term memory from prior turns. NEVER emit a fact already covered there.
 - If this turn refines, corrects, or completes a stored fact, DO emit it \u2014 as one fuller, self-contained restatement (a full restatement of the corrected claim overwrites the old record in place; it is never a diff).
@@ -3223,6 +3240,16 @@ FINAL REMINDER:
 - Output ONLY valid JSON matching the exact schema above. No markdown code fences, no explanations, preamble, or postscript.`
   });
 }
+function buildVocabularySection2(knownCategories, knownTags) {
+  if (knownCategories.length === 0 && knownTags.length === 0) return "";
+  const lines = [];
+  if (knownCategories.length > 0)
+    lines.push(
+      `KNOWN CATEGORIES (reuse one when it fits; only mint a new plural family noun when none applies): ${knownCategories.join(", ")}`
+    );
+  if (knownTags.length > 0) lines.push(`KNOWN TOPICS (reuse these tag labels when they fit): ${knownTags.join(", ")}`);
+  return lines.join("\n");
+}
 function buildExtractionCorrectionPrompt(error) {
   return `Your previous response was not valid.
 Error: ${error}

package/dist/schemas/index.mjs

@@ -490,14 +490,18 @@ var ExtractionSchema = z.object({
   facts: z.array(z.string()),
   /**
    * 2–6 stable, reusable lowercase topic labels describing the text; the open
-   * vocabulary that powers topic-filtered recall.
+   * vocabulary that powers topic-filtered recall. Tags are NARROW and
+   * specific — entity names, product names, game titles (e.g. `amd`,
+   * `stellar blade`, `stellar blade blood rain`).
    */
   tags: z.array(z.string()),
   /**
-   * One broad lowercase family label for the whole turn-side (e.g. `work`,
-   * `pets`, `games`) — groups the narrow tags into one topic family for the
-   * constellation's community tier and the relink job's per-category passes.
-   * Optional: a turn with nothing durable may omit it.
+   * One broad lowercase PLURAL family label for the whole turn-side (e.g.
+   * `stocks`, `pets`, `games`) — groups the narrow tags into one topic family
+   * for the constellation's community tier and the relink job's per-category
+   * passes. Never a specific entity, product, company, or game title: `amd`
+   * belongs under `stocks`; `stellar blade` belongs under `games`. Optional:
+   * a turn with nothing durable may omit it.
    */
   category: z.string().optional()
 });

package/dist/tools/index.mjs

@@ -960,10 +960,10 @@ ${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.'
+    'One broad lowercase PLURAL category the fact belongs to, e.g. "stocks", "games", "pets", "work" \u2014 a family noun, never a specific entity/product/company/game name ("amd" \u2192 "stocks"; "stellar blade" \u2192 "games"). 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"].'
+    'Optional topic labels (lowercase, reusable, NARROW \u2014 entity/product/game names) so future recall can filter by topic, e.g. ["contacts", "sam"], ["amd"], ["stellar blade"].'
   )
 });
 function createMemoryPartitionRememberTool(deps) {

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.9",
+  "version": "0.1.11",
   "packageManager": "pnpm@11.25.0",
   "license": "MIT",
   "type": "module",
@@ -60,7 +60,7 @@
     "turndown": "^7.2.4"
   },
   "peerDependencies": {
-    "ai": "^7.0.84",
+    "ai": "^7.0.85",
     "zod": "^4.5.4"
   },
   "peerDependenciesMeta": {