Every step has the same four parts:

• Do / say: what you do or say.
• She does: what she clicks or types on her PC or phone.
• Worked when: what you see when it is done.
• If it fails: the fix, then the fallback.

Two rules all evening: she types every password herself, and nothing is ever sent without her approval.

Parts marked First run on Windows tonight were built and tested on a Mac (some with stand-in tools), never on Windows. Each one carries its fallback.

• The kit comes from GitHub. The repo is hassanmaq112/rumi-brain. It is committed on the mini and nothing is pushed yet: mini bob pushes it live on the call, after the invite.
• WhatsApp: Rumi gets a WhatsApp number of its own, linked by QR to a small program on her PC, and answers only her number. Linking her own WhatsApp is the fallback.
• Phone access: a start page on her own free Cloudflare account (a pages.dev address) that opens the portal on her PC through Tailscale Funnel. No domain, no DNS change, nothing moved.
• Windows: the extra test run was skipped. The Claude chat through the portal, Tailscale, the lock answers, the WhatsApp program and the publish script all run on Windows for the first time on her PC tonight.

1. The setup summary shows every line OK, or a TODO we chose to leave, and no FAIL.
2. Claude Code is signed in to her own Claude account under her own Windows user.
3. The portal opens on her PC and on her phone.
4. Her portal account exists: email, her password, authenticator code, 10 recovery codes written down.
5. Settings shows "Settings lock: on".
6. A test chat answered, and one draft approved in Approvals ("not sent").
7. WhatsApp linked to the Brain's number (or her own number as the fallback) and answering her.
8. One real statement month in Books with categories and a CPA export.
9. The items to collect are in, or each has a date. The next call is booked.

