TypeSafe / Jev

Verified against TypeSafe's official documentation on 20 September 2026. These are concrete contracts, not a claim of certification or universal best practice.

• Introduction: independent, atomic questions share a state and are composed by code. Taste-lint keeps one rule per judgment and batches independent questions. Request sharing never merges source provenance.
• Noul: the number is the probability of yes. It is not severity, a quality score, or the separate confidence field returned by other primitives. A high value must mean the named condition is present; an advisory styling judgment is not proof of a defect. The report preserves individual probabilities before presentation grouping.
• How to build: deterministic work stays in code. State supplies relevant context. Applicability, counting, thresholds, and fixes remain deterministic. Existing labelled text state is retained to preserve cache semantics. Changing it to structured state needs an evaluation and a deliberate cache invalidation, not a cosmetic migration.
• Confidence: action thresholds depend on the domain and stakes. Jev rules stay review-only until the existing corpus/tuning gate supports promotion. The diagnostic agent-labelled sample is not enough evidence to change thresholds.
• API reference: direct requests use POST /v1/systemone and bearer authentication. The adapter validates probabilities and usage, retries 429 and 529 with bounded backoff, and does not retry authentication errors. Tests cover overload, malformed responses, and attempts. Provider bodies and credentials are never persisted.

The Vercel gateway is a separate transport contract. TypeSafe's direct API docs do not certify the gateway's evaluation route. The existing adapter and its wire-format tests remain the owner. No new SDK or provider dependency was added.

Run contract

Preparation decides applicability once. Execution consumes the prepared work, consults the answer cache, and reports outcomes. Both lint and eval use this seam. Skipped checks never become negative labels. Unknown means an applicable check could not be resolved. It is not a pass.

summary.failing is computed from complete rule findings, severity, and fail-on policy. Text and exit codes consume that result. JSON v1 retains grouped and the legacy . Additive , , and expose the complete evidence and eligible denominators. SARIF contains all unsuppressed rule findings.