jev-table 0.1.0__tar.gz

jev_table-0.1.0/.github/workflows/ci.yml

@@ -0,0 +1,26 @@
+name: CI
+
+on:
+  push:
+    branches: [master, main]
+  pull_request:
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    env:
+      # jevassert (pack loader) is resolved from PyPI; local dev uses the
+      # sibling checkout via [tool.uv.sources].
+      UV_NO_SOURCES: "1"
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v5
+      - run: uv sync --all-groups
+      - name: Lint
+        run: uv run ruff check .
+      - name: Tests
+        run: uv run pytest
+      - name: Dry-run self-check (no key, sends nothing)
+        run: >-
+          uv run jev-table examples/sms-triage/sample.csv
+          --spec examples/sms-triage/pack.yaml --dry-run

jev_table-0.1.0/.github/workflows/release.yml

@@ -0,0 +1,19 @@
+name: Release
+
+on:
+  push:
+    tags: ["v*"]
+
+jobs:
+  pypi:
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      id-token: write
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v5
+      - name: Build
+        run: uv build
+      - name: Publish to PyPI (trusted publishing)
+        run: uv publish

jev_table-0.1.0/.gitignore

@@ -0,0 +1,9 @@
+.venv/
+__pycache__/
+*.pyc
+.pytest_cache/
+.ruff_cache/
+dist/
+build/
+*.egg-info/
+.DS_Store

jev_table-0.1.0/AGENTS.md

@@ -0,0 +1,50 @@
+# jev-table — agent notes
+
+Local-first CLI that adds Jev columns to CSVs. Part of the
+`jevassert` → `jev-packs` → `jev-table` suite.
+
+## Layout
+
+- `src/jev_table/spec.py` — column spec loader (jev-packs format v0, see
+  jev-packs `SPEC.md`) + threshold/review semantics.
+- `src/jev_table/engine.py` — dedupe, resume cache, concurrency, per-row
+  orchestration. No HTTP here.
+- `src/jev_table/transport.py` — the only module that talks to an endpoint
+  (typesafe-sdk; mock it in tests).
+- `src/jev_table/output.py` — CSV/JSONL input, CSV columns, review flags,
+  corrections file. `_row` is reserved (corrections identity).
+- `src/jev_table/corrections.py` — replay human corrections (edited cells or
+  ids removed from `review` = confirm-as-is; first occurrence per key wins) and
+  emit `cases.jsonl` that must satisfy `jevassert.packs.load_pack`.
+- `src/jev_table/report.py` — `stats.json` + `stats.md`.
+- `src/jev_table/cli.py` — wiring only.
+- `tests/helpers.py` — `MockTransport`, pack/CSV builders.
+
+## Commands
+
+```sh
+uv sync --all-groups
+uv run ruff check .
+uv run pytest
+uv run jev-table examples/sms-triage/sample.csv --spec examples/sms-triage/pack.yaml --dry-run
+```
+
+## Invariants
+
+- Never send row data anywhere except the configured endpoint; no telemetry.
+- `check`-style tests must pass without a key: mock the transport, never call
+  the live API in tests.
+- Review semantics follow jev-packs `SPEC.md`: a label auto-accepts only above
+  its floor; no floor (or no thresholds) means review.
+- Output columns are a stable interface: input columns + one per question
+  (+ `_confidence` for choice/score) + `review` + `error`.
+- Spec parsing/validation is delegated to `jevassert.packs`
+  (`load_pack(..., require_cases=False)` — table specs are unlabeled). Do not
+  add a second parser here.
+
+## Release
+
+Tag `vX.Y.Z` on `master`; the `release.yml` workflow publishes to PyPI via
+trusted publishing. Bump `__version__` in `src/jev_table/__init__.py` first.
+
+No external promotion (HN/Reddit/social) without the owner's approval.

jev_table-0.1.0/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

jev_table-0.1.0/PKG-INFO

