docs: producer-context hygiene — the three-class floor (closes #22) - #45
Merged
Conversation
The adapter-author half of the #22 commission; the normative half is the Privacy Considerations section in action-state-group/agent-action-capsule#35 (merged as #41). On any conflict, the profile text wins — this page says so up front. One page: the three admission classes as a table (clear-safe handles / digest-only payloads / never-enters identity+secrets, including as digests), the binding-not-naming class test, allow-list-as-code with the ADK adapter's _SAFE_CONTEXT_ATTRS tuple as the reference shape, the MCP adapter's documented client-software-only session reach as the one deliberate exception that proves the floor, and a five-question authoring checklist as the pre-ship audit. Original PR #26 (thisjody, fork context-hygiene branch) failed the neutrality gate solely because fork PRs don't receive the NEUTRALITY_TERMS secret by design. Rebased as this same-repo branch so the gate can actually run. Author credit preserved — content is Jody's own, unchanged. Signed-off-by: stevenmih <stevenmih88-3@gmail.com>
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.
Same-repo rebase of #26 (thisjody), which fails
neutralitysolely because fork PRs don't receive theNEUTRALITY_TERMSsecret by design. Content unchanged — author credit preserved.The adapter-author half of the #22 commission; the normative half is the Privacy Considerations section in action-state-group/agent-action-capsule#35, merged as #41. On any conflict, the profile text wins — this page says so up front.
One page: the three admission classes as a table (clear-safe handles / digest-only payloads / never-enters identity+secrets, including as digests), the binding-not-naming class test, allow-list-as-code with the ADK adapter's
_SAFE_CONTEXT_ATTRStuple as the reference shape, the MCP adapter's documented client-software-only session reach as the one deliberate exception that proves the floor, and a five-question authoring checklist as the pre-ship audit.Closes #22.
🤖 Generated with Claude Code