Recipe catalog / memory-relation
Compare a new fact with memory
How does newFact relate to existingMemory?
You need to compare a new fact with an existing memory for agreement or change.
Explore this recipe interactively ยท Source and implementation guide
Use memory-relation in TypeScript
Install with npm install jev-recipes. Requires Node.js 22.9 or newer and ES modules. Set TYPESAFE_API_KEY in your server environment for live calls, which send input to TypeSafe and use API quota. See the installation guide.
import { memoryRelation } from 'jev-recipes/memory-relation';
const result = await memoryRelation({
"existingMemory": "The project uses npm.",
"newFact": "We have switched this project from npm to pnpm."
});
console.log(result);
Input contract
| Field | Type | Needed |
|---|---|---|
| existingMemory | string | Required |
| newFact | string | Required |
| context | string | Optional |
| minConfidence | number | Optional |
Full input and result schemas
{
"input": {
"$schema": "https://json-schema.org/draft/2020-12/schema",
"type": "object",
"properties": {
"existingMemory": {
"type": "string"
},
"newFact": {
"type": "string"
},
"context": {
"type": "string"
},
"minConfidence": {
"type": "number",
"minimum": 0,
"maximum": 1
}
},
"required": [
"existingMemory",
"newFact"
]
},
"result": {
"$schema": "https://json-schema.org/draft/2020-12/schema",
"type": "object",
"properties": {
"model": {
"type": "string"
},
"usage": {
"type": "object",
"properties": {
"input_tokens": {
"type": "integer",
"minimum": 0,
"maximum": 9007199254740991
},
"output_tokens": {
"type": "integer",
"minimum": 0,
"maximum": 9007199254740991
}
},
"required": [
"input_tokens",
"output_tokens"
],
"additionalProperties": false
},
"status": {
"type": "string",
"enum": [
"ready",
"review"
]
},
"verdict": {
"type": "string",
"enum": [
"repeats",
"supplements",
"updates",
"conflicts",
"unrelated",
"unclear"
]
},
"confidence": {
"type": "number",
"minimum": 0,
"maximum": 1
},
"probabilities": {
"type": "object",
"propertyNames": {
"type": "string",
"enum": [
"repeats",
"supplements",
"updates",
"conflicts",
"unrelated",
"unclear"
]
},
"additionalProperties": {
"type": "number",
"minimum": 0,
"maximum": 1
},
"required": [
"repeats",
"supplements",
"updates",
"conflicts",
"unrelated",
"unclear"
]
}
},
"required": [
"model",
"usage",
"status",
"verdict",
"confidence",
"probabilities"
],
"additionalProperties": false
}
}Saved example result
This hand-authored response demonstrates the contract. It is not a model accuracy measurement. Run it without an API key: npx jev-recipes demo memory-relation.
{
"model": "demo-fixture",
"usage": {
"input_tokens": 0,
"output_tokens": 0
},
"status": "ready",
"verdict": "updates",
"confidence": 0.96,
"probabilities": {
"repeats": 0,
"supplements": 0,
"updates": 1,
"conflicts": 0,
"unrelated": 0,
"unclear": 0
}
}
Evaluation evidence
No verified live accuracy measurement is available. Evaluate representative cases before using this decision in your workflow.
Use the evaluation guide to measure this decision on your own labeled cases.
Limitations
- Compares two supplied facts. It does not select a memory to overwrite or resolve conflicts by timestamp alone.
Related recipes
- memory-value: Use memory-value to assess usefulness before deciding how to store a fact.