Repository navigation
Add optional decision-model family schema - #16
Merged
Merged
Conversation
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
1 participant
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.
The catalogue cannot distinguish a bounded decision offering from chat generation. Add optional
decision.modelswith an explicit underlying model identity and independently sourced provider contracts. Existing version 1 snapshots remain valid and generate byte-for-byte unchanged until a decision card is authored.The additive
decision_contractrecords each provider's actual question vocabulary, input forms, typed-choice behavior and documented bounds. Decision cards reject inherited chat-only fields. The checker validates source URLs and inverted bounds; provider contracts and prices remain independent.This is the schema/tooling portion of #15. Model data will be a separate dependent PR. The field design is grounded in the OpenAI native Decisions reference, Vercel's compatible Decisions contract, and OpenRouter's distinct Decisions contract; no provider behavior or price is added in this PR.
Validation: catalogue build/check, all 287 pytest checks, pinned formatter and complete diff review pass. Tests cover omission of the optional family, source-to-contract generation, provider bindings, sourced bounds and rejection of accidental chat fields.