JevKit

Jev example · Invoices & expenses

The invoice already paid

A matching paid invoice number should change the route.

Workflows & decisionschoicenoulscore

State

This is the context Jev receives before answering the typed question.

{
  "invoice": {
    "number": "INV-44",
    "vendor": "Blue Supply",
    "total": 280
  },
  "prior_payments": [
    {
      "invoice": "INV-44",
      "vendor": "Blue Supply",
      "total": 280,
      "status": "settled"
    }
  ],
  "delivery": "Confirmed"
}

Typed questions (3)

Review route

choice

Which review route fits the provided records? Arithmetic, actual payment and account changes are outside this test.

Try in Playground
  • ready | Supporting evidence is complete with no unresolved issue
  • documents | Required delivery or approval evidence is missing
  • correction | Invoice details require a corrected document
  • duplicate | Records show this invoice was already paid
  • verify_vendor | An unverified vendor or payment-detail change needs review
  • dispute | An unresolved billed item conflicts with supplied evidence

Charges supported

noul

Does the evidence support all billed items and quantities?

Try in Playground

Uncertainty

score

How much material ambiguity remains in the supplied invoice evidence?

Try in Playground
  • No material ambiguity
  • Minor clarification
  • Important missing evidence
  • Conflicting or highly suspicious evidence

Try changing the scenario

Change the prior invoice number and compare.

Catalog source: TypeSafeAI/typesafe-playground, reused under MIT. This is an independent community catalog, not an official TypeSafe AI product.

Background source: Inspired by TypeSafe workflow evals; examples authored for this playground

Browse all examplesLoad first question