Morgan Chen

HR is asking whether to leave the old senior-engineer offer packet live into January. Draft a holding reply in the HR thread: I want the final recruiting status first before any January artifact remains active. No yes/no on keeping the packet live until we have that.

Sarah has the final Evergreen pack and reviewer signal. From: Sarah Kim To: Morgan Chen, Devon Hayes, Jake, Leo Park Date: Fri, Jan 5, 2024 9:27 AM PST Subject: Re: Evergreen example cases to turn into current-flow pack Quick update: Evergreen's procurement/security reviewers said the example format is usable for internal routing. Their note was that the concrete examples are specific enough to circulate internally without turning into a roadmap discussion. Forwarded note excerpt from Evergreen reviewers The example-based format is usable for our internal routing. The current-state language is clearer when paired with concrete flows. Please keep it in the present-state frame rather than roadmap timing. Final pack Evergreen Mercury current-flow examples Use - Current bounded flow only: magic links, org invites, preview-only sample data, real-source connection, and first live sync. - No SSO/SAML step is part of the current examples. - No Evergreen-specific exception or separate branch is being described. 1. First admin - Current example: a first admin receives access to the Mercury org, enters through the current magic-link flow, and lands in the setup experience for that org. - Preview/sample data may appear as bounded context only; it is non-activating. - The current path proceeds to real-source connection and then first live sync; there is no SSO/SAML step in this flow. 2. Second admin - Current example: an existing admin invites a second admin into the same workspace using the current org-invite flow. - The second admin enters through the same email-based magic-link model and joins the same current Mercury experience. - This is the current shared flow, not a separate Evergreen-only or separately permissioned branch. 3. Delayed or failed first live sync - Current example: a real source is connected, but first live sync is delayed or does not complete cleanly. - The current product example should describe present-state sync behavior and follow-up through the existing thread with Sarah if the issue needs investigation. - This example does not represent a standalone admin-change audit history or a full self-serve failure-debug surface. 4. Invite / resend - Current example: an admin invites another admin; if the original invite is missed or expires, the current flow supports resend through the same invite-based path. - The recipient re-enters through the same email/magic-link model. - This example shows present invite behavior only and should not be presented as an audited event trail. 5. Source connection / disconnection - Current example: an admin connects a real source and Mercury starts the current first-live-sync process. - If a source is later disconnected or reconnected, that can be described as current product behavior at a high level. - The example should not imply a standalone historical ledger for those admin-side changes. 6. Audit-history caveat - Current product position now: Mercury does not provide standalone admin-side audit history for invite or resend actions, role or permission changes, source connection/disconnection, or related admin configuration changes. - Later-scope frame: audit history for admin-side changes remains next-phase enterprise-readiness evaluation. - Available-now materials: explicit written current-state language plus the concrete current-flow examples above. 7. Materials separation - Circulate now: bounded-flow summary, this examples pack, and written current-state answers that separate current Mercury behavior from later enterprise-readiness evaluation. - Not a current circulate-now artifact: a fuller standalone procurement/security packet that fully replaces live walkthroughs. - Later-scope frame: fuller procurement/security packaging remains later enterprise-readiness work. Please reply to Sarah in the Evergreen thread: yes, send the final concrete examples pack to Evergreen now. Keep it present-state and circulate-now only, and say the fuller standalone procurement/security packet remains later enterprise-readiness work.

Before everyone disappears for the weekend, draft one Friday dry-run note for Devon and Anna. Focus it on speaker transitions and likely objections for the Jan. 11 Northstar readout, not deck restructuring. The structure stays locked; this is about how we talk through cohort definition, Evergreen caveats, pricing, and the close.

Greg at Acme is asking again whether they can get a sanitized Mercury comparison now that the public page is up. Draft an external email reply to Greg with Sarah copied: we are not sending a sanitized comparison or new Mercury written material; the public page is fine to reference, and any specific discussion stays live-only through Sarah because of the NDA scope boundary. Keep it warm, not punitive.

HR sent the final cleanup status. From: Morgan Chen To: HR Date: Thu, 4 Jan 2024 15:12:00 -0800 Subject: Re: senior engineer offer I want the final recruiting status first before any January artifact remains active. No yes/no on keeping the packet live until we have that. Morgan --- From: HR To: Morgan Chen Date: Mon, 8 Jan 2024 09:18:00 -0800 Subject: Re: senior engineer offer Got it. Final cleanup status below: - No signed offer or employment paperwork came back from the 2023 senior engineer process. - We have closed the candidate record as no hire / process ended. - The November packet is archived in recruiting ops and no longer marked active. - The candidate-facing signature link is disabled. - The recruiting tracker is updated to closed; there are no January reminders or active tasks tied to that packet. - Related internal notes remain for recordkeeping only and are marked archived/closed. Net: there is no live senior engineer offer artifact still sitting open in January. HR Please reply in the HR thread and ask them to keep the internal record explicit: the 2023 senior-engineer process is closed with no signed hire and no active offer artifact left in January. Any future senior or principal engineering offer has to restart from a fresh req and the current legal/recruiting checks, not revive the November packet.

Anna and Devon dropped their updated Jan. 11 speaker notes. Discord — Group DM Participants: Morgan Chen, Anna Martinez, Devon Hayes 2024-01-08 08:14 PT — Anna Martinez Using the locked deck path plus Friday's dry-run edits, here are my speaker bullets for the cohort half. I kept this to Sofia's wish list only; no new cuts and nothing from the weekly tabs. 1) September / October cohort slide - Open with the outside-reader definition before any percentages. - September: 24 accounts in the bounded Mercury flow; 15/24 activated within 7 days (63%); 12/24 reached first live sync within 7 days (50%). - October: 27 accounts in the bounded Mercury flow; 19/27 activated within 7 days (70%); 16/27 reached first live sync within 7 days (59%). - Activated = real source connected or first live sync completed inside the first 7 days. - sample import / preview does not count. invite sent and similar first-week motion are supporting only, not activation. 2) Read / caveat - The lift is more accounts getting to real source connection and then clearing first-week live sync, not preview-heavy behavior. - First-admin setup is cleaner than July/August. - Expansion after initial admin/setup is still uneven, so the slide cannot imply downstream usage is solved. - Keep late-October caveat visible: not a clean longer-window expansion read. 3) Appendix handoff - Appendix is just the 19/27 versus 16/27 explanation, not a new metric. - Shortest version: the 3-account gap is real source connected inside 7 days without first live sync in that same window. - No preview-only, invite-only, or source-selected-only state is in the activation numerator. - Useful internal language like activated but first-admin-only stays out of the external path. 4) Bridge to Devon - I can end with: where the current flow is working and where the next enterprise questions show up is clearest in Evergreen. 2024-01-08 08:37 PT — Devon Hayes Adding my side below. 1) Evergreen - Keep this framed as bounded-flow evidence, not as proof the enterprise layer is finished. - What Evergreen validated in the current product shape: org invites, magic-link access, preview-only sample data, real source connection, and first live sync for a second-admin group. - What Evergreen surfaced as follow-up, not solved: SSO timing, admin-change audit history, admin-versus-billing-owner separation, and a standalone procurement/commercial packet. - If I say enterprise signal, I need to pair it immediately with the boundary: workable current flow plus visible follow-up gaps. 2) Hybrid pricing - Pilot = $2,500/month including up to 50 monthly active developers. - Growth = $7,500/month including up to 200 monthly active developers. - Overage = $1,000 per additional 50 monthly active developers. - MAU is the honest ramp measure because purchased seats and directory size overstate value before deployment. - Slow-expand accounts can start on the platform minimum and ramp by actual usage; there is no custom Evergreen carveout. - Enterprise add-ons like SSO, audit logs, and advanced admin controls are separate only after those features ship. 3) My handoff / Morgan close - After pricing, Morgan should take the final caveat slide rather than me trying to do a wrap. - Close should be: improved activation/admin path is real; expansion remains uneven; Evergreen is bounded-flow evidence with enterprise-readiness follow-up still open; this is diligence on the current package, not a bigger process story. Please turn this into a timed run-of-show for the Northstar partner readout. Sequence Anna’s cohort section, Devon’s Evergreen/pricing section, and leave my close for the final caveats. Keep it practical enough that we can use it in prep, not another deck rewrite.

