{
 "schema_version": 1,
 "generated": "2026-10-20",
 "id": "kyegomez-open-jev--prototype-typed-questions-over-json-state",
 "repo": "kyegomez/open-jev",
 "repo_url": "https://github.com/kyegomez/open-jev",
 "repo_slug": "kyegomez-open-jev",
 "title": "Prototype typed yes/no, choice, and score questions over JSON state",
 "page_title": "How to prototype typed yes/no, choice, and score questions over JSON state with Open Jev",
 "summary": "Write your own nested state and declare Noul, Choice, and Score questions to test how the typed readouts behave.",
 "who": "An engineer building a proof of concept for routing or triage decisions over structured records, who wants to see whether a typed readout fits the shape of the problem.",
 "problem": "Free-text generation is hard to constrain to a fixed set of labels, and it is unclear how a typed readout API would handle a custom record.",
 "outcome": "A small script that encodes one state dictionary once and returns a list of typed answers for several declared questions.",
 "steps": [
  "Clone and install as in the install section: `git clone https://github.com/kyegomez/open-jev` then `python -m pip install \"torch>=2.0\"`",
  "Build a JSON-like state dictionary that matches the structure of your records",
  "Declare questions with Noul for true or false, Choice with your options, and Score with ordered labels",
  "Create the model with JevConfig and call it inside torch.no_grad() on a list of states and a list of questions",
  "Print each answer and check that Choice answers use only the options you declared"
 ],
 "agent_prompt": "Using the repo at https://github.com/kyegomez/open-jev, write a script that builds a state dictionary from <your record file>, declares one Noul, one Choice, and one Score question, and prints the answers. Expected output is one typed answer per question; verify that every Choice answer is one of the declared options.",
 "agents": [
  "any"
 ],
 "difficulty": "Intermediate",
 "time": "45 minutes",
 "basis": "readme",
 "caveat": "The included tokenizer is a deterministic hash tokenizer, so answers will not be meaningful until a trained tokenizer and model exist, and the README says typed output does not guarantee correct predictions.",
 "category": "Research",
 "tags": [
  "Research"
 ],
 "lang": "python",
 "requirements": [
  "Python 3.10 or newer (recommended in the README)",
  "git installed",
  "PyTorch 2.0 or newer",
  "Basic familiarity with running Python scripts from a terminal"
 ],
 "risk": "none",
 "seen_in_the_wild": false,
 "mentioned_publicly": false,
 "risks": [],
 "best": false,
 "score": 0.9,
 "evidence": [],
 "url": "https://dedupedai.com/use-cases/kyegomez-open-jev/prototype-typed-questions-over-json-state/",
 "md": "https://dedupedai.com/use-cases/kyegomez-open-jev/prototype-typed-questions-over-json-state/index.md",
 "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 hello@dedupedai.com and we will look at it promptly.",
 "api": "https://dedupedai.com/api/v1/usecases/kyegomez-open-jev--prototype-typed-questions-over-json-state.json",
 "api_version": "v1"
}