KCAE.Profiles:2.1 - A bounded Jev role

The TypeSafe interface takes a state and typed questions. It can fill a screening or classification role when inputs, meanings and subsequent operations are controlled. It does not replace source acquisition, explanation, deterministic calculation or final domain judgement. Model documentation describes English as the primary language and calls for testing other languages. Text-only inputs require an adequate prior transformation of a diagram or table. Treat version, limits, prices and availability as implementation inputs to verify at use, not durable properties of this framework.

The Jev 1.13 jaggedness account identifies sensitivities including negation, indirection, mathematical content, long irrelevant state and adversarial instructions. Give the assessor a focused state and explicit criterion, test the forms your cases use, and calculate exact arithmetic in code after semantic facts are obtained. A typed shape reduces parsing ambiguity; it is not an accuracy certificate. Keep retrieved instructions as untrusted source content, not a change to the assessor’s authority.

Use a generative reader when the task needs an explanation, missing-condition recovery, query construction or a new connection that the fixed questions cannot express. Use an appropriate specialist when interpretation or authority depends on that profession. Combine roles only when the receiving result and total cost justify them.