Recipe catalog / answer-invalidation
Check an answer after a source change
Does updatedEvidence still support the entire claim that was based on previousEvidence?
You need to check whether updated evidence still supports a previously supported claim.
Explore this recipe interactively ยท Source and implementation guide
Use answer-invalidation 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 { answerInvalidation } from 'jev-recipes/answer-invalidation';
const result = await answerInvalidation({
"claim": "Guests can export reports.",
"previousEvidence": "Guests can export reports.",
"updatedEvidence": "Exporting reports is restricted to workspace owners. Guests cannot export."
});
console.log(result);
Input contract
| Field | Type | Needed |
|---|---|---|
| claim | string | Required |
| previousEvidence | string | Required |
| updatedEvidence | string | Required |
| minConfidence | number | Optional |
Full input and result schemas
{
"input": {
"$schema": "https://json-schema.org/draft/2020-12/schema",
"type": "object",
"properties": {
"claim": {
"type": "string"
},
"previousEvidence": {
"type": "string"
},
"updatedEvidence": {
"type": "string"
},
"minConfidence": {
"type": "number",
"minimum": 0,
"maximum": 1
}
},
"required": [
"claim",
"previousEvidence",
"updatedEvidence"
]
},
"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": [
"still_supported",
"invalidated",
"unclear"
]
},
"confidence": {
"type": "number",
"minimum": 0,
"maximum": 1
},
"probabilities": {
"type": "object",
"propertyNames": {
"type": "string",
"enum": [
"still_supported",
"invalidated",
"unclear"
]
},
"additionalProperties": {
"type": "number",
"minimum": 0,
"maximum": 1
},
"required": [
"still_supported",
"invalidated",
"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 answer-invalidation.
{
"model": "demo-fixture",
"usage": {
"input_tokens": 0,
"output_tokens": 0
},
"status": "ready",
"verdict": "invalidated",
"confidence": 0.96,
"probabilities": {
"still_supported": 0,
"invalidated": 1,
"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
- Assesses one supplied claim and source revision. It does not monitor changes, compare release dates, or invalidate a cache automatically.
Related recipes
- cache-match: Use cache-match to check reuse for a new question when evidence has not changed.