jev-cli 0.4.1__tar.gz

jev_cli-0.4.1/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 tumf
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

jev_cli-0.4.1/PKG-INFO

@@ -0,0 +1,302 @@
+Metadata-Version: 2.4
+Name: jev-cli
+Version: 0.4.1
+Summary: Small dependency-free CLI for TypeSafe Jev
+Keywords: typesafe,jev,cli,ai
+License-Expression: MIT
+License-File: LICENSE
+Classifier: Development Status :: 3 - Alpha
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Typing :: Typed
+Requires-Python: >=3.13
+Project-URL: Homepage, https://github.com/tumf/jev-cli
+Project-URL: Issues, https://github.com/tumf/jev-cli/issues
+Project-URL: Repository, https://github.com/tumf/jev-cli
+Description-Content-Type: text/markdown
+
+# jev-cli
+
+A small, dependency-free CLI for [TypeSafe Jev](https://docs.typesafe.ai/introduction). Send text or JSON state, ask typed questions, and receive machine-readable `noul`, `choice`, or `score` answers.
+
+The `jev` command is useful when application code needs a fast classification or judgment instead of generated prose.
+
+> **Unofficial:** This is an independent community project. It is not affiliated with, maintained by, or endorsed by TypeSafe AI.
+
+## Features
+
+- Supports all three Jev primitives: `noul`, `choice`, and `score`
+- Sends multiple questions in one request with `run`
+- Accepts text, JSON, files, and stdin
+- Emits compact JSON by default
+- Can print only the primary value for shell scripts
+- Uses structured stderr errors and meaningful exit codes
+- Has no runtime dependencies outside Python's standard library
+
+## Requirements
+
+- Python 3.13 or later
+- [uv](https://docs.astral.sh/uv/)
+- GNU Make
+- A TypeSafe API key
+
+## Install
+
+Clone the repository and install the command with `uv tool` through the Makefile. This installs `jev` into uv's executable directory and verifies the installed version.
+
+```bash
+git clone https://github.com/tumf/jev-cli.git
+cd jev-cli
+make install
+```
+
+Verify that the command is available:
+
+```bash
+jev --version
+```
+
+Expected output:
+
+```text
+jev 0.4.1
+```
+
+## Authentication
+
+The recommended approach for automation is the `TYPESAFE_API_KEY` environment variable. It takes precedence over the credential file.
+
+```bash
+export TYPESAFE_API_KEY='your-api-key'
+jev auth status
+```
+
+For local use, enter the key at the hidden prompt. `auth set` does not accept the key as a command-line argument, which keeps it out of process arguments and shell history.
+
+```bash
+jev auth set
+jev auth status
+jev auth test
+```
+
+For non-interactive automation, piping the key to `jev auth set` remains supported.
+
+`auth status` reports only whether a key is available. `auth test` sends a minimal request to Jev and verifies that the key is accepted. Neither command prints the key.
+
+The fallback credential path follows XDG conventions:
+
+- `$XDG_CONFIG_HOME/jev-cli/credentials.json` when `XDG_CONFIG_HOME` is set
+- `~/.config/jev-cli/credentials.json` otherwise
+
+The credential directory is created with mode `0700`; the file is written atomically with mode `0600`.
+
+## Quick start
+
+`--question` and `--state` also accept the short forms `-q` and `-s`. `--value` has no short form.
+
+## Install the bundled Agent Skill
+
+`jev-cli` currently bundles the `jev-cli` skill. Install it for the current project or globally:
+
+```bash
+jev install-skills
+jev install-skills --global
+```
+
+Use `--claude` to target Claude's skill directory instead:
+
+```bash
+jev install-skills --claude
+jev install-skills --global --claude
+```
+
+The command prints JSON. It refreshes only copies it previously installed and refuses to overwrite an unmanaged skill directory.
+
+Ask whether a message expresses urgency. `--value` prints only the resulting probability from `0` to `1`.
+
+```bash
+jev noul \
+  --question 'Does this message express urgency?' \
+  --state 'Please restore service today.' \
+  --value
+```
+
+Example output:
+
+```text
+0.98
+```
+
+Without `--value`, the command returns the complete API response as JSON, including model and token usage.
+
+```bash
+jev noul \
+  --question 'Does this message express urgency?' \
+  --state 'Please restore service today.' \
+  --pretty
+```
+
+## Question types
+
+### Noul: yes/no probability
+
+Use `noul` for one focused yes/no judgment. The value is the probability that the answer is yes.
+
+```bash
+jev noul \
+  --question 'Does this message request a refund?' \
+  --state 'The integration is broken, but I do not want a refund.' \
+  --value
+```
+
+### Choice: select one option
+
+Use `choice` when the answer must be one of a known set. Each option uses `KEY=DESCRIPTION` syntax.
+
+```bash
+jev choice \
+  --question 'Which team should handle this?' \
+  --state 'The payment integration keeps failing.' \
+  -o 'billing=Payment, charge, or refund issues' \
+  -o 'technical=Bugs or integration failures' \
+  -o 'other=None of these' \
+  --pretty
+```
+
+### Score: evaluate ordered levels
+
+Use `score` for an ordered scale. Levels are numbered from zero in the order supplied.
+
+```bash
+jev score \
+  --question 'How frustrated is the customer?' \
+  --state 'This has failed for three days. Please help.' \
+  -l 'Calm' \
+  -l 'Concerned but civil' \
+  -l 'Very angry' \
+  --value
+```
+
+## Input formats
+
+### Standard input
+
+Omit the state or pass `-` to read it from stdin. This is useful for pipelines and avoids putting sensitive input in shell history.
+
+```bash
+printf '%s' 'Please resolve this today.' | \
+  jev noul --question 'Does this message express urgency?' --value
+```
+
+### File input
+
+Prefix a path with `@` to read its contents.
+
+```bash
+jev noul \
+  --question 'Does this document mention security risks?' \
+  --state @document.txt \
+  --value
+```
+
+### JSON state
+
+Use `--json-state` to parse the state as JSON. Instructions can refer to named fields.
+
+```bash
+printf '%s' '{"message":"Please respond today"}' | \
+  jev noul \
+  --question 'Does `message` express urgency?' \
+  --json-state \
+  --value
+```
+
+## Batch questions
+
+Jev evaluates questions independently against the same state. Use `run` to send a complete System One request and avoid one API call per question.
+
+Create `request.json`:
+
+```json
+{
+  "state": {
+    "message": "The payment integration has failed for three days. Please fix it today."
+  },
+  "model": "jev-latest",
+  "questions": {
+    "department": {
+      "type": "choice",
+      "instructions": "Which team should handle `message`?",
+      "criteria": {
+        "billing": "Payment, charge, or refund issues",
+        "technical": "Bugs or integration failures",
+        "other": "None of these"
+      }
+    },
+    "urgent": {
+      "type": "noul",
+      "instructions": "Does `message` express urgency?"
+    }
+  }
+}
+```
+
+Send it in one request:
+
+```bash
+jev run request.json --pretty
+```
+
+A request can also be piped through stdin:
+
+```bash
+cat request.json | jev run - --pretty
+```
+
+## Output and automation
+
+The default stdout is one JSON object. Logs and structured errors go to stderr, so stdout can be piped directly into another program.
+
+Use `--value` with `noul`, `choice`, or `score` when a script needs only the primary answer:
+
+```bash
+if awk 'BEGIN { exit !(ARGV[1] >= 0.9) }' \
+  "$(jev noul --question 'Is this urgent?' --state 'Restore service today.' --value)"; then
+  echo urgent
+fi
+```
+
+Use `--model` to select another model available to the account:
+
+```bash
+jev noul --question 'Is this urgent?' --state 'Restore service today.' \
+  --model jev-latest \
+  --pretty
+```
+
+## Exit codes
+
+| Code | Meaning |
+|---:|---|
+| `0` | Success |
+| `1` | Unexpected API response or other error |
+| `2` | Invalid arguments or input |
+| `3` | Missing or rejected authentication |
+| `4` | Connection, rate-limit, or transient server error |
+
+An error is emitted as JSON on stderr:
+
+```json
+{"ok": false, "error": "TypeSafe API key is not stored; run: jev auth set"}
+```
+
+## Scope and limitations
+
+The `jev` command is a thin client for focused System One judgments. It does not generate prose, perform arithmetic, compare dates, or replace application-level validation. Keep deterministic work in code and use Jev for semantic judgments.
+
+The CLI sends the supplied state and questions to the TypeSafe API. Do not submit data that your organization is not permitted to send to that service.
+
+## License
+
+[MIT](LICENSE)

jev_cli-0.4.1/README.md

@@ -0,0 +1,284 @@
+# jev-cli
+
+A small, dependency-free CLI for [TypeSafe Jev](https://docs.typesafe.ai/introduction). Send text or JSON state, ask typed questions, and receive machine-readable `noul`, `choice`, or `score` answers.
+
+The `jev` command is useful when application code needs a fast classification or judgment instead of generated prose.
+
+> **Unofficial:** This is an independent community project. It is not affiliated with, maintained by, or endorsed by TypeSafe AI.
+
+## Features
+
+- Supports all three Jev primitives: `noul`, `choice`, and `score`
+- Sends multiple questions in one request with `run`
+- Accepts text, JSON, files, and stdin
+- Emits compact JSON by default
+- Can print only the primary value for shell scripts
+- Uses structured stderr errors and meaningful exit codes
+- Has no runtime dependencies outside Python's standard library
+
+## Requirements
+
+- Python 3.13 or later
+- [uv](https://docs.astral.sh/uv/)
+- GNU Make
+- A TypeSafe API key
+
+## Install
+
+Clone the repository and install the command with `uv tool` through the Makefile. This installs `jev` into uv's executable directory and verifies the installed version.
+
+```bash
+git clone https://github.com/tumf/jev-cli.git
+cd jev-cli
+make install
+```
+
+Verify that the command is available:
+
+```bash
+jev --version
+```
+
+Expected output:
+
+```text
+jev 0.4.1
+```
+
+## Authentication
+
+The recommended approach for automation is the `TYPESAFE_API_KEY` environment variable. It takes precedence over the credential file.
+
+```bash
+export TYPESAFE_API_KEY='your-api-key'
+jev auth status
+```
+
+For local use, enter the key at the hidden prompt. `auth set` does not accept the key as a command-line argument, which keeps it out of process arguments and shell history.
+
+```bash
+jev auth set
+jev auth status
+jev auth test
+```
+
+For non-interactive automation, piping the key to `jev auth set` remains supported.
+
+`auth status` reports only whether a key is available. `auth test` sends a minimal request to Jev and verifies that the key is accepted. Neither command prints the key.
+
+The fallback credential path follows XDG conventions:
+
+- `$XDG_CONFIG_HOME/jev-cli/credentials.json` when `XDG_CONFIG_HOME` is set
+- `~/.config/jev-cli/credentials.json` otherwise
+
+The credential directory is created with mode `0700`; the file is written atomically with mode `0600`.
+
+## Quick start
+
+`--question` and `--state` also accept the short forms `-q` and `-s`. `--value` has no short form.
+
+## Install the bundled Agent Skill
+
+`jev-cli` currently bundles the `jev-cli` skill. Install it for the current project or globally:
+
+```bash
+jev install-skills
+jev install-skills --global
+```
+
+Use `--claude` to target Claude's skill directory instead:
+
+```bash
+jev install-skills --claude
+jev install-skills --global --claude
+```
+
+The command prints JSON. It refreshes only copies it previously installed and refuses to overwrite an unmanaged skill directory.
+
+Ask whether a message expresses urgency. `--value` prints only the resulting probability from `0` to `1`.
+
+```bash
+jev noul \
+  --question 'Does this message express urgency?' \
+  --state 'Please restore service today.' \
+  --value
+```
+
+Example output:
+
+```text
+0.98
+```
+
+Without `--value`, the command returns the complete API response as JSON, including model and token usage.
+
+```bash
+jev noul \
+  --question 'Does this message express urgency?' \
+  --state 'Please restore service today.' \
+  --pretty
+```
+
+## Question types
+
+### Noul: yes/no probability
+
+Use `noul` for one focused yes/no judgment. The value is the probability that the answer is yes.
+
+```bash
+jev noul \
+  --question 'Does this message request a refund?' \
+  --state 'The integration is broken, but I do not want a refund.' \
+  --value
+```
+
+### Choice: select one option
+
+Use `choice` when the answer must be one of a known set. Each option uses `KEY=DESCRIPTION` syntax.
+
+```bash
+jev choice \
+  --question 'Which team should handle this?' \
+  --state 'The payment integration keeps failing.' \
+  -o 'billing=Payment, charge, or refund issues' \
+  -o 'technical=Bugs or integration failures' \
+  -o 'other=None of these' \
+  --pretty
+```
+
+### Score: evaluate ordered levels
+
+Use `score` for an ordered scale. Levels are numbered from zero in the order supplied.
+
+```bash
+jev score \
+  --question 'How frustrated is the customer?' \
+  --state 'This has failed for three days. Please help.' \
+  -l 'Calm' \
+  -l 'Concerned but civil' \
+  -l 'Very angry' \
+  --value
+```
+
+## Input formats
+
+### Standard input
+
+Omit the state or pass `-` to read it from stdin. This is useful for pipelines and avoids putting sensitive input in shell history.
+
+```bash
+printf '%s' 'Please resolve this today.' | \
+  jev noul --question 'Does this message express urgency?' --value
+```
+
+### File input
+
+Prefix a path with `@` to read its contents.
+
+```bash
+jev noul \
+  --question 'Does this document mention security risks?' \
+  --state @document.txt \
+  --value
+```
+
+### JSON state
+
+Use `--json-state` to parse the state as JSON. Instructions can refer to named fields.
+
+```bash
+printf '%s' '{"message":"Please respond today"}' | \
+  jev noul \
+  --question 'Does `message` express urgency?' \
+  --json-state \
+  --value
+```
+
+## Batch questions
+
+Jev evaluates questions independently against the same state. Use `run` to send a complete System One request and avoid one API call per question.
+
+Create `request.json`:
+
+```json
+{
+  "state": {
+    "message": "The payment integration has failed for three days. Please fix it today."
+  },
+  "model": "jev-latest",
+  "questions": {
+    "department": {
+      "type": "choice",
+      "instructions": "Which team should handle `message`?",
+      "criteria": {
+        "billing": "Payment, charge, or refund issues",
+        "technical": "Bugs or integration failures",
+        "other": "None of these"
+      }
+    },
+    "urgent": {
+      "type": "noul",
+      "instructions": "Does `message` express urgency?"
+    }
+  }
+}
+```
+
+Send it in one request:
+
+```bash
+jev run request.json --pretty
+```
+
+A request can also be piped through stdin:
+
+```bash
+cat request.json | jev run - --pretty
+```
+
+## Output and automation
+
+The default stdout is one JSON object. Logs and structured errors go to stderr, so stdout can be piped directly into another program.
+
+Use `--value` with `noul`, `choice`, or `score` when a script needs only the primary answer:
+
+```bash
+if awk 'BEGIN { exit !(ARGV[1] >= 0.9) }' \
+  "$(jev noul --question 'Is this urgent?' --state 'Restore service today.' --value)"; then
+  echo urgent
+fi
+```
+
+Use `--model` to select another model available to the account:
+
+```bash
+jev noul --question 'Is this urgent?' --state 'Restore service today.' \
+  --model jev-latest \
+  --pretty
+```
+
+## Exit codes
+
+| Code | Meaning |
+|---:|---|
+| `0` | Success |
+| `1` | Unexpected API response or other error |
+| `2` | Invalid arguments or input |
+| `3` | Missing or rejected authentication |
+| `4` | Connection, rate-limit, or transient server error |
+
+An error is emitted as JSON on stderr:
+
+```json
+{"ok": false, "error": "TypeSafe API key is not stored; run: jev auth set"}
+```
+
+## Scope and limitations
+
+The `jev` command is a thin client for focused System One judgments. It does not generate prose, perform arithmetic, compare dates, or replace application-level validation. Keep deterministic work in code and use Jev for semantic judgments.
+
+The CLI sends the supplied state and questions to the TypeSafe API. Do not submit data that your organization is not permitted to send to that service.
+
+## License
+
+[MIT](LICENSE)

jev_cli-0.4.1/pyproject.toml

@@ -0,0 +1,32 @@
+[project]
+name = "jev-cli"
+version = "0.4.1"
+description = "Small dependency-free CLI for TypeSafe Jev"
+readme = "README.md"
+license = "MIT"
+license-files = ["LICENSE"]
+requires-python = ">=3.13"
+dependencies = []
+keywords = ["typesafe", "jev", "cli", "ai"]
+classifiers = [
+    "Development Status :: 3 - Alpha",
+    "License :: OSI Approved :: MIT License",
+    "Programming Language :: Python :: 3",
+    "Programming Language :: Python :: 3.13",
+    "Typing :: Typed",
+]
+
+[project.urls]
+Homepage = "https://github.com/tumf/jev-cli"
+Repository = "https://github.com/tumf/jev-cli"
+Issues = "https://github.com/tumf/jev-cli/issues"
+
+[project.scripts]
+jev = "jev_cli:main"
+
+[build-system]
+requires = ["uv_build>=0.8.15,<0.9.0"]
+build-backend = "uv_build"
+
+[tool.uv.build-backend]
+source-include = ["tests/**", "skills/**", "scripts/embed_skills.py"]

jev_cli-0.4.1/scripts/embed_skills.py

@@ -0,0 +1,22 @@
+#!/usr/bin/env python3
+"""Copy canonical repository skills into the Python package."""
+
+from pathlib import Path
+import shutil
+
+
+ROOT = Path(__file__).resolve().parents[1]
+SOURCE = ROOT / "skills"
+DESTINATION = ROOT / "src" / "jev_cli" / "bundled_skills"
+
+
+def main() -> None:
+    shutil.rmtree(DESTINATION, ignore_errors=True)
+    DESTINATION.mkdir(parents=True)
+    for skill in sorted(SOURCE.iterdir()):
+        if skill.is_dir() and (skill / "SKILL.md").is_file():
+            shutil.copytree(skill, DESTINATION / skill.name)
+
+
+if __name__ == "__main__":
+    main()