docs(arch): Mermaid diagrams for DeRoT key issuance, VM upgrade, and trust verification#32
Open
docs(arch): Mermaid diagrams for DeRoT key issuance, VM upgrade, and trust verification#32
Conversation
cl4wb0t
force-pushed
the
more-deployment-docs
branch
2 times, most recently
from
2ae0294 to
9dbf34a
Compare
…and trust verification Three new architecture docs in architectureDocs/deployment/: - derot-key-issuance.md — sequence diagram of how a CVM obtains its keys from Onchain KMS (DstackApp + DstackKms contracts on Base) - vm-code-upgrade.md — flowchart of the full upgrade lifecycle: build, governance whitelist approval, deploy, and key issuance for the new code - trust-stack-verification.md — four-layer trust model (Application, Platform, Network, Governance) with both a layer overview diagram and a detailed verifier sequence diagram; includes the full VR-1–VR-4 checklist Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
cl4wb0t
force-pushed
the
more-deployment-docs
branch
from
9dbf34a to
8c813fe
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
derot-key-issuance.md— sequence diagram: CVM boot → TDX attestation → Onchain KMS verifies quote + DstackKms OS whitelist + DstackApp compose-hash whitelist → keys issuedvm-code-upgrade.md— flowchart: build new image → compute compose-hash → governance tx to whitelist on DstackApp → deploy → new CVM boot → key issuance (blocked if whitelist not in place)trust-stack-verification.md— two diagrams: (1) four-layer trust model overview (Application / Platform / Network / Governance), (2) detailed verifier sequence (fetch attestation from/.dstack/, Intel DCAP quote check, Base contract checks, TLS/evidence/CAA checks); plus the full VR-1–VR-4 checklist tableAll diagrams reference existing requirements in
planning/requirements.mdandplanning/PLAN.md.Test plan
🤖 Generated with Claude Code