Choose supplied copy that matches your brand voice
Supply a voice brief, required facts and three candidate sentences. Select a fitting option, or reject all when none preserves the facts and mandatory rules.
Select a sentence against a concrete voice briefLive API
The decision
A good sentence still has to be true.
A sentence can sound right and still change the message. A friendly refund notice with the wrong amount is not a valid rewrite. This exercise gives Jev three existing candidates, a factual brief and a voice policy. It returns A, B, C or Reject all. The model does not generate replacement wording.
The source post describes a larger loop in which another model proposes rewrites and Jev selects among them. Here we isolate the selection step so you can inspect the exact text and change the brief. The six writing tasks are original synthetic examples, not the author's private voice samples or evidence that the full loop improves writing.
A useful brief separates mandatory facts from stylistic preferences. Put deadlines, amounts, product availability and known uncertainty in the first group. Then specify the audience and a few observable style rules. Plain wording is a preference; preserving a refund amount is a requirement. When those conflict, the requirement wins.
Mailchimp's voice and tone guide distinguishes a relatively consistent voice from tone that changes with the reader's situation. We use that distinction as editorial context, not as a claim to reproduce its brand. An outage notice should suit a frustrated customer even when everyday product announcements sound more upbeat.
AI-generated concept illustration of a note-to-evidence comparison; not a real repository analysis.
How it works
Choose a sentence in four steps.
Give factual requirements priority over style preferences.
01
Write the brief
Name the audience, mandatory facts and a few concrete voice rules.
02
Supply candidates
Keep three distinct sentence options labeled A, B and C.
03
Inspect the choice
Read the leading label and competing probabilities, including Reject all.
04
Review the final copy
Map the label back to its original text and verify facts before publishing.
Our API test
Six candidate sets tested through the API
Six candidate sets tested through the API
Writing brief
Observed label
Leading probability
Plain shipping notice
A
99%
Calm outage update
B
99%
Specific product update
C
98%
Every option changes a fact
Reject all
98%
Candidate contains an instruction
B
98%
Every amount is wrong
Reject all
99%
Six live Jev requests on September 27, 2026. Original synthetic functional checks, not an accuracy or speed benchmark. Fresh distributions may differ.Verified
Understand the results
In an application, map the returned label back to the unchanged candidate string from that request
In an application, map the returned label back to the unchanged candidate string from that request.
Read the example notes
Store the brief version, candidate IDs, required facts, selected label and probability distribution together. This prevents a later rewrite of candidate B from silently changing what an earlier selection meant. The demo displays a decision; it does not save or publish copy.
Calm outage update
For Reject all, ask an editor or a separate writing tool to propose a new set that preserves the facts.
Read the example notes
For a close distribution, show the alternatives for review. The highest probability is a ranking under the supplied question, not a measured likelihood of campaign success or proof of factual accuracy. A human still verifies the final message before publication.
Source and example scope
The table records one live API response for each synthetic brief.
Read the example notes
These checks cover an outage, a shipment notice, a product update, changed deadlines, quoted instructions and incorrect refund amounts. They do not measure general writing quality, authorship detection or resistance to every prompt injection. Fresh calls may return different probabilities.
Using the result in your application
Download the exact fixture and runner below.
Read the example notes
With Node.js 24, install @typesafe-ai/sdk@0.6.0 and set TYPESAFE_API_KEY privately in your server or shell. Run node run-choice-sample.mjs observed-voice.json deadline to send one request. The script performs no retries and logs the response with elapsed time. Do not place your key in browser code or in a public fixture.