KEEP BESIDE AN API PROPOSAL

The words we are using

Each term names a different responsibility in the library or its caller.

Term	Meaning here	Concrete example
Primitive	A basic model operation that other behavior composes.	Noul, Choice, or Score.
State	The content a model evaluates.	A command and the user's intent.
Question / answer	The judgment requested / the values returned.	A risk predicate / its estimated probability.
Rubric	Ordered descriptions defining the levels of a Score.	Incomplete → usable → complete.
Ergonomics	How clear, convenient, and hard to misuse an interface is.	The editor knows the selected value is a `Team`.
Convenience API	A reusable interface that packages common work.	An assessment function that builds several questions.
Syntactic sugar	Shorter syntax with an equivalent underlying meaning.	Python's decorator notation.
Abstraction	A boundary that exposes useful operations while hiding their implementation details.	`Jevaluator` handles SDK execution and answer validation.
Batch	Several independent questions sharing one state and one logical API call.	Score one draft for relevance and clarity. SDK retries may make more HTTP attempts.
Fan-out	Run independent evaluations over different inputs, with explicit concurrency.	Evaluate a collection of documents.
Policy / workflow	A rule for what action to take / the sequence of evaluations and actions.	Review high-risk commands; rank candidates, then inspect a shortlist.
Backend / adapter	The engine performing an evaluation / a translator to its interface.	Jev / code that sends Jev's request format.
Probability / confidence	An outcome estimate / the provider's distribution summary.	Keep both values; do not substitute one for the other.
Static typing / validation	Check caller code before execution / check actual values at runtime.	Reject an incorrect answer attribute / reject an unrequested option.