JEQ

Intelligence you can pipe.

JEQ is a typed judgment CLI for scripts, agents, and systems. It turns a question
and JSON state into evidence that can move through a Unix pipeline.

printf '%s\n' '{"id":"a","text":"billing is urgent"}' \
  | jeq map --as urgency --input ndjson --questions-json \
    '{"questions":{"urgency":{"type":"noul","instructions":"Is this urgent?"}}}' \
  | jeq gate --as policy --input ndjson --value-pointer /_jeq/urgency/answers/urgency/noul \
    --pass-min 0.8 --reject-max 0.2

Quick start

On Linux, install the verified release archive with the installer:

curl -fsSL https://raw.githubusercontent.com/cristianoliveira/jeq/main/scripts/install-jeq-linux.sh \
  -o /tmp/install-jeq-linux.sh
bash /tmp/install-jeq-linux.sh

On macOS, install through the Homebrew tap:

brew tap cristianoliveira/tap
brew install cristianoliveira/tap/jeq
jeq version

Alternatively, install from the pinned release candidate with Nix:

nix run github:cristianoliveira/jeq/v0.1.0-rc.1 -- version
nix profile install github:cristianoliveira/jeq/v0.1.0-rc.1

Then set TYPESAFE_API_KEY and run an explicit judgment. Start with the focused
guides:

• Installation
• Getting started
• Jev mental model
• Composition
• Reduce a bounded collection
• CLI reference
• Architecture
• Examples

Boundaries

• Evaluation commands make network requests. validate validates locally.
• Input is untrusted data. Do not treat model output, IDs, or excerpts as commands.
• Review prompts, state, and output before sending. Do not send credentials or
  private data unintentionally.
• API usage costs money. Retries, batch size, and model choice affect cost.
• Output and exit codes are designed for pipelines; policy reject and
  uncertain are non-zero. Verbose traces go to stderr.
• JEQ does not own actions, memory, sessions, or release tags. The caller owns
  state, credentials, retries, and automation policy.

More documentation

• Development
• Release candidate notes
• MIT License