Skip to content

docs: explain the storage model and what is protected on disk today - #604

Open
andersalm wants to merge 4 commits into
developfrom
docs/storage-model-and-current-state
Open

andersalm wants to merge 4 commits into
developfrom
docs/storage-model-and-current-state

Conversation

@andersalm

Copy link
Copy Markdown
Contributor

Deepen notes

  1. Expert view: trace each store from write to recovery and state protection only where the code shows it; keep every limitation at least as strong as it was.
  2. Raw material: develop at 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).
  3. Methods: followed each store's path, write, encryption, key and export; compared the wording on develop with each round; mutation runs against the new test.
  4. Independent check: 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.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant