Updated 6m ago
✦ squircle · your morning brief Wed, Jun 17 · 11:08

Good morning, Sara. Overnight I cleared and your KPIs are healthy — withdrawals 98.7%, settlement 1.4s. One thing needs a human call before the margin engine resolves it the wrong way. Tessellate is notified and Lena's on it — you're clear. You let the engine handle Tessellate per policy — you're clear.

2 rituals today
squircle handled these overnight · 7 · no action needed read-only

Your priorities today

✦ NEEDS YOU margin-health · VIP relationship ~30 min to liquidation

Tessellate Capital is ~30 min from auto-liquidation — reach out first?

Tessellate Capital (tier-1 VIP · top-20 by volume · $340M/mo · ~$0.95M/mo fees) has a cross-margin account whose health fell from 148% → 112% in 90 min as BTC-PERP dropped 4.2%. At 100% the engine starts force-closing their $61.8M long. Two automated margin-call emails went out (130%, 115%) — no reply in 40 min. The tier-1 playbook lets us offer a top-up window first. squircle won't decide whether to intervene — that's your call.

Margin health
112% was 148%
Liquidation at
$59,050 −3.6%
Position
$61.8M long BTC
✦ squircle — VIP outreach here isn't a favor: PLAYBOOK-204 grants the same top-up window to every tier-1 institutional account at this band. It's documented and consistent. The engine still liquidates at 100% if they don't act.
Loops in Lena Voss · drafts the heads-up · per PLAYBOOK-204
Watching — nothing sent yet. squircle will resurface this the moment health drops below 108%.
✦ DRAFTED · YOUR SEND Lena Voss tagged · VIP channel

Send Tessellate the top-up window

squircle drafted the heads-up per PLAYBOOK-204 and tagged Lena Voss (their relationship owner). It computed the exact ask: to clear the band they'd add ~$2.1M collateral or trim ~$11M notional. squircle won't message a client on its own — review and send.

“Hi Tessellate desk — your cross-margin account is at 112% health (auto-liquidation at 100%). To hold your BTC-PERP position you'd want to add ~$2.1M collateral or trim ~$11M notional in the next ~30 min. You can top up in-app or reply here — we're watching alongside you. — Crypto.com Institutional”
✓ SENT awaiting Tessellate's top-up

Sent — now close the loop with Aaron

Tessellate has the window and Lena's on the relationship. A $61.8M VIP near-liquidation is a CPO-visible event — squircle drafted the 2-line status for #margin-health and a heads-up to Aaron:

“Tessellate (tier-1 VIP) hit 112% margin health ~11:02 as BTC-PERP fell 4.2%. Auto margin-calls got no reply, so we triggered the PLAYBOOK-204 top-up outreach — Lena owns it, top-up window sent. Engine still liquidates at 100% if they don't act. No other tier-1 account is at risk.”
Slack #margin-health · #Sara <> Aaron
✓
Tessellate notified — you're clear
Lena owns the relationship · Aaron notified · engine still watching
Policy-standard — you're clear
No client outreach · engine liquidates at 100% per the tier-1 agreement · logged to audit
For the record: squircle did not contact Tessellate. The decision and reason are logged to their account record for the audit trail.
✦ GET AHEAD proactive · margin-health watch

One move to stay ahead: this is the 3rd tier-1 account to test the band this month. Set a watch so squircle surfaces a Move (same card, your call) the instant any tier-1 account crosses 125% — you stop being the bottleneck, and it still never acts for you.

✓ Watch armed — squircle will surface a Move when any tier-1 account crosses 125%. It alerts; you decide. Edit in Roadmap → routines.
That's everything — squircle will ping you if Tessellate's health drops again.
Healthy — squircle is monitoring, no action
Client-facing margin comms are logged to the account record & visible to Compliance — VIP outreach follows PLAYBOOK-204, never ad-hoc.

✦ squircle — who's on the Tessellate margin outreach right now.your payments squad & the institutional desk — no one's been pulled in yet.

Presence is shared across your squad only.
✓