docs: note nostr cutover future work
This commit is contained in:
@@ -258,17 +258,21 @@ Interpretation:
|
||||
|
||||
## Remaining work
|
||||
|
||||
1. Create Ezra bot in BotFather
|
||||
2. Create Bezalel bot in BotFather
|
||||
3. Add both to the `Timmy Time` Telegram group
|
||||
4. Run `scripts/wire_wizard_telegram_bots.sh <ezra_token> <bezalel_token>`
|
||||
5. Restart Ezra/Bezalel services
|
||||
6. Prove distinct replies from:
|
||||
- Alexander
|
||||
- Timmy
|
||||
- Ezra
|
||||
- Bezalel
|
||||
7. Tighten provider-auth proof so both houses can answer directly with console-provable success
|
||||
1. Let Anthropic quota clear so Ezra can move from auth-correct to fully awake
|
||||
2. Decide whether Ezra should stay Anthropic-primary or gain a temporary fallback lane while quota is exhausted
|
||||
3. Preserve and harden service-level proof so both houses stay stable across restarts
|
||||
4. Future messaging cutover: move this wizard-house conversation layer off Telegram and into a private Nostr client with distinct identities for each agent
|
||||
|
||||
### Nostr future-work note
|
||||
|
||||
Future state to pursue:
|
||||
- Timmy gets his own Nostr identity
|
||||
- Ezra gets his own Nostr identity
|
||||
- Bezalel gets his own Nostr identity
|
||||
- communications move from Telegram dependence to an owned private Nostr client / relay pattern
|
||||
- wizard-to-wizard and operator-to-wizard traffic becomes sovereign, attributable, and non-platform-dependent
|
||||
|
||||
This future work has been recorded as a follow-on Gitea issue so it is not lost as mere chat context.
|
||||
|
||||
## Verdict
|
||||
|
||||
|
||||
Reference in New Issue
Block a user