Recipe catalog / workaround-fit
Check workaround fit
Can workaround address issue without violating constraints?
You need to check whether a workaround addresses an issue within the stated constraints.
Explore this recipe interactively ยท Source and implementation guide
Use workaround-fit 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 { workaroundFit } from 'jev-recipes/workaround-fit';
const result = await workaroundFit({
"issue": "The desktop application cannot open a report.",
"workaround": "Open the report in the web application.",
"constraints": "The customer has web access and needs only to view the report."
});
console.log(result);
Input contract
| Field | Type | Needed |
|---|---|---|
| issue | string | Required |
| workaround | string | Required |
| constraints | string | Required |
| minConfidence | number | Optional |
Full input and result schemas
{
"input": {
"$schema": "https://json-schema.org/draft/2020-12/schema",
"type": "object",
"properties": {
"issue": {
"type": "string"
},
"workaround": {
"type": "string"
},
"constraints": {
"type": "string"
},
"minConfidence": {
"type": "number",
"minimum": 0,
"maximum": 1
}
},
"required": [
"issue",
"workaround",
"constraints"
]
},
"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": [
"fits",
"conflicts",
"unclear"
]
},
"confidence": {
"type": "number",
"minimum": 0,
"maximum": 1
},
"probabilities": {
"type": "object",
"propertyNames": {
"type": "string",
"enum": [
"fits",
"conflicts",
"unclear"
]
},
"additionalProperties": {
"type": "number",
"minimum": 0,
"maximum": 1
},
"required": [
"fits",
"conflicts",
"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 workaround-fit.
{
"model": "demo-fixture",
"usage": {
"input_tokens": 0,
"output_tokens": 0
},
"status": "ready",
"verdict": "fits",
"confidence": 0.96,
"probabilities": {
"fits": 1,
"conflicts": 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
- Assesses described compatibility. It does not establish operational safety, execute a workaround, or grant access.
Related recipes
- troubleshooting-fit: Use troubleshooting-fit to assess a diagnostic procedure rather than a workaround.