jev-recipes 0.2.0 → 0.4.0

package/recipes/change-meaning/README.md

@@ -1,49 +0,0 @@
-# Assess a text revision
-
-Does the revision from before to after change material meaning, conditions, or obligations? Rephrasing that preserves the same meaning is editorial only.
-
-```ts
-import { changeMeaning } from 'jev-recipes/change-meaning';
-
-const result = await changeMeaning({
-  before: 'Guests may export reports.',
-  after: 'Only workspace owners may export reports.',
-});
-
-console.log(result.status, result.verdict);
-```
-
-## Input
-
-| Field           | Accepts                                      |
-| --------------- | -------------------------------------------- |
-| `before`        | Non-empty text                               |
-| `after`         | 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                                                                                               |
-| ----------------- | ----------------------------------------------------------------------------------------------------- |
-| `meaning_changed` | The revision changes a material fact, condition, instruction, or implication.                         |
-| `editorial_only`  | The revision preserves material meaning and changes only wording or presentation, or makes no change. |
-| `unclear`         | The material effect cannot be determined from the supplied text.                                      |
-
-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 passages. It does not parse a repository diff or perform exact numeric and date comparisons.
-
-## Example input
-
-[demo.json](demo.json) contains editable input and a hand-authored response. After installing `jev-recipes`, `npx jev-recipes demo change-meaning` shows the result offline. The fixture is an illustration, not an accuracy measurement. `npx jev-recipes describe change-meaning` shows the input and result schemas.

package/recipes/citation-match/README.md

