jev-recipes 0.2.0 → 0.3.0

package/dist/recipes/step-complete/metadata.d.ts

@@ -1,8 +0,0 @@
-export declare const metadata: {
-    id: string;
-    title: string;
-    description: string;
-    category: "workflow";
-    tags: string[];
-    limitations: string[];
-};

package/dist/recipes/step-complete/metadata.js

@@ -1,10 +0,0 @@
-export const metadata = {
-    id: 'step-complete',
-    title: 'Check one completion condition',
-    description: 'Does evidence establish that condition has been met?',
-    category: 'workflow',
-    tags: ['workflow', 'step', 'complete'],
-    limitations: [
-        'Assesses supplied evidence for one condition. Use exact system state checks when the condition can be determined in code.',
-    ],
-};

package/dist/recipes/step-progress/metadata.d.ts

@@ -1,8 +0,0 @@
-export declare const metadata: {
-    id: string;
-    title: string;
-    description: string;
-    category: "workflow";
-    tags: string[];
-    limitations: string[];
-};

package/dist/recipes/step-progress/metadata.js

@@ -1,10 +0,0 @@
-export const metadata = {
-    id: 'step-progress',
-    title: 'Check step progress',
-    description: 'How does observation change progress toward objective relative to previousState?',
-    category: 'workflow',
-    tags: ['workflow', 'step', 'progress'],
-    limitations: [
-        'Compares one observation with a supplied prior state. It does not measure elapsed time or schedule the next step.',
-    ],
-};

package/dist/recipes/summary-coverage/metadata.d.ts

@@ -1,8 +0,0 @@
-export declare const metadata: {
-    id: string;
-    title: string;
-    description: string;
-    category: "answer-quality";
-    tags: string[];
-    limitations: string[];
-};

package/dist/recipes/summary-coverage/metadata.js

@@ -1,11 +0,0 @@
-export const metadata = {
-    id: 'summary-coverage',
-    title: 'Check summary coverage',
-    description: 'Check whether a summary preserves each supplied point.',
-    category: 'answer-quality',
-    tags: ['answer-quality', 'summary', 'coverage', 'rag', 'evidence'],
-    limitations: [
-        'Checks the points you supply. It does not select important points from a transcript or detect unrelated invented statements.',
-        'Supply 1 to 50 items per list, each with a unique non-empty ID and non-empty text.',
-    ],
-};

package/dist/recipes/ticket-match/metadata.d.ts

@@ -1,8 +0,0 @@
-export declare const metadata: {
-    id: string;
-    title: string;
-    description: string;
-    category: "support";
-    tags: string[];
-    limitations: string[];
-};

package/dist/recipes/ticket-match/metadata.js

@@ -1,10 +0,0 @@
-export const metadata = {
-    id: 'ticket-match',
-    title: 'Compare support tickets',
-    description: 'Do firstTicket and secondTicket describe the same underlying reported issue?',
-    category: 'support',
-    tags: ['support', 'ticket', 'match'],
-    limitations: [
-        'Does not merge tickets or establish a shared root cause from similar symptoms alone. Compare exact identifiers in code.',
-    ],
-};

package/dist/recipes/tone-check/metadata.d.ts

@@ -1,8 +0,0 @@
-export declare const metadata: {
-    id: string;
-    title: string;
-    description: string;
-    category: "answer-quality";
-    tags: string[];
-    limitations: string[];
-};

package/dist/recipes/tone-check/metadata.js

@@ -1,11 +0,0 @@
-export const metadata = {
-    id: 'tone-check',
-    title: 'Check writing criteria',
-    description: 'Check a draft against each supplied writing criterion.',
-    category: 'answer-quality',
-    tags: ['answer-quality', 'tone', 'check', 'rag', 'evidence'],
-    limitations: [
-        'Checks supplied writing criteria. It does not rewrite text, determine factual accuracy, or check exact character counts.',
-        'Supply 1 to 50 items per list, each with a unique non-empty ID and non-empty text.',
-    ],
-};

package/dist/recipes/tool-fit/metadata.d.ts

@@ -1,8 +0,0 @@
-export declare const metadata: {
-    id: string;
-    title: string;
-    description: string;
-    category: "workflow";
-    tags: string[];
-    limitations: string[];
-};

