DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to route support tickets with typed Jev answers with Jevcore

Ask Jev yes/no and choice questions about a ticket and act only on confident answers.

Who it is forA developer running a Node service that triages incoming support tickets and needs routing decisions without a model round-trip.

The problemRouting code built on free-text model replies is hard to test and can quietly act on unsure answers.

The outcomeEach ticket gets typed urgency and team answers with probability and confidence, and an unsure answer produces a review step instead of an automatic action.

What you need first

  • Node 20 or later for jevcore and jevcore-mcp, or Node ^22.19.0 or >=24.0.0 for jevcore-dsh
  • A local checkout of the repo for the DeepSeek Harness install path
  • DeepSeek Harness, if you use the plugin or the gates
  • A TypeSafe or OpenRouter key only if you choose a live route; the default is the offline mock

Steps

  1. Run npm install jevcore in the service so the core package is available to plain Node. (inferred, check the README)
  2. Check that the runtime is Node 20 or later, the requirement for the core package.
  3. Import the core package and call its ask function with a state object and noul and choice questions; the README shows this call through ctx.get('jev') inside DSH, so confirm the plain Node exports before wiring it. (inferred, check the README)
  4. Read result.answers for probability and confidence, and apply an explicit confidence floor as in src/policy.ts, sending unsure answers to a human queue.

Prompt for your agent

In the PerryLink/jevcore repo, write a Node script that asks Jev a noul question ('Does this convey urgency?') and a choice question over the ticket text in <ticket file>. Expected output: the probability and confidence for each answer. Verify that the startup line reports egress=OFF and provider=mock, so no network call was made.

Caveat. The README shows the ask call inside DSH through ctx.get('jev'), and the plain Node import path is not shown, so verify the package exports before depending on them.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page