docs: revise M9-A0 trusted boundary contract - #113
Merged
Conversation
Signed-off-by: Jay Shen <shenjiecode@gmail.com>
This was referenced Aug 22, 2026
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
2026.4.14as the research target;before_prompt_buildandtool_result_persistfrom the trusted security boundary;TrustedModelCallBoundaryfor immutable Package/bootstrap admission before the provider request;TrustedToolExecutionBoundaryfor synchronous ToolResult spool closure before releasing a tool result;Scope boundary
This PR changes the canonical design only. It does not implement either boundary, change OpenClaw, or start M9-A. The revised M9-A0 spike must be rerun and reviewed before implementation.
Verification
git diff --checkRefs #112
Related: #110, #111