Glossary: Signal
Signal is a typed Jev (System One) answer your code can consume: a noul, a Choice winner plus probabilities, or a Score expectation plus legend. It is not a generated “insight” sentence, not a chain of thought, and not an official TypeSafe response field named signal. You send state and a questions map to POST /v1/systemone; each question returns one atomic payload.
This glossary entry is for builders who already heard of Jev / System One and need a citable definition before they treat unused state fields as “features.” jev.pro is an independent unofficial field guide — not affiliated with TypeSafe AI. Confirm field names against docs.typesafe.ai. We do not sell or issue API keys.
How it shows up
Keep signals atomic. Ticket “priority” that secretly mixes severity, frustration, and engineer-readiness is three Scores, then a formula you own — see composite scoring on the Score primitive page. Log the full probabilities map: the top label hides close races. Unused state fields are not signals; they are billed input and can distract jev-1.13. Filter them before the call.
Choice returns choice, probabilities (sum to 1), and confidence. Score returns score (may be fractional), legend, probabilities, and confidence. Noul returns only noul in [0, 1] — no confidence. Question IDs are yours; TypeSafe says they are not used in inference. Write the complete question in instructions.
A signal becomes a verdict only after your threshold and action space run. Persist both in a decision trace. Schema-safe ≠ factually correct: a valid billing choice can still be the wrong team.
Contrast
Signal vs verdict. The signal is what Jev returned. The verdict is the allow / hold / block / route / abstain your service committed. Reviewers should be able to disagree with the policy without blaming the model for a rule you wrote.
Signal vs state. State is the text or JSON under evaluation. Signals are the typed answers. Facts belong in state; judgments belong in instructions and criteria.
Signal vs intent. Intent is a common Choice key for “what kind of request is this?” It is one kind of signal, not a synonym for every answer.
Signal vs generated insight. Jev does not write explanations. If you need a paragraph for a ticket, call an LLM after and label it generated assistance — never “Jev thought.”
Common mistakes
- Bundling three judgments into one Score and calling the blob “the signal.”
- Treating unused JSON fields as latent features. They bill and can hurt
jev-1.13accuracy. - Reading
answers.foo.confidenceon a Noul (undefined). - Asking Jev to emit an insight sentence into a typed slot.
- Skipping the full probability map in logs so close races look like landslides.
See also
FAQ
Is signal an official field?
No. Unofficial name for answer payloads on Choice, Score, and Noul.
Can unused state fields be signals?
They are input, billed, and can distract jev-1.13. Filter them.
One signal per HTTP call?
No. Batch independent questions in one questions map. Docs say extra questions cost tokens and barely change latency — a vendor description, not an SLA from this site.
Does a 200 mean the signal is true?
No. 200 means the request parsed. Judge against labels.
Limits
This is a jev.pro working definition unless TypeSafe uses the same word as an API field. We do not invent search volume. Schema-safe answers are not automatically factually correct.
Disclaimer
This is an independent unofficial site and is not affiliated with TypeSafe AI; official documentation is available at https://docs.typesafe.ai. Never treat jev.pro as TypeSafe official documentation. We do not sell, issue, or proxy API keys.