caelum0x 5fc8aacd95 feat: rebrand OpenJev to Umpirix across README, CLI, SDKs and PyPI packages
Owner rename (GitHub repo already caelum0x/openjev -> caelum0x/umpirix,
origin updated): rebrands every user-facing surface while keeping full
backward compatibility.

- README.md: title, badges, clone/MCP commands, SDK table, model-family
  table and a new "Renamed from OpenJev" section (mirroring the existing
  "Renamed from opentypesafe" section) documenting every old->new mapping.
  Never claims Umpirix is or was made by TypeSafe; "Jev-compatible" kept
  only where it describes wire compatibility.
- CLI (scripts/cli.mjs): primary bin is now `umpirix`; `openjev` and
  `opentypesafe` still work and print a one-line rename notice (detected
  via the invoked bin's basename). package.json's `name` is now "umpirix"
  and all three bin names are installed.
- Site/app title: the single SITE_NAME constant (src/lib/seo/site.ts) is
  now "Umpirix", which cascades into every page's <title> and JSON-LD; the
  nav sidebar brand text (app-shell.tsx) and OG site title (og/site.json)
  updated too.
- SDK package names: @openjev/sdk -> @umpirix/sdk, @openjev/lite ->
  @umpirix/lite, @openjev/ai-sdk -> @umpirix/ai-sdk (sdk/js, sdk/js-lite,
  sdk/ai-sdk, plus the dependent sdk/scribase-decisions package and its
  source re-export). All import sites, peer/dev dependency keys, jsr.json
  and doc comments updated to match. Verified free on npm (404) as of
  2026-11-11. sdk/js (193 tests) and sdk/js-lite (99 tests) both typecheck
  and test clean after the rename; `npm pack --dry-run` confirmed real,
  correctly-named tarballs for both.
- PyPI: openjev-client -> umpirix-client (sdk/python), openjev-adapters ->
  umpirix-adapters (adapters/python); both plain names confirmed free on
  PyPI (404) as of 2026-11-11. The importable module stays `openjev` /
  `openjev_adapters` for compatibility. Found and fixed a real regression
  from the distribution rename: both packages' `_version.py` read
  `importlib.metadata.version()` by the old hardcoded distribution name,
  which would have raised PackageNotFoundError post-rename — now tries the
  new name first, falls back through the old names. `uv sync` + `uv build`
  + `uvx twine check` pass clean for both under the new names (681 + 452
  tests pass respectively); `adapters/python/pyproject.toml`'s
  `[tool.uv.sources]` key updated to match so the local editable override
  still resolves. No PyPI token exists on this machine, so nothing was
  published — exact commands are in PUBLISHING.md for whoever holds the
  credentials.
- PUBLISHING.md: renamed package table, documented the verified-clean local
  builds above, and the owner-gated npm (@umpirix org doesn't exist yet,
  needs browser 2FA) / PyPI (token removed) bootstrap steps.
- Root `npm run typecheck` / `npm test` (138 pass) / `npm run gold` (61
  pass) all clean after every change above.
- hackathons/geekroom-2026/demo-umpirix.mp4: the existing real
  narrated Bifrost demo capture (119.8s, Deepgram aura-2-asteria-en
  narration, -14.6 LUFS measured) copied to the name this task's submission
  expects, plus its real raw captures (media/raw, media/terminal) and a
  real SRT built from the narration's own word-level timestamps
  (media/demo-umpirix.srt) for caption generation. Known gap, not hidden:
  the capture's on-screen app UI still reads "OpenJev" (pre-rebrand,
  pre-redeploy) — a fresh re-record after this rebrand ships to the running
  app is a real follow-up, noted in plans/openjev.md.

Also pushed a companion one-line copy fix to caelum0x/scribase (commit
a8c2f72, not this repo): scribase.com/decisions now says "Built on
Umpirix" instead of "Built on OpenJev", deployed live (verified 200,
"Built on Umpirix" present).

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2026-11-11 18:59:19 +03:00
..

OpenJev Python SDK

