Repository navigation
Conversation
Built-by: Codex
Built-by: Codex
Built-by: Codex
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.
Deepen notes
b8a3e111b;elastos/crates/elastos-server/src/auth.rs:6190(encrypted file envelope),elastos/crates/elastos-server/src/api/auth_gateway.rs:1825(Recovery Kit export),capsules/system/browser/system.js:2827(the download control).scripts/storage-documentation.test.mjs, 5 tests. A wrong Recovery Kit coverage cell and a second name for the Kit each fail it. A wrong "encrypted" cell in another row does not (a reviewer's mutation run showed this), so the table still depends on review. Reviewed in four rounds by a different model family (Claude Opus): fail, pass with notes, pass with notes, pass.Change
Documentation only, plus one test. No behaviour changes.
docs/STORAGE_AND_ACCESS.mdopens with the model in plain words: two kinds of data (finished things and living things), five building blocks (working copy, revision, head, key, replica), and the rule that a fingerprint (CID) names a saved revision, never a store that is still changing. The target and today's behaviour are kept apart.SECURITY.mdgains a dated table of what is on disk today, store by store: where it is, whether it is encrypted, with which key, and whether the Recovery Kit covers it. It states that keys are stored next to the data they protect and who can therefore read a person's data, including a host at any time.docs/GLOSSARY.mdanddocs/INSTALL.mduse one name, Recovery Kit, for the one file System downloads, and link to the table instead of repeating it.Not verified: nothing was built or installed. The table rows come from reading the source. The test checks path parts, the Browser protection flags, the export fields and the Kit's name; it does not check encryption at run time.
Refs #567, #210, #603.