@@ -1,51 +0,0 @@
-# Match claims to citations
-
-Find passages that support a supplied claim. Each passage is checked independently against the entire claim.
-
-```ts
-import { citationMatch } from 'jev-recipes/citation-match';
-
-const result = await citationMatch({
-  claim: 'Reset links expire after 30 minutes.',
-  passages: [
-    {
-      id: 'reset',
-      text: 'Password reset links expire after 30 minutes.',
-    },
-    {
-      id: 'billing',
-      text: 'Invoices are available on the Billing page.',
-    },
-  ],
-});
-
-console.log(result.status, result.passageIds);
-```
-
-## Input
-
-| Field           | Accepts                                      |
-| --------------- | -------------------------------------------- |
-| `claim`         | Non-empty text                               |
-| `passages`      | 1 to 50 `{ id, text }` items with unique IDs |
-| `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
-
-`passageIds` contains every passage that independently supports the entire claim at or above the confidence threshold. `checks` preserves the verification result for each passage. If any passage qualifies, overall status is `ready`, even if other checks need review. With no qualifying passage, uncertainty produces `review`; otherwise a confident no-match returns `ready` with an empty list.
-
-Results include model and token usage. Decisions below `minConfidence` require review. Inspect the outcome as well as the status.
-
-## Reuse and calls
-
-Uses the public [`verify`](../verify/README.md) recipe once, with one claim/evidence pair per passage. It adds selection of confidently supported passage IDs. A live invocation makes one logical Jev request; SDK retries can add transport attempts. All item questions are sent in that request.
-
-## Limits
-
-Returns passages that independently support the entire claim. Joint support across several individually incomplete passages is not assessed.
-
-## Example input
-
-[demo.json](demo.json) contains editable input and a hand-authored response. After installing `jev-recipes`, `npx jev-recipes demo citation-match` shows the result offline. The fixture is an illustration, not an accuracy measurement. `npx jev-recipes describe citation-match` shows the input and result schemas.

package/recipes/citation-needed/README.md

@@ -1,49 +0,0 @@
-# Check citation requirements
-
-Do citationRules require evidence for statement? Apply the supplied rules rather than an unstated citation policy.
-
-```ts
-import { citationNeeded } from 'jev-recipes/citation-needed';
-
-const result = await citationNeeded({
-  statement: 'Reset links expire after 30 minutes.',
-  citationRules:
-    'Cite documentation for claims about product behavior. Greetings need no citations.',
-});
-
-console.log(result.status, result.verdict);
-```
-
-## Input
-
-| Field           | Accepts                                      |
-| --------------- | -------------------------------------------- |
-| `statement`     | Non-empty text                               |
-| `citationRules` | 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                                                                                          |
-| ------------- | ------------------------------------------------------------------------------------------------ |
-| `needed`      | The statement falls within a category requiring citation under the supplied rules.               |
-| `unnecessary` | The supplied rules explicitly exempt this statement or clearly do not require a citation for it. |
-| `unclear`     | The rules or statement do not establish whether a citation is required.                          |
-
-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 a supplied citation policy; does not find sources or determine whether a statement is true.
-
-## Example input
-
-[demo.json](demo.json) contains editable input and a hand-authored response. After installing `jev-recipes`, `npx jev-recipes demo citation-needed` shows the result offline. The fixture is an illustration, not an accuracy measurement. `npx jev-recipes describe citation-needed` shows the input and result schemas.

package/recipes/clarify/README.md

@@ -1,61 +0,0 @@
-# Check required information
-
-Identify which supplied requirements are present, missing, or ambiguous in a request and its context.
-
-```ts
-import { clarify } from 'jev-recipes/clarify';
-
-const result = await clarify({
-  request: 'Please cancel it.',
-  context: 'The customer has a storage subscription and a pending hardware order.',
-  requirements: [
-    {
-      id: 'target',
-      description: 'Which product or order should be changed',
-    },
-    {
-      id: 'action',
-      description: 'What change the customer wants',
-    },
-  ],
-});
-
-console.log(result.canProceed);
-```
-
-## Input
-
-| Field           | Accepts                                                                                  |
-| --------------- | ---------------------------------------------------------------------------------------- |
-| `request`       | Non-empty text containing the request                                                    |
-| `context`       | Optional non-empty conversation context or application facts                             |
-| `requirements`  | 1 to 50 `{ id, description }` items with unique non-empty IDs and non-empty descriptions |
-| `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. Types are inferred from this folder's Zod 4 schemas.
-
-## Result
-
-| Verdict     | Meaning                                                                     |
-| ----------- | --------------------------------------------------------------------------- |
-| `present`   | The required information is explicit or unambiguously implied.              |
-| `missing`   | The required information is absent.                                         |
-| `ambiguous` | Relevant information has multiple plausible meanings or conflicting values. |
-
-`checks` preserves each requirement ID with its verdict, status, confidence, and probabilities. A check is ready when its confidence reaches `minConfidence`. Overall `status` is `review` if any check falls below the threshold.
-
-`canProceed` is true only when every check is ready and present. `missing` and `ambiguous` contain confidently classified requirement IDs. A confident ambiguity assessment can be ready while `canProceed` remains false. Low-confidence checks also block proceeding, even if both ID lists are empty.
-
-The result includes model and token usage. Inspect the outcome as well as its review status.
-
-## Reuse and calls
-
-Uses the shared item-check helper. This folder owns the requirement criteria, follow-up ID lists, and can-proceed decision. All requirement questions are sent in one request. A live invocation makes one logical Jev request; SDK retries can add transport attempts.
-
-## Limits
-
-Your application supplies the requirements and maps their IDs to follow-up questions. The recipe does not discover requirements, generate questions, validate identity, or enforce exact field formats.
-
-## Example input
-
-[demo.json](demo.json) contains editable input and a hand-authored response. After installing `jev-recipes`, `npx jev-recipes demo clarify` shows an offline illustration, not an accuracy measurement. Use `npx jev-recipes describe clarify` to inspect the input and result schemas.

package/recipes/confirmation-match/README.md

