Skip to content

Park M5 as issues; status #168

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
lannbot merged 1 commit into from
Sep 7, 2026
Merged

Park M5 as issues; status #168

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -41,5 +41,6 @@ automerge document synced between devices over subduction and the iroh
relay; pairing by code + SAS into a device group that is the sync policy;
app content sealed as keyhive/BeeKEM envelopes; Google Drive as a dumb
ciphertext store (OAuth split between kernel and shell; a fake Drive in
e2e). Next: passkey unseal and recovery (M5). The settings UI is deliberately minimal
pending a redesign.
e2e); app history rolled up as sedimentree fragments. Passkey unseal
(#166) and recovery kits (#167) are parked as issues. The settings UI is
deliberately minimal pending a redesign.
5 changes: 3 additions & 2 deletions docs/design.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -484,8 +484,9 @@ native tests, so browser gates are mandatory for every visor change.
destination egress, the picker) waits for a second provider: one
backend does not justify a boundary. S3 is deferred; Drive is what a
person has.
- **M5** passkey PRF rung, recovery kits, Drive provider.
- Parked: app worker (above); native shell; JS producers.
- Parked, as issues: the passkey PRF unseal rung (#166), recovery kits
(#167); app worker (above); native shell; JS producers; S3 and the
provider component boundary (a second provider).

## polyengine is consumed from JSR

Expand Down