christian-taillon/telltale-systemone
User repository on GitHub
Reference Telltale analyzer.v1 extension that evaluates guard packs with a System One model
- Forks
- 0
- Last pushed
- Updated Oct 2026
Repo stats from the GitHub API, cached Oct 2026.
Jev directory
CommunityJev Integrations & Adapters
Telltale Systemone
A reference Telltale analyzer.v1 extension that asks a TypeSafe System One model (Jev) narrow typed questions about agent actions, with the questions defined in configurable guard packs while Telltale keeps its deterministic rules, policy and telemetry.
- Stars
- 0
- Language
- Rust
- License
- APACHE-2.0
- Reading time
- 2 min
- Published by
- Community
- Author
- christian-taillon
- Last verified
- Oct 2026
Highlights
- Reference analyzer.v1 extension for Telltale that asks Jev narrow typed questions defined in configurable guard packs.
- The model supplies only probabilities; the pack supplies category, severity, risk points and every threshold.
- Sits beside Telltale's deterministic rules instead of replacing them; Telltale keeps policy, telemetry and findings.
- The analyzer.v1 plugin is built and tested with 24 tests; the Telltale host side is only a proposed extension.
- Rust, Apache-2.0, created and pushed 2026-10-08 with 0 stars and 0 forks.
Watch out
README and GitHub metadata reviewed 2026-10-17; the captured excerpt cuts off inside the status table, so installation, guard-pack configuration, HTTP provider details and any evaluation results are not visible, and the host side is not implemented yet.
Questions about this entry
Short answers drawn from the linked project or page.
A reference analyzer.v1 extension for Telltale that asks a TypeSafe System One model (Jev) narrow typed questions about agent actions, with the questions defined in configurable guard packs.
The extension sends questions from guard packs to the System One API and receives probabilities; the model supplies only those probabilities, while the pack supplies the Telltale category, severity, risk points and every threshold, keeping the decision rules auditable.
No. The README states it sits beside Telltale's deterministic rules and does not replace them; Telltale keeps acquisition, privacy, identities, findings, policy and telemetry, with the analyzer producing a detector result of kind guard_model.
A configurable set of narrow, typed questions asked of the model about agent actions. The pack owns the category, severity, risk points and thresholds, so changing policy means editing the pack rather than retraining or reprompting the model.
Per the status table, the analyzer.v1 plugin is built and tested with 24 tests, while the Telltale host side that spawns, validates and converts results is a proposed extension not yet in Telltale, recorded as direction rather than accepted work.
The repository is Apache-2.0 licensed and written in Rust, created and pushed on 2026-10-08 with 0 stars and 0 forks; the captured digest shows no releases or benchmark numbers.
The captured excerpt cuts off inside the status table and the development-principles note, so installation, guard-pack configuration, the HTTP provider details and any evaluation results are not visible here.
Reactions & coverage
Posts, threads, and videos about this entry from around the web.
YouTube: Kubernetes admission control with a decision model, fail-closed.
Hacker News: SafeDep Gryph plus Jev checks for compromised coding-agent behavior.
2 pointsDetecting Compromised AI Coding Agents with Jev and GryphRead the thread on Hacker NewsX: Jev and Laya on security queries
X: Testing Jev for prompt injection
More Jev resources like this
An LLM-agnostic guardrail API built on Jev: it checks prompts and responses against YAML policies and returns PASSED, BLOCKED or FAILED. It sits between your app and any LLM provider, so guardrail decisions do not depend on the provider you call.
Jev Integrations & Adapters#community#github#guardrails
Community
alpkeskin/jev-guardrailGo
alpkeskin/jev-guardrailGoAgent governance integration where Jev judges two Noul checks per tool call (beyond scope, destructive), an admission policy decides which judgments may become evidence, and admitted evidence degrades Trust, Delegation and Authorization in persistent R2R relation state.
Jev Integrations & Adapters#community#governance#agent-security
Community
Thneoly/r2r-jevRust
Thneoly/r2r-jevRustA Kubernetes admission webhook that asks Jev to allow, flag, or deny a manifest change for intent-shaped policies a Rego rule cannot express, keeping hard rules in Rego and failing closed by default.
Jev Integrations & Adapters#community#go#kubernetes
Community
A Tauri desktop model router for AI agents: one local gateway at 127.0.0.1:9527 that manages providers and routing rules, converts between OpenAI and Anthropic protocols, and uses OpenRouter Jev to pick the model for each request.
Jev Integrations & Adapters#community#github#rust
Community
thinkany-ai/autojevRust
thinkany-ai/autojevRustAn open-source platform for creating, distributing, and running sovereign EU-compliant LLMs: one Rust binary with OpenAI- and Ollama-compatible APIs, decisions answered as probabilities in milliseconds, and an audit trail designed for the EU AI Act.
Jev Tools & CLIs#community#github#local-llm
Community
eullm/eullmPython
eullm/eullmPythonx402 risk-check provider that scores agent counterparties before payment: OFAC, phishing and drainer feeds, transaction simulation, drainer-kit fingerprints and a Jev model reading context for injected instructions, issuing an ES256-signed attestation per verdict.
Jev Integrations & Adapters#community#x402#payments
From the Jev guides
Original write-ups on what this entry is for.
From the Jev AI model community
Posts from builders shipping with Jev right now.