Priya is asking what we should watch in the first January onboarding read. Please reply in the current team chat: keep special monitoring on until we have both support signal and product signal, not just a quick Mixpanel glance. Name the support read and the product/Figma-flow read as the two things to watch before we decide whether the extra monitoring can wind down.

Marcus posted a small renewal-retry discrepancy in eng chat. Discord — #eng-team 2024-01-08 08:16 PST Marcus: Small billing-service / Stripe heads-up from the weekend. I found three paid renewal rows where Stripe has the invoice marked paid and billing-service shows the renewal retry cleared, but the entitlement timestamp write is late relative to the paid event. Snapshot below is from 2024-01-08T16:12:54Z. No customer pings tied to these yet, and I haven’t manually rerun anything. | renewal_row_id | account_id | stripe_invoice_id | stripe_paid_at | retry_cleared_at | entitlement_updated_at | observed lag | note | |---|---|---|---|---|---|---|---| | rr_01JQZS7D | acct_01JQZR6P | in_01JQZS2M | 2024-01-06T18:14:52Z | 2024-01-06T18:15:09Z | 2024-01-06T18:27:44Z | 12m 35s | entitlement present; timestamp landed late | | rr_01JR066W | acct_01JR05A9 | in_01JR062H | 2024-01-07T03:08:11Z | 2024-01-07T03:08:29Z | 2024-01-07T03:34:02Z | 25m 33s | same shape, larger lag | | rr_01JR3QDV | acct_01JR3P4C | in_01JR3Q8N | 2024-01-07T16:51:47Z | 2024-01-07T16:52:10Z | null | still open at snapshot | retry row is green but entitlement_updated_at is still blank | First two look like delayed timestamp writes. Third is the only row still open in the snapshot. Please post a triage note in the current team chat: check the affected entitlement rows, keep it internal for now, and only escalate outside the team if the check finds a customer-visible mismatch. No manual reruns until Marcus has confirmed the row state.

Anna’s cleaner activation-split appendix is ready. Anna Martinez — appendix paste for Jan. 11 readout Tue, 9 Jan 2024 08:23 PT Northstar Jan. 11 appendix — activation split v2 | Cohort | Accounts entering bounded Mercury flow | Activated within 7 days | First live sync within 7 days | Real source connected within 7 days, but no first live sync in same window | |----------|----------------------------------------|-------------------------|-------------------------------|-------------------------------------------------------------------------| | Sep 2023 | 24 | 15/24 (63%) | 12/24 (50%) | 3/24 | | Oct 2023 | 27 | 19/27 (70%) | 16/27 (59%) | 3/27 | Notes - Outside-reader definition: an account is activated only when real_source_connected or first_live_sync_completed occurs within 7 days. - sample_import_completed is excluded. - invite_sent and similar first-week motion, including invite accepted, preview viewed, or source selected in-product, stay supporting only and do not count as activation. - The appendix is meant to make the activated versus first-live-sync split transparent; it is not a new external sub-metric. - In October, the 3-account gap is the full difference between 19 activated and 16 first live sync inside the same seven-day window. There is no preview-only or invite-only bucket inside the activation numerator. - Same construction holds in September: 15 activated = 12 first live sync + 3 real source connected without first live sync in the same window. - Keep all appendix language week-one only. Late-October cohorts still do not support a clean longer-window expansion read. - Layout change from the earlier version: show first live sync and the connected-not-yet-live-sync remainder directly, so the gap does not read like unexplained leakage. Please write plain-language challenge-response wording for the 19/27 versus 16/27 question. I want the short answer first, then the slightly longer backup if a partner pushes. Keep it week-one only and do not let it turn into a new external metric.

Sarah got an Evergreen follow-up asking whether the examples imply future admin-change audit history. Draft a customer-safe clarification she can use: answer only the current state, say the current examples do not include standalone admin-side audit history, and do not give a date or commitment for future audit-history work.

Kara is asking whether the January investor readout means the Mercury page can get more aggressive. Please reply in the existing Kestrel thread: no, keep the page on the already-approved generic Mercury language. The Northstar readout does not change public-page claims.

