User repository on GitHub
Provider-independent, strongly typed decision and evaluation model for .NET. TypeSafe JEV is the first provider.
- Forks
- 0
- Last pushed
- Updated Oct 2026
Repo stats from the GitHub API, cached Oct 2026.
CommunityJev Repos & SDKs
Decisionkit Dotnet
A pre-release .NET decision library that keeps the domain in a dependency-free Core assembly and reaches Jev through a pluggable provider, so changing vendors does not mean rewriting your application model.
- Stars
- 1
- Language
- C#
- License
- MIT
- Published by
- Community
- Author
- iamjonatha
- Last verified
- Oct 2026
About this project
A strongly typed, provider-independent decision engine for .NET, with TypeSafe JEV support. DecisionKit lets a .NET application model a decision the way the domain sees it — typed questions, typed answers, explicit probabilities and scores — and execute that decision against a pluggable provider. TypeSafe JEV is the first production provider; it is not the architecture. Pre-release — under active development. The public API is unstable until 1.0.0. See the roadmap for what is implemented and what comes next.
Quoted from the project's README. Read the full README.
Used inJev for Software & DevTools
- Languages
- C# / .NET
Highlights
- Four packages with a one-way dependency: Core has no Jev, HTTP or JSON knowledge, and only Jev, Extensions and Testing point at it.
- A question fixes the type of its answer at compile time, and unknown response shapes are preserved as raw data rather than discarded.
- Failures are distinguishable without parsing a message: validation, auth, transport, timeout, cancellation, rate limiting, serialization.
- The testing package supplies fake and deterministic providers, injected failures and TimeProvider latency, so tests run with no HTTP at all.
Watch out
The README states pre-release under active development with the public API unstable until 1.0.0, and points to a roadmap that separates what exists from what is being considered, so pin your package version. Retrying is off by default for a specific reason: JEV has no idempotency mechanism, so a repeated call is a second evaluation that is billed again and may answer differently, which makes enabling it your application's decision rather than the library's. TypeSafe JEV is the first production provider but explicitly not the architecture, and only that path is exercised in practice. The quick start is split too: the snippet compiles against Core while the Jev provider is demonstrated separately, so read both before assuming one path works end to end. Targets net8.0 and net10.0. Independent of TypeSafe, MIT. Copy reviewed against the repository README on 2026-10-04, not from running it.
Questions about this entry
Short answers drawn from the linked project or page.
The author's claim is the opposite, and the package graph is the evidence: DecisionKit.Core has no dependencies and contains no provider URL, header, credential or DTO, and the dependency arrow only ever points at Core. The Jev package holds the TypeSafe protocol, transport, auth and resilience; the domain knows nothing about any of it. Swapping providers is meant to leave your application model untouched, though in practice only the Jev path is written.
You can, but understand the cost first. Retrying is off by default because JEV has no idempotency mechanism, so a repeated call is a second evaluation that is billed again and may return a different answer. The library surfaces this rather than deciding for you: configure JevRetryPolicy.Standard with MaxAttempts, and catch DecisionTransientException to inspect DecisionRetryability and RetryAfter before deciding to rethrow.
The compile-time part is the strongest claim: a question determines the type of its answer, so Department team = result.Get(routing).Value.Selection and double score = result.Get(frustration).Value.Value come back without casts. Beyond that, treat the surface as movable until 1.0.0 per the README's own status note, and check the roadmap for what is implemented versus proposed.
DecisionKit.Testing replaces the provider entirely, so no HTTP is involved. FakeDecisionProvider lets you script per-question answers and assert on the captured call list, Fails and FailsTimes inject errors, latency is simulated through a TimeProvider, and DeterministicDecisionProvider derives stable answers for deterministic runs and samples. AOT and trimming guarantees are documented separately.
builder.Services.AddDecisionKit().AddJevProvider on a configuration section. The provider registers as a singleton, takes an IHttpClientFactory client, your logger and your TimeProvider, and validates configuration while the host starts. JevProviderOptions carries the Endpoint, AttemptTimeout, OperationTimeout and Retry policy together, and the provider asks its credential provider on every call, so a rotated key takes effect without rebuilding anything.
Known shapes map to typed models, and unknown shapes are preserved as raw data rather than discarded. The design principle is stated as forward compatibility with unknown never thrown away, so a provider that adds a field does not break your result type, and you can still inspect what actually came back instead of losing it to a parse failure.
API keys are never logged, never serialized into diagnostics, and never included in exceptions. Request and response payloads are not logged by default, raw protocol capture is opt-in and can be disabled entirely, and HTTPS is required for production endpoints. The library is MIT-licensed, independent of TypeSafe, and targets net8.0 and net10.0.
More Jev resources like this
3GitHub stars
Unofficial .NET 10 HTTP client for TypeSafe Jev and the Jev-compatible local Laya server that posts the shared /v1/systemone body and returns typed Choice, Score and Noul answers, with no runtime package dependencies.
Jev Repos & SDKs#community#jevbest#catalog-import
Community
pinkroosterai/SystemOneSharpC#
pinkroosterai/SystemOneSharpC#27GitHub stars
SwiftPM client for the TypeSafe System One API that mirrors the official JavaScript SDK, with typed Choice, Noul, and Score questions over Codable answers.
Jev Repos & SDKs#community#jevbest#catalog-import
Community
krzyzanowskim/TypeSafeSwift
krzyzanowskim/TypeSafeSwift15GitHub stars
PHP 8.2+ client for Jev that sends a state with typed noul, choice, and score questions and returns one typed answer per question ID with probabilities and usage.
Jev Repos & SDKs#community#jevbest#catalog-import
Community
sanmai/typesafe-ai-phpPHP
sanmai/typesafe-ai-phpPHP45GitHub stars
Go SDK plus a pipeline-friendly CLI for typed decisions, covering single questions, batched question maps, retries, and line-oriented filtering over stdin.
Jev Repos & SDKs#community#jevbest#catalog-import
Community
mattn/go-jevGo
mattn/go-jevGo8GitHub stars
PowerShell module that asks Jev typed yes-no, choice, and score questions from the pipeline, raising named answers as object properties for filtering and selection.
Jev Repos & SDKs#community#jevbest#catalog-import
Community
dfinke/JevPowerShell
dfinke/JevPowerShell1GitHub stars
C# client for Jev, TypeSafe AI's System One model. Typed Noul, Choice and Score questions go out with one state in a single round trip and come back with a value, a probability distribution and a confidence number. Choice questions can be built from an enum, so the compiler finds the switch branch you forgot.
Jev Repos & SDKs#community#awesomejev#catalog-import
Community
RavenValentin/TypeSafe.JevC#
RavenValentin/TypeSafe.JevC#From the Jev guides
Original write-ups on what this entry is for.
Closed weights have not stopped the ecosystem from rebuilding the shape in the open. API-compatible servers, retrained heads on small models, and inference-time tricks that skip generation entirely.
Jev Repos & SDKs#open-models#research#local
Read article
From the Jev community
Posts from builders shipping with Jev right now.