skills-jev

Quiet research lab — prove that JCR and jevwire can talk to Jev through OpenRouter’s Decisions API, via a tiny local System One proxy. Linked from the tiesa.tech carousel once the card is approved.

Smoke status

loading…
—OpenRouter direct
—jevwire noul
—jevwire choice
—JCR SDK path

Results are written by tools/smoke.mjs to public/data/smoke.json at publish time. This page does not call OpenRouter from the browser.

What this proves

Architecture

jevwire / JCR (TypeSafeClient) │ POST /v1/systemone (Bearer ignored by proxy) ▼ openrouter-systemone-proxy · 127.0.0.1:8799 │ map jev-latest → typesafe/jev-1.13 │ Authorization: Bearer $OPENROUTER_API_KEY ▼ openrouter.ai/api/alpha/decisions │ ▼ TypeSafe Jev 1.13 → typed answers { noul | choice | score }

Optional Mermaid (render elsewhere):

flowchart LR
  A[jevwire / JCR SDK] -->|/v1/systemone| B[local proxy :8799]
  B -->|/api/alpha/decisions| C[OpenRouter]
  C --> D[typesafe/jev-1.13]

Adapter notes

Model aliases

jev-latest, jev-1.13.0, jev-1.13 → typesafe/jev-1.13.

JCR full resolve

Smoke covers the SDK path and the first routing choice (single vs compound). A full resolveCapabilities() walk needs the capabilities tree (many Jev calls) and, for compound requests, an OpenAI decomposer. That is the next workload once this path is green.

Vendor clones

Upstream jevwire (MIT, Brainwires) and jcr (MIT, Niaz Morshed) live as sibling checkouts — not republished as the product. See vendor/NOTICE.md.

Raw smoke.json

loading…