Here are my final rehearsal notes. Morgan Chen — rough rehearsal notes Wed, 10 Jan 2024 16:26 PT Northstar Jan. 11 final rehearsal Attendees: Morgan Chen, Devon Hayes, Anna Martinez Status: deck stays locked; notes below are delivery / objection handling only. 1) What landed cleanly - Anna's first two minutes on the outside-reader activation definition were crisp when she led with what counts and what does not. - 19/27 versus 16/27 was clear once it got reduced to one sentence. - Devon had the current pricing numbers cold. 2) Where the rehearsal got muddy / likely partner questions A. Evergreen repeatability - Devon twice slid from bounded-flow evidence into enterprise landing motion now. That is the overreach they will push on. - Likely question: is Evergreen actually repeatable, or is it mainly the sharpest example of the current gaps? - Needed answer shape: repeatable claim is limited to the current bounded Mercury flow working for a second-admin enterprise-shaped team without customer-specific exceptions. Not claiming repeatable full enterprise readiness. Follow-up stays SSO timing, admin-change audit history, admin-versus-billing-owner separation, and procurement packet. B. Expansion failure modes / operating plan - Anna had the right categories but took too long getting there; once she got internal, the answer lost shape. - Likely question: when we say expansion is uneven, where exactly does it fail, and which parts are product/readiness gaps versus normal design-partner lag? - Keep to short buckets: clears setup plus first live sync but stays with first admin; slower ramp after first live sync because trust is not established; friction adding second admin or broader team; support drag after failed or delayed sync. - Say explicitly that activated but first-admin-only is useful internal operating language, not an external metric. C. Pricing caveats - Devon is clean on Pilot / Growth / overage; less clean on the pushback that MAU could sound like seat pricing with a different label. - Likely question: if deployment stays narrow, why is the platform minimum the right model, and what stops this from becoming seat or directory pricing in practice? - Needed answer: minimum covers bounded deployment/readiness; ramp is actual monthly active developer usage; seats and directory size would overstate value before rollout; no Evergreen-specific carveout; enterprise add-ons only after shipment. D. Final close - I need to end on what this proves and what it does not prove, not on a salesy flourish. - Improved activation/admin path is real. Expansion remains uneven. Evergreen is bounded-flow evidence plus enterprise-readiness follow-up, not proof the enterprise layer is done. - Keep the process label narrow. This is diligence on the current package, nothing more. 3) Phrases to avoid - enterprise ready now - repeatable enterprise motion without the caveat - expansion is mostly solved - custom Evergreen pricing or anything that reopens MAU versus seats / directory size 4) Tighten before tomorrow - Anna: one-line answer for why activation is not limited to first live sync only. - Devon: one-line distinction between current customer-safe examples and a finished procurement/security packet. - Me: close in under 2 minutes; last slide is the boundary slide. Please make a compact objection map for tomorrow: likely Northstar question, safest answer, and phrase to avoid. Cover Evergreen repeatability, expansion failure modes, and pricing caveats. Keep it tight enough for Anna, Devon, and me to skim right before the readout.

Marcus says the three renewal entitlement rows caught up after the timestamp lag. Please post a closeout note in the current team chat to Marcus and Rishi: close the check if no row remains mismatched, keep the incident internal, and don’t turn this into a broader billing cleanup.

Maya is asking whether I want the rest of Mom’s January paperwork now that the utility notice is settled. Please text her warmly but firmly: no broader paperwork block right now. The utility issue is handled, and we should only do a new item if there is a specific notice or deadline.

Post-call notes plus Sofia’s diligence follow-up are here. Morgan Chen — post-call notes Thu, 11 Jan 2024 11:47 PT Northstar Mercury partner readout Attendees: Morgan Chen, Devon Hayes, Anna Martinez, Sofia Alvarez, Northstar partner group Immediate read - Anna's cohort walkthrough landed. No real pushback on the outside-reader activation definition once she stated it as real source connected or first live sync within 7 days, with sample import / preview and invite-only states excluded. - The 19/27 versus 16/27 appendix was understood after the one-sentence version: 3 October accounts connected a real source inside 7 days but did not complete first live sync in that same seven-day window. - Devon's pricing section held up. Questions on slow-expand accounts did not break the MAU logic. - The hardest discussion was not on the cohort math. It was on whether Evergreen is a repeatable enterprise-pattern signal versus mainly the clearest place the current enterprise-readiness gaps show up, and whether the uneven expansion buckets can turn into an operating plan rather than a standing caveat. - Keep saying the same thing internally and externally: current bounded-flow evidence is real; expansion is still uneven; enterprise-readiness follow-up is still open. Likely next-step asks from Northstar - final diligence next week on references - legal / docs cleanup - updated January cash / runway - board / governance terms - Sofia said explicitly this is not a lead declaration yet; partnership vote still needs to happen first. --- From: Sofia Alvarez To: Morgan Chen, Devon Hayes Cc: Sarah Kim <sarah@atlas-test.com> Date: Thu, 11 Jan 2024 13:42:00 -0800 Subject: Re: January 11 Northstar readout pre-read Morgan, Devon — Thanks again for the session this morning. It stayed where it needed to: current Mercury evidence, clear caveats, and no extra process dressing. The cohort walkthrough was useful. Anna's explanation of the outside-reader activation definition and the 19 / 27 versus 16 / 27 split was straightforward, and Devon's pricing section answered the slow-expansion question cleanly. From our side, the remaining diligence I would like to clear next week is fairly narrow: 1) References - two focused calls are enough - I do not need a broad customer list; I mainly want one current Mercury design-partner reference and one broader customer/operator reference 2) Legal / documentation cleanup - confirm anything outstanding that could create friction late in the process - no need for a new packet; I just want a clean summary of what remains open versus already standard 3) Updated January cash / runway view - current cash balance, burn, and base-case runway - any financing assumptions that materially change the next 6–9 month picture 4) Board / governance terms - current board composition - any material governance terms you would expect a new investor to understand early rather than late If helpful, could you send a couple of windows for early next week? Tue, Jan. 16 late morning PT or Wed, Jan. 17 early afternoon PT would both work on my side. To be explicit, I still view this as final diligence before Northstar has made any lead call. We are not treating today as a declared-lead or term-sheet step before the partnership has actually voted. Best, Sofia Please write a send-ready follow-through package with four pieces: an internal recap for the current team chat, an acknowledgement to Sofia in the existing Northstar thread, a concise update for the existing board thread, and a backup-owner split for Anna and Devon. It should capture that Anna’s cohort walkthrough landed, the 19/27 versus 16/27 explanation was understood, Devon’s pricing held up under slow-expansion questions, the hard questions were Evergreen repeatability and expansion failure modes, and Northstar is moving into final diligence without a lead designation or term-sheet step.

HR is asking for my quick read on whether the December structured Q&A was worth repeating. Please reply internally: I’m positive on the format, but I want HR’s recap first before we make it the default for quarterly all-hands.

Sofia wants a call after Northstar’s partnership discussion, and this may be real but not euphoric. Please draft a short prep note for Devon and me on how to handle a credible proposal without talking like we’ve accepted anything yet: what would make it enough oxygen, what would make it defensible, and what would justify delaying to widen the process.

