Deciding when work is finished with typed questions
Chinese X post describing a workflow that asks Jev yes/no, either-or and score questions to decide when work is finished.
This summary is based on how curated lists describe the project; its README was not available to review.
Overview
This is a social media post, written in Chinese, in which a practitioner describes using Jev for the wrap-up judgment: deciding whether a piece of work is actually finished. According to the list summary, they ask Jev yes/no, either-or and score questions from a local CLI when their machine is on, and from a cloud SDK script when it is not.
It is a practical example of task-completion verification with typed questions instead of asking an LLM whether it is done. No code is linked in the record.
What the decision model decides
| Type | Question | Answers |
|---|---|---|
| Yes / no | Is this work finished?(inferred) | yes · no |
| Score | How complete is the work?(inferred) | — |
How it works
- Describe the current work state
- Ask Jev typed completion questions via CLI or SDK
- Decide to wrap up or continue based on answers
Strengths
- Simple, repeatable completion check
- Works from a local CLI or a cloud script
Caveats
- List-only; no code or evaluation
At a glance
- Type
- Discussion
- Status
- discussion
- Runtime
- CLI / cloud SDK script
Use cases and integrations
How curated lists describe it
X (Chinese): a practitioner's workflow for the wrap-up judgment, asking Jev yes/no, either-or and score questions from a local CLI when the machine is on and from a cloud SDK script when it is not.
yibie/awesome-jev
Frequently asked questions
What is the post about?
Using typed Jev questions to decide when work is finished.
How is Jev called?
From a local CLI or a cloud SDK script, according to the summary.
Is there code?
Not linked in the directory record.
Related projects
Auto-updated bilingual leaderboard of Jev ecosystem projects, tutorials and discussions, discovered daily and sorted by GitHub stars.
ProjectproductionChatGPT-style web chat where every word of every reply is a Jev multiple-choice decision over a ~1,800-word vocabulary plus END.
ProjectprototypeTypeScriptExperiment that deliberately misuses Jev as a text generator by asking which symbol comes next and sampling from the returned distribution.
ProjectresearchPythonChat client that makes Jev write by asking Next word? over a 20,000-word dictionary in 255-word buckets plus a run-off.
ProjectresearchPythonIssue in the Orcha multi-agent orchestration project proposing to move judgment calls onto Jev to cut model cost.
ProjectdiscussionPythonAuto-generated write-up of a Reddit post claiming an open RLCD-trained Jev model; content is generic and largely inaccurate.
ProjectPython