@@ -0,0 +1,220 @@
+Metadata-Version: 2.5
+Name: jev-table
+Version: 0.1.0
+Summary: AI columns for CSV files: classify every row with TypeSafe's Jev, with confidence, a review queue and a cost preview. Local-first, resumable, BYO key.
+Project-URL: Homepage, https://github.com/dtduc-git/jev-table
+Project-URL: Issues, https://github.com/dtduc-git/jev-table/issues
+Project-URL: Changelog, https://github.com/dtduc-git/jev-table/releases
+Author-email: Duke - Duc Dinh <dtduc.contact@gmail.com>
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: classification,confidence,csv,data-cleaning,etl,jev,llm,typesafe
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: Intended Audience :: Science/Research
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Scientific/Engineering :: Artificial Intelligence
+Classifier: Topic :: Utilities
+Requires-Python: >=3.10
+Requires-Dist: jevassert<0.2.0,>=0.1.0
+Requires-Dist: typesafe-sdk<0.8.0,>=0.7.0
+Description-Content-Type: text/markdown
+
+# jev-table
+
+[![CI](https://github.com/dtduc-git/jev-table/actions/workflows/ci.yml/badge.svg)](https://github.com/dtduc-git/jev-table/actions/workflows/ci.yml)
+[![License](https://img.shields.io/badge/license-Apache--2.0-blue.svg)](LICENSE)
+
+AI columns for CSV files, backed by [TypeSafe's Jev](https://typesafe.ai):
+label every row with **typed answers, probabilities and a review queue** —
+deduplicated, resumable, with a cost preview before you spend anything.
+
+> Independent community tool. Not affiliated with TypeSafe AI.
+
+```sh
+uvx jev-table messages.csv --spec pack.yaml --dry-run     # estimate cost, send nothing
+uvx jev-table messages.csv --spec pack.yaml               # writes messages.jev.csv + stats
+```
+
+| message | category | urgency | mentions_money | review |
+|---|---|---|---|---|
+| WINNER!! Claim your $500 gift card… | spam | high | 0.99 | |
+| Your appointment is confirmed… | ham | normal | 0.02 | |
+| [weird message] | | | | category;urgency |
+
+## The column spec is a pack
+
+Columns come from a [jev-packs](https://github.com/dtduc-git/jev-packs) pack
+(format [spec v0](https://github.com/dtduc-git/jev-packs/blob/main/SPEC.md)) —
+questions as data, no prompts in code:
+
+```yaml
+spec: 0
+id: sms-triage
+version: 0.1.0
+license: CC0-1.0
+tested: null
+description: Label messages as spam/ham and score urgency.
+state:
+  fields: [message]          # CSV columns sent as the state
+questions:
+  category:
+    type: choice
+    instructions: "Is `message` unsolicited commercial spam, or a message the recipient expects?"
+    options:
+      spam: "Unsolicited bulk or promotional message."
+      ham: "Personal, transactional or service message."
+      unknown: "Cannot tell from the message alone."
+  urgency:
+    type: score
+    instructions: "How soon does `message` need a human look?"
+    levels: [low, normal, high, unknown]
+  mentions_money:
+    type: noul
+    instructions: "Does `message` mention an amount of money or a payment?"
+thresholds:
+  category: {spam: 0.8, ham: 0.8}
+  urgency: {low: 0.7, normal: 0.7, high: 0.7}
+  mentions_money: {true: 0.85, false: 0.85}
+```
+
+See [`examples/sms-triage/`](examples/sms-triage/) for a runnable pair. Specs
+are parsed by the same canonical loader the rest of the suite uses
+(`jevassert.packs`); golden cases are optional for table specs.
+
+## Review is the point
+
+A label auto-accepts only when its probability clears its floor in
+`thresholds`. Everything else — low probability, a label with no floor (like
+`unknown`), or a question with no thresholds at all — lands in the `review`
+column:
+
+```
+data.jev.csv               # your rows + answers + confidence + review + error
+data.jev.corrections.csv   # one row per flagged state (needs a human)
+data.jev.stats.json/.md    # cost, latency, automation rate, distributions
+data.jev.cache.jsonl       # resume cache (delete to force a full re-run)
+```
+
+`review` lists the flagged question ids (`category;urgency`), so you can filter
+in any spreadsheet. `category_confidence` and `urgency_confidence` carry the
+model's confidence for choice/score answers.
+
+Fix a row by editing its answer cell, or delete the id from `review` to confirm
+it as-is, then replay — corrected rows make no API calls and their flags clear:
+
+```sh
+jev-table messages.csv --spec pack.yaml \
+  --corrections messages.jev.corrections.csv \
+  --emit-cases messages.jev.cases.jsonl
+```
+
+`--emit-cases` writes the corrected rows as a `cases.jsonl` in jev-packs
+format v0: a golden set you can hand to `jevassert record` for evidence. That
+is the suite flywheel — jev-table labels, you review, jevassert measures,
+jev-packs publishes.
+
+## How it works
+
+- **Dedupe** — identical rows (same state, questions and model) are sent once
+  and fanned back out. Duplicates are free, and corrections list one row per
+  unique state.
+- **All questions, one call per row** — Jev evaluates every question in
+  parallel against one state; batching is [an order of magnitude cheaper and
+  faster](https://docs.typesafe.ai/cookbooks/parallel_questions) than one call
+  per question.
+- **Resume** — every successful row is appended to the cache, so a rerun only
+  calls what's missing. Errors are never cached and are retried next run.
+- **Concurrency** — 8 in-flight requests by default, auto-capped when states
+  are large so you stay under the token-rate limit. `--concurrency` overrides.
+- **Cost preview** — `--dry-run` estimates tokens (chars/4) across the whole
+  input and prints expected dollars at $0.042/Mtok input (output is free);
+  every real run also reports actual vs estimated tokens.
+- **Safety cap** — files over 10,000 rows need `--yes` after a dry run.
+
+Retries and 429/529 backoff come from the official TypeSafe SDK.
+
+## Privacy
+
+Row data (only the `state.fields` you declared) is sent to the endpoint you
+configure — `https://api.typesafe.ai` by default, or anything Jev-compatible
+via `--base-url`. Nothing else leaves your machine: no telemetry, no analytics,
+no uploads. `--dry-run` sends nothing at all. TypeSafe's
+[data handling](https://docs.typesafe.ai/models#data-handling): requests are
+not used for training.
+
+## CLI
+
+```
+jev-table INPUT --spec SPEC [--out PATH] [--model NAME] [--base-url URL]
+           [--limit N] [--concurrency N] [--dry-run]
+           [--corrections PATH] [--emit-cases PATH] [--yes] [--no-cache]
+```
+
+`INPUT` is a CSV or a flat JSONL (scalar values only; JSONL keeps numbers and
+booleans as-is in the state sent to Jev).
+
+| flag | meaning |
+|---|---|
+| `--spec` | pack.yaml file or its directory (required) |
+| `--out` | output CSV (default `<input>.jev.csv`) |
+| `--model` | Jev model or alias (default `jev-latest`; pin a version to freeze behavior) |
+| `--base-url` | Jev-compatible endpoint (local replicas welcome) |
+| `--limit N` | process the first N rows |
+| `--dry-run` | estimate tokens/cost; sends nothing, needs no key |
+| `--corrections PATH` | replay human edits from a `*.corrections.csv` (needs `_row`) |
+| `--emit-cases PATH` | write corrected rows as `cases.jsonl` (jev-packs format v0) |
+| `--yes` | allow more than 10,000 rows |
+| `--no-cache` | disable the resume cache |
+
+Exit codes: `0` done (review rows are fine), `1` at least one row errored,
+`2` bad input or refused run. Requires `TYPESAFE_API_KEY` (any non-empty
+value works for local endpoints).
+
+## Non-goals
+
+No web UI, no hosted service, no Excel/PDF (CSV in, CSV out), no auto-written
+criteria, no telemetry. Columns come from the spec, never from prompts in code.
+
+## jev-table vs jev-agent-tool
+
+[`jev-agent-tool`](https://github.com/dtduc-git/jev-agent-tool) gives you the
+primitive: `evaluate_batch` over 1–50 records. jev-table is the workflow on
+top: dedupe, resume, cost preview, review queue, corrections and stats — for
+whole files, not batches. If you are writing a script, use the primitive. If
+you are labeling a spreadsheet, use jev-table.
+
+## Development
+
+```sh
+uv sync --all-groups
+uv run ruff check .
+uv run pytest
+uv run jev-table examples/sms-triage/sample.csv --spec examples/sms-triage/pack.yaml --dry-run
+```
+
+`jev-table` imports the pack loader from [`jevassert`](https://github.com/dtduc-git/jevassert)
+(`jevassert.packs`). Locally, `uv sync` resolves it from the sibling checkout
+via `[tool.uv.sources]`; CI resolves it from PyPI (`uv sync --no-sources`), so
+`jevassert` must be published before CI can run.
+
+Live smoke against the public UCI SMS Spam dataset (which ships gold labels):
+
+```sh
+python scripts/fetch_sms_spam.py sms-spam-sample.csv 200
+TYPESAFE_API_KEY=... uv run jev-table sms-spam-sample.csv --spec examples/sms-triage/pack.yaml
+uv run python scripts/report_accuracy.py sms-spam-sample.jev.csv --question category
+```
+
+Releases: push a `v*` tag; GitHub Actions builds and publishes to PyPI via
+trusted publishing.
+
+## License
+
+Apache-2.0. The SMS Spam Collection dataset is CC BY 4.0 (Almeida et al.,
+2011) and fetched, never vendored.