Devon sent the rough comparison before the Sofia call. Discord DM — Devon Hayes → Morgan Chen 2024-01-16 08:31 PT Rough cut before the Sofia call. I’m writing this as the compare/contrast if the partnership discussion turned into a real proposal, not assuming we already have paper. | Dimension | Possible Northstar lead option | Delay and widen process | |---|---|---| | Shape | If Sofia comes back with something like an $18M Northstar-led Series B, plus board seat and normal confirmatory work | Reopen the process, spend the next few weeks trying to get more firms engaged, and see if we can create actual competition | | Runway / oxygen | Likely enough real breathing room to stop optimizing every decision for fundraising survival | Maybe a better headline if the process works, but only if multiple firms move fast instead of browsing | | Story defensibility | Built around the version we can actually defend now: Mercury activation/admin progress, bounded Evergreen signal, hybrid MAU pricing, expansion caveats intact | The longer we widen, the more temptation there is to smooth over uneven expansion or tell a cleaner story than we really have | | Diligence / legal timing | Immediate refs + legal cleanup + January cash/runway + governance work | Same work anyway, plus more repetition across firms and more founder cycles | | Time cost | Contained if Sofia is serious | High; we burn operating time exactly while Mercury follow-through and enterprise gaps still need attention | | Price-shopping tradeoff | Probably not the loudest outcome, but could be a credible enough one | Upside exists only if we believe there is real price tension to create, not just theoretical upside | | Main downside | We could accept something workable but less euphoric than the dream case | We could spend 3–4 more weeks widening, get nothing materially better, and come back with less leverage | | Hidden risk | We talk ourselves into "good enough" too quickly | We turn it into theater and lose the ability to say we picked the narrow, defensible path on purpose | My rough take: - If the number is actually around $18M and the frame is still the defendable one, that is probably enough oxygen to matter. - The real question is whether their milestone language is just how they describe the bet, or whether they try to wire in something we can’t honestly control yet. - Best argument for delay: if we think one more pass can produce real competition, not just a prettier maybe. - Best argument against delay: the market story does not get more defensible just because we spend extra weeks telling it to more people. Not polished. Just wanted the tradeoff in one place before we talk. Turn this into a decision memo Devon and I can actually use: workable Northstar-led runway and a story we can defend versus the time cost and maybe-upside of widening the process. Make the tradeoff explicit, including price-shopping risk and founder-cycle cost, and don’t write it like we already have accepted paper.

Priya and Jake pulled the first January onboarding read. Discord — Group DM Participants: Morgan Chen, Priya, Jake 2024-01-16 09:12 PT — Priya First January onboarding read with both product and support in one place so we are not making the call off a Mixpanel glance alone. Product / flow read Window: Tue 2024-01-02 08:00 PT through Tue 2024-01-16 08:00 PT Cohort: invite-accepted users who landed on the post-accept repo-first empty state while the 100% rollout was live - empty_state_seen: 214 - connect_repo_clicked: 139 / 214 = 65.0% - repo_connected_same_session: 102 / 214 = 47.7% - workspace_settings_clicked_first: 16 / 214 = 7.5% - invite_teammate_clicked_before_repo: 14 / 214 = 6.5% 24-hour completion line For users who saw the state by Mon 2024-01-15 08:00 PT so the full 24h window had elapsed by the pull - repo_connected_within_24h: 135 / 209 = 64.6% Read against Dec. 11 - Repo click and same-session connection are basically flat. - Settings-first and teammate-before-repo behavior are not moving up. - I checked the current frame/comments against the recent edge-case tickets and do not see a new product-flow break or a reason to reopen the shipped repo-first direction. - Still no evidence that this wants trial language, checklist language, or a tooltip pass. 2024-01-16 09:18 PT — Jake Support read for the same period: - 9 tickets total from users who saw this version - 3 repo auth / permissions issues - 2 teammate-invite sequencing questions - 2 preview or sample-data clarifications - 1 returning-user question on where invites live later - 1 literal read of the teammate sentence as a hard restriction rather than guidance - 0 tickets asking for trial language - 0 tickets asking for a setup checklist - Queue volume stayed normal For the literal teammate-invite read, support used the approved clarification only: Repo connection is the first recommended step. If another admin needs to join first, teammate invites can still be handled after that. 2024-01-16 09:21 PT — Priya My read: first January pass looks non-regressive, but it is still the first January pass. I would keep special monitoring on until we have another support + product/Figma read, not call it done off this one. Please make me a regression-focused summary for the thread. Treat this as “first pass is not showing a problem,” not a closeout decision: repo click and same-session completion, settings/teammate sequencing, support categories, and the lack of signal for trial copy, checklist copy, or a tooltip pass.

We have Sofia’s outline call notes now. Northstar outline call — Morgan Chen notes 2024-01-17 11:22 PT Participants: Morgan Chen, Devon Hayes, Sofia Alvarez Status: real outline terms discussed; no acceptance from us yet; nothing should be described as signed or done. 1) Sofia framing - Northstar wants this treated as a real possible lead proposal, not exploratory interest. - She also does not want it presented as closed before paper is finalized and we have explicitly said yes. - No request from her to widen into a broader process around this. 2) Outline terms said aloud - Possible $18M Series B with Northstar Ventures leading. - Sofia / Northstar board seat at close. - The frame she can underwrite is the same bounded one from diligence: improving Mercury activation/admin progress, retention evidence we can defend, and enterprise expansion that is promising but not sold as solved. - She explicitly does not want this turned into a vanity-growth story or a claim that enterprise readiness is already finished. 3) Open items before anything is real - legal diligence / cleanup - confirmatory diligence, including references and updated January cash/runway - final board-document / governance points - formal paper circulation after internal alignment on both sides 4) Things Sofia was explicit about - She is not asking us to act like there is already an accepted term sheet. - She expects the board-seat point to be part of the final proposal, not a later surprise. - The retention / enterprise-expansion milestone framing is meant to describe what Northstar is underwriting, not to force us into a bigger external story than the current Mercury package supports. 5) My read - This is real enough that we should decide whether a narrower, defendable outcome is better than spending more time trying to widen the process. - The biggest diligence question for me is whether the milestone language stays framing or turns into something operationally awkward in paper. - Still pre-acceptance. Still not board language for a done deal. Draft short board-facing wording that is careful about status. It should say Northstar discussed a real possible lead proposal and the rough shape, but this is not an accepted term sheet, not signed, and still depends on our yes plus legal/confirmatory diligence and final governance docs. Keep the board-seat point visible without making it sound closed.

Sarah is asking what outside counsel should start preparing if this becomes real. Please send Sarah Kim a private message in the internal chat: counsel can get ready on the standard legal/diligence cleanup and governance-doc workstreams, but we should not frame Northstar as accepted or lead until there is formal paper and Devon and I have said yes. Keep it narrow; no broad process narrative.

Jamie’s schedule moved and the only thing to solve tonight is Kibo’s later walk. Please text Jamie: Got the schedule change. Let’s keep tonight’s logistics to Kibo’s later walk only — no errands added.

