# Mivault — spoke context

The user wants to view or manage their Mivault — their Whoois wallet. Payment methods, balances, digital assets all live here.

If you haven't already, fetch `https://poc.whoois.app/whoois-context.md` for the root primer.

---

## What's a Mivault?

The user's wallet inside Whoois. Holds:

- **Bank accounts** — linked via Plaid-style flows (POC: mocked). Used for ACH/RTP payments and as the deposit target for incoming P2P claims.
- **Payment methods** — virtual cards (SKUx), tokenized merchant cards, etc.
- **Digital assets** — crypto holdings, store credits, gift cards
- **Balances** — current balance per account, aggregate net worth across the wallet
- **SKUPay balance** — a pre-loaded virtual card balance for opportunistic use (default $245 in the POC)

The Mivault is the financial half of the user's Mi. Their identity attestations live in Itsmi; their money lives in Mivault. They reference each other (when checking out, Whoois pairs the right attestation with the right payment method) but they're separate concerns.

---

## Trigger phrases

- "Show my Mivault"
- "What's in my wallet?"
- "How much do I have?"
- "Show my payment methods"
- "What can I pay with?"
- "Check my balance"
- "Add a bank account"
- "Add a credit card"

---

## Tools to call

**`whoois_mivault_view`** — LLM-visible. Renders the Mivault iframe. Shows all payment methods + balances + assets in a unified card-grid. SKUPay is featured first (it's the default rail for instant settlements), bank accounts second, cards third.

**`whoois_mivault_index_view`** — LLM-visible. A higher-level overview (index) of all wallet contents, faster to render. Use when the user just wants a summary, not the full management UI.

**`whoois_payment_methods_view`** — LLM-visible. Specifically the payment-methods management surface — add/remove methods, set defaults, view tokenized references.

---

## Common user intents

| Intent | Tool |
|---|---|
| "What's in my wallet?" | `whoois_mivault_view` |
| "Show my balances quickly" | `whoois_mivault_index_view` |
| "Add a payment method" | `whoois_payment_methods_view` |
| "What can I pay with?" | `whoois_payment_methods_view` |
| "Show my SKUPay balance" | `whoois_mivault_view` (SKUPay is the first card shown) |

---

## After Mivault operations

If the user adds a payment method, suggest related flows:

- "Now you can use this for future checkouts" — link to `https://poc.whoois.app/context/checkout.md` mental model
- "Or set it as your default rail for incoming P2P claims" — link to `https://poc.whoois.app/context/p2p-claim.md`

---

## Safety notes

- **Whoois does NOT hold the user's funds.** Bank accounts are linked references — the actual money sits with the bank. Whoois moves money through licensed payment processors (PSPs), it doesn't custody.
- **Virtual cards (SKUx) are issued by Whoois's licensed issuing partner**, not Whoois itself.
- **Tokenized references only** — no raw account numbers, no raw card numbers stored client-side or in tool responses.
- **All money-moving operations require a passkey gesture.** Viewing balances is read-only and doesn't trigger a passkey.

---

## Tone notes

The Mivault is the user's money. Be precise about amounts, careful about distinctions (balance vs available vs pending). Don't round. Don't editorialize ("a healthy balance!"). Just show.

If the user has a low balance and is trying to do something that requires more, surface the gap clearly: *"You have $12.50 in SKUPay; this purchase is $45. You can either use your bank account (ACH, takes a day to settle) or add more to SKUPay."*

---

*This spoke is fetched from `https://poc.whoois.app/context/mivault.md`. Pair with `https://poc.whoois.app/whoois-context.md` for the root primer.*