docs: the Marmot v2 rollout is done -- new rooms on the current profile, the legacy slot retired (v2 Phase 9)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
01da88ce97
commit
f90506aaba
2 files changed
+34
-12
No files matched your search
+1
-1
@@ -33,7 +33,7 @@ the [retired](./retired/) notes now.
|
||||
| [jvm-target.md](./jvm-target.md) | what desktop support cost, phased — why the native chain was already done, why an empty source set in our phoenix fork was the real blocker, and why DAO tests need none of it |
|
||||
| [npub-profile-preview.md](./npub-profile-preview.md) | showing the person before a direct message is started from a pasted npub — why the preview is a screen keyed by public key, what "found" means when a row can be a placeholder, and the phase that makes the button honest about a key package that never comes |
|
||||
| [material-design-conformance.md](./material-design-conformance.md) | what the M3 foundations actually require, measured against all 43 screens — the colour pairing that renders the app's own proposals invisible, and eight phases that put the decisions back in the theme |
|
||||
| [marmot-v2.md](./marmot-v2.md) | bringing the group layer onto the Marmot current profile after the quartz 1.15.2 bump — the nine rules that reach this app, why the room's id and the routing id have to become two values, nine phases from reading both profiles to publishing before applying, and the one fork the library cannot yet settle |
|
||||
| [marmot-v2.md](./marmot-v2.md) | bringing the group layer onto the Marmot current profile after the quartz 1.15.2 bump — the nine rules that reach this app, why the room's id and the routing id have to become two values, nine phases from reading both profiles to publishing before applying, the rollout that put new rooms on the current profile and retired the legacy KeyPackage slot, and the one fork the library cannot yet settle |
|
||||
| [marmot-kmp.md](./marmot-kmp.md) | moving the group layer off quartz's engine and onto marmot-kmp, mls-kmp and crypto-kmp — why staying on quartz 1.15.2 is staying on an engine that left, the 228 import lines and the one rule that places all but two of them, the group state on a device that must still open afterwards, nine phases that put the swap in one commit and the evidence around it, how often this app persists a group once a sent message no longer rewrites it, and the schema change that followed, opened from the version the app ships |
|
||||
| [giza-wallet-removal.md](./giza-wallet-removal.md) | taking every wallet out of Giza, phased and built but for moving off the wallet library (7b). Covers why a Giza member declines a Bennu peer's wallet proposal instead of ignoring or signing it, why the wallet's kinds are retired rather than freed, why a recovery phrase stays as a key backup that has to derive the same npub and id byte for byte, and why the threshold crypto keeps the build tied to the wallet library until the last phase |
|
||||
| [member-admin-promotion.md](./member-admin-promotion.md) | making a member an admin and back, phased and built, promotion with a share and demotion with a refresh under the experimental enrollment, under three rules: every admin holds a share, every commit in a keyed room is a proposal until the group's threshold signature is on it, and a robust group keeps at least three admins. Covers why the commit rides inside the group's signature and the rule inside the group's state, which lets every device refuse an unsigned commit with the libraries as they are, why a member's own leave stays exempt, and why a removed admin comes back as an admin when re-invited today |
|
||||
|
||||
+33
-11
@@ -15,9 +15,10 @@ invite race the current pipeline has, which v2's publish rule is the real fix fo
|
||||
The second explains why a room's id *is* a key -- and that is the thing v2's routing
|
||||
rule is about to collide with.
|
||||
|
||||
**Built**, phases 0-8, one commit each and three follow-ups where a phase's commit
|
||||
had left a line of its own phase unbuilt; Phase 9 is the rollout and is process
|
||||
rather than code, and where it stands is noted at its end. The phases are kept as
|
||||
**Built and rolled out**, phases 0-8, one commit each and three follow-ups where a
|
||||
phase's commit had left a line of its own phase unbuilt; Phase 9, the rollout, is
|
||||
done -- new rooms are made on the current profile and the legacy KeyPackage slot is
|
||||
retired -- and what that took is noted at its end. The phases are kept as
|
||||
written because they are the reasoning, and the code reads better against the
|
||||
argument it came from than against a summary of itself. It is deliberately ordered
|
||||
so that the phases that buy interoperability with other v2 clients come before the
|
||||
@@ -422,7 +423,8 @@ transition, because an old build of this app decodes kind:30443 content as a bar
|
||||
KeyPackage and would otherwise be unable to invite anyone who upgraded. The
|
||||
current-profile leaf also advertises `0xF2EE`, so a *new* build can be invited into
|
||||
a legacy room with either package; the second slot exists purely for old inviters
|
||||
and is retired in Phase 9.
|
||||
and is retired in Phase 9. *It has been: the app publishes the current-profile
|
||||
package alone, `MarmotProfile.PUBLISHED`.*
|
||||
|
||||
One wrinkle decides the publish order. `MarmotKeyPackageDao` hands an inviter the
|
||||
peer's *newest* package by `created_at`, and an old build does exactly that and
|
||||
@@ -527,7 +529,7 @@ One constant, `MarmotProfile.DEFAULT_FOR_NEW_ROOMS`, legacy until Phase 9 flips
|
||||
and read only by the two creation sites. A current-profile room can only ever hold
|
||||
Phase 3 builds, so flipping the constant is the moment this app's users stop being
|
||||
able to make rooms for members who have not upgraded -- which is why it is the last
|
||||
act of the rollout and not part of this phase.
|
||||
act of the rollout and not part of this phase. *Phase 9 has flipped it.*
|
||||
|
||||
### Refusals at the add step
|
||||
|
||||
@@ -851,12 +853,32 @@ the first current-profile room a user creates (Phase 4 flipped; it can never hol
|
||||
an old build), and the envelope (Phase 2; a legacy room that ever sends one has a
|
||||
member who cannot read it, which is why it never does).
|
||||
|
||||
**Where it stands.** Everything above ships built and unflipped:
|
||||
`MarmotProfile.DEFAULT_FOR_NEW_ROOMS` is `LEGACY`, both KeyPackage slots are
|
||||
published and kept, and no room this app has made is on the current profile
|
||||
unless a caller asked for one by name -- the tests do; the creation screens do
|
||||
not. The first door is behind us the moment a build with the bump runs. The
|
||||
other two wait on the flip, which waits on the people this app's users invite.
|
||||
**Where it stands.** Done, both steps, on 2026-11-20.
|
||||
|
||||
- **The flip.** `MarmotProfile.DEFAULT_FOR_NEW_ROOMS` is `CURRENT`. Every creation
|
||||
site -- a direct message, a convenient room, a keyed room and its subgroups -- makes
|
||||
a current-profile group, and the pickers ask a peer for their current-profile
|
||||
package. Rooms made before stay legacy, as the plan said they would: the
|
||||
governance in [member-admin-promotion.md](./member-admin-promotion.md) reads the
|
||||
current profile's admin policy, so a room that wants it is a new room.
|
||||
- **The retirement**, without the thirty days. `MarmotProfile.PUBLISHED` is the
|
||||
current profile alone; `KeyPackageEvent.build` has no caller and the legacy leaf
|
||||
builder is gone from `DatabaseMarmotRepository`, which refuses to be asked for a
|
||||
legacy package rather than skip it. The notary republishes only what `PUBLISHED`
|
||||
names, so a legacy bundle still active from before is left to be consumed and is
|
||||
not replaced. Not waiting a KeyPackage lifetime was the project's call, and its
|
||||
cost is old inviters: Bennu carries phases 0-8 as well, so a current Bennu build
|
||||
invites and is invited as before, but a build of either from before Phase 3 can no
|
||||
longer invite this app's users once their last legacy package is consumed.
|
||||
|
||||
What a legacy room still does without the slot: it invites with the current-profile
|
||||
package, which advertises `0xF2EE`. `RobustGroupAdminsJvmTest` runs its legacy-room
|
||||
cases that way -- every phone publishes the one package the app does, and joins a
|
||||
legacy room from it.
|
||||
|
||||
The three doors are all behind us now. A build before Phase 3 can be neither
|
||||
invited into a room this app makes nor invite this app's users into one of its own,
|
||||
and it is told so at the add step.
|
||||
|
||||
---
|
||||
|
||||
|
||||
Reference in new issue
Block a user