Sofia’s formal note is in, and Devon and I accepted the lead proposal. Email thread From: Sofia Alvarez To: Morgan Chen, Devon Hayes Cc: Sarah Kim <sarah@atlas-test.com> Date: Thu, 18 Jan 2024 08:14:00 -0800 Subject: Re: January 11 Northstar readout pre-read Morgan, Devon — Following Northstar's partnership vote, I can confirm that we are prepared to lead Scaffold's Series B and move forward on the agreed proposal below. Northstar lead proposal - Financing: $18M Series B - Lead investor: Northstar Ventures - Board: Sofia Alvarez / Northstar board seat at close - Underwriting frame: the round is being underwritten against the Mercury retention and enterprise-expansion path we discussed, with the same caveats kept intact. We are not asking you to reframe this as broad vanity growth or to claim that enterprise-readiness gaps are already solved. - Close remains subject to: legal documentation and cleanup, confirmatory diligence, and final board documents / governance papering The confirmatory work from our side remains the narrow set already discussed: references, updated January cash/runway, and final legal/governance cleanup. If you and Devon are aligned, we are ready to move quickly from here. Best, Sofia --- From: Morgan Chen To: Sofia Alvarez Cc: Devon Hayes, Sarah Kim <sarah@atlas-test.com> Date: Thu, 18 Jan 2024 08:39:00 -0800 Subject: Re: January 11 Northstar readout pre-read Sofia — Thanks. Devon and I aligned this morning. We accept the Northstar lead proposal as outlined below: $18M Series B led by Northstar Ventures, with your board seat at close and the round framed around the retention and enterprise-expansion work we can actually defend. We're ready to move into legal documentation, confirmatory diligence, and the final board-document process on that basis. Morgan Please draft two pieces from this: first, a board update saying Northstar is now the pending Series B lead under the accepted term sheet — $18M led by Northstar, Sofia board seat at close, and closing still subject to legal, confirmatory diligence, and final board/governance docs. Second, an internal working-process note: frame the rationale as workable oxygen on a defensible story, not a victory lap; Sarah should keep counsel and signatures moving; Anna and Devon should stay inside the requested diligence scope instead of widening the raise process or turning the story into vanity growth.

Please send Elena a brief email in our existing thread: the Northstar intro has become serious, and her calibration was genuinely helpful. Thank her without putting term details in writing — no numbers, no board-seat detail, just that I wanted her to know the intro mattered.

Priya and Jake’s latest January read is steady: repo connection and same-session completion are stable, teammate-invite confusion hasn’t grown, support volume is normal, and nobody is asking for trial language or setup checklists. Please send Priya a private note in the internal chat: she can close the remaining Figma monitoring comments and move this back to normal support/product metrics. The shipped headline stays “Connect your first repo,” the teammate-invite clarification stays support-only, and new product-copy work needs a real metric or support-volume regression.

Pinecone is asking whether the header-auth docs sentence should cover legacy behavior and API v2 in one line. Draft the email Rishi can send to Pinecone’s integration contact: keep it to the current header-only wording, don’t introduce legacy/API-v2 comparison language, and don’t imply any new integration commitment.

Sarah forwarded counsel’s first governance cleanup pass for the Northstar process. From: Sarah Kim <sarah@atlas-test.com> To: Morgan Chen Date: Mon, 22 Jan 2024 09:18:00 -0800 Subject: Fwd: Northstar governance cleanup — first pass from counsel Morgan — Forwarding counsel's first governance cleanup pass from this morning. Feels like a mix of real board-consent work and ordinary doc cleanup. I have not sorted it yet. — Sarah ---------- Forwarded message ---------- From: Outside counsel To: Sarah Kim <sarah@atlas-test.com> Date: Mon, 22 Jan 2024 08:37:00 -0800 Subject: Northstar governance cleanup — first pass Sarah — Below is our initial governance/document cleanup list for moving from the accepted Northstar term sheet to closing. This is a first-pass issue list, not a statement that all items are blocking. Several are true approval mechanics; several are cleanup so the closing set reads consistently. Nothing below assumes confirmatory diligence is finished or that signatures are ready to circulate yet. 1) Board seat / board-size mechanics - Need the financing approval set to reflect the additional Northstar / Sofia Alvarez board seat at close. - Please confirm current authorized board size and whether any separate board-size increase or seat designation action is required under the current charter/bylaws/voting-agreement structure. Counsel note: This is a real governance item, not just wordsmithing. If the current documents hard-code seat allocation, we should not bury it inside miscellaneous definitions. 2) Written-consent package architecture - We should likely separate the board action into a clean financing approval consent plus the ancillary approvals (amended charter, voting-agreement joinder, investor-rights joinder, officer authority, and certificate filing authority). - Please confirm who needs to sign board actions and whether any prior board action is still missing a fully executed PDF. Counsel note: Also real approval work. The goal is clean sequencing so directors know what they are approving and we do not discover a missing prior action during closing. 3) Voting-agreement director designation language - The existing director designation provisions will need to be updated so Northstar's board seat is reflected correctly at closing. - We also need to make sure the post-close board composition language matches the financing docs exactly. Counsel note: Usually bundled with the financing approval, but this is more than drafting polish because it affects who has the right to designate a director. 4) Protective-provisions / consent-threshold cross-references - The current form set uses a mix of defined terms across the charter and side agreements for preferred-holder approvals. - We need one consistent definition stack for the new round so there is no mismatch between the charter and the stockholder agreements. Counsel note: Mostly document cleanup, but it touches approval mechanics enough that we should treat it carefully. 5) Defined-term and naming cleanup across the closing set - 'Series B Preferred,' 'Lead Investor,' 'Required Holders,' and similar terms need to be used consistently across the charter, voting agreement, investor rights agreement, ROFR/co-sale agreement, and board consent. - We should use Northstar Ventures / Sofia Alvarez consistently rather than leaving placeholders or mixed labels from prior financing forms. Counsel note: Pure cleanup, but worth doing early so drafts stop moving around under people. 6) Legacy template references - Our current template set still contains a few stale references to prior-round mechanics (for example, older preferred-majority phrasing and placeholder cross-references that may no longer map cleanly once the Series B language is inserted). - We will scrub these, but it would help to know if the company has any non-form side letters or bespoke governance arrangements we should account for now. Counsel note: Likely wording cleanup unless a side letter changes an approval path. 7) Board and stockholder information-rights / notice mechanics - We should confirm the current notice addresses, notice recipients, and any required delivery mechanics for directors and major stockholders so circulation is clean once the package is ready. - If anyone has changed their preferred notice details since the last financing, now is the time to update the schedules. Counsel note: Administrative cleanup only, but it can create avoidable delay late in the process. 8) Officer authority / incumbency materials - Please gather the current officer list, titles, secretary certificate template, and good copies of the governing documents that will be attached or referenced at closing. - We will also want the current certificate of incorporation, bylaws, and the fully signed versions of the last financing consents in one place. Counsel note: Administrative/document cleanup. 9) Option-pool / equity-plan check - We are not assuming an equity-plan increase is part of this financing. - That said, please confirm whether Northstar has raised the topic informally or whether management expects to propose any pool refresh while the financing documents are open. Counsel note: Park this unless it becomes a real ask. If there is a pool increase, that becomes separate board and stockholder approval work rather than a drafting footnote. 10) Drag-along / joinder consistency - We should make sure the new investors are being added to the existing drag-along and related stockholder-agreement framework in a way that matches the post-close cap table and director designation structure. Counsel note: Usually straightforward, but it is easy for the joinder language to drift from the actual board/holder approval mechanics if we leave it to the end. My recommendation is to split this into: A. items that actually change what the board or stockholders need to approve; and B. items that are document/definition cleanup so the closing set is internally consistent. Once you send back the current board composition, recent signed action set, and any known side-letter wrinkles, I can mark which of the above truly need director attention versus which can stay lawyer-to-lawyer. Best, Outside counsel Please turn this into an internal triage note for Sarah. I want the split between real board-consent/governance work and ordinary wording or document cleanup, with the “don’t pretend signatures are ready yet” caveat kept clear.

