feat: add azure-cvm-sev-snp platform (v0.4.0)#105
Merged
Conversation
Azure confidential VMs run AMD SEV-SNP behind a Hyper-V paravisor: the SNP report is read from the vTPM and the guest does not control REPORT_DATA, so the runtime binding rides a vTPM AK-signed quote rather than the SNP report_data. Give it a distinct runtime.platform value so a consumer keying on runtime.platform knows the root of trust is vTPM-rooted, not direct-silicon. Adds the value to the RuntimeInfo model and both JSON schema enums, docs, and bumps the version to 0.4.0. Hardware-validated on a live Azure SEV-SNP VM via cMCP. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This was referenced Jul 21, 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
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.
Adds a distinct
azure-cvm-sev-snpvalue to theRuntimeInfoplatform Literal and the JSON schema enum, releasing as v0.4.0.Why
Azure confidential VMs run AMD SEV-SNP behind a Hyper-V paravisor. The SNP report is read from the vTPM and the guest does not control
REPORT_DATA(the paravisor binds the vTPM AK there), so the runtime binding rides a vTPM AK-signed quote rather than the SNPreport_data. Giving it its ownruntime.platformvalue (distinct fromamd-sev-snp) means a consumer keying onruntime.platformknows the root of trust is vTPM-rooted, not direct-silicon.This was hardware-validated on a live Azure SEV-SNP VM during the cMCP work (agentrust-io/cmcp#407), which previously mapped Azure onto
amd-sev-snpto avoid this release. With v0.4.0 published, cMCP switches to the distinct value.Changes
RuntimeInfo.platformLiteral + both JSON schema enums (src/agentrust_trace/schema/trace-v0.1.json,schema/trace-claim.json)Backward compatible (additive enum value). 89 tests pass locally.
🤖 Generated with Claude Code