jev-recipes 0.2.0 → 0.3.0

package/recipes/memory-scope/README.md

@@ -1,50 +0,0 @@
-# Identify memory scope
-
-What is the narrowest explicitly supported scope of fact in context? Do not generalize a one-off instruction into a lasting user preference.
-
-```ts
-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.status, result.verdict);
-```
-
-## Input
-
-| Field           | Accepts                                      |
-| --------------- | -------------------------------------------- |
-| `fact`          | Non-empty text                               |
-| `context`       | Non-empty text                               |
-| `minConfidence` | Optional number from 0 to 1; defaults to 0.8 |
-
-See [shared options and behavior](../README.md#shared-options-and-behavior) for client configuration, validation, and errors.
-
-## Result
-
-| Verdict   | Meaning                                                                   |
-| --------- | ------------------------------------------------------------------------- |
-| `user`    | The fact explicitly applies to the user across projects or tasks.         |
-| `project` | The fact applies to the identified project across its tasks.              |
-| `task`    | The fact applies to the current task only.                                |
-| `session` | The fact applies to this conversation session across its immediate tasks. |
-| `unclear` | The intended scope is not established.                                    |
-
-The result includes `verdict`, `confidence`, and all choice `probabilities`. `unclear` always requires review, even at high confidence. Other verdicts can be ready, including negative assessments.
-
-Results include model and token usage. Decisions below `minConfidence` require review. Inspect the outcome as well as the status.
-
-## Reuse and calls
-
-Uses the shared choice helper for the Jev call and response parsing. This folder owns its question, verdict criteria, and review policy. A live invocation makes one logical Jev request; SDK retries can add transport attempts.
-
-## Limits
-
-Identifies semantic scope. It does not identify a storage tenant, establish consent, or persist a memory.
-
-## Example input
-
-[demo.json](demo.json) contains editable input and a hand-authored response. After installing `jev-recipes`, `npx jev-recipes demo memory-scope` shows the result offline. The fixture is an illustration, not an accuracy measurement. `npx jev-recipes describe memory-scope` shows the input and result schemas.

package/recipes/memory-value/README.md

@@ -1,50 +0,0 @@
-# Assess a candidate memory
-
-How useful is fact for future work under purpose? Distinguish lasting relevance from a current-task detail. Use the supplied purpose rather than assuming every personal fact is worth retaining.
-
-```ts
-import { memoryValue } from 'jev-recipes/memory-value';
-
-const result = await memoryValue({
-  fact: 'The user prefers short, direct support replies.',
-  purpose: 'Help the user draft customer support replies across sessions.',
-});
-
-console.log(result.status, result.verdict);
-```
-
-## Input
-
-| Field           | Accepts                                      |
-| --------------- | -------------------------------------------- |
-| `fact`          | Non-empty text                               |
-| `purpose`       | Non-empty text                               |
-| `context`       | Optional non-empty text                      |
-| `minConfidence` | Optional number from 0 to 1; defaults to 0.8 |
-
-See [shared options and behavior](../README.md#shared-options-and-behavior) for client configuration, validation, and errors.
-
-## Result
-
-| Verdict         | Meaning                                                                       |
-| --------------- | ----------------------------------------------------------------------------- |
-| `ongoing_value` | The fact has a clear recurring use for the supplied purpose beyond this task. |
-| `task_only`     | The fact helps the current task but has no established recurring use.         |
-| `incidental`    | The fact has no clear use for the supplied purpose.                           |
-| `unclear`       | Its future usefulness cannot be established.                                  |
-
-The result includes `verdict`, `confidence`, and all choice `probabilities`. `unclear` always requires review, even at high confidence. Other verdicts can be ready, including negative assessments.
-
-Results include model and token usage. Decisions below `minConfidence` require review. Inspect the outcome as well as the status.
-
-## Reuse and calls
-
-Uses the shared choice helper for the Jev call and response parsing. This folder owns its question, verdict criteria, and review policy. A live invocation makes one logical Jev request; SDK retries can add transport attempts.
-
-## Limits
-
-Assesses usefulness only. Storage consent, sensitive-data policy, retention, and deletion must be enforced separately.
-
-## Example input
-
-[demo.json](demo.json) contains editable input and a hand-authored response. After installing `jev-recipes`, `npx jev-recipes demo memory-value` shows the result offline. The fixture is an illustration, not an accuracy measurement. `npx jev-recipes describe memory-value` shows the input and result schemas.

package/recipes/passage-duplicate/README.md

@@ -1,49 +0,0 @@
-# Compare passages for duplication
-
-How much material information do firstPassage and secondPassage share? Different wording can express the same information. Shared subject matter alone does not make a duplicate.
-
-```ts
-import { passageDuplicate } from 'jev-recipes/passage-duplicate';
-
-const result = await passageDuplicate({
-  firstPassage: 'Select Forgot password to receive a reset email.',
-  secondPassage: 'Use Forgot password and we will email a reset link.',
-});
-
-console.log(result.status, result.verdict);
-```
-
-## Input
-
-| Field           | Accepts                                      |
-| --------------- | -------------------------------------------- |
-| `firstPassage`  | Non-empty text                               |
-| `secondPassage` | Non-empty text                               |
-| `minConfidence` | Optional number from 0 to 1; defaults to 0.8 |
-
-See [shared options and behavior](../README.md#shared-options-and-behavior) for client configuration, validation, and errors.
-
-## Result
-
-| Verdict       | Meaning                                                                   |
-| ------------- | ------------------------------------------------------------------------- |
-| `duplicate`   | Both passages convey substantially the same material information.         |
-| `overlapping` | They share material information but at least one adds meaningful details. |
-| `distinct`    | They convey materially different information.                             |
-| `unclear`     | The meaning cannot be compared reliably.                                  |
-
-The result includes `verdict`, `confidence`, and all choice `probabilities`. `unclear` always requires review, even at high confidence. Other verdicts can be ready, including negative assessments.
-
-Results include model and token usage. Decisions below `minConfidence` require review. Inspect the outcome as well as the status.
-
-## Reuse and calls
-
-Uses the shared choice helper for the Jev call and response parsing. This folder owns its question, verdict criteria, and review policy. A live invocation makes one logical Jev request; SDK retries can add transport attempts.
-
-## Limits
-
-Compares a supplied pair. It does not search a corpus, cluster documents, or remove content.
-
-## Example input
-
-[demo.json](demo.json) contains editable input and a hand-authored response. After installing `jev-recipes`, `npx jev-recipes demo passage-duplicate` shows the result offline. The fixture is an illustration, not an accuracy measurement. `npx jev-recipes describe passage-duplicate` shows the input and result schemas.

package/recipes/preference-kind/README.md

@@ -1,48 +0,0 @@
-# Identify a stated preference
-
-Does statement express an ongoing preference, a factual assertion, or a temporary request? Do not treat a task-specific instruction as a lasting preference without evidence of scope.
-
-```ts
-import { preferenceKind } from 'jev-recipes/preference-kind';
-
-const result = await preferenceKind({
-  statement: 'For this reply, please use bullet points.',
-});
-
-console.log(result.status, result.verdict);
-```
-
-## Input
-
-| Field           | Accepts                                      |
-| --------------- | -------------------------------------------- |
-| `statement`     | Non-empty text                               |
-| `context`       | Optional non-empty text                      |
-| `minConfidence` | Optional number from 0 to 1; defaults to 0.8 |
-
-See [shared options and behavior](../README.md#shared-options-and-behavior) for client configuration, validation, and errors.
-
-## Result
-
-| Verdict             | Meaning                                                                                              |
-| ------------------- | ---------------------------------------------------------------------------------------------------- |
-| `preference`        | The statement expresses an ongoing choice or preferred way of working.                               |
-| `fact`              | The statement asserts information without expressing a preference or requesting an action.           |
-| `temporary_request` | The statement asks for something in the current situation without establishing a lasting preference. |
-| `unclear`           | The intended kind cannot be established.                                                             |
-
-The result includes `verdict`, `confidence`, and all choice `probabilities`. `unclear` always requires review, even at high confidence. Other verdicts can be ready, including negative assessments.
-
-Results include model and token usage. Decisions below `minConfidence` require review. Inspect the outcome as well as the status.
-
-## Reuse and calls
-
-Uses the shared choice helper for the Jev call and response parsing. This folder owns its question, verdict criteria, and review policy. A live invocation makes one logical Jev request; SDK retries can add transport attempts.
-
-## Limits
-
-Classifies a statement. It does not infer unexpressed preferences or grant permission to store personal information.
-
-## Example input
-
-[demo.json](demo.json) contains editable input and a hand-authored response. After installing `jev-recipes`, `npx jev-recipes demo preference-kind` shows the result offline. The fixture is an illustration, not an accuracy measurement. `npx jev-recipes describe preference-kind` shows the input and result schemas.

package/recipes/promise-check/README.md

@@ -1,48 +0,0 @@
-# Check reply commitments
-
-Does reply promise actions or outcomes beyond allowedCommitments? A conditional possibility is not a guarantee. Judge the whole reply; one unsupported promise is enough.
-
-```ts
-import { promiseCheck } from 'jev-recipes/promise-check';
-
-const result = await promiseCheck({
-  reply: 'Your refund is guaranteed.',
-  allowedCommitments: 'We may promise to review a refund request. We cannot promise approval.',
-});
-
-console.log(result.status, result.verdict);
-```
-
-## Input
-
-| Field                | Accepts                                      |
-| -------------------- | -------------------------------------------- |
-| `reply`              | Non-empty text                               |
-| `allowedCommitments` | Non-empty text                               |
-| `minConfidence`      | Optional number from 0 to 1; defaults to 0.8 |
-
-See [shared options and behavior](../README.md#shared-options-and-behavior) for client configuration, validation, and errors.
-
-## Result
-
-| Verdict              | Meaning                                                                                   |
-| -------------------- | ----------------------------------------------------------------------------------------- |
-| `within_commitments` | Every promise is permitted by the supplied commitments, or the reply contains no promise. |
-| `unsupported`        | At least one promise exceeds or contradicts the supplied commitments.                     |
-| `unclear`            | The wording or allowed commitments leave a promise ambiguous.                             |
-
-The result includes `verdict`, `confidence`, and all choice `probabilities`. `unclear` always requires review, even at high confidence. Other verdicts can be ready, including negative assessments.
-
-Results include model and token usage. Decisions below `minConfidence` require review. Inspect the outcome as well as the status.
-
-## Reuse and calls
-
-Uses the shared choice helper for the Jev call and response parsing. This folder owns its question, verdict criteria, and review policy. A live invocation makes one logical Jev request; SDK retries can add transport attempts.
-
-## Limits
-
-Reviews expressed promises. It does not approve refunds, establish contractual obligations, or execute actions.
-
-## Example input
-
-[demo.json](demo.json) contains editable input and a hand-authored response. After installing `jev-recipes`, `npx jev-recipes demo promise-check` shows the result offline. The fixture is an illustration, not an accuracy measurement. `npx jev-recipes describe promise-check` shows the input and result schemas.

package/recipes/query-equivalence/README.md

@@ -1,50 +0,0 @@
-# Compare question meaning
-
-Do firstQuestion and secondQuestion request the same information under the same stated conditions? Shared vocabulary or topic alone is not equivalence.
-
-```ts
-import { queryEquivalence } from 'jev-recipes/query-equivalence';
-
-const result = await queryEquivalence({
-  firstQuestion: 'How can I reset my password?',
-  secondQuestion: 'What should I do if I forgot my password?',
-});
-
-console.log(result.status, result.verdict);
-```
-
-## Input
-
-| Field            | Accepts                                      |
-| ---------------- | -------------------------------------------- |
-| `firstQuestion`  | Non-empty text                               |
-| `secondQuestion` | Non-empty text                               |
-| `context`        | Optional non-empty text                      |
-| `minConfidence`  | Optional number from 0 to 1; defaults to 0.8 |
-
-See [shared options and behavior](../README.md#shared-options-and-behavior) for client configuration, validation, and errors.
-
-## Result
-
-| Verdict      | Meaning                                                                    |
-| ------------ | -------------------------------------------------------------------------- |
-| `equivalent` | Both questions request the same information with compatible conditions.    |
-| `related`    | They share a topic but differ in a material information need or condition. |
-| `different`  | They request different subjects or unrelated information.                  |
-| `unclear`    | The intended meanings cannot be resolved.                                  |
-
-The result includes `verdict`, `confidence`, and all choice `probabilities`. `unclear` always requires review, even at high confidence. Other verdicts can be ready, including negative assessments.
-
-Results include model and token usage. Decisions below `minConfidence` require review. Inspect the outcome as well as the status.
-
-## Reuse and calls
-
-Uses the shared choice helper for the Jev call and response parsing. This folder owns its question, verdict criteria, and review policy. A live invocation makes one logical Jev request; SDK retries can add transport attempts.
-
-## Limits
-
-Compares supplied questions. It does not rewrite them or establish that an existing answer is still valid.
-
-## Example input
-
-[demo.json](demo.json) contains editable input and a hand-authored response. After installing `jev-recipes`, `npx jev-recipes demo query-equivalence` shows the result offline. The fixture is an illustration, not an accuracy measurement. `npx jev-recipes describe query-equivalence` shows the input and result schemas.

package/recipes/query-specificity/README.md

@@ -1,47 +0,0 @@
-# Check question specificity
-
-Does question, interpreted with context, identify a focused information need? A broad but clear request differs from an ambiguous reference or missing subject.
-
-```ts
-import { querySpecificity } from 'jev-recipes/query-specificity';
-
-const result = await querySpecificity({
-  question: 'Tell me everything about software.',
-});
-
-console.log(result.status, result.verdict);
-```
-
-## Input
-
-| Field           | Accepts                                      |
-| --------------- | -------------------------------------------- |
-| `question`      | Non-empty text                               |
-| `context`       | Optional non-empty text                      |
-| `minConfidence` | Optional number from 0 to 1; defaults to 0.8 |
-
-See [shared options and behavior](../README.md#shared-options-and-behavior) for client configuration, validation, and errors.
-
-## Result
-
-| Verdict     | Meaning                                                                                 |
-| ----------- | --------------------------------------------------------------------------------------- |
-| `specific`  | The subject and requested information are sufficiently clear and focused.               |
-| `too_broad` | The intended subject is clear but the request spans an open-ended range of information. |
-| `ambiguous` | The subject, reference, or intended information has multiple unresolved meanings.       |
-
-The result includes `verdict`, `confidence`, and all choice `probabilities`. `ambiguous` always requires review, even at high confidence. Other verdicts can be ready, including negative assessments.
-
-Results include model and token usage. Decisions below `minConfidence` require review. Inspect the outcome as well as the status.
-
-## Reuse and calls
-
-Uses the shared choice helper for the Jev call and response parsing. This folder owns its question, verdict criteria, and review policy. A live invocation makes one logical Jev request; SDK retries can add transport attempts.
-
-## Limits
-
-Assesses focus only. Use clarify when the application has explicit required fields to check.
-
-## Example input
-
-[demo.json](demo.json) contains editable input and a hand-authored response. After installing `jev-recipes`, `npx jev-recipes demo query-specificity` shows the result offline. The fixture is an illustration, not an accuracy measurement. `npx jev-recipes describe query-specificity` shows the input and result schemas.

package/recipes/reference-resolve/README.md

@@ -1,54 +0,0 @@
-# Resolve a reference
-
-Which supplied candidate does reference refer to in message and context? Resolve only this reference. Do not invent an entity or break a genuine tie.
-
-```ts
-import { referenceResolve } from 'jev-recipes/reference-resolve';
-
-const result = await referenceResolve({
-  message: 'Please cancel the hardware order, not my subscription.',
-  reference: 'the hardware order',
-  candidates: [
-    {
-      id: 'order',
-      text: 'A pending hardware order.',
-    },
-    {
-      id: 'subscription',
-      text: 'An active monthly storage subscription.',
-    },
-  ],
-});
-
-console.log(result.status, result.selection);
-```
-
-## Input
-
-| Field           | Accepts                                      |
-| --------------- | -------------------------------------------- |
-| `message`       | Non-empty text                               |
-| `reference`     | Non-empty text                               |
-| `candidates`    | 1 to 50 `{ id, text }` items with unique IDs |
-| `context`       | Optional non-empty text                      |
-| `minConfidence` | Optional number from 0 to 1; defaults to 0.8 |
-
-See [shared options and behavior](../README.md#shared-options-and-behavior) for client configuration, validation, and errors.
-
-## Result
-
-`verdict` is `matched`, `none`, or `ambiguous`. A confident match returns the original item ID in `selection`. A low-confidence match keeps that ID only in `suggestedSelection`. `none` returns a null selection and can be `ready`; `ambiguous` always requires review. Probabilities are grouped under `candidates` by your original IDs, plus `none` and `ambiguous`.
-
-Results include model and token usage. Decisions below `minConfidence` require review. Inspect the outcome as well as the status.
-
-## Reuse and calls
-
-Uses the shared candidate-selection helper. This folder owns its selection question and input schema. A live invocation makes one logical Jev request; SDK retries can add transport attempts.
-
-## Limits
-
-Resolves a supplied reference among candidates. It does not extract references, verify identity, or authorize changes.
-
-## Example input
-
-[demo.json](demo.json) contains editable input and a hand-authored response. After installing `jev-recipes`, `npx jev-recipes demo reference-resolve` shows the result offline. The fixture is an illustration, not an accuracy measurement. `npx jev-recipes describe reference-resolve` shows the input and result schemas.

package/recipes/repeated-attempt/README.md

@@ -1,50 +0,0 @@
-# Compare attempted approaches
-
-Does proposedAttempt use essentially the same approach as previousAttempt for objective? Rewording the same query without a material strategy change counts as the same approach.
-
-```ts
-import { repeatedAttempt } from 'jev-recipes/repeated-attempt';
-
-const result = await repeatedAttempt({
-  objective: 'Find reset documentation.',
-  previousAttempt: 'Search the help center for password reset.',
-  proposedAttempt: 'Search the same help center for reset password.',
-});
-
-console.log(result.status, result.verdict);
-```
-
-## Input
-
-| Field             | Accepts                                      |
-| ----------------- | -------------------------------------------- |
-| `objective`       | Non-empty text                               |
-| `previousAttempt` | Non-empty text                               |
-| `proposedAttempt` | Non-empty text                               |
-| `minConfidence`   | Optional number from 0 to 1; defaults to 0.8 |
-
-See [shared options and behavior](../README.md#shared-options-and-behavior) for client configuration, validation, and errors.
-
-## Result
-
-| Verdict              | Meaning                                                                    |
-| -------------------- | -------------------------------------------------------------------------- |
-| `same_approach`      | The proposed attempt repeats the material method and relevant assumptions. |
-| `different_approach` | The proposed attempt changes a material method, source, or assumption.     |
-| `unclear`            | The attempts are not described precisely enough to compare.                |
-
-The result includes `verdict`, `confidence`, and all choice `probabilities`. `unclear` always requires review, even at high confidence. Other verdicts can be ready, including negative assessments.
-
-Results include model and token usage. Decisions below `minConfidence` require review. Inspect the outcome as well as the status.
-
-## Reuse and calls
-
-Uses the shared choice helper for the Jev call and response parsing. This folder owns its question, verdict criteria, and review policy. A live invocation makes one logical Jev request; SDK retries can add transport attempts.
-
-## Limits
-
-Compares two attempts only. Counting repeats, deciding whether a retry is justified, and stopping loops belong in application code.
-
-## Example input
-
-[demo.json](demo.json) contains editable input and a hand-authored response. After installing `jev-recipes`, `npx jev-recipes demo repeated-attempt` shows the result offline. The fixture is an illustration, not an accuracy measurement. `npx jev-recipes describe repeated-attempt` shows the input and result schemas.

package/recipes/reply-template-match/README.md

@@ -1,52 +0,0 @@
-# Select a reply template
-
-Which supplied approved template applies to request and context? Match any stated template conditions and do not select a template that promises unsupported actions.
-
-```ts
-import { replyTemplateMatch } from 'jev-recipes/reply-template-match';
-
-const result = await replyTemplateMatch({
-  request: 'How do I reset my password?',
-  templates: [
-    {
-      id: 'reset',
-      text: 'For password reset requests: Select Forgot password on the sign-in page.',
-    },
-    {
-      id: 'invoice',
-      text: 'For invoice requests: Open Billing and select Download invoice.',
-    },
-  ],
-});
-
-console.log(result.status, result.selection);
-```
-
-## Input
-
-| Field           | Accepts                                      |
-| --------------- | -------------------------------------------- |
-| `request`       | Non-empty text                               |
-| `templates`     | 1 to 50 `{ id, text }` items with unique IDs |
-| `context`       | Optional non-empty text                      |
-| `minConfidence` | Optional number from 0 to 1; defaults to 0.8 |
-
-See [shared options and behavior](../README.md#shared-options-and-behavior) for client configuration, validation, and errors.
-
-## Result
-
-`verdict` is `matched`, `none`, or `ambiguous`. A confident match returns the original item ID in `selection`. A low-confidence match keeps that ID only in `suggestedSelection`. `none` returns a null selection and can be `ready`; `ambiguous` always requires review. Probabilities are grouped under `candidates` by your original IDs, plus `none` and `ambiguous`.
-
-Results include model and token usage. Decisions below `minConfidence` require review. Inspect the outcome as well as the status.
-
-## Reuse and calls
-
-Uses the shared candidate-selection helper. This folder owns its selection question and input schema. A live invocation makes one logical Jev request; SDK retries can add transport attempts.
-
-## Limits
-
-Selects a supplied template. It does not fill placeholders, approve its content, personalize it, or send a response.
-
-## Example input
-
-[demo.json](demo.json) contains editable input and a hand-authored response. After installing `jev-recipes`, `npx jev-recipes demo reply-template-match` shows the result offline. The fixture is an illustration, not an accuracy measurement. `npx jev-recipes describe reply-template-match` shows the input and result schemas.

package/recipes/rerank/README.md

@@ -1,55 +0,0 @@
-# Rerank evidence
-
-Select supplied passages by how directly they help answer a query, then order them by relevance.
-
-```ts
-import { rerank } from 'jev-recipes/rerank';
-
-const result = await rerank({
-  query: 'How do I reset my password?',
-  items: [
-    {
-      id: 'billing',
-      text: 'Invoices appear on the Billing page.',
-    },
-    {
-      id: 'reset',
-      text: 'Select Forgot password to receive a reset link.',
-    },
-  ],
-  topK: 1,
-});
-
-console.log(result.items);
-```
-
-## Input
-
-| Field          | Accepts                                                                    |
-| -------------- | -------------------------------------------------------------------------- |
-| `query`        | Non-empty text describing the information needed                           |
-| `items`        | 1 to 100 `{ id, text }` items with unique non-empty IDs and non-empty text |
-| `topK`         | Optional integer from 1 to 100; defaults to 5                              |
-| `minRelevance` | Optional number from 0 to 1; defaults to 0.5                               |
-
-See [shared options and behavior](../README.md#shared-options-and-behavior) for client configuration, validation, and errors. Types are inferred from this folder's Zod 4 schemas.
-
-## Result
-
-`items` contains passages at or above `minRelevance`, ordered from highest relevance to lowest and limited to `topK`. Each item keeps its ID and text and adds `relevance`. Equal values preserve input order. The input array is not changed.
-
-`status` is `ready` when at least one passage qualifies, otherwise `review`. `evaluated` reports the number of supplied items. Relevance comes from independent yes/no questions, so values do not sum to 1 and have no separate confidence field.
-
-The result includes model and token usage. Inspect the outcome as well as its review status.
-
-## Reuse and calls
-
-Uses shared input preparation, instruction handling, the SDK client, and yes/no answer parsing. This folder owns the relevance question, filtering, and ordering. All item questions are sent in one request. A live invocation makes one logical Jev request; SDK retries can add transport attempts.
-
-## Limits
-
-Relevance does not establish that a passage is true or sufficient to answer the entire query. Use answerability to assess the selected evidence. This recipe does not retrieve documents or generate an answer.
-
-## Example input
-
-[demo.json](demo.json) contains editable input and a hand-authored response. After installing `jev-recipes`, `npx jev-recipes demo rerank` shows an offline illustration, not an accuracy measurement. Use `npx jev-recipes describe rerank` to inspect the input and result schemas.

package/recipes/resolution-check/README.md

@@ -1,49 +0,0 @@
-# Check reported resolution
-
-Does message establish that the customer reports issue as resolved? Courtesy or thanks without a resolution statement is not enough. Assess the reported state, not the actual system state.
-
-```ts
-import { resolutionCheck } from 'jev-recipes/resolution-check';
-
-const result = await resolutionCheck({
-  issue: 'The customer cannot sign in.',
-  message: 'The reset worked. I can sign in now.',
-});
-
-console.log(result.status, result.verdict);
-```
-
-## Input
-
-| Field           | Accepts                                      |
-| --------------- | -------------------------------------------- |
-| `issue`         | Non-empty text                               |
-| `message`       | Non-empty text                               |
-| `context`       | Optional non-empty text                      |
-| `minConfidence` | Optional number from 0 to 1; defaults to 0.8 |
-
-See [shared options and behavior](../README.md#shared-options-and-behavior) for client configuration, validation, and errors.
-
-## Result
-
-| Verdict      | Meaning                                                                             |
-| ------------ | ----------------------------------------------------------------------------------- |
-| `resolved`   | The customer clearly reports this issue is solved or the desired outcome now works. |
-| `unresolved` | The customer clearly reports this issue persists or the attempted fix failed.       |
-| `unclear`    | The message does not establish whether this issue is resolved.                      |
-
-The result includes `verdict`, `confidence`, and all choice `probabilities`. `unclear` always requires review, even at high confidence. Other verdicts can be ready, including negative assessments.
-
-Results include model and token usage. Decisions below `minConfidence` require review. Inspect the outcome as well as the status.
-
-## Reuse and calls
-
-Uses the shared choice helper for the Jev call and response parsing. This folder owns its question, verdict criteria, and review policy. A live invocation makes one logical Jev request; SDK retries can add transport attempts.
-
-## Limits
-
-Interprets the customer report. It does not verify the system state, close a ticket, or treat courtesy alone as resolution.
-
-## Example input
-
-[demo.json](demo.json) contains editable input and a hand-authored response. After installing `jev-recipes`, `npx jev-recipes demo resolution-check` shows the result offline. The fixture is an illustration, not an accuracy measurement. `npx jev-recipes describe resolution-check` shows the input and result schemas.

package/recipes/response-needed/README.md

@@ -1,48 +0,0 @@
-# Check whether a reply is needed
-
-Does message require a substantive reply in context? A question, request, correction needing follow-through, or unresolved issue requires a reply. A simple closing acknowledgment does not.
-
-```ts
-import { responseNeeded } from 'jev-recipes/response-needed';
-
-const result = await responseNeeded({
-  message: 'Thanks, that solved it!',
-  context: 'The assistant provided password reset instructions.',
-});
-
-console.log(result.status, result.verdict);
-```
-
-## Input
-
-| Field           | Accepts                                      |
-| --------------- | -------------------------------------------- |
-| `message`       | Non-empty text                               |
-| `context`       | Optional non-empty text                      |
-| `minConfidence` | Optional number from 0 to 1; defaults to 0.8 |
-
-See [shared options and behavior](../README.md#shared-options-and-behavior) for client configuration, validation, and errors.
-
-## Result
-
-| Verdict           | Meaning                                                                        |
-| ----------------- | ------------------------------------------------------------------------------ |
-| `reply_needed`    | The message requests or requires substantive follow-through.                   |
-| `no_reply_needed` | The message closes or acknowledges the exchange without an unresolved request. |
-| `unclear`         | The supplied context does not establish whether a response is expected.        |
-
-The result includes `verdict`, `confidence`, and all choice `probabilities`. `unclear` always requires review, even at high confidence. Other verdicts can be ready, including negative assessments.
-
-Results include model and token usage. Decisions below `minConfidence` require review. Inspect the outcome as well as the status.
-
-## Reuse and calls
-
-Uses the shared choice helper for the Jev call and response parsing. This folder owns its question, verdict criteria, and review policy. A live invocation makes one logical Jev request; SDK retries can add transport attempts.
-
-## Limits
-
-Assesses conversational need. Channel-specific response obligations and customer service policies remain application rules.
-
-## Example input
-
-[demo.json](demo.json) contains editable input and a hand-authored response. After installing `jev-recipes`, `npx jev-recipes demo response-needed` shows the result offline. The fixture is an illustration, not an accuracy measurement. `npx jev-recipes describe response-needed` shows the input and result schemas.