Now part of Scribase: scribase.com/decisions. This SDK itself is unchanged and still distributed as openjev-client — the link above is a Jev-compatible quickstart that uses this package, not a rename or a republish.

openjev is an open Python client for OpenJev — a self-hostable decision engine that speaks the same System One /v1 wire protocol as the upstream TypeSafe AI API, so a single client works unchanged against:

  • a self-hosted OpenJev deployment (default base URL: http://localhost:8080)
  • the hosted TypeSafe AI API at https://api.typesafe.ai

This SDK is derived from @typesafe-ai/typesafe-sdk-python (MIT). See NOTICE for attribution. The request/response shapes (model + state + questions-as-dict) and the public class names (TypeSafeClient, AsyncTypeSafeClient, …) are kept identical so existing TypeSafe code is drop-in compatible.

Quickstart

Install the SDK:

Not yet published to PyPI (pending owner account auth). The plain PyPI name openjev belongs to an unrelated project — verified openjev-sdk and pyjev are taken too — so this package is distributed as openjev-client (the importable module stays openjev). Once published: pip install openjev-client. Until then, install from a clone:

git clone https://github.com/caelum0x/openjev
pip install ./openjev/sdk/python
# or: uv add ./openjev/sdk/python

No API key is needed for a self-hosted server: the client talks to http://localhost:8080 by default and sends no Authorization header unless a key is configured. Start the server (npm run dev in the repository root), then:

from openjev import Choice, TypeSafeClient

with TypeSafeClient() as client:
    response = client.system_one(
        state={"document": "I was charged twice. Please fix this ASAP."},
        questions={
            "category": Choice(
                instructions="What is this ticket about?",
                criteria={"billing": None, "technical": None, "other": None},
            ),
        },
    )

print(response.choices["category"].choice)

Configuration

Point the SDK at a self-hosted OpenJev endpoint or the upstream TypeSafe AI API by setting environment variables or passing arguments to the client constructor.

Purpose Primary (OpenJev) Back-compat alias (legacy)
API key (optional) OPENJEV_API_KEY TYPESAFE_API_KEY
Base URL OPENJEV_BASE_URL TYPESAFE_BASE_URL
Default model OPENJEV_DEFAULT_MODEL TYPESAFE_DEFAULT_MODEL
Log level OPENJEV_LOG_LEVEL TYPESAFE_LOG_LEVEL

The primary OPENJEV_* variable is checked first; the TYPESAFE_* alias is consulted only when the primary variable is absent so that callers already using TYPESAFE_* continue to work without changes.

Default base URL when no variable is set: http://localhost:8080.

Example — point at a self-hosted deployment (the key line is only needed if your server issues keys):

export OPENJEV_BASE_URL="https://systemone.internal.example.com"
export OPENJEV_API_KEY="ots_live_..."   # optional

Example — point at the upstream TypeSafe AI API using the back-compat alias:

export TYPESAFE_BASE_URL="https://api.typesafe.ai"
export TYPESAFE_API_KEY="ts_live_..."
from openjev import TypeSafeClient

# Explicit override also works and takes precedence over the environment:
client = TypeSafeClient(
    base_url="https://systemone.internal.example.com", api_key="..."
)

Trust layer (OpenJev servers)

from openjev import Choice, TypeSafeClient

with TypeSafeClient() as client:
    questions = {
        "intent": Choice(
            instructions="What does the customer want?",
            criteria={"refund": None, "status": None},
            abstain=True,
        )
    }
    result = client.system_one(
        "Where is my order?",
        questions,
        model="auto",                 # local first, LLM only for low-confidence questions
        calibration_id="cal_...",     # confidence fitted on your own labels
    )
    intent = result.choices["intent"]
    if intent.abstained:
        print("out of scope", intent.ood)

    # Shadow mode: compare with your production LLM or human labels.
    client.shadow.run(
        "Where is my order?",
        questions,
        incumbent={"kind": "label", "answers": {"intent": "status"}},
    )
    summary = client.shadow.summary(days=7)

License

MIT — see LICENSE and NOTICE.