Repository navigation
Conversation
wolfy-j
marked this pull request as ready for review
October 7, 2026 22:25
skhaz
approved these changes
Oct 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Applications can evaluate predicates, fixed choices, and ordinal scores through OpenAI's Decisions endpoint using the existing
llm.evaluate(state, questions, options)interface. The native OpenAI driver now implements the evaluator contract and reuses its credentials, HTTP transport, retry policy, and error classification.The adapter sends text or JSON evidence to
/v1/decisions, uses opaque question names, and maps answers back to caller slots. It converts OpenAI's zero-based scores to the existing one-based reading contract while preserving full distributions and separate confidence. Refusals fail the whole evaluation; incomplete or malformed answers cannot return successful partial readings. Unsupported generation options fail explicitly. Usage counters retain disjoint input/cache categories and raw provider usage for accounting. A small client guard converts scalar/null JSON responses into errors before metadata attachment.The README documents direct calls, model discovery, predicate criteria, score meaning, refusals, supported inputs/options, endpoint-specific pricing, and the dedicated live-test flag. This integration supports text/JSON evidence; typed image inputs require a future contract extension. The official API is currently beta with
gpt-6-lunasupport. References: guide, API reference.Validation: full LLM lint passes on signature-verified Wippy 0.3.45a (125 entries), module manifest checks pass, package dry run passes, and Astra source review found no code blockers. All CI checks pass, including the full 1,632-test LLM suite (run). New tests cover mapping and malformed/refused responses, usage consistency, HTTP retries, facade/model routing, and native versus compatibility contract binding. Live API tests are opt-in and have not been run; no paid API calls were made.