jev-system-one-reference
Independent Markdown reference on the Jev API, patterns and limits, written for engineers and coding assistants to build from.
This repository is mostly documentation or write-up rather than runnable code.
Overview
Jev / System One Reference is a documentation repository maintained by Sebastian Bennis, not an official TypeSafe publication and not an application, SDK or service. Its main file covers the Jev API, implementation patterns, known limitations, a source catalogue and an unpopulated project handover template.
The intended workflow is to attach the reference to a coding-assistant session, supply a project brief and existing files, and ask the assistant for an implementation, verification and an updated handover that separates completed work from planned work. The README stresses that naming a file or sharing a URL does not mean the assistant has read it, and that the worked examples (such as a support-ticket router returning a team, urgency judgement and review status) are prompts, not evidence of a tested integration. It describes Jev as accepting text or structured state for typed judgements, not generating code, conversation or audio.
What the decision model decides
| Type | Question | Answers |
|---|---|---|
| Other | Reference material on designing Jev Choice, Score and Noul questions (worked example: team, urgency and review status for a support message) | — |
How it works
- Attach the reference file to an assistant session
- Provide a project brief and current files
- Assistant implements Jev calls following the reference
- Assistant verifies and updates a private handover file
Strengths
- Single self-contained reference for assistants
- Explicit about limitations and what Jev cannot do
- Handover template for continuity across sessions
Caveats
- Documentation only; no code or tests
- Independent and may lag official docs
Getting started
Start with Jev_System_One_Reference.md and attach it to your coding assistant session.At a glance
- Type
- Service
- Has code
- no
- Has tests
- no
Use cases and integrations
How curated lists describe it
Independent Jev / System One reference with API examples, implementation guidance and reusable prompts for engineers and coding assistants.
hellogumbo/awesome-jev
Frequently asked questions
Is this official TypeSafe documentation?
No. It is an independent reference maintained by Sebastian Bennis.
How should I use it with an AI assistant?
Attach the Markdown file directly, give a project brief, and ask for implementation, verification and an updated handover.
Does it include working code?
No. The prompts and brief are worked examples, not a tested integration.
Related projects
Claude skill that gives a ten-line gut-check on whether Jev could help with what you are building, citing tested patterns.
Agent skillbetaMarkdownThirty worked Jev uses in ten levels, from a smart if statement to a pi coding agent that writes its own Jev questions.
ProjectbetaTypeScriptAgent skill that makes a coding agent try Jev first for bounded judgments like classify, rank or gate, and log each attempt.
Agent skillbetaPythonAccenture thought piece and site on stack migration with Google Cloud, placing Jev as the System 1 layer that routes, classifies and gates.
MCP serverdiscussionRustCommunity directory of Jev apps, resources and runnable offline examples, with a guide skill and a searchable JevList web UI.
ArticleproductionTypeSafe's official cookbook for a two-stage skill-suggestion workflow that selects a skill and can reject the shortlist.
Articleproduction