package/dist/recipes/tool-fit/metadata.js

@@ -1,10 +0,0 @@
-export const metadata = {
-    id: 'tool-fit',
-    title: 'Check a tool fit',
-    description: 'Can the capabilities explicitly described in tool perform task?',
-    category: 'workflow',
-    tags: ['workflow', 'tool', 'fit'],
-    limitations: [
-        'Assesses a supplied capability description. It does not discover tools, validate credentials, or grant permission.',
-    ],
-};

package/dist/recipes/topic-shift/metadata.d.ts

@@ -1,8 +0,0 @@
-export declare const metadata: {
-    id: string;
-    title: string;
-    description: string;
-    category: "conversation";
-    tags: string[];
-    limitations: string[];
-};

package/dist/recipes/topic-shift/metadata.js

@@ -1,10 +0,0 @@
-export const metadata = {
-    id: 'topic-shift',
-    title: 'Detect a topic shift',
-    description: 'Does message stay with currentTopic, introduce a different topic, or contain both?',
-    category: 'conversation',
-    tags: ['conversation', 'topic', 'shift'],
-    limitations: [
-        'Compares one message with a supplied topic. It does not generate topic labels or split conversation threads.',
-    ],
-};

package/dist/recipes/troubleshooting-fit/metadata.d.ts

@@ -1,8 +0,0 @@
-export declare const metadata: {
-    id: string;
-    title: string;
-    description: string;
-    category: "support";
-    tags: string[];
-    limitations: string[];
-};

package/dist/recipes/troubleshooting-fit/metadata.js

@@ -1,10 +0,0 @@
-export const metadata = {
-    id: 'troubleshooting-fit',
-    title: 'Check troubleshooting applicability',
-    description: 'Does procedure address symptoms under the described circumstances?',
-    category: 'support',
-    tags: ['support', 'troubleshooting', 'fit'],
-    limitations: [
-        'Assesses a supplied procedure; it does not diagnose a root cause, generate steps, or execute them.',
-    ],
-};

package/dist/recipes/turn-intent/metadata.d.ts

@@ -1,8 +0,0 @@
-export declare const metadata: {
-    id: string;
-    title: string;
-    description: string;
-    category: "conversation";
-    tags: string[];
-    limitations: string[];
-};

package/dist/recipes/turn-intent/metadata.js

@@ -1,10 +0,0 @@
-export const metadata = {
-    id: 'turn-intent',
-    title: 'Identify a conversation turn',
-    description: 'What is the primary communicative purpose of message in context?',
-    category: 'conversation',
-    tags: ['conversation', 'turn', 'intent'],
-    limitations: [
-        'Returns the primary purpose only. It does not split a message into separate requests or execute instructions.',
-    ],
-};

package/dist/recipes/urgency-signal/metadata.d.ts

@@ -1,8 +0,0 @@
-export declare const metadata: {
-    id: string;
-    title: string;
-    description: string;
-    category: "support";
-    tags: string[];
-    limitations: string[];
-};

package/dist/recipes/urgency-signal/metadata.js

@@ -1,10 +0,0 @@
-export const metadata = {
-    id: 'urgency-signal',
-    title: 'Detect an explicit urgency request',
-    description: 'Does message explicitly request urgent attention?',
-    category: 'support',
-    tags: ['support', 'urgency', 'signal'],
-    limitations: [
-        'Detects an expressed urgency request. Compute deadline proximity and apply incident or service priority rules in code.',
-    ],
-};

package/dist/recipes/verify/metadata.d.ts

@@ -1,8 +0,0 @@
-export declare const metadata: {
-    id: string;
-    title: string;
-    description: string;
-    category: "retrieval";
-    tags: string[];
-    limitations: string[];
-};

package/dist/recipes/verify/metadata.js

@@ -1,11 +0,0 @@
-export const metadata = {
-    id: 'verify',
-    title: 'Verify claims',
-    description: 'Check each supplied claim against its paired evidence.',
-    category: 'retrieval',
-    tags: ['rag', 'grounding', 'claims'],
-    limitations: [
-        'Checks only supplied claims; does not establish source truth or completeness.',
-        'Provide 1 to 100 claims with unique IDs.',
-    ],
-};

