docs(tee): clarify in-tree appraisal is aTLS fallback, not primary gate#398
Merged
Conversation
docs(tee): clarify in-tree appraisal is aTLS fallback, not primary gate Record the layering intent for NRAS post-attestation appraisal: when cMCP is composed with a platform that attests in the aTLS handshake, the platform verdict is authoritative and the in-tree path stands down. It remains the standalone fallback for deployments with no aTLS peer. Docstring-only. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.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.
@
What
Two-line addition to the
try_appraisedocstring intee/nras.pyrecording the layering intent for NRAS post-attestation appraisal.Why
When cMCP is composed with a platform that performs attestation in the aTLS handshake, the platform verdict is authoritative and the in-tree appraisal path stands down. It stays as the standalone fallback for deployments with no aTLS peer. Nothing in the repo said this, so the note stops anyone from later treating the opt-in/non-fatal NRAS path as the enforcing gate.
Scope
CMCP_NRAS_API_KEY).🤖 Generated with Claude Code
@