@@ -1,49 +0,0 @@
-# Interpret a confirmation
-
-Does response clearly agree to or reject this exact proposal? Do not treat politeness, acknowledgment, a question, or agreement to only part of the proposal as full agreement.
-
-```ts
-import { confirmationMatch } from 'jev-recipes/confirmation-match';
-
-const result = await confirmationMatch({
-  proposal: 'Cancel the storage subscription now.',
-  response: 'How much would I save?',
-});
-
-console.log(result.status, result.verdict);
-```
-
-## Input
-
-| Field           | Accepts                                      |
-| --------------- | -------------------------------------------- |
-| `proposal`      | Non-empty text                               |
-| `response`      | 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                                                                                |
-| --------- | -------------------------------------------------------------------------------------- |
-| `agrees`  | The response clearly agrees to this complete proposal.                                 |
-| `rejects` | The response clearly rejects this proposal.                                            |
-| `unclear` | The response is conditional, partial, ambiguous, unrelated, or only an acknowledgment. |
-
-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 language only. Approval identity, authority, scope, expiration, and action permissions remain application checks.
-
-## Example input
-
-[demo.json](demo.json) contains editable input and a hand-authored response. After installing `jev-recipes`, `npx jev-recipes demo confirmation-match` shows the result offline. The fixture is an illustration, not an accuracy measurement. `npx jev-recipes describe confirmation-match` shows the input and result schemas.

package/recipes/context-role/README.md

@@ -1,49 +0,0 @@
-# Identify a passage role
-
-What role does passage play in answering question? Classify its contribution without establishing whether its claims are true.
-
-```ts
-import { contextRole } from 'jev-recipes/context-role';
-
-const result = await contextRole({
-  question: 'How do I reset my password?',
-  passage: 'Passwords help protect access to accounts.',
-});
-
-console.log(result.status, result.verdict);
-```
-
-## Input
-
-| Field           | Accepts                                      |
-| --------------- | -------------------------------------------- |
-| `question`      | Non-empty text                               |
-| `passage`       | 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                                                                          |
-| ----------------- | -------------------------------------------------------------------------------- |
-| `direct_evidence` | The passage directly supplies information needed to answer the question.         |
-| `background`      | The passage helps interpret the topic but does not directly answer the question. |
-| `unrelated`       | The passage contributes neither an answer nor useful background.                 |
-| `unclear`         | Its relationship to the question 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 passage contribution. It does not rank sources or prove the answer is supported.
-
-## Example input
-
-[demo.json](demo.json) contains editable input and a hand-authored response. After installing `jev-recipes`, `npx jev-recipes demo context-role` shows the result offline. The fixture is an illustration, not an accuracy measurement. `npx jev-recipes describe context-role` shows the input and result schemas.

package/recipes/correction-target/README.md

@@ -1,52 +0,0 @@
-# Locate a correction target
-
-Which supplied field or statement is message correcting? Identify the target, not the replacement value. Use ambiguous when the message corrects multiple targets without a single primary target.
-
-```ts
-import { correctionTarget } from 'jev-recipes/correction-target';
-
-const result = await correctionTarget({
-  message: 'The billing email is finance@example.com, not support@example.com.',
-  targets: [
-    {
-      id: 'billing-email',
-      text: 'Billing email: support@example.com',
-    },
-    {
-      id: 'shipping-city',
-      text: 'Shipping city: Portland',
-    },
-  ],
-});
-
-console.log(result.status, result.selection);
-```
-
-## Input
-
-| Field           | Accepts                                      |
-| --------------- | -------------------------------------------- |
-| `message`       | Non-empty text                               |
-| `targets`       | 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 one correction target. It does not extract a replacement value or update a record.
-
-## Example input
-
-[demo.json](demo.json) contains editable input and a hand-authored response. After installing `jev-recipes`, `npx jev-recipes demo correction-target` shows the result offline. The fixture is an illustration, not an accuracy measurement. `npx jev-recipes describe correction-target` shows the input and result schemas.

package/recipes/document-role/README.md

