feat(risk): bind owner preference after private P3 ingress - #292
Merged
Conversation
Co-Authored-By: Codex <noreply@openai.com>
Pigbibi
force-pushed
the
feat/risk-observation-ingress
branch
from
August 27, 2026 09:29
77e79ce to
f9095b3
Compare
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.
Summary\n- add a private, hash-bound long-horizon P3 observation contract\n- require an explicit owner risk preference before Composer input is built\n- keep raw return paths out of recommendations, console output, and AI context\n\n## Safety\n- no network, account, broker, policy-write, P4/P5/P6, or strategy-config capability\n- malformed/tampered observations fail closed\n\n## Verification\n- python3 -m unittest discover -s python/tests -q (232 passed)\n- git diff --check