If Angel is out — the one page¶

Decided 2026-09-15 (task 139): Yara Rosado is the emergency person. If Angel cannot be reached for a day, she can keep customers whole with what is below. Nothing here is a password; the passwords live in the vault, in a collection she can open.

What Yara can already do today¶

Answer customers: she has her own Workspace mailbox; hello@ and purchasing@ are aliases that also reach Angel's. Reply from her own address and copy hello@.
Ship an order: ERP (erp.embeddedera.com, her own Google login) → Sales → the order → Ship. Labels print from the Labels tile on the home page. SOP-007 Sales Orders.
See every task and take one: tasks.embeddedera.com; the board rules are SOP-017.
Buy parts: her ERP role covers purchase orders (SOP-004) and she holds the supplier logins she uses day to day.

What she needs the vault for (Vaultwarden, collection "Emergency")¶

Refund a customer: the payment rail's login (Stripe once task 23 is done; until then the bank card portal) — refund from the original charge, never by a new transfer.
Website emergency (a wrong price, a dead page): the Cloudflare Pages login can roll back the last deploy; do not edit code.
Domain and mail: the registrar and Google Workspace admin logins, only to keep mail and DNS alive, not to change them.

The order of operations when it happens¶

Tell customers with open orders where things stand, same day, from her own mailbox.
Ship what is built and tested; do not start new builds without Angel.
Refund anything that cannot ship within the promised lead time plus a week.
Write what she did as a Done comment on the relevant tasks; the register keeps the record.
If it lasts more than a week, call the CPA (number in the vault) and tell the bank.

Gaps to close (tasks)¶

Create the vault collection "Emergency" and share it with Yara — Angel.
Payment rail (task 23) — until it exists, refunds are manual.
A tested restore of the server from backup (task 86) so a hardware failure does not need Angel.