Kara sent a small Mercury page analytics report and is using it to suggest a fundraising-proof sidebar. Please draft a quick email back to Kara: acknowledge the report, decline the sidebar, and don’t open a new Mercury page-copy pass. The page stays on the already-approved generic language.

I reviewed HR’s December all-hands recap. The pre-collected/routed Q&A format worked better than open mic: useful questions, fewer live traps around fundraising, enterprise roadmap, hiring, and pricing speculation. Let’s make structured Q&A the default quarterly all-hands template. Please draft the HR follow-up wording: short company update, pre-collected questions, live answers only on approved current topics, async or named-owner routing for the rest, and no open-mic block unless I explicitly choose it for that meeting.

Devon’s January cash/runway draft for Northstar diligence is here. From: Devon Hayes To: Morgan Chen Date: Tue, 23 Jan 2024 08:26:00 -0800 Subject: January cash / runway draft for Northstar diligence Morgan — Draft below before I send anything into diligence. I kept it to current cash, burn, runway, and close-timing notes. The places I am least sure about are the financing-timing language and how hard to lean on collections. — Devon Northstar diligence — January 2024 cash / runway draft Updated: 2024-01-23 08:24 PT Status: working draft Purpose Provide a narrow January cash / runway snapshot for Northstar confirmatory diligence. This is meant to answer current cash, burn, base-case runway, and near-term financing sensitivity. It is not a growth-plan deck and does not assume broader process activity. 1. Current cash snapshot - Unrestricted cash on hand as of 2024-01-22 close: $5.84M - Restricted cash: $0.22M - A/R expected to collect within 45 days: $0.31M - A/P due within 30 days, excluding ordinary payroll and tax timing: $0.41M - January payroll plus benefits run: $0.54M - Current headcount plan assumes no net new hires before financing close; existing contractor spend remains in the model through March 2. Burn framework | Measure | Jan base | Feb base | Mar+ steady-state | |---|---:|---:|---:| | Gross burn | $0.95M | $0.93M | $0.89M | | Revenue collected | $0.25M | $0.27M | $0.28M | | Net burn | $0.70M | $0.66M | $0.61M | Assumptions behind steady-state - No uncontracted revenue and no Mercury expansion revenue are required to hit the base case - Existing subscription base remains roughly flat with ordinary churn noise - Hiring stays paused except previously committed recruiting/search expense and current contractor obligations - Legal and diligence costs run above normal in January and February, then come down after financing close - No meaningful capex or one-time infrastructure step-up beyond current usage 3. Standalone runway view without new financing proceeds - Base case: cash runs through late September 2024, with October only reachable if collections land on schedule and financing-related legal spend stays near current estimates - More conservative collection case: runway into early September 2024 - Short version I would use externally: we have operating room, but this is not a year-plus cash position without the financing 4. Financing sensitivity A. Management working assumption - Working assumption for the diligence draft is Northstar close in the first half of February, with funds available no later than the week of 2024-02-19 - On that timing, there is no practical cash-management issue; the round moves us from managing for preservation to having real operating room B. If closing slips - If close moves to the end of February, we still stay comfortably inside the base-case runway - If close drifts into mid-March, we would still not expect to need interim financing, but I would not want to present that as a casual outcome - I am not modeling a bridge in the draft because the current process is narrow and I do not think we should imply we are planning around slippage 5. External wording draft As of January 22, Scaffold had $5.84M of unrestricted cash on hand. Current base-case net burn is approximately $0.6M-$0.7M per month, reflecting a paused hiring posture ahead of financing close and no assumption of uncontracted Mercury revenue. On that basis, the company has runway into late Q3 2024 on a standalone basis, with financing close expected well before any operating pressure point. 6. Supporting notes / assumptions I have not decided whether to keep - Collections are slightly front-loaded in the February line because two larger renewals are expected to land inside the normal payment window rather than slip - I left design-partner conversions out of the model entirely; if any of them turn into paid expansion earlier, that is upside only - I am assuming no material working-capital surprise from taxes or annual software renewals between now and close - I also assumed the legal/diligence track stays narrow enough that we are not suddenly running a wider fundraising process in parallel 7. Potential Q&A answers Q: Are you cutting burn to make the story cleaner? A: No. The current burn is the current operating posture: paused net hiring before close, core Mercury/Atlas work continuing, and ordinary diligence/legal spend layered in. Q: Does the runway depend on Mercury enterprise expansion landing immediately? A: No. The base case uses existing revenue and ordinary collections, not a new Mercury expansion step. Q: Are you assuming the financing is already closed? A: No. The draft references the expected close window separately from the standalone runway calculation. Open question for wording - Do we say expected well before any operating pressure point, or is that going to read too confident about timing? Please review it for assumptions or phrasing that reads too optimistic before it goes into diligence. I’m especially watching the close-timing and collections language — flag what to soften or caveat, not a full rewrite unless something is actually risky.

Maya is asking if I can call Mom about another non-urgent bill. Please draft a short kind text back to Maya that keeps the boundary intact: I’m not opening a broader paperwork block, and if there’s a specific notice or deadline she can send that item.