package/dist/recipes/workaround-fit/metadata.d.ts

@@ -1,8 +0,0 @@
-export declare const metadata: {
-    id: string;
-    title: string;
-    description: string;
-    category: "support";
-    tags: string[];
-    limitations: string[];
-};

package/dist/recipes/workaround-fit/metadata.js

@@ -1,10 +0,0 @@
-export const metadata = {
-    id: 'workaround-fit',
-    title: 'Check workaround fit',
-    description: 'Can workaround address issue without violating constraints?',
-    category: 'support',
-    tags: ['support', 'workaround', 'fit'],
-    limitations: [
-        'Assesses described compatibility. It does not establish operational safety, execute a workaround, or grant access.',
-    ],
-};

package/examples/support/README.md

@@ -1,60 +0,0 @@
-# Support assistant
-
-A support workflow built from the recipe catalog. The workflow lives here so each recipe remains independently usable.
-
-From the repository, after `npm run build`:
-
-```sh
-npm run example:support
-```
-
-The default run uses hand-authored Jev responses and a saved draft from [demo.json](demo.json). It requires no API key and makes no model calls.
-
-To use live Jev decisions with the same saved draft:
-
-```sh
-npm run example:support -- --live
-```
-
-This loads `TYPESAFE_API_KEY` from `.env`, sends synthetic fixture inputs to TypeSafe, and makes up to six Jev requests with retries disabled. There is no generative model call. The output identifies the mode, outcome, and decisions made before stopping.
-
-After installing a packed or released package, you can run the compiled example directly:
-
-```sh
-node node_modules/jev-recipes/dist/examples/support/index.js
-node --env-file=.env node_modules/jev-recipes/dist/examples/support/index.js --live
-```
-
-## Follow the flow
-
-Read [workflow.ts](https://github.com/agencyenterprise/jev-recipes/blob/main/examples/support/workflow.ts) from top to bottom:
-
-1. `handoff` checks escalation rules first. A human request or uncertainty stops here.
-2. `clarify` checks the information needed to proceed.
-3. `route` selects the support handler. Its name is passed to the draft callback.
-4. `rerank` selects useful passages from evidence the application already retrieved.
-5. `answerability` checks whether those passages answer the question.
-6. Your `draftAnswer` callback creates claims with references to selected evidence IDs.
-7. `verify` checks each claim against the referenced original passages.
-8. The final answer joins only those checked claims after all are supported.
-
-The workflow rejects references to evidence that was not selected. The callback supplies IDs, never replacement evidence text. The final response contains no unchecked prose outside the supplied claims. Claim verification still does not establish source truth or guarantee that the answer covers every part of the question.
-
-## Adapt it
-
-Copy `workflow.ts` and `schema.ts` into your application. Replace their repository-relative imports with `jev-recipes` or individual recipe exports. The example schemas also use lower-level recipe schemas; either define your application's shapes locally or derive them from each exported input schema's `.shape`.
-
-Supply your own routes, requirements, handoff rules, and retrieved evidence. Replace the runner's saved-draft callback with your existing generation code, returning `{ claims: [{ id, claim, evidenceIds }] }`. The callback receives the original request, optional conversation context, selected route, and selected passages. You choose the model and framework.
-
-A caller can import the source workflow within this repository:
-
-```ts
-import { answerSupportRequest } from './workflow.js';
-
-const result = await answerSupportRequest(input, draftAnswer, { client });
-if (result.outcome === 'answered') console.log(result.answer);
-```
-
-The possible outcomes are `answered`, `human`, `review`, `clarification`, `no_evidence`, `cannot_answer`, and `unverified`. Stopped results identify the `stage`. Results include completed `decisions` for inspection. Only `answered` includes an answer; errors in inputs, draft references, model responses, or transport throw.
-
-This example does not retrieve documents, send responses, open tickets, or make account changes. Your application handles those actions and follows its own review policy. The example is not an accuracy benchmark.

package/examples/support/demo.json

@@ -1,156 +0,0 @@
-{
-  "input": {
-    "request": "How do I reset my password?",
-    "routes": {
-      "account": "Sign-in, passwords, and account access",
-      "billing": "Invoices, payments, and subscriptions"
-    },
-    "requirements": [
-      {
-        "id": "intent",
-        "description": "The customer identifies what they need help with."
-      }
-    ],
-    "handoffRules": [
-      {
-        "id": "requested-human",
-        "description": "The customer explicitly asks to speak with a human support representative."
-      }
-    ],
-    "evidence": [
-      {
-        "id": "password-reset",
-        "text": "Select Forgot password on the sign-in page to receive a password reset link."
-      },
-      {
-        "id": "invoices",
-        "text": "Download invoices from the Billing page."
-      }
-    ],
-    "topK": 1
-  },
-  "draft": {
-    "claims": [
-      {
-        "id": "reset-instructions",
-        "claim": "Select Forgot password on the sign-in page to receive a password reset link.",
-        "evidenceIds": ["password-reset"]
-      }
-    ]
-  },
-  "responses": {
-    "rule_0": {
-      "model": "demo-fixture",
-      "usage": {
-        "input_tokens": 0,
-        "output_tokens": 0
-      },
-      "answers": {
-        "rule_0": {
-          "type": "choice",
-          "choice": "does_not_match",
-          "confidence": 0.96,
-          "probabilities": {
-            "matches": 0.015,
-            "does_not_match": 0.97,
-            "unclear": 0.015
-          }
-        }
-      }
-    },
-    "requirement_0": {
-      "model": "demo-fixture",
-      "usage": {
-        "input_tokens": 0,
-        "output_tokens": 0
-      },
-      "answers": {
-        "requirement_0": {
-          "type": "choice",
-          "choice": "present",
-          "confidence": 0.96,
-          "probabilities": {
-            "present": 0.97,
-            "missing": 0.015,
-            "ambiguous": 0.015
-          }
-        }
-      }
-    },
-    "route": {
-      "model": "demo-fixture",
-      "usage": {
-        "input_tokens": 0,
-        "output_tokens": 0
-      },
-      "answers": {
-        "route": {
-          "type": "choice",
-          "choice": "account",
-          "confidence": 0.96,
-          "probabilities": {
-            "account": 0.97,
-            "billing": 0.015,
-            "__review__": 0.015
-          }
-        }
-      }
-    },
-    "item_0,item_1": {
-      "model": "demo-fixture",
-      "usage": {
-        "input_tokens": 0,
-        "output_tokens": 0
-      },
-      "answers": {
-        "item_0": {
-          "type": "noul",
-          "noul": 0.97
-        },
-        "item_1": {
-          "type": "noul",
-          "noul": 0.04
-        }
-      }
-    },
-    "answerability": {
-      "model": "demo-fixture",
-      "usage": {
-        "input_tokens": 0,
-        "output_tokens": 0
-      },
-      "answers": {
-        "answerability": {
-          "type": "choice",
-          "choice": "sufficient",
-          "confidence": 0.96,
-          "probabilities": {
-            "sufficient": 0.97,
-            "partial": 0.01,
-            "insufficient": 0.01,
-            "conflicting": 0.01
-          }
-        }
-      }
-    },
-    "claim_0": {
-      "model": "demo-fixture",
-      "usage": {
-        "input_tokens": 0,
-        "output_tokens": 0
-      },
-      "answers": {
-        "claim_0": {
-          "type": "choice",
-          "choice": "supported",
-          "confidence": 0.96,
-          "probabilities": {
-            "supported": 0.97,
-            "contradicted": 0.015,
-            "unsupported": 0.015
-          }
-        }
-      }
-    }
-  }
-}

package/recipes/README.md

@@ -1,128 +0,0 @@
-# Recipe catalog
-
-66 small decisions for AI applications. Every recipe has its own input and result schemas, example, and usage guide. The package exports camelCase functions from kebab-case paths: `answerCoverage` from `jev-recipes/answer-coverage`, for example.
-
-After `npm install jev-recipes`, browse the groups below or use `npx jev-recipes list <query>` and `npx jev-recipes describe <recipe>` from your app’s directory. Discovery needs no API key. Each recipe guide describes its inputs, results, limits, and review policy.
-
-## Answer quality
-
-| Recipe                                               | Function            | Decision                                                                                               |
-| ---------------------------------------------------- | ------------------- | ------------------------------------------------------------------------------------------------------ |
-| [`answer-coverage`](answer-coverage/README.md)       | `answerCoverage`    | Check whether a draft answers each supplied question.                                                  |
-| [`answer-relevance`](answer-relevance/README.md)     | `answerRelevance`   | How directly does draft address request?                                                               |
-| [`citation-match`](citation-match/README.md)         | `citationMatch`     | Find supplied passages that independently support an entire claim.                                     |
-| [`citation-needed`](citation-needed/README.md)       | `citationNeeded`    | Do citationRules require evidence for statement?                                                       |
-| [`answer-consistency`](answer-consistency/README.md) | `answerConsistency` | Do firstStatement and secondStatement make compatible claims about the same subject and circumstances? |
-| [`summary-coverage`](summary-coverage/README.md)     | `summaryCoverage`   | Check whether a summary preserves each supplied point.                                                 |
-| [`certainty-match`](certainty-match/README.md)       | `certaintyMatch`    | Does the certainty expressed in draft match assessment?                                                |
-| [`promise-check`](promise-check/README.md)           | `promiseCheck`      | Does reply promise actions or outcomes beyond allowedCommitments?                                      |
-| [`tone-check`](tone-check/README.md)                 | `toneCheck`         | Check a draft against each supplied writing criterion.                                                 |
-| [`draft-compare`](draft-compare/README.md)           | `draftCompare`      | Which draft better satisfies request under rubric?                                                     |
-
-## Retrieval and evidence
-
-| Recipe                                                   | Function              | Decision                                                                                                     |
-| -------------------------------------------------------- | --------------------- | ------------------------------------------------------------------------------------------------------------ |
-| [`rerank`](rerank/README.md)                             | `rerank`              | Select and order relevant passages.                                                                          |
-| [`verify`](verify/README.md)                             | `verify`              | Check claims against supplied evidence.                                                                      |
-| [`answerability`](answerability/README.md)               | `answerability`       | Check whether evidence can answer the question.                                                              |
-| [`retrieval-needed`](retrieval-needed/README.md)         | `retrievalNeeded`     | Does request require facts beyond context?                                                                   |
-| [`freshness-needed`](freshness-needed/README.md)         | `freshnessNeeded`     | Does question require a current or time-specific state that can change, or stable conceptual knowledge?      |
-| [`source-applicability`](source-applicability/README.md) | `sourceApplicability` | Does the scope described in passage apply to scenario?                                                       |
-| [`evidence-conflict`](evidence-conflict/README.md)       | `evidenceConflict`    | Do firstPassage and secondPassage give incompatible evidence relevant to question under the same conditions? |
-| [`passage-duplicate`](passage-duplicate/README.md)       | `passageDuplicate`    | How much material information do firstPassage and secondPassage share?                                       |
-| [`evidence-novelty`](evidence-novelty/README.md)         | `evidenceNovelty`     | Does passage add material information relevant to question beyond existingEvidence?                          |
-| [`cache-match`](cache-match/README.md)                   | `cacheMatch`          | Does cachedAnswer address question with the same relevant meaning and conditions as originalQuestion?        |
-| [`query-equivalence`](query-equivalence/README.md)       | `queryEquivalence`    | Do firstQuestion and secondQuestion request the same information under the same stated conditions?           |
-| [`context-role`](context-role/README.md)                 | `contextRole`         | What role does passage play in answering question?                                                           |
-| [`query-specificity`](query-specificity/README.md)       | `querySpecificity`    | Does question, interpreted with context, identify a focused information need?                                |
-
-## Conversation
-
-| Recipe                                               | Function            | Decision                                                                           |
-| ---------------------------------------------------- | ------------------- | ---------------------------------------------------------------------------------- |
-| [`clarify`](clarify/README.md)                       | `clarify`           | Find missing or ambiguous requirements.                                            |
-| [`turn-intent`](turn-intent/README.md)               | `turnIntent`        | What is the primary communicative purpose of message in context?                   |
-| [`followup-link`](followup-link/README.md)           | `followupLink`      | Which supplied earlier request does message follow up on?                          |
-| [`reference-resolve`](reference-resolve/README.md)   | `referenceResolve`  | Which supplied candidate does reference refer to in message and context?           |
-| [`intent-change`](intent-change/README.md)           | `intentChange`      | How does message change currentGoal?                                               |
-| [`correction-target`](correction-target/README.md)   | `correctionTarget`  | Which supplied field or statement is message correcting?                           |
-| [`confirmation-match`](confirmation-match/README.md) | `confirmationMatch` | Does response clearly agree to or reject this exact proposal?                      |
-| [`cancellation-check`](cancellation-check/README.md) | `cancellationCheck` | Does message ask to cancel, pause, or continue task?                               |
-| [`topic-shift`](topic-shift/README.md)               | `topicShift`        | Does message stay with currentTopic, introduce a different topic, or contain both? |
-| [`response-needed`](response-needed/README.md)       | `responseNeeded`    | Does message require a substantive reply in context?                               |
-| [`resolution-check`](resolution-check/README.md)     | `resolutionCheck`   | Does message establish that the customer reports issue as resolved?                |
-
-## Tools and tasks
-
-| Recipe                                             | Function           | Decision                                                                                 |
-| -------------------------------------------------- | ------------------ | ---------------------------------------------------------------------------------------- |
-| [`route`](route/README.md)                         | `route`            | Choose a handler for a request.                                                          |
-| [`handoff`](handoff/README.md)                     | `handoff`          | Check your rules for involving a human.                                                  |
-| [`tool-fit`](tool-fit/README.md)                   | `toolFit`          | Can the capabilities explicitly described in tool perform task?                          |
-| [`argument-fit`](argument-fit/README.md)           | `argumentFit`      | Does proposedValue for argument express the intended value in request and context?       |
-| [`result-usefulness`](result-usefulness/README.md) | `resultUsefulness` | Does result provide information useful for task?                                         |
-| [`result-outcome`](result-outcome/README.md)       | `resultOutcome`    | What outcome does result report for task?                                                |
-| [`action-scope`](action-scope/README.md)           | `actionScope`      | Is proposedAction within the work requested in request and constraints?                  |
-| [`step-progress`](step-progress/README.md)         | `stepProgress`     | How does observation change progress toward objective relative to previousState?         |
-| [`repeated-attempt`](repeated-attempt/README.md)   | `repeatedAttempt`  | Does proposedAttempt use essentially the same approach as previousAttempt for objective? |
-| [`step-complete`](step-complete/README.md)         | `stepComplete`     | Does evidence establish that condition has been met?                                     |
-| [`failure-kind`](failure-kind/README.md)           | `failureKind`      | Which supplied category best describes the observed failure?                             |
-| [`instruction-fit`](instruction-fit/README.md)     | `instructionFit`   | Does the explicit scope of instruction cover task and context?                           |
-
-## Customer support
-
-| Recipe                                                   | Function             | Decision                                                                     |
-| -------------------------------------------------------- | -------------------- | ---------------------------------------------------------------------------- |
-| [`issue-impact`](issue-impact/README.md)                 | `issueImpact`        | What practical impact does message explicitly describe?                      |
-| [`attempted-step`](attempted-step/README.md)             | `attemptedStep`      | Does conversation establish whether the customer already performed step?     |
-| [`workaround-fit`](workaround-fit/README.md)             | `workaroundFit`      | Can workaround address issue without violating constraints?                  |
-| [`ticket-match`](ticket-match/README.md)                 | `ticketMatch`        | Do firstTicket and secondTicket describe the same underlying reported issue? |
-| [`incident-match`](incident-match/README.md)             | `incidentMatch`      | Which supplied incident is supported as a match for ticket?                  |
-| [`troubleshooting-fit`](troubleshooting-fit/README.md)   | `troubleshootingFit` | Does procedure address symptoms under the described circumstances?           |
-| [`frustration-signal`](frustration-signal/README.md)     | `frustrationSignal`  | Does message express frustration or dissatisfaction in its wording?          |
-| [`urgency-signal`](urgency-signal/README.md)             | `urgencySignal`      | Does message explicitly request urgent attention?                            |
-| [`feedback-kind`](feedback-kind/README.md)               | `feedbackKind`       | What is the primary kind of feedback in message?                             |
-| [`reply-template-match`](reply-template-match/README.md) | `replyTemplateMatch` | Which supplied approved template applies to request and context?             |
-
-## Memory
-
-| Recipe                                         | Function         | Decision                                                                                   |
-| ---------------------------------------------- | ---------------- | ------------------------------------------------------------------------------------------ |
-| [`memory-value`](memory-value/README.md)       | `memoryValue`    | How useful is fact for future work under purpose?                                          |
-| [`memory-scope`](memory-scope/README.md)       | `memoryScope`    | What is the narrowest explicitly supported scope of fact in context?                       |
-| [`memory-relation`](memory-relation/README.md) | `memoryRelation` | How does newFact relate to existingMemory?                                                 |
-| [`preference-kind`](preference-kind/README.md) | `preferenceKind` | Does statement express an ongoing preference, a factual assertion, or a temporary request? |
-| [`fact-stability`](fact-stability/README.md)   | `factStability`  | Is fact about an enduring or historical attribute, or a state that is expected to change?  |
-
-## Knowledge maintenance
-
-| Recipe                                                 | Function             | Decision                                                                                                |
-| ------------------------------------------------------ | -------------------- | ------------------------------------------------------------------------------------------------------- |
-| [`document-role`](document-role/README.md)             | `documentRole`       | What is the primary purpose of document?                                                                |
-| [`audience-fit`](audience-fit/README.md)               | `audienceFit`        | Does the level of explanation in document fit the knowledge and needs explicitly described in audience? |
-| [`change-meaning`](change-meaning/README.md)           | `changeMeaning`      | Does the revision from before to after change material meaning, conditions, or obligations?             |
-| [`answer-invalidation`](answer-invalidation/README.md) | `answerInvalidation` | Does updatedEvidence still support the entire claim that was based on previousEvidence?                 |
-| [`field-select`](field-select/README.md)               | `fieldSelect`        | Which supplied candidate is the value of field in document?                                             |
-
-## Shared options and behavior
-
-- Pass `{ client, model, signal }` as an optional second argument to any recipe. The default client reads `TYPESAFE_API_KEY` from the process environment.
-- Recipes that accept `minConfidence` default it to `0.8`. Rerank uses `minRelevance`, defaulting to `0.5`. Each guide explains which outcomes require review and how individual checks affect the overall decision.
-- `ready` describes confidence in the assessment. Inspect the verdict too: a ready result can describe a conflict, missing information, or an unsuitable candidate.
-- Candidate selectors return `selection` only for a ready match. `suggestedSelection` preserves a low-confidence suggestion. Candidate probabilities use your supplied IDs; no candidate match and ambiguity are separate outcomes.
-- Item checks preserve each item's ID, verdict, confidence, and status. The coverage and tone recipes also provide `allAnswered`, `allPreserved`, or `allPassed` as appropriate.
-- Model and token usage accompany every result. Inputs and model responses are validated with Zod 4. Invalid input, malformed answers, and provider failures throw.
-- Shared `{ id, text }` lists accept 1 to 50 items with unique non-empty IDs. Route accepts up to 254 routes; rerank and verify accept up to 100 items. Each guide documents its input limits. Provider context limits may require smaller inputs; content is not silently truncated.
-
-## Reuse and side effects
-
-Recipes share small helpers for choices, candidate selection, and item checks. Rerank uses independent yes/no relevance scores. Each recipe owns its question and decision rules. `citation-match` composes the public `verify` function; its guide and catalog `uses` field name that dependency.
-
-Each current recipe makes one logical Jev request per live invocation. Batch checks place their questions in that request. SDK retries can add transport attempts. The recipes return decisions without executing application actions. The separate support example makes up to six logical requests and can stop early.
-
-## Examples and limits
-
-Every `demo.json` includes input and a hand-authored response. These examples illustrate behavior; they are not model accuracy results. Use `example <recipe>` to obtain editable input and `demo <recipe>` to inspect an offline illustration when desired.
-
-Application code owns exact arithmetic, dates, identifiers, access controls, consent, and storage. Recipe guides describe the limits of each semantic decision. Larger applications combine the recipes in caller code; see [Cool projects](../README.md#cool-projects).