Automated README summary
Automatically summarized from the README on 16 Oct 2026; not a run by jevbooks. Run instructions and author-reported outcomes still need verification.
What it is
A Python playground of go-to-market workflows built with Jev: lead triage, deal risk, reply triage, MEDDPICC extraction, account dedup, deal reactivation, and an MCP server.
How it uses Jev
The README does not describe how Jev is used in code, which decisions it makes, or what state it receives.
Model judgments from README excerpts
Project signals use repository metadata, an existing summary and the first 700 README characters, not the full project. “Not found” means not detected in that material; it does not establish absence. These are the original judgments with recorded models and dates, not source audits or run results.
Models & evaluation dates
- Inclusion gate
jev-1.13.0- Project signals
jev-1.13.0- Category
jev-1.13.0- Pattern tags
jev-1.13.0
Evidence
These signals use repository metadata, an existing summary and at most 700 cleaned README characters. ≥ 0.60 means reported in that excerpt; ≤ 0.40 means not found there. The middle band is inconclusive. None is a source-code audit or a test result. The runnable-tool question excludes research experiments; the recommendation question asks for a learning shortlist, not a quality verdict.
- Jev is core to the projectunclear0.58
- Shows a System One patternnot found in the excerpt0.10
- Describes handling uncertaintynot found in the excerpt0.05
- Reports measured numbersnot found in the excerpt0.07
- Is a runnable toolunclear0.46
- Top-10 learning shortlist signalunclear0.40
- Is a replica of the modelnot found in the excerpt0.09
- Solves a common problem (0–2)score on a 0–2 scale1.35 / 2
- About JevFound in material0.90
no-judgment band (0.40–0.60)
Design patterns
No pattern scored above the reporting threshold.
The Jev model and date for each judgment stage are listed above. Card written by DeepSeek V4.1 Flash from the README on 16 Oct 2026.