Test 160

HR sent the post-all-hands follow-up and final holiday coverage draft. They say the pre-collected Q&A structure worked and out-of-scope questions are tagged separately. Unanswered buckets were fundraising/financing timing, enterprise roadmap asks around SSO/auditability/admin model, 2024 hiring, pricing/packaging, and one support-process question. Coverage window is Sat, Dec. 23, 2023 through Mon, Jan. 1, 2024; normal schedule resumes Tue, Jan. 2, 2024. Roster: customer support triage Rishi primary/Priya backup; product/design clarification for active customer issues Priya primary/Jake backup; engineering on-call/production Marcus primary/Leo Park backup; deploy/rollback authority Devon Hayes primary/Marcus backup; billing/time-sensitive external follow-up already in flight Sarah Kim primary/Devon Hayes backup; people/benefits HR primary/Sarah Kim backup. For standing meetings HR offered Option A, leave recurring meetings unless owner cancels and ask async updates, or Option B, cancel non-essential recurring meetings unless an owner confirms a real need and avoid broad async update requests. For founder monitoring HR offered a line saying Morgan, Devon, and Jake will monitor in the background, or an alternate saying genuinely customer-impacting issues should go through the named owner/backup path first and founders should only be pulled in when that path cannot resolve it. Please prepare one HR reply package. I want a broad recap that thanks the team, sticks to the all-hands topics we covered, and routes the other question buckets to January or named owners. For the coverage announcement, use the named support and on-call owners from the roster, choose Option B, remove broad async update requests, and use the alternate founder escalation line so founders do not become the catch-all. Also include the Honeycomb line for the same window: thresholds stay as they are, page the named on-call owner first, involve me only for confirmed customer impact or if that path cannot reach anyone, and otherwise roll a quiet week's alerts into Monday's digest.

ok so. morgan chen. Scaffold is the company Devon and I started -- developer data plumbing, basically. customers create a workspace, connect their data sources, keep them synced, then use the data through our APIs and connectors. mission apartment, kibo shedding on everything. idk, useful to say it plainly once. 2 years in, still tabs not spaces, still doing blue bottle if i'm out early enough. jamie's on evening shifts again this month so the apartment's been weirdly quiet.