Skip to content

feat: add refund intake schema selection examples#14

Merged
rlippmann merged 3 commits into
mainfrom
schema-selection3
Jun 28, 2026
Merged

feat: add refund intake schema selection examples#14
rlippmann merged 3 commits into
mainfrom
schema-selection3

Conversation

@rlippmann

Copy link
Copy Markdown
Owner

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

  • Enforcement point: schema selection
  • Domain: refund intake / customer support routing
  • Technology/runtime: Python runtime and TypeScript runtime
  • Example type: minimal example
  • Does this use directive drafter? should normally be no: no
  • Does this derive state from model output? must be no for primary examples: no

Checklist

  • Repository scaffolding / governance change
  • One primary enforcement point
  • Explicit authoritative state
  • No model-derived state mutation
  • Adversarial stub or equivalent test
  • Observable runtime behavior change
  • Domain vocabulary is natural
  • Framework is secondary to the enforcement point
  • Docs updated
  • Tests/smoke checks added where practical

Notes

Validation run:

  • uv run pytest python/tests/test_refund_intake_example.py
  • npm test from typescript/examples/schema_selection/refund_intake

@rlippmann
rlippmann merged commit 97dc5cf into main Jun 28, 2026
5 checks passed
@rlippmann
rlippmann deleted the schema-selection3 branch June 28, 2026 04:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant