Repository navigation
fix terminology within "Keys" mermaid diagram - #41
Merged
Merged
Conversation
There was a problem hiding this comment.
🟢 Approval recommended
The changes are limited to a documentation diagram, with only a minor legend correction remaining.
1 open issue
What changed in this PR
Updates the security architecture’s Keys diagram to clarify signing relationships and visually distinguish key types.
Changes:
- Corrects the trusted-public-key relationship from “decrypts” to “signs.”
- Simplifies trusted-key terminology and adds shapes for the Account Key and trusted public keys.
- Removes the dashed-border styling.
| File | Description |
|---|---|
docs/architecture/security.md |
Updates terminology, relationships, and styling in the Keys diagram. |
Review effort: Balanced
dkocher
approved these changes
Oct 23, 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.

as suggested in #29 (comment):
The user's private signer key is used to sign the public keys of trusted users.
also changed the shape of the "account key" and "vault recovery key", denoting that they are a potentially long-living "paper key".
flowchart TB subgraph keystore["Device keystore — locked/unlocked outside Katta"] devkey["Private Device Key<br/>Public Device Key"] end userkeys["Private User Key<br/>Private Signer Key"] accoukey["Account Key"]@{shape: paper-tape} membekey["Vault Member Key"] recovkey["Private Vault Recovery Key"]@{shape: paper-tape} trusted["Public Keys<br/>of trusted users"]@{shape: procs} uvf["vault.uvf payload<br/><i>Katta Server and S3 bucket</i>"] devkey -- decrypts --> userkeys accoukey -- decrypts --> userkeys userkeys -- decrypts --> accoukey userkeys -- decrypts --> membekey userkeys -- decrypts --> recovkey userkeys -- signs --> trusted membekey -- decrypts --> uvf recovkey -- decrypts --> uvf