@@ -1,51 +0,0 @@
-# Identify document purpose
-
-What is the primary purpose of document? Judge the actual content rather than a title alone. Choose unclear if several purposes are equally central.
-
-```ts
-import { documentRole } from 'jev-recipes/document-role';
-
-const result = await documentRole({
-  document:
-    'New in this release: workspace exports now include archived reports. Fixed an invoice download error.',
-});
-
-console.log(result.status, result.verdict);
-```
-
-## Input
-
-| Field           | Accepts                                      |
-| --------------- | -------------------------------------------- |
-| `document`      | 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                                                        |
-| ----------------- | -------------------------------------------------------------- |
-| `policy`          | Defines rules, permissions, requirements, or allowed behavior. |
-| `tutorial`        | Teaches a task through a guided sequence.                      |
-| `reference`       | Describes interfaces, features, or facts for lookup.           |
-| `troubleshooting` | Helps diagnose or resolve a described problem.                 |
-| `release_note`    | Describes changes in a release or update.                      |
-| `other`           | Has a clear purpose outside the listed roles.                  |
-| `unclear`         | The primary role 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
-
-Returns one primary role from the supplied text. It does not read files, split mixed documents, or create an index.
-
-## Example input
-
-[demo.json](demo.json) contains editable input and a hand-authored response. After installing `jev-recipes`, `npx jev-recipes demo document-role` shows the result offline. The fixture is an illustration, not an accuracy measurement. `npx jev-recipes describe document-role` shows the input and result schemas.

package/recipes/draft-compare/README.md

@@ -1,54 +0,0 @@
-# Compare two drafts
-
-Which draft better satisfies request under rubric? Evaluate only the supplied criteria. Treat presentation order as irrelevant and allow a tie or neither.
-
-```ts
-import { draftCompare } from 'jev-recipes/draft-compare';
-
-const result = await draftCompare({
-  request: 'Explain how to reset a password.',
-  firstDraft: 'Select Forgot password on the sign-in page.',
-  secondDraft: 'Contact billing to download an invoice.',
-  rubric: 'Prefer a direct answer to the requested task.',
-});
-
-console.log(result.status, result.verdict);
-```
-
-## Input
-
-| Field           | Accepts                                      |
-| --------------- | -------------------------------------------- |
-| `request`       | Non-empty text                               |
-| `firstDraft`    | Non-empty text                               |
-| `secondDraft`   | Non-empty text                               |
-| `rubric`        | 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                                                                       |
-| --------- | ----------------------------------------------------------------------------- |
-| `first`   | Only the first draft is suitable, or it clearly better satisfies the rubric.  |
-| `second`  | Only the second draft is suitable, or it clearly better satisfies the rubric. |
-| `tie`     | Both drafts are suitable and neither is meaningfully better under the rubric. |
-| `neither` | Neither draft satisfies the request and rubric.                               |
-| `unclear` | There is insufficient information to make the comparison.                     |
-
-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
-
-Makes a relative judgment against your rubric. A preferred draft can still contain unsupported facts.
-
-## Example input
-
-[demo.json](demo.json) contains editable input and a hand-authored response. After installing `jev-recipes`, `npx jev-recipes demo draft-compare` shows the result offline. The fixture is an illustration, not an accuracy measurement. `npx jev-recipes describe draft-compare` shows the input and result schemas.

package/recipes/evidence-conflict/README.md

