docs: qualify sealed-channel status in README#39
Merged
Conversation
The sealed peer channel is described in the profile and how-it-works
sections as if payloads are already sealed to a verified attested
measurement, but LIMITATIONS.md states the enclave-measurement binding
is not yet wired on a live call ("do not assume a payload is confined
to a specific attested measurement"). Add the in-progress qualifier at
the point of claim and a status note on the how-it-works flow, so the
README matches LIMITATIONS.md and ROADMAP.md. Docs-only. (#38)
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.
The profile section and the how-it-works flow describe the sealed peer channel as if payloads are already sealed to a verified attested measurement (
README.md"decrypts only inside the verified enclave").LIMITATIONS.mdis more careful: the channel encryption is implemented, but binding the seal to a verified hardware measurement on a live inbound call is not yet wired ("do not assume a payload is confined to a specific attested measurement").This adds the in-progress qualifier at the point of claim and a short status note on the how-it-works flow, so the README matches
LIMITATIONS.mdandROADMAP.md. The detailed accounts inLIMITATIONS.md/ROADMAP.mdare already accurate and are unchanged; this only aligns the README's forward-looking statements. Docs-only.Closes #38
🤖 Generated with Claude Code