Small decisions. Interesting possibilities.Submit contentSubmit

How it uses Jev

When deterministic routing has no matching tool, code may adopt an eligible Jev route. It uses the family answer and matching family-specific tool answer only when confidence meets threshold and the tool is registered; otherwise it falls back.

What Jev decides

Illustrative source-defined Jev questionExample answers · not a recorded Jev response · Source ↗
Question 1 · family
YOUR APP
INSTRUCTION

The user_request is a Chinese (or English) request for a divination / astrology computation. Which technique family does it ask for? Judge only from what the request says. If it names none of the families, or is not a divination request at all, choose unknown.

STATE

Meta state has `user_request` after local redaction; optional `technique_names` and `known_setting_keys` are included when available.

JEV · CHOICE
  1. western_natal
  2. western_predictive
  3. horary_election_western
  4. india
  5. bazi
  6. ziwei
  7. liureng
  8. sanshi
  9. yijing_divination
  10. numerology_shenshu
  11. zeri
  12. calendar
  13. reference_data
  14. unknown

App workflow

  1. Prepare

    Deterministic routing prepares a decision surface and redacts local evidence according to configured scope.

  2. Consult and gate

    When enabled, Jev returns typed judgments; code records the result and decides whether the threshold and mode permit adoption.

  3. Fallback

    When unavailable or outside enforcement conditions, deterministic behavior remains in control.

Why it is interesting

It makes model judgments auditable and limits their authority through deterministic gates, shadow mode, local redaction, and threshold evaluation.