@@ -1,51 +0,0 @@
-# Compare evidence for conflicts
-
-Do firstPassage and secondPassage give incompatible evidence relevant to question under the same conditions? Different scopes are not automatically contradictions.
-
-```ts
-import { evidenceConflict } from 'jev-recipes/evidence-conflict';
-
-const result = await evidenceConflict({
-  question: 'Can guests export reports?',
-  firstPassage: 'Guests can export reports.',
-  secondPassage: 'Guests cannot export reports.',
-});
-
-console.log(result.status, result.verdict);
-```
-
-## Input
-
-| Field           | Accepts                                      |
-| --------------- | -------------------------------------------- |
-| `firstPassage`  | Non-empty text                               |
-| `secondPassage` | Non-empty text                               |
-| `question`      | 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                                                                            |
-| ----------------- | ---------------------------------------------------------------------------------- |
-| `compatible`      | The passages address the same scope and can both be true.                          |
-| `conflicting`     | The passages address the same scope and make incompatible claims.                  |
-| `different_scope` | The apparent comparison concerns different subjects, circumstances, or conditions. |
-| `unclear`         | The scope or meaning cannot be resolved from the supplied evidence.                |
-
-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
-
-Does not decide which source is authoritative. Exact numbers, timestamps, and version ordering should be compared in code.
-
-## Example input
-
-[demo.json](demo.json) contains editable input and a hand-authored response. After installing `jev-recipes`, `npx jev-recipes demo evidence-conflict` shows the result offline. The fixture is an illustration, not an accuracy measurement. `npx jev-recipes describe evidence-conflict` shows the input and result schemas.

package/recipes/evidence-novelty/README.md

@@ -1,56 +0,0 @@
-# Check new evidence
-
-Does passage add material information relevant to question beyond existingEvidence? New information may conflict with existing evidence; novelty alone is not correctness.
-
-```ts
-import { evidenceNovelty } from 'jev-recipes/evidence-novelty';
-
-const result = await evidenceNovelty({
-  question: 'How do I reset my password and when does the link expire?',
-  passage: 'Reset links expire after 30 minutes.',
-  existingEvidence: [
-    {
-      id: 'steps',
-      text: 'Select Forgot password to receive a reset link.',
-    },
-  ],
-});
-
-console.log(result.status, result.verdict);
-```
-
-## Input
-
-| Field              | Accepts                                      |
-| ------------------ | -------------------------------------------- |
-| `passage`          | Non-empty text                               |
-| `existingEvidence` | 1 to 50 `{ id, text }` items with unique IDs |
-| `question`         | 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                                                                           |
-| --------------------- | --------------------------------------------------------------------------------- |
-| `adds_information`    | The passage adds a material relevant fact or distinction not already represented. |
-| `repeats_information` | It only repeats information already represented.                                  |
-| `irrelevant`          | It contributes no information relevant to the question.                           |
-| `unclear`             | Its contribution cannot be determined from the supplied material.                 |
-
-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 novelty within the supplied set. It does not establish correctness or decide when retrieval must stop.
-
-## Example input
-
-[demo.json](demo.json) contains editable input and a hand-authored response. After installing `jev-recipes`, `npx jev-recipes demo evidence-novelty` shows the result offline. The fixture is an illustration, not an accuracy measurement. `npx jev-recipes describe evidence-novelty` shows the input and result schemas.

package/recipes/fact-stability/README.md

@@ -1,47 +0,0 @@
-# Assess fact stability
-
-Is fact about an enduring or historical attribute, or a state that is expected to change? Classify the kind of information, not whether this particular fact is currently true.
-
-```ts
-import { factStability } from 'jev-recipes/fact-stability';
-
-const result = await factStability({
-  fact: 'The API is currently experiencing an outage.',
-});
-
-console.log(result.status, result.verdict);
-```
-
-## Input
-
-| Field           | Accepts                                      |
-| --------------- | -------------------------------------------- |
-| `fact`          | 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                                                                                                              |
-| ------------ | -------------------------------------------------------------------------------------------------------------------- |
-| `stable`     | The fact describes a historical event, definition, or enduring attribute unlikely to change in the relevant context. |
-| `changeable` | The fact describes a current state, preference, configuration, or other information that can change.                 |
-| `unclear`    | The kind or relevant timescale 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
-
-Does not establish truth, expiration times, or freshness. Refresh policies and timestamp comparisons belong in code.
-
-## Example input
-
-[demo.json](demo.json) contains editable input and a hand-authored response. After installing `jev-recipes`, `npx jev-recipes demo fact-stability` shows the result offline. The fixture is an illustration, not an accuracy measurement. `npx jev-recipes describe fact-stability` shows the input and result schemas.