Skip to content
Metatext Decide — typed decisions for your agents, with a probability on every answerGet early access
Metatext
Sign Up

system-one

Provider-neutral TypeScript runtime: write choice, noul and score once and run them on Jev, Reflex or any System One endpoint.

Servicebeta
View on GitHub ↗Live demo ↗

Overview

system-one is a small TypeScript runtime that treats System One as the abstraction and providers as implementation details. Applications write choice, noul and score questions once against a SystemOneProvider interface, then run them on TypeSafe Jev, a local Reflex server, any compatible /v1/systemone endpoint, or a custom provider. It includes one SystemOne client, typed builders, heterogeneous questions over shared state, an HTTP provider, strict fail-closed protocol validation and deterministic mock providers for tests.

It deliberately leaves policy to the application: no routing strategy, model tiers, confidence thresholds, automatic escalation, hidden retries or fallbacks. Two packages are published: system-one-core and pi-system-one, a Pi extension exposing a single system_one tool for batched decisions. A separate project, Pi-Bifrost, consumes the core for routing. It has been tested against jev-latest (resolved to jev-1.13.0). The list notes there is no licence file.

What the decision model decides

TypeQuestionAnswers
Yes / noIs this bug browser specific?—
ChoiceChoice questions built with typed builders—

How it works

  1. Configure a provider (Jev, Reflex, HTTP endpoint or custom)
  2. Build typed questions over shared state
  3. Call SystemOne and validate the response strictly
  4. Apply your own thresholds and policy in application code

Strengths

  • Swap providers without changing decision code
  • Strict validation fails closed
  • Deterministic mocks for tests

Caveats

  • No licence file per the list
  • Policy, retries and fallback are left to you

Getting started

npm install system-one-core, then configure the HTTP provider with baseUrl https://api.typesafe.ai and TYPESAFE_API_KEY.

At a glance

Type
Service
Status
beta
Language
TypeScript
Runtime
Node library + Pi extension
Has code
yes
Has tests
yes

Use cases and integrations

How curated lists describe it

  • Provider-neutral System One runtime for TypeScript and Pi.

    wh000wh000/awesome-jev-live

  • Provider-neutral System One runtime for TypeScript and Pi.

    hellogumbo/awesome-jev

  • Provider-neutral TypeScript runtime for typed decisions: the same call runs against Jev, a local implementation, or any `/v1/systemone` endpoint. No licence file.

    MrJev/awesome-jev

Frequently asked questions

What problem does system-one solve?

It decouples application decision code from whichever System One provider you start with.

Does it include routing or thresholds?

No; those belong to the application by design.

Is there a Pi integration?

Yes, pi-system-one exposes a system_one tool.

Related projects

  • openpave-jev

    PAVE skill and CLI for typed Choice, Score and Noul decisions via local Laya, any /v1/systemone server, TypeSafe Jev or an EPM gateway.

    Agent skillbetaTypeScript
  • System One Connector

    Go CLI and single-binary MCP server giving Claude Code, Codex, Hermes and pi an evaluate tool backed by Jev, d1, CLM or Laya.

    MCP serverbetaGo
  • jev

    CPU-only local Jev-style decision service plus an oh-my-pi extension that retargets the agent's judge provider to it.

    PluginprototypeC++, TypeScript
  • jev-mcp (freepik-company)

    Go MCP server giving any client typed Jev decisions via OpenRouter or TypeSafe, with validated answers and no paid retries.

    MCP serverproductionGo
  • askjev

    Unofficial hosted or local Jev MCP server giving agents a quick second opinion: it picks yes/no, scale or choice and returns probabilities.

    MCP serverbetaTypeScript
  • decidealot

    Docker service exposing local Laya, Von, a CLM head or hosted Jev through one TypeSafe-compatible HTTP and MCP endpoint.

    MCP serverbetaPython