docs: reconcile adaptive-context bundle with the protocol spec (#27) - #61
Merged
Conversation
Draw the protocol/product boundary and classify every delta from the adaptive-context bundle (stella context-frame-spec.md / directive-schema.md / CGP build prompt; oxagen docs/specs/adaptive-context) against the CGP spec. - ADR 0007: the protocol/product boundary. The bundle's task-wide `ContextFrame` is the host-owned `CompiledContextFrame`, not the protocol's atomic `ContextFrame`. Records what the protocol owns vs. what hosts/providers own; keeps frames as evidence (not directives) while leaving the #28 exchange profile free to carry directive *records*; rejects the CGEP rename — canonical name stays Context Graph Protocol (CGP) / contextgraph/1.0-draft. - adaptive-context-reconciliation.md: the delta table for #27. Each item is adopt-upstream / push-downstream / reject, routed to a spec change or a normative-track issue (#49, #28, #5, #50, #12, #10; #6 unchanged). Claude-Session: https://claude.ai/code/session_01NGCCkBsqCdJiNvFBHQKgyw
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
There was a problem hiding this comment.
Sorry @macanderson, you have reached your weekly rate limit of 500000 diff characters.
Please try again later or upgrade to continue using Sourcery
) Add an explicit coverage row for every issue in the #5-#13 range #27 names, including the ones the bundle does not touch (#7 graph, #11 query filters, #13 HTTP auth) and the ones already closed by prior work (#8 token_cost), so 'every adopted item is routed' is verifiable at a glance. Claude-Session: https://claude.ai/code/session_01NGCCkBsqCdJiNvFBHQKgyw
macanderson
marked this pull request as ready for review
July 24, 2026 03:19
There was a problem hiding this comment.
Sorry @macanderson, you have reached your weekly rate limit of 500000 diff characters.
Please try again later or upgrade to continue using Sourcery
macanderson
enabled auto-merge (squash)
July 24, 2026 03:19
macanderson
disabled auto-merge
July 24, 2026 03:19
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.
Closes the analysis half of #27: draws the protocol/product boundary and classifies every delta from the adaptive-context bundle against the CGP spec.
What's here
ContextFrameis the host-ownedCompiledContextFrame, not the protocol's atomicContextFrame— the name collision is the root of the drift. Records what the protocol owns vs. hosts/providers; keeps frames as evidence (not directives) while leaving the P1: Specify the Context Exchange Provider profile #28 exchange profile free to carry directive records; rejects the CGEP rename (canonical name stays Context Graph Protocol (CGP) /contextgraph/1.0-draft).Disposition
as_of). Specify subscribe (staleness push / frame invalidation) or drop it before the freeze #6 unchanged.as_of_*field names; portableproject_id; policy-executing operations.Enforcement
Structural: normative frame text lives in exactly one place; downstream docs (stella, oxagen) hold only a pinned
NORMATIVE-HOME:pointer, landing in companion PRs. The downstream canary (#29) guards the code side.Does not touch the frozen 1.0 core, publish crates, or cut a tag (pre-freeze).
https://claude.ai/code/session_01NGCCkBsqCdJiNvFBHQKgyw