Skip to content

rlippmann/context-compiler-example-integrations

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

3 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Context Compiler Example Integrations

What runtime behavior changes when authoritative state exists?

These examples demonstrate how Context Compiler's authority contract can influence runtime behavior across different AI pipeline stages.

Prompt reinjection influences model behavior.

Context Compiler influences runtime behavior.

Each example:

  • demonstrates a single runtime enforcement point
  • uses explicit authoritative state
  • remains meaningful with an adversarial model stub
  • focuses on the enforcement point rather than the framework

Ecosystem map

Repo Question
context-compiler What is the authority contract?
context-compiler-directive-drafter How is authority acquired?
context-compiler-example-integrations Where can authority be enforced?

Enforcement-point catalog

Enforcement Point Domain Technology
Gateway middleware Customer support routing LiteLLM Proxy
Schema selection Order / incident intake Ollama
Checkpoint continuation Travel booking FastAPI
Execution authorization Expense approval simple tool runner
Retrieval filtering HR policy / product docs Simple metadata-filtered retriever
Request construction / context assembly Writing assistant Open WebUI
Tool gating Calendar / email / admin MCP

How this repo is organized

Technology is secondary to enforcement point.

Examples are organized by enforcement point, not framework.

Python and TypeScript share the taxonomy. Implementations may differ by language.

There is no parity requirement between Python and TypeScript examples.

Python examples may arrive before TypeScript examples.

TypeScript examples may wait until the TypeScript directive-drafter split exists.

Repository boundaries

This repo is:

  • an examples/integrations repo
  • organized around runtime enforcement points
  • not a library/package repo
  • not the authority contract
  • not the directive drafter
  • not an acquisition-layer repo
  • not a framework showcase

Current layout

Contribution expectations

Primary examples in this repo should:

  • use explicit authoritative state
  • avoid deriving Context Compiler state from model output
  • remain meaningful with an adversarial stub
  • demonstrate observable runtime behavior changes

See CONTRIBUTING.md and AGENTS.md for repository rules.

License

Apache-2.0

About

No description, website, or topics provided.

Resources

License

Code of conduct

Contributing

Security policy

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors

Languages