8 Commits

Author SHA1 Message Date
03c7e2c397 fix(license): consistent Apache-2.0/MIT split + migrate 3 examples from private audit
- Root LICENSE: replace the short-form notice with the full canonical
  Apache-2.0 text (fixes GitHub's "Other" license detection); update the
  OpenJev -> Umpirix copyright line in LICENSE/NOTICE, otsone/NOTICE and
  sdk/python/LICENSE+NOTICE (missed by the rebrand pass).
- sdk/ai-sdk: was MIT with no LICENSE/NOTICE and no upstream fork trail
  (unlike sdk/js, sdk/python, adapters/python, skills, which are real
  TypeSafe AI SDK forks and correctly keep MIT per their NOTICE). It is
  original Umpirix code, so switch it to Apache-2.0 with its own
  LICENSE/NOTICE, matching the root.
- README Licensing section: list sdk/ai-sdk under Apache-2.0 and
  sdk/scribase-decisions under MIT, and spell out why the TypeSafe-forked
  directories stay MIT (their MIT terms require preserving the notice).
- Audited caelum0x/openjev-private (read-only clone): it's an older,
  mostly-superseded snapshot of this repo. Migrated the 3 self-contained,
  secret-free example scripts it had that this repo didn't (raw-HTTP, no
  SDK dependency): content-moderation, lead-scoring, support-ticket-routing
  (Python + Node.js, each with a sample JSONL), plus
  scripts/reproduce-leaderboard.mjs (wired to a new `npm run
  bench:reproduce`) for leaderboard reproducibility. Left behind in
  private: src/lib/seo/retired.ts (a reversed decision - this repo now has
  live /compare pages) and the hosted-SaaS pieces already superseded by
  this repo's own, newer versions of the same files.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2026-11-11 19:08:57 +03:00
74e3b24f7a fix(classify): close lexicon gaps behind the lexical engine's shared-word mislabels
The classify CLI's lexical engine had zero lexicon coverage for "feature"
and "praise" (only "bug" was covered) and none at all for generic
sentiment (positive/negative/neutral), so bare-label runs of the CLI's
own README example either tied on everything or confidently mislabeled a
praise/feature row as a bug whenever a bug-shaped word like "crash"
appeared. Add two small, additive synonym groups to the existing lexicon.

Measured on a new 65-row synthetic gold set (examples/classify-eval.jsonl,
run via `npm run classify-eval`, scripts/classify-eval.mjs): 32.3% -> 49.2%
accuracy counting ties as wrong, 67.7% -> 71.1% on rows the engine
actually committed to; the sentiment set alone went 5.0% -> 35.0%. The
product-wide gold regression suite (`npm run gold`) still passes 61/61 —
every change is a new synonym entry, not an edit to an existing one.

README now documents the measured numbers, the --threshold tradeoff
(0.55 raises decided-row accuracy to 83.8% at the cost of more abstains),
and the real remaining limit: a bag-of-words engine can't fully resolve
a praise sentence that mentions "crash" from an actual bug report.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2026-11-11 14:26:12 +03:00
60c6d3ebba fix: keyless triage example, lite README import name, JSON-RPC parse error on /v1/mcp
- examples/triage-tickets.py no longer passes a placeholder key or says the SDK requires one
- sdk/js-lite README imported from @caelum/typesafe, which does not resolve; use @openjev/lite
- POST /v1/mcp answers a non-JSON body with a JSON-RPC -32700 error instead of the REST envelope
2026-11-11 09:33:19 +03:00
fb424b56e3 feat(cli): openjev classify, label text with no server
New subcommand that imports the engine straight from src/ with Node type
stripping: no server, no key, no model download. Reads one text per line on
stdin, or a .txt, .csv (--column) or .jsonl (--field) file; prints a table or
JSON lines, or writes .csv / .jsonl with --out. Each row gets a label, a
probability and the engine that answered (embedding when the gte-small model
is installed, else lexical). --threshold blanks low-probability rows for
review, and near-ties are always left blank. Labels accept an optional
description (name:description).

Exit codes: 2 for usage errors, 1 for missing files, columns or bad JSON.
2026-11-11 07:43:28 +03:00
26becee66a feat(api): official TypeSafe SDKs work unchanged against OpenJev
Found by running typesafe-sdk 0.7.5 and @typesafe-ai/sdk 0.7.0 against a
local server and fixed:
- zstd (and gzip/deflate/br) request bodies are decoded; the SDKs compress
  bodies of 1 KiB or more, which used to fail with a 500
- GET /v1/models also returns models: [{ name, description, release_date }]
- every systemone, batch and models response carries x-typesafe-request-id
- a base URL ending in /v1 (or /api/v1) resolves to the same handlers
- request errors carry a detail list; a non-JSON body is a 400, not a 500
- multipart (image asset) requests get a clear 415

Adds examples/official-sdk.py and .mjs, a /docs/typesafe-sdk page, a README
block and a COMPARISON.md section, limited to what was observed to pass.
2026-11-11 05:41:06 +03:00
d3ba32ac12 fix(sdk): make the API key optional in the Python, JS and lite SDKs
A self-hosted server needs no key, but all three SDKs threw before the first
request. The key is now optional: without one no Authorization header is sent.
A key that is present is validated as before.

Release prep: openjev-client 0.7.2, @openjev/sdk 0.6.1, @openjev/lite 0.2.1.
2026-11-11 05:36:35 +03:00
4eb0edf7d5 feat(adoption): comparison doc, Python example, examples index, npm keywords
Adoption-ranked work from plans/research/ai-and-active-next-2026-11-11.md
section 2 (openjev_next list), skipping items that need training/eval or a
live deploy this pass:

- docs/COMPARISON.md: honest OpenJev vs TypeSafe Jev vs Kev vs OpenAI
  Decisions API table, sourced from already-verified facts in
  plans/openjev.md's 2026-11-06 research entry, with our own real
  otsone-mini/otsone-base/system-one numbers and their caveats stated
  (item #4, "public comparison writeup").
- examples/triage-tickets.py: a real runnable Python SDK example (Choice +
  Score + Noul ticket triage), verified end to end against a mocked
  TypeSafe2/httpx2 transport; examples/README.md indexes both examples.
  Fixes a real gap found while writing it: TypeSafeClient() always
  requires a non-empty api_key even against a keyless self-hosted server
  (server-side "unknown keys pass through") -- worked around in the
  example with a documented placeholder, not changed in the SDK itself.
- sdk/js/package.json: @openjev/sdk had no `keywords` field at all (its
  sibling @openjev/lite and both Python packages do) -- real npm-search
  discoverability gap on the flagship package, fixed; publint still
  passes clean.

Not done this pass (needs model eval/training or a live deploy, out of
scope under the no-training/no-deploy constraints): Kev-style versioned
eval-suite naming (#1), growing gold.json with a real holdout split (#2),
a hosted try-it-now demo widget (#3).
2026-11-11 04:22:00 +03:00
caelum0x
4847e35451 OpenJev: open-source typed decision service
Typed decision/classification service with an in-process gte-small ONNX
embedding engine and lexical fallback, JS/Python SDKs, adapters, and the
otsone model family. Apache-2.0 (sub-packages keep their MIT licenses).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-25 00:12:36 +03:00