Skip to content

docs: feature jev-handler in the README, a guide and a runnable example - #90

Merged
rrrodzilla merged 5 commits into
mainfrom
docs/jev-handler-guide
Sep 30, 2026
Merged

rrrodzilla merged 5 commits into
mainfrom
docs/jev-handler-guide

Conversation

@rrrodzilla

Copy link
Copy Markdown
Contributor

jev-handler is the headline of primitives 0.12.0 and engine 0.14.0 shipped with one README table row and a short subsection for it. This puts it in front of a reader.

  • README: a "Judgment as a Pipeline Step" section, the example under Zero-Code Pipeline Examples, a Features line and a Documentation link.
  • docs/primitives/jev-handler.md: a guide covering the questions file, the answer shapes, routing on confidence and on error.kind, rate limits, secrets and every flag (checked against jev-handler --help from the 0.12.0 release).
  • config/examples/jev-triage/: a runnable topology. Run against the released 0.12.0 binaries with a local mock of the evaluation endpoint: all three confidence bands, an unreachable endpoint (error.kind = transport) and a missing TYPESAFE_API_KEY behave as documented.
  • Pointers from getting-started, concepts, examples, handlers and config/examples/README.md.
  • CLAUDE.md: a Step 0 docs gate in the release process, so a release is not tagged again without its docs.

Docs and example config only. No code changes.

Reads one message, asks Jev three typed questions through jev-handler, and routes the verdict into a confidence band with jq selectors. Run against primitives 0.12.0 with a local mock of the evaluation endpoint: all three bands, an unreachable endpoint (error.kind transport) and a missing TYPESAFE_API_KEY behave as the comments say.
jev-handler was the headline of primitives 0.12.0 and had one table row in the README and a short subsection in handlers.md. Adds a README section, docs/primitives/jev-handler.md (questions file, answer shapes, routing on confidence and on error.kind, rate limits, flags checked against jev-handler --help), and pointers from getting-started, concepts, examples and the documentation list.
0.14.0 was tagged with green CI and no open gated issues, and without checking that the docs described what it shipped. Step 0 makes that check explicit, including merging each release branch into main so the default-branch README shows the release.
The shipped-config test reads every .toml under config/ as an EmergentConfig. The jev-triage example ships a questions.toml for jev-handler next to its emergent.toml, which is a different format, so it joins the manifests the test already skips by name.
@rrrodzilla
rrrodzilla merged commit c3bbc51 into main Sep 30, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant