docs: the direct guardian of a member's wallet is built, and the notes it touched say so (Phase 7)

member-wallet-guarding-group.md is marked built, with a table of where
the build chose differently from the plan. The member-guarded-wallets
note's Phases 10 and 11 and the guardians note's How an ancestor finds
the coins point to it, and the README's reading order places it.

Still to do by hand: the signet run with three emulators.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Kgothatso NgakoandClaude Opus 5.5 committed 2026-10-24 12:10:14 +02:00
1 parent abb2c550ab
commit e15855faad
4 files changed
+37 -4

No files matched your search

+3
View File
@@ -63,6 +63,9 @@ takes the guardians note's derivation unchanged and gives the key path to one
person: read that note and the policy note's D2 first, then this note's table
of why a birth certificate will not do, its Phase 0, and its table of where the
build chose differently before the code.
The member-wallet-guarding-group note is a phased plan that has been built,
and changes what the member-guarded-wallets note's Phases 10 and 11 draw, not
what they verify: read those two phases first.
The subgroup-wallet-policy note is a phased plan that has been built. It
reads as the guardians note's *whose choice it is* reversed: read
that section, then this note's Phase 0, whose five decisions shape every phase
+6 -1
View File
@@ -343,7 +343,12 @@ needed one level at a time, not between the grandchild and the root directly.
Since [member-guarded-wallets.md](./member-guarded-wallets.md) the thing
forwarded may also be a member wallet certificate, which the guarding group
signed itself and so needs no forwarding into that group.
signed itself and so needs no forwarding into that group. Since
[member-wallet-guarding-group.md](./member-wallet-guarding-group.md) the notice
carrying one also carries, as a `certificate` tag, the guarding group's own
birth certificate, so a group above that was never in its room can name it.
Like the statement, the tag is checked rather than trusted, and an older build
ignores it.
Once it has the statement, the ancestor watches the descendant's addresses on the
Electrum client it already holds — unknown script hashes are ignored, so this
+8 -1
View File
@@ -760,6 +760,10 @@ replaces and settles.
The guardian side is built. What changes is what a guarded wallet can be.
[member-wallet-guarding-group.md](./member-wallet-guarding-group.md) later
gathered these rows by person and named, on each, the group that directly
guards the wallet.
### `GuardianManager.GuardedWallet` learns its subject
```kotlin
@@ -845,7 +849,10 @@ wallet for you*. An empty section with the button hidden is not shown at all.
There is a new section, **Wallets your groups guard**, listing every guarded
wallet this device knows of whose subject is that npub. These come from each
group's own certificates and from forwarded notices, so a root sees a
grandchild's member. Each row reads *Guarded by #Ekklesia*, with the amount within
grandchild's member. (Since [member-wallet-guarding-group.md](./member-wallet-guarding-group.md),
D7, there is one entry per wallet: *Guarded by* names the group that signed its
certificate, and each group here holding a leaf has a line of its own beneath.)
Each row reads *Guarded by #Ekklesia*, with the amount within
this group's reach, and *Spend* for a share-holder, which opens
`GroupSendRoute(chatRoomId = <the guardian room>, guardedChatRoomId = W)`, the
guardian spend that exists today. When the profile shown is the active one, the
+20 -2
View File
@@ -12,8 +12,25 @@ Read [member-guarded-wallets.md](./member-guarded-wallets.md) first, Phases 10
and 11 especially. This plan changes what those phases draw. It does not change
what they verify.
**Not built.** Written against `263a25a7`, schema v31. No phase needs a schema
change.
**Built**, phases 1-6, one commit each, written against `263a25a7`, schema v31;
no phase changed the schema. `GuardedWallet.directGuardianChatRoomId`,
`GuardianManager.foundingNameOf`, `GuardedWalletNoticeEvent.certificateIn`,
`byPerson` and `MemberWalletManager.byWallet` are the entry points. The phases
below are kept as written; where the build chose differently the table says so.
| what the plan said | what it turned out to be |
|---|---|
| D3, third source: 30331 notices told to *any* room here | only those told to the holding room, which `guardedWalletsOf` already reads. Reaching every room would have been a query by kind across rooms, the one new query the plan said it did not need |
| Phase 2: `foundingNameOf` | and `foundingCertificateOf` beside it, which returns the checked event: Phase 3 forwards the certificate, not the name |
| Phase 3, step 4: each told row paired with its own carried certificate, and the copy with one wins a fold | every certificate the room's notices carry is pooled, with the ones its 30331 statements embed, and offered to every wallet. Each is checked against the room and parent it would name, so one that certifies neither is never used, and the fold needs no tiebreak |
| Phase 3, not in the plan | *Tell the groups above* offers only guardians above the room it is shown from. It offered every guardian but that room, so a device in P and M was asked to tell M about M's own member's wallet -- found writing the two-hop test |
| Phase 5, step 2: `guarded_by_this_group`, `n_guarded_wallets` | noun phrases inside `guarded_by_s` -- `this_group`, `a_group_below_s`, `a_group_below_this_one` -- so the button descriptions can use the same phrase mid-sentence; `n_wallets`, since *2 guarded wallets, guarded by 2 groups* says it twice; and `s_comma_s` to join the two plurals |
| Phase 5, step 3: `guardedWalletName` gives `@alice · Savings` | every such sentence is *X's guarded wallet*, and *@alice · Savings's* does not read. A labelled wallet is *@alice's guarded wallet “Savings”*, an unlabelled one *@alice's wallet guarded by #M* |
| Phase 5, step 4: `displayName` becomes `@alice · Savings` | `displayName` is unchanged; `Spender.Guardian` gains `label`, and `ProposedSpend.guardedWallet` appends it the same way. The transcript's *The group signed …* line and the send form's title use it too |
| Phase 4: cards nearest first, then by guardian name | then by label as well, so two wallets under one group keep an order |
| Phase 6: `GuardedHereWallet(walletId, label, guardianName, holders)` | and `below`, the group it is known to sit below, for the line when no holder can name the guardian; with neither it is *another group*. `GuardedHere.guardianName`, which was the holder's room name, is now `holderName` |
Still to do by hand: Phase 7's run on signet.
---
@@ -416,6 +433,7 @@ a dimension. `readableContent()` is already on the list's root.
## Phase 7 — docs, the audit, and by hand
- **This note**: *Built*, plus a table of where the build chose differently.
Done.
- [member-guarded-wallets.md](./member-guarded-wallets.md): Phases 10 and 11 get
a pointer here. Phase 11's *Guarded by #Ekklesia* is changed to say that the
holder now appears on the holder's own line.