1. Open this page, the Meet link from the calendar invite, and the superpowers list (https://rumi-superpowers.pages.dev) for the top-10 talk.
2. Open github.com/hassanmaq112/rumi-brain in your browser, signed in, for the invite. The repo is empty until the push.
3. Make sure mini bob is up and knows two jobs are coming on the call: push rumi-brain and create a Release with the two WhatsApp program files (terra-wa-amd64.exe and terra-wa-arm64.exe). Not confirmed: whether the mini has a GitHub login that can create a Release. Fallback: the kit's ready-made zip already holds both files.
4. Check your phone's WhatsApp for any message from her.
5. Decide how you drive: she shares her screen on Meet and clicks while you read out each line. Backup: Chrome Remote Desktop with a support code (not tried; Windows Quick Assist needs a Windows PC on your side).
6. Recording: ask her OK at the start. If a recording bot joins and your Google account is a free one, the call may stop at 60 minutes: rejoin the same link (possible, not confirmed).
7. Have somewhere to note what you collect (section near the end).

Do / say:

• "Tonight we install Rumi on your PC, on your own Claude plan. Then your login, your phone, WhatsApp, and your first real statement in the books."
• "For WhatsApp, Rumi needs a second phone number of its own: WhatsApp Business on a second SIM or eSIM. It must be a real mobile number, not Google Voice or another internet number, which WhatsApp often refuses. Rumi answers only you. No one else's messages are read."
• "No second number tonight? We can link your own WhatsApp and you talk to Rumi in your 'Message yourself' chat. Nothing else in your WhatsApp is read."
• "You type every password yourself. Nothing is ever sent anywhere without your approval."
• Ask her OK to record.

Worked when: she knows the plan, and you know whether a second number is coming tonight.

Do / say: check each one. Anything missing she creates now, while the setup runs later.

She has:

1. Her PC plugged in, signed in to her own Windows account, and that account is an administrator (Settings > Accounts > Your info says "Administrator").
2. Claude: her own paid Claude plan (Pro or Max), and she can sign in at claude.ai. An API-only account will not work: the portal then says "The Brain is not signed in on this computer".
3. GitHub: a free account at github.com. Ask her username (you need it in step 2).
4. Cloudflare: a free account at dash.cloudflare.com, or she makes one in step 9 when the script asks.
5. Tailscale: a free account (sign in with Google or Microsoft is fine), and the Tailscale app on her phone.
6. An authenticator app on her phone (Google Authenticator or Microsoft Authenticator).
7. Paper for 10 recovery codes (she has no password manager).
8. One real monthly bank or card statement as a PDF, and 2 or 3 receipt photos on her phone.
9. For WhatsApp: the phone with the Brain's number, if she has it.

If something is missing: Claude plan not paid: she buys Pro on claude.ai now (her card, her screen). No admin rights: stop, she signs in with the administrator account of the PC.

The kit is a local repo on the mini today: nothing is pushed, and its README tells her to clone github.com/hassanmaq112/rumi-brain. The WhatsApp program files are not in git; she downloads them from the repo's Releases.

Do / say:

1. Decide which repo she clones. Default: hassanmaq112/rumi-brain (private, we invite her). If instead the kit goes to a repo on HER GitHub account, tell mini bob to change the clone address in the README (two lines, around lines 20 and 34) to her repo before the push.
2. On the repo page: Settings > Collaborators > Add people, type her GitHub username, send the invite.
3. Tell mini bob: push the kit now (it pushes with the repo's own deploy key).
4. Tell mini bob: create a Release on that same repo and attach both WhatsApp program files (terra-wa-amd64.exe and terra-wa-arm64.exe). This must be done before she gets to the WhatsApp step.

She does: opens the invite email from GitHub (or github.com/notifications) and clicks Accept invitation.

Worked when: she can open the repo and sees the files (README.md, SETUP-WINDOWS.ps1, portal) and, on the right side, Releases with the two .exe files.

If it fails:

• She sees "404": she is not signed in, or signed in to another GitHub account. Sign in with the invited account; resend the invite if needed.
• The push fails: mini bob reports why. While it fixes it, carry on with the opening talk and the items to collect.
• Her repo was chosen but the README was pushed with the old address: she clones her own repo address anyway (step 3 uses whatever address the repo page shows under the green Code button); mini bob fixes the README after.
• No Release yet (not confirmed tonight: whether the mini can create one): carry on without the WhatsApp program. The portal works without it. Before step 10, either the Release goes up and she downloads the file, or mini bob attaches the kit's ready-made zip (it holds both files) and she copies the file into portal\bin. Then run the setup once more.

She does (with git, best for updates later):

1. Start > type PowerShell > open it (normal is fine here). Install git:

winget install --id Git.Git -e

2. Close that window, open a new PowerShell window, then:

cd $HOME
git clone https://github.com/hassanmaq112/rumi-brain.git

3. If a GitHub sign-in window opens, she signs in with her GitHub account.
4. The WhatsApp program: on the GitHub page, Releases > newest release > download terra-wa-amd64.exe (her PC; only an ARM laptop needs terra-wa-arm64.exe). If the browser warns, choose Keep. Move the file into the folder rumi-brain\portal\bin.

Worked when: the folder rumi-brain is in her user folder and the .exe sits in portal\bin.

If it fails:

• "winget is not available": Microsoft Store > App Installer > Update, then try again.
• Fallback without git: on the GitHub page, green Code button > Download ZIP > right-click > Extract All into her user folder. Then use that folder name in the next step.

She does:

1. Start > type PowerShell > right-click Windows PowerShell > Run as administrator.
2. Then:

cd "$HOME\rumi-brain"
powershell -ExecutionPolicy Bypass -File .\SETUP-WINDOWS.ps1

3. Warning: do not click inside the blue setup window while it runs. A click puts it in select mode (the title starts with "Select") and the setup freezes. Fix: press Esc once and it carries on.
4. Warning: the portal can take 2 to 3 minutes to start the first time. Wait. Do not run the script again while it is still running.

Do / say: use the wait to collect her top 10 superpowers in order and talk through WhatsApp (see "Collect before 21:00").

Worked when: a summary table of 13 steps. On this first run expect OK for steps 1, 2, 4, 8, 9 (step 9 must say "settings lock: OK") and TODO for the sign-ins and choices (3, 5, 6, 7, 10, 11, 12). No FAIL, with one exception: if the WhatsApp program is not in portal\bin yet, step 12 says FAIL with a download line (expected; add the file, see steps 2, 3 and 10). Step 13 (voice) is optional. Step 1 turns sleep off while plugged in and lists pending Windows updates.

If it fails:

• "Please run as administrator": reopen PowerShell with Run as administrator.
• Windows updates pending: start them in Settings > Windows Update, carry on, reboot at the end, run the setup again.
• The window looks stuck and the title starts with "Select": press Esc once.
• Step 4 "did not answer within 90 s" in the summary: the portal's first start was slow (seen today on a test PC). Wait 2 to 3 minutes, then open http://127.0.0.1:8710. Once it answers, carry on: the setup runs again anyway after step 5 and will show step 4 OK.
• Step 4 fails while installing the portal's parts: check the internet and run it again. First run on Windows tonight (this install path is new). Fallback: the kit's ready-made zip, which has the parts inside (mini bob can attach it to the Release).
• Step 9 "PROBLEM": Task Scheduler > Rumi Portal > Properties > General: "Run with highest privileges" must be OFF.
• Anything else: run the check script below and read its output.

powershell -ExecutionPolicy Bypass -File .\CHECK-WINDOWS.ps1

She does:

1. Open a new, normal Windows Terminal (NOT as administrator: the login belongs to her Windows user).
2. Type claude and press Enter.
3. Pick any theme (Enter). Login method: Claude account with subscription.
4. The browser opens claude.ai: she signs in with her own Claude account and clicks Authorize.
5. Back in the Terminal: if it asks to trust the folder, Yes. Then type /exit.
6. Run the setup again in the administrator window (same line as step 4).

Worked when: the summary shows step 3 OK (a login is saved).

If it fails:

• "claude is not recognized": close the Terminal and open a new one (the setup adds it to her PATH).
• The login page loops: sign out of claude.ai in the browser, then try again.
• "Not available for your plan": she needs Pro or Max.
• "Signature not valid": stop and tell mini bob.

She does: opens http://127.0.0.1:8710 in her browser.

Worked when: the Rumi sign-up page shows. From now on the portal starts by itself every time she signs in to Windows.

If it fails:

• Read the last lines of the log: %USERPROFILE%\RumiPortal\logs\portal.log
• Task Scheduler > Rumi Portal > Run, then reload the page.
• Port already in use: run the setup again with -Port 8720 at the end.

She does:

1. Click the Tailscale icon near the clock > Log in > sign in with her own Tailscale account.
2. On her phone: Tailscale app, same account, switched on.
3. Run the setup again as administrator, this time with bookkeeping and a test chat:

powershell -ExecutionPolicy Bypass -File .\SETUP-WINDOWS.ps1 -LoadBookkeeping -TestChat

Optional, only on fast internet (about 200 MB): add -InstallVoice at the end so voice notes on WhatsApp turn into text.

Worked when: step 3 OK, step 6 OK with an address like https://her-pc.her-tailnet.ts.net, step 10 OK (the Brain answered), step 11 OK (bookkeeping skill installed). Step 7 stays TODO until her sign-up, step 12 until WhatsApp.

First run on Windows tonight: Tailscale on Windows (step 6) and the Brain answering through the portal (step 10).

If it fails:

• Step 6 "NeedsLogin": the Tailscale login did not finish. Click the icon again.
• Step 10 "not signed in": redo step 5 as HER user, not an administrator account.
• Step 10 "usage limit": her plan's window is used up; it shows when it resets. Carry on.
• Tailscale will not work at all: finish everything on the PC tonight; the phone moves to the follow-up.

Do / say: get the one-time setup code from her PC (in PowerShell):

Get-Content $env:USERPROFILE\RumiPortal\data\SETUP-CODE.txt

She does:

1. On the PC, open http://127.0.0.1:8710/signup. Enter the setup code, her email, and a password she types herself.
2. Scan the QR code with the authenticator app on her phone, then type the 6-digit code.
3. Write the 10 recovery codes on paper and keep it safe.
4. On her phone (Tailscale on), open the ts.net address from step 7 and sign in.
5. Optional: Settings > Add a passkey on each device.

Worked when: the home page says "Good morning" (or the time of day), on the PC and on the phone. Then the lock check: Settings shows "Settings lock: on", and the superpowers list is read-only with "To add something new, please contact your setup contact."

If it fails:

• Wrong code: wait for the next code in the authenticator app.
• Setup code gone: Task Scheduler > Rumi Portal > End, then Run. A new code is made while no account exists.
• Locked after 5 wrong tries: wait 15 minutes.
• Phone will not open it: Tailscale on the phone must be switched on, same account.

Do / say: "This gives Rumi a simple web address on your own free Cloudflare account, so your phone opens it from anywhere. The page is only a link; your password and authenticator code protect the portal. No domain, nothing moved."

She does (PowerShell as administrator):

powershell -ExecutionPolicy Bypass -File "C:\Program Files\RumiPortal\publish.ps1"

1. First time only: a Tailscale page opens, Enable Funnel: she approves it (signed in to her Tailscale).
2. The script installs Cloudflare's tool (1 to 2 minutes, nothing to do).
3. A Cloudflare page opens: she signs up free or signs in, then clicks Allow.

Worked when: the summary shows [6/6] OK: deployed: https://rumi-xxxxxx.pages.dev and "Her start page". Test on her phone with Wi-Fi OFF: the pages.dev address shows "Opening your Rumi", then the Rumi sign-in page. Add it to the home screen. It keeps itself up to date at every portal start.

First run on Windows tonight (tested with stand-in tools only).

If it fails:

• "Funnel is not on": open the link it prints, sign in to HER Tailscale, approve, run the script again.
• The phone says "can't find": the public name can take up to 10 minutes. Wait and retry.
• "The Cloudflare login did not finish": run it again and finish the browser step (copy the printed link into her normal browser if the wrong one opened). "Sees 2 accounts": run again with -AccountId and the id it prints.
• "Could not install" or "could not be reached": check the internet, run again.
• Admin path (she prefers not to do the Cloudflare part): she invites your personal email to her Cloudflare account (Manage Account > Members > Invite members > whole account > role Administrator), and you publish from your own computer later, never the mini.
• Fallback: skip it tonight. Tailscale on her phone already opens the portal (step 7).
• Undo at any time: the same line with -Unpublish at the end.

Do / say: "Rumi answers only your number. Groups, other people and status updates are ignored: not read, not saved. Rumi never messages anyone else by itself: 'send this to Maya' becomes a draft in Approvals that you copy and send yourself."

She does:

1. On the PC, portal > Settings > WhatsApp: link, numbers, status.
2. On the phone with Rumi's number: WhatsApp > Settings (iPhone: Settings tab; Android: the three dots) > Linked devices > Link a device > scan the code on the PC screen.
3. Under Who Rumi answers, type her personal WhatsApp number with the country code (US: 1 and the 10 digits) > Save.
4. Click Send me a test message: her phone gets "Hello from Rumi. WhatsApp is linked ...".
5. From her personal WhatsApp she messages Rumi's number "hi".
6. Run the setup again (administrator window, same line as step 4).

Worked when: the page says linked and connected; "typing..." shows, then Rumi answers in 10 to 30 seconds; the setup shows step 12 OK (linked: True).

The switches (one file): every WhatsApp feature is ON by default and each has an on/off switch in one config file. Ask her what she does not need (voice notes in or out, photos, documents, video, typing dots, read ticks, quiet hours 22:00 to 07:00 for announcements, the "Message yourself" chat). To change one:

notepad $env:USERPROFILE\RumiPortal\data\wa-config.json

Set the switch to false, save. The program reads the file again within 30 seconds. Each switch has a help line in the file.

What she must know: the Rumi phone must come online at least every 2 weeks (just open WhatsApp on it), or the link drops. Her PC must be on and signed in for answers; messages sent while it is off are answered when it is back.

First run on Windows tonight (the WhatsApp program itself; voice notes to text only if -InstallVoice ran).

If it fails:

• The code will not scan: wait for the next code (it refreshes every 15 seconds), hold the phone steady. Or choose Link with a code instead, type the Rumi number, and on the phone choose Link with phone number instead.
• "The WhatsApp bridge is not running": Task Scheduler > Rumi Portal > End, then Run, reload the page. Program missing: download it from Releases into portal\bin (step 3) and run the setup again.
• She writes and gets no answer: the page must say linked and connected; her number must be exactly as saved, with the country code; she must write to Rumi's number.
• No second number tonight: link her own WhatsApp with the same scan. She then talks to Rumi in her "Message yourself" chat.
• Still failing: WhatsApp moves to the follow-up call. The portal and the books are not affected.

Do / say: "Let's put one real month in. Your statement stays on your PC."

She does:

1. Portal > Books > upload ONE real monthly statement PDF. Wait while the Brain reads it (a minute or so).
2. Check a few rows and amounts against her PDF.
3. Answer any question card (an unknown payee or reference).
4. Change one category, so she sees the rule learned for that payee.
5. Open the monthly summary (business vs personal, recurring) and make the CPA export (XLSX and CSV).
6. If time: a receipt photo from her phone through the portal camera, matched to its line.

Worked when: the month shows in Books with categories, and the export files download.

Do not: load the made-up sample statement on her PC (its rows would stay in her books). No real statement ready: show the flow on her first real PDF in the follow-up instead.

If it fails:

• The upload stays "reading": wait a minute.
• "error": Books > Try again.
• "usage limit": her plan's window is used up; it shows when it resets. Do it in the follow-up.
• Deleting statements after the CPA has them: Books > Delete statements, with a typed DELETE. Not tonight.

She does, in the portal Chat:

1. "Hello Rumi, what can you help me with?" A reply streams in.
2. "Please connect my Gmail." Rumi answers: "please contact your setup contact about this."
3. "Send this to my sister: ..." Rumi answers: "It is in Approvals. Approve it there, then copy and send it."
4. Open Approvals: show edit and drop, then Approve. It says "Approved by you, not sent". She copies the text.

Do / say: "Rumi never sends anything by itself. Every message waits in Approvals; you approve it, copy it, and send it yourself."

Worked when: the draft shows "Approved by you, not sent".

If it fails: "not signed in": redo step 5 as her own user. "usage limit": try later.

Do / say:

1. Recap: what is set up tonight, and what comes next with dates.
2. Collect what is still missing (next section).
3. Book the next call: the review of her 50 to 70 samples, plus anything moved from tonight (WhatsApp, the phone page).
4. Remind her: keep the PC on and plugged in (sleep is already off while plugged in). If Windows updates were pending, reboot now; the portal comes back by itself a few minutes after she signs in.
5. Her own copy of these steps is the README on the GitHub page.

Running late? If you are 15 minutes or more behind at 20:15, drop in this order: passkey, voice install, receipt photo, reboot check, the Cloudflare start page (Tailscale already works), then WhatsApp (her own number as the quick fallback, or the follow-up call). Never drop: her Claude sign-in, her sign-up and recovery codes, the lock check, the test chat, one real statement.

1. Her 10 superpowers in order (from the list sent on 4 November). Known so far: bookkeeping first, app creation last.
2. 50 to 70 sample transactions: statement PDFs, receipt photos, screenshots. Tonight at least one real month; the rest with a date.
3. Her GitHub username (needed in step 2).
4. The Brain's WhatsApp number (she types it on the phone and in Settings herself; nothing to write down here).

If time allows:

5. Which bank accounts are business and which are personal.
6. Her bookkeeping categories (she uses Rocket Money today).
7. Whether the CPA hand-over on Thursday 12 or Friday 13 November still stands.
8. Access to her app from the US developer, and a working design link.

1. The review call over her 50 to 70 samples (date set tonight).
2. Anything moved from tonight: WhatsApp, the phone start page, voice notes to text.
3. The phone agent research: does it fit in the 10 or not.
4. A review of her US-built app, once she has access.
5. The Alexa check for her affirmations.
6. The weekly Friday update (next: Friday 13 November).
7. The walkthrough and a short written guide.
8. The next extras on the plan: a morning brief on her days and times, voice, a home-screen icon and a PC app window.