WeFlow CLI
For each article, the client sends a state containing the title and up to 4,000 characters of body.
For each article, the client sends a state containing the title and up to 4,000 characters of body.
For each article, the client sends a state containing the title and up to 4,000 characters of body. One request asks for its topic (Choice), practical relevance to the stated environmental-science/computing reader (Score), and whether it contains immediately usable material (Noul). The caller stores these structured answers; summaries and other generated prose remain in the LLM path.
Which topic does this article belong to?
Article title and the first 4,000 body characters, formatted as “标题:… 正文: …”. The state does not include date, source, or prior labels.
Does the article contain something concrete the reader can use today, such as a new tool, method, data source, codebase, or reproducible result, rather than only informational news, opinion, or personal writing?
Article title and the first 4,000 body characters, formatted as “标题:… 正文: …”. The state does not include date, source, or prior labels.
The CLI fetches articles for a requested date and calls the Jev classification path for each article when configured.
Up to six worker slots call the article-level client. Successful decisions are attached to article records; a failed Jev classification for one article falls back to the full LLM classification prompt.
For successfully judged articles, the LLM receives the summary-only prompt; Jev does not generate summaries.
It separates topic, usefulness, and inclusion into distinct typed decisions, then lets the daily workflow fall back to its previous LLM classification path when a Jev call fails.