Fact 162
Morgan Chen requested an internal email reply to Devon Hayes stating that Mercury hardening follow-through and API v2 support cleanup may close only when evidence already exists, onboarding is to remain in monitoring, no fresh investor-packaging requests should go to product owners, and non-customer-impacting work must wait until January.
Source evidence (1)
000933Dec 19, 2023 / 09:03 UTC-08:00
Devon sent the closeout rows for the reduced holiday stretch. Discord DM — Devon Hayes -> Morgan Chen Tue Dec 19, 2023 08:41 AM PT Final 2023 ship-list closeout rows before the reduced holiday stretch. I cut this to only the rows owners are still asking about. Main thing I need from you is the line on what counts as real closeout this week versus what just waits for January. | Area | Closeout row | What can actually close this week | Owner note / question | | --- | --- | --- | --- | | Mercury hardening follow-through | Keep only launch-confidence follow-through already tied to existing evidence: sync reliability, retry behavior, admin handoff rough edges, and copy/UI bugs that materially affect clean Mercury evidence. | If the evidence or fix is already in hand, owners can close it. If it needs fresh analysis, a new writeup, or holiday heroics, it is not a 2023 closeout item. | Jake / Marcus / Leo Park stay on the bug-shaped work only. Priya only where wording/UI is part of the fix. Do you want the owner note to say explicitly that anything not customer-impacting rolls to January? | | Onboarding monitoring | Keep this in monitoring only. No new tooltip, help, or checklist pass before year-end. | Teams can watch repo-first completion, teammate-invite confusion, and support volume, but there is nothing new to open unless the current rollout clearly worsens. | Priya / Jake. My read is this should go out as watch-and-log, not do-more. | | API v2 support cleanup | Close only the targeted support-path work that is already real: pin the GraphQL quickstart in search, keep stale v1 hits down, and tighten the support macro / auth-error landing path. | If the update is already tested, let it land. If it needs a fresh docs sweep or migration rethink, park it. | Rishi. Still user-facing cleanup, not a migration reopen. | | Northstar-related prep asks | Small asks keep surfacing around screenshot refresh, appendix wording, a cleaner activation explainer, or a short support-pattern note before people go mostly offline. | My instinct is none of this becomes an owner ask unless the work also improves actual product evidence right now. Otherwise it is January or stays with the small Morgan / Devon / Anna group. | I need your exact line here so owners do not hear investor packaging by accident. | Two quick reads from my side - Mercury hardening and API v2 cleanup are the only rows I would still call real owner closeout work this week. - Anything that needs new data pulling, fresh packaging, or non-customer-impacting polish feels like a January problem, not something to sneak into the reduced schedule. Please draft an internal email reply to Devon. Line I want owners to hear: Mercury hardening follow-through and API v2 support cleanup can close only when the evidence already exists; onboarding stays in monitoring; no fresh investor-packaging asks go to product owners; and anything not customer-impacting waits until January.
Message 000933 in history