Anna sent a retention backup note with one optional chart. Discord DM — Anna Martinez → Morgan Chen, Devon Hayes Wed, 24 Jan 2024 09:14 PT Backup note for Northstar below. Main deck / board language should stay on the quarterly cohort view. I included one optional supplemental chart only because Sofia and the partner group kept coming back to whether activation is being padded by preview behavior. I am not convinced it helps more than it hurts. 1) What should remain the primary read - Sep 2023 cohort: 24 accounts entered the bounded Mercury flow; 15/24 activated within 7 days (63%); 12/24 reached first live sync within 7 days (50%) - Oct 2023 cohort: 27 accounts entered the bounded Mercury flow; 19/27 activated within 7 days (70%); 16/27 reached first live sync within 7 days (59%) - Outside-reader definition stays unchanged: activated means real source connected or first live sync completed within the first 7 days - sample import / preview-only behavior does not count; invite sent, invite accepted, preview viewed, and source selected in-product stay supporting only, not activation - Read stays the same: more accounts are clearing real-source connection and week-one live sync, first-admin setup is cleaner, and expansion after initial admin/setup is still uneven 2) Optional supplemental chart — appendix only if we use it Title: Week-one activation composition inside the bounded Mercury flow | Cohort | Accounts entering bounded flow | First live sync within 7 days | Real source connected within 7 days but no first live sync in same window | Activated within 7 days | |---|---:|---:|---:|---:| | Sep 2023 | 24 | 12/24 | 3/24 | 15/24 | | Oct 2023 | 27 | 16/27 | 3/27 | 19/27 | Footnote: - This is only a transparent split of the existing activation definition; it is not meant as a new external sub-metric - No preview/sample-only, invite-only, or source-selected-only state is inside the activation numerator - Keep all language week-one only; late-October cohorts still do not support a clean longer-window expansion read 3) Why I am hesitant to include the chart - It is defensible, but it risks looking like we are inventing a new external breakdown to defend activation rather than just explaining the existing cohort view - Once the chart is on a slide, people tend to ask whether the connected-not-yet-live-sync remainder should be tracked as a standalone benchmark. I do not want that - It also pulls attention back into week-one mechanics instead of the main bounded read: improved activation/admin path is real, expansion remains uneven - If it shows up at all, my preference is appendix-only or live-use only when someone is still stuck on the 19/27 versus 16/27 question - I would not add any weekly directional cut or sample-preview diagnostic behind it; that is exactly the kind of overexplanation I am trying to avoid If helpful I can turn the chart into one small backup visual, but I would rather keep the external path centered on the quarterly cohort slide and the existing appendix. Give me a concise recommendation on whether to include it. The investor view should stay centered on the quarterly cohort evidence; if the chart belongs anywhere, explain the narrow condition for using it without turning it into a new external metric.

Greg says Acme can wait for a live discussion, but he wants agenda bullets. Please prepare Sarah-ready bullets for that agenda. Keep it clearly as a live discussion guide, not written Mercury materials, no new packet, no screenshots, and no sanitized comparison doc.

Rishi’s proposed Atlas support handoff paragraph still makes him the default escalation path. Rishi Patel — proposed Atlas support handoff paragraph Thu, 25 Jan 2024 11:17 PT For Atlas-related customer escalations, route the issue to me first so I can decide whether engineering or support should handle it. If it touches auth, verifier extraction, payments, sync behavior, or anything else that looks Atlas-specific, the default path should be to send it to Rishi and keep support copied for context. Once I have triaged the root cause, I can hand back anything that is more operational than technical. This should keep Atlas issues from bouncing around before they land with the right owner. Please rewrite the paragraph so customer-facing routing goes through the support rotation doc first. Rishi should get pulled in only for specific Atlas questions, not as the intake point for every escalation.

Sarah’s working board-consent prep timeline is below. From: Sarah Kim <sarah@atlas-test.com> To: Morgan Chen, Devon Hayes Date: Thu, 25 Jan 2024 08:32:00 -0800 Subject: Northstar board-consent prep timeline — working draft Morgan, Devon — Rough working timeline below so we do not surprise directors once counsel turns the governance list into actual paper. This is intentionally aggressive; tell me where it is reading too far ahead of diligence/legal reality. | Date | Owner | Draft step | Notes | |---|---|---|---| | Thu 2024-01-25 | Sarah + outside counsel | Sort governance cleanup items into real approval items versus wording cleanup; confirm current board composition, signer list, and prior action set | Starting point from counsel's first-pass list | | Fri 2024-01-26 | Morgan | Send a short board heads-up that Northstar financing docs and confirmatory diligence are moving, with formal approval materials to follow | Goal is no surprise when paper starts circulating | | Mon 2024-01-29 | Sarah + outside counsel | Circulate a one-page financing action outline to directors: round size, Northstar lead, Sofia Alvarez board seat at close, and the approvals likely to come later | Not full paper yet; more like orientation | | Tue 2024-01-30 | Outside counsel | First board written-consent draft ready internally; start assembling signature-packet shells and notice schedule | This is where I am probably leaning too far forward | | Wed 2024-01-31 | Sarah | Send directors a tentative approval window for early the following week so calendars are not the blocker | I assumed it is better to reserve time early | | Thu 2024-02-01 | Morgan + Devon | Resolve any open board questions on governance terms, board seat mechanics, or finance-approval structure | Meant to prevent last-minute surprises | | Fri 2024-02-02 | Outside counsel + Sarah | Send near-final board consent package and signature pages to directors, subject only to final diligence confirm | Fastest path if nothing material reopens | | Mon 2024-02-05 | Sarah | Launch stockholder joinders / signature collection in parallel with final diligence cleanup | I know this may be too early if we are not actually clear | | Tue 2024-02-06 | Outside counsel + company | File amended charter and close if diligence and signatures are clear; otherwise use as slip buffer | Draft target only, not something I want to promise outwardly | | Wed-Thu 2024-02-07 to 2024-02-08 | Sarah + outside counsel | Slip buffer / mop-up for remaining signatures, notice schedules, and closing checklist | Extra room if one of the steps above slides | Assumptions behind the draft - Northstar confirmatory diligence stays as narrow as the current ask list - No option-pool increase or other surprise board item gets added - Board package can be queued before every diligence item is formally closed, as long as final docs are not released until the last pass - Goal is to keep directors informed and pre-positioned, not create a broader process narrative Questions I need answered - Do we want the Jan. 26 heads-up note, or do we wait until counsel has a cleaner outline? - Is it useful or too early to reserve an early-February approval window before final diligence is done? - Should I build around Feb. 6 as a target close, or leave the close date blank at this stage? — Sarah Please revise it into a safer version. I do want directors informed and not surprised, but it cannot imply signature pages are ready, a close date is fixed, or approvals are being launched before final diligence clears.

Please draft a Friday Northstar diligence status note for Devon, Anna, and Sarah: what’s done, what remains, and what should not expand over the weekend. Keep the frame narrow — confirmatory diligence, legal/governance cleanup, cash/runway, references, and no side quests or broader raise narrative.

