From f0de93554d29cb71470dfbfc8e94cf5a4c820b2f Mon Sep 17 00:00:00 2001 From: Alexander Whitestone Date: Sun, 29 Mar 2026 15:13:48 -0400 Subject: [PATCH] docs: note nostr cutover future work --- .../2026-03-29-wizard-houses-launch-report.md | 26 +++++++++++-------- 1 file changed, 15 insertions(+), 11 deletions(-) diff --git a/reports/production/2026-03-29-wizard-houses-launch-report.md b/reports/production/2026-03-29-wizard-houses-launch-report.md index 409b41e..c565abf 100644 --- a/reports/production/2026-03-29-wizard-houses-launch-report.md +++ b/reports/production/2026-03-29-wizard-houses-launch-report.md @@ -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 ` -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