Awesome Jev — yibie

No, and the list says so loudly. Inclusion only checks that the source is public and citable, that it genuinely uses Jev for a typed decision, and that the summary fits one sentence. It does not review code quality, security, maturity, or whether the project runs at all.

Because they move. The README currently reports 60 classification and routing entries, 47 verification and guardrails, 40 scoring and ranking, and 10 adaptive and realtime UI. Each entry is filed in exactly one category, by its direct application domain, so a project can look absent from a category you expect it in.

No. The list verifies neither that a project compiles nor that its published numbers reproduce. Its own checklist asks you to confirm the code really calls the Jev API, that a runnable check exists, that any figure is traceable, how much of the repo is code, and whether a licence is present.

Unclear. The README states MIT, but the repository ships no licence file, which leaves the terms of reuse and redistribution unsettled. The contributing guide does say removal is as valid a contribution as addition.

The README is generated, not hand-edited: contributors edit per-category files and a build script regenerates the homepage as an aggregate, so the newest accepted entries appear without drilling into subpages. That also explains why the counts on the homepage move as categories are updated.

Fifteen, from classification and routing through adaptive UI, verification and guardrails, scoring and ranking, agent decisions, data labeling, evaluation, calibration and research, infrastructure and SDKs, games, robotics, finance, compliance and legal, and content moderation, plus a related-practices category. A scientific-pipelines category is still being seeded at zero.

It holds credible public practice signals such as threads, forum discussions and interviews that describe real Jev usage even when there is no strong standalone case page. The list treats it as separate from the build categories, which are each a single entry filed by its direct Jev application domain.