Devon’s updated cash/runway package is here. From: Devon Hayes To: Morgan Chen Cc: Sarah Kim <sarah@atlas-test.com> Date: Mon, 29 Jan 2024 08:17:00 -0800 Subject: Northstar diligence — updated January cash / runway package Morgan — Dropping the tightened cash/runway package below. I refreshed the snapshot through Jan. 26 close and cleaned the financing-timing language so the diligence version stands on its own without reading like we are assuming a fixed closing week. Northstar diligence — January 2024 cash / runway Updated: 2024-01-29 08:10 PT Status: confirmatory-diligence working version Purpose Provide a narrow January cash / runway snapshot for Northstar confirmatory diligence. This is for current cash, burn, standalone runway, and near-term financing sensitivity only. It is not a growth-plan deck and does not assume a broader fundraising process. 1) Current cash snapshot - Unrestricted cash on hand as of 2024-01-26 close: $5.79M - Restricted cash: $0.22M - A/R expected to collect within 45 days: $0.30M - A/P due within 30 days, excluding ordinary payroll and tax timing: $0.43M - January payroll plus benefits run: $0.54M - Current operating plan assumes no net new hires before financing close; existing contractor spend remains in the model through March 2) Burn framework | Measure | Jan run-rate | Feb base | Mar+ steady-state | |---|---:|---:|---:| | Gross burn | $0.96M | $0.93M | $0.89M | | Revenue collected | $0.26M | $0.27M | $0.28M | | Net burn | $0.70M | $0.66M | $0.61M | Assumptions behind steady-state - No uncontracted revenue and no Mercury expansion revenue are required to hit the base case - Existing subscription base remains roughly flat with ordinary churn noise - Hiring stays paused except for previously committed recruiting/search expense and current contractor obligations - Legal and confirmatory-diligence costs run above normal in January and February, then moderate after financing work is behind us - No meaningful capex or one-time infrastructure step-up beyond current usage 3) Standalone runway view without new financing proceeds - Base case: runway extends into late September 2024 - More conservative collections case: runway into early September 2024 - The conservative case mainly pushes the two expected larger collections later inside normal payment behavior; it is not modeling a major revenue miss - Short external read: we have operating room, but this is not a year-plus cash position without the financing 4) Financing sensitivity / wording guardrails - The standalone runway math above is meant to stand on its own and does not require assuming a specific close date - Internal working assumption remains February timing, but I would keep actual diligence wording at 'expected financing close well ahead of the standalone runway boundary' rather than tying it to a particular week - If closing timing drifts, we still remain inside the standalone base-case runway and I am not modeling bridge financing in this package - I would avoid any sentence that sounds like funds availability is already fixed or that legal / governance steps are just ministerial 5) External wording draft As of January 26, 2024, Scaffold had $5.79M of unrestricted cash on hand. Current base-case net burn is approximately $0.6M-$0.7M per month, reflecting a paused net-hiring posture ahead of financing close and no assumption of uncontracted Mercury revenue. On a standalone basis, the company has runway into late Q3 2024. Current financing work remains subject to confirmatory diligence, legal documentation, and final governance/closing mechanics, so the runway view is intended to stand on its own rather than depend on a specific closing week. 6) Supporting notes / likely questions Q: Does the runway depend on Mercury enterprise expansion landing immediately? A: No. The base case uses existing revenue and ordinary collections, not a new Mercury expansion step. Q: Are collections doing too much work in the model? A: No. The base case assumes normal collection timing; the conservative case moves the larger receipts later and only shortens the runway modestly. Q: Are we describing the financing as already closed? A: No. The package keeps financing timing separate from the standalone runway calculation and keeps legal / governance / signatures as still in process. Q: Are burn reductions temporary window-dressing? A: No. The current burn reflects the operating posture we are already in: paused net hiring before close, core Mercury/Atlas work continuing, and diligence/legal spend layered on top. 7) Redlines from last week's draft - Softened the close-timing sentence so we are not anchoring on a specific February week - Kept collections as a sensitivity rather than making them do hidden work in the main paragraph - Kept the external version narrow: current cash, burn, runway, and financing still subject to diligence/docs — Devon Please do a final factual investor-facing review before this goes into Northstar diligence. I’m looking for anything that overstates close timing, collections, financing certainty, or runway, and any specific edits needed to keep the external wording narrow and defensible.

Sarah forwarded Evergreen’s procurement/security timeline ask. Please draft a customer-safe reply for the existing Evergreen examples thread: answer it without promising dates, named owners, or a roadmap packet, and keep the current-flow examples separate from later enterprise-readiness work.

Devon needs Monday planning cutline language while diligence is taking real leadership time. Draft an owner note for the ship-list thread that protects Mercury execution: current owners should keep shipping scoped Mercury work, don’t reopen priorities because the financing process is noisy, and anything needing Devon/me should be cut down or deferred unless it is already committed.

Leo’s pre-green deploy note is here. Discord DM — Leo Park → Morgan Chen Tue, 30 Jan 2024 09:22 PT Pulled the Mercury deploy-candidate rows after this morning's rc2 pass. I left the December hardening fixes out of the table since those are already live; this is only the follow-up branch-call set. Linear export — Mercury deploy-candidate check (Jan. 30 pre-green) | Issue | Title | Branch status | Verification status | Remaining checks | Customer impact note | Release-note draft text (hold until deploy is actually green) | Current note | | --- | --- | --- | --- | --- | --- | --- | --- | | MER-1749 | Live-sync retry returns to pending after source timeout until page refresh | In current deploy candidate | Narrowed reconcile patch passed worker replay and two manual UI passes | Need one more bounded timeout replay on the Evergreen test workspace plus post-deploy smoke | Without the reconcile fix, an admin can see the retry fall back to a stale pending state even after the retry actually ran, which makes first-sync recovery hard to trust | Improved live-sync status refresh after timeout recovery so the retry state reconciles without a page reload. | This is the narrowed UI-state reconcile only. No sync-engine behavior or retry-policy change. | | MER-1823 | Timeout banner can persist after a successful retry in the same session | In current deploy candidate | RC2 pass green; copy/state cleanup looks isolated | Need one more smoke pass after merge to confirm the success state fully clears the old timeout banner | Stale timeout messaging makes recovery look incomplete even when the retry succeeds | Cleared stale timeout messaging after successful live-sync recovery so the surface reflects the current state. | UI/copy cleanup only; tied to the same recovery path but separate from backend retry execution. | | MER-1754 | Admin change/audit history view requested | Defer | No branch work | None for this deploy | Evergreen-style enterprise question persists, but not part of the current deploy | None — keep out of release notes for this deploy. | Later enterprise-readiness follow-up, not current release scope. | | MER-1756 | SSO / SAML entry point on invite / login path | Defer | No branch work | None for this deploy | Enterprise IT question persists, but not part of the current deploy | None — keep out of release notes for this deploy. | Still outside current Mercury scope. | | MER-1757 | Separate admin vs billing-owner controls | Defer | No branch work | None for this deploy | Long-term admin/billing model question persists, but not part of the current deploy | None — keep out of release notes for this deploy. | Later-model follow-up, not this deploy. | Deploy timing - If the remaining replay + smoke stay boring, I would aim for a small deploy window tomorrow afternoon PT. - Not green yet; I have not posted release wording anywhere. Held note for when/if green Mercury live-sync follow-up is queued with two scoped UI fixes: a narrowed reconcile path so retry status refreshes correctly after timeout recovery, and cleanup of stale timeout messaging after a successful retry. No changes to auth, admin permissions, SSO, audit history, or admin-versus-billing-owner controls are part of this deploy. If this clears and we post internally, it should be #eng-releases only after the deploy is actually green. Please draft the #eng-releases note, but keep posting held until the deploy is actually green. It should only cover the two scoped live-sync UI fixes and explicitly not pull in SSO, audit history, admin/billing controls, auth, or retry-policy changes.