From 5fc82894361a53c021e0c072438c43892c7d4969 Mon Sep 17 00:00:00 2001 From: archipelago Date: Thu, 6 Aug 2026 11:07:36 -0400 Subject: [PATCH] capture: Routstr funding UX in AIUI dropdown (operator request) Co-Authored-By: Claude Fable 5 --- .../2026-08-06-routstr-funding-ux-in-aiui.md | 35 +++++++++++++++++++ 1 file changed, 35 insertions(+) create mode 100644 .planning/todos/pending/2026-08-06-routstr-funding-ux-in-aiui.md diff --git a/.planning/todos/pending/2026-08-06-routstr-funding-ux-in-aiui.md b/.planning/todos/pending/2026-08-06-routstr-funding-ux-in-aiui.md new file mode 100644 index 00000000..fa6369d9 --- /dev/null +++ b/.planning/todos/pending/2026-08-06-routstr-funding-ux-in-aiui.md @@ -0,0 +1,35 @@ +--- +captured: 2026-08-06 +source: operator, during 13-14 test prep on dev3 +area: aiui + neode-ui + core (assistant.budget-*) +--- + +# Routstr funding UX in AIUI's provider dropdown + +Operator request, verbatim intent: Routstr should appear in the AI-provider dropdown in AIUI +itself; picking it (or a "fund" affordance next to it) surfaces funding options **in the chat**, +all funding options usable, with status updates in the chat. + +Sketch of what exists to build on: +- Backend: `assistant.budget-get`/`assistant.budget-set` RPCs (13-13); allowance is the D-05 + arithmetic ceiling; payment rides the node's existing Cashu wallet via + `swarm::payment::auto_pay_token` (accepted-mints list applies). +- AIUI already has a provider dropdown (embedded mode currently hides provider choice since + D-17 delegates backend selection node-side — this feature would surface Routstr as a + *visible, fundable* leg rather than a silent fallback). +- Status updates in chat: budget-exhausted already returns a plain-language stop (S-12); + extend to show remaining allowance / spend-per-turn as chat status lines. + +Design questions for the planner: +- Embedded mode's D-17 principle (node picks the backend) vs. operator explicitly choosing + Routstr — reconcile (an explicit choice is an operator override, likely fine, but must not + bypass D-04's Ollama-first privacy default silently). +- Funding flows: from node wallet balance (existing), receive-ecash paste, Lightning→ecash? + "All funding options" = enumerate what the wallet actually supports today. +- Confirm-gate interaction: setting/raising an allowance is a spend authorization — should it + require the D-11 trusted-chrome confirmation? (Probably yes: it is the one place the model + could otherwise social-engineer a budget raise.) + +Not scheduled into 13-15 (device-close is already scoped); candidate for a 13.x gap plan or +the next milestone. Routstr protocol residual (0/9 claims live-verified) still applies — the +funding UX should land alongside or after the first live-provider probe succeeds.