feat: add refund intake schema selection examples#14
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
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.
Summary
Adds generic refund-intake schema-selection examples for Python and TypeScript.
Both examples show a host application selecting a refund-intake workflow/schema from Context Compiler authoritative state, without relying on an LLM, prompt text, or model output.
Why
This fills the generic schema-selection enforcement-point example.
The examples demonstrate that schema selection is controlled by explicit compiler state: use refund_intake authorizes the refund workflow, while refund-like or adversarial request text alone does not select it.
Example metadata
Checklist
Notes
Validation run: