Recipe catalog / memory-scope
Identify memory scope
What is the narrowest explicitly supported scope of fact in context?
You need to identify the narrowest supported scope of a fact or preference.
Explore this recipe interactively ยท Source and implementation guide
Use memory-scope 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 { memoryScope } from 'jev-recipes/memory-scope';
const result = await memoryScope({
"fact": "Use two-space indentation in this repository.",
"context": "The user is describing the conventions for the billing service repository."
});
console.log(result);
Input contract
| Field | Type | Needed |
|---|---|---|
| fact | string | Required |
| context | string | Required |
| minConfidence | number | Optional |
Full input and result schemas
{
"input": {
"$schema": "https://json-schema.org/draft/2020-12/schema",
"type": "object",
"properties": {
"fact": {
"type": "string"
},
"context": {
"type": "string"
},
"minConfidence": {
"type": "number",
"minimum": 0,
"maximum": 1
}
},
"required": [
"fact",
"context"
]
},
"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": [
"user",
"project",
"task",
"session",
"unclear"
]
},
"confidence": {
"type": "number",
"minimum": 0,
"maximum": 1
},
"probabilities": {
"type": "object",
"propertyNames": {
"type": "string",
"enum": [
"user",
"project",
"task",
"session",
"unclear"
]
},
"additionalProperties": {
"type": "number",
"minimum": 0,
"maximum": 1
},
"required": [
"user",
"project",
"task",
"session",
"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-scope.
{
"model": "demo-fixture",
"usage": {
"input_tokens": 0,
"output_tokens": 0
},
"status": "ready",
"verdict": "project",
"confidence": 0.96,
"probabilities": {
"user": 0,
"project": 1,
"task": 0,
"session": 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
- Identifies semantic scope. It does not identify a storage tenant, establish consent, or persist a memory.
Related recipes
- memory-subject: Use memory-subject to identify whom a candidate memory describes before assessing its scope.
- preference-kind: Use preference-kind to distinguish ongoing preferences from temporary instructions.