System One / Provider-neutral runtime

One interface.
Any System One provider.

A provider-neutral TypeScript runtime for bounded AI decisions. Use TypeSafe Jev, Reflex, compatible /v1/systemone endpoints, or your own SystemOneProvider.

Get started GitHub

01 / What — System One

System One is
the abstraction.

Applications depend on one bounded decision interface instead of a specific model. Choice, noul, and score can be evaluated together against the same shared state.

CHOICE bounded option
coding
0.82
research
0.11
writing
0.05
example → selected: coding
NOUL proposition
example → P(statement = true)
SCORE ordered scale
example → score: 2.7

provider boundary → Jev · Reflex · compatible /v1/systemone endpoint · custom SystemOneProvider

02 / Interop — Swap the provider

Swap the provider.
Keep the application.

Application code stays fixed. Only provider configuration changes.

CORE / NPM npm install system-one-core
SOURCE
BOUNDARY APPLICATION CODE = UNCHANGED
APPLICATION provider-neutral 
01 import { SystemOne, HttpSystemOneProvider } from "system-one-core";
02
03 const provider = new HttpSystemOneProvider({
04   baseUrl: "http://localhost:8008",
05 });
06
07 const systemOne = new SystemOne({ provider });
08 const result = await systemOne.evaluate(request);

03 / Pi — One primitive, two consumers

System One
for Pi.

pi-system-one exposes System One directly to agents. Pi-Bifrost consumes the same core runtime for routing. Both depend on the primitive; neither owns it.

system-one-core provider-neutral primitive
consumer 01 / agent capability

pi-system-one

Adds a single system_one tool beside Pi's existing capabilities.

system_one choice noul score
pi install npm:pi-system-one Learn more
consumer 02 / routing

pi-bifrost

Uses the same System One boundary for routing decisions without owning provider-specific logic.

routing policy confidence escalation
pi install npm:pi-bifrost Learn more