feat: add prompt construction examples#21
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 Python and TypeScript prompt-construction examples.
The examples demonstrate that Context Compiler authoritative state influences host-owned prompt assembly. The host constructs prompts from explicit authoritative state, while Context Compiler owns the state that determines which prompt guidance is applied.
Why
Prompt construction is a distinct enforcement point.
These examples show that prompt content changes because authoritative state changes, not because of user requests embedded in the current message. The host assembles prompts before any model call would occur.
The examples use a writing-assistant domain with style preferences to demonstrate observable prompt construction behavior.
Example metadata
Checklist
Notes
Both implementations demonstrate:
The examples intentionally stop at prompt construction. No model call is performed. This keeps the enforcement point focused on host-owned prompt assembly rather than model compliance or generation quality.
TypeScript validation scripts were updated so the new example participates in repository validation.