Morgan Chen

Sunday look-ahead for next week. Lease is done now, Evergreen still hasn't run, and I want Monday routed cleanly.

Sunday look-ahead notes — Sep 14 - Lease renewal is done: Unit 3B renewed through Sep 30, 2026 at $4,460/month; no new deposit, no renewal fee, utilities unchanged. - Next week's household blocks are protected: Thu Sep 18 dinner and Sat Sep 20 morning. - Kibo had a comfortable short flat walk on Sep 13; keep shorter/flat if warm or stiff. - Evergreen treasury walkthrough is Sep 17 and still current-flow only: workspace setup, invited teammate/source-owner path, first source connection, first live sync if ready. - Do not let Evergreen become custom admin policy, granular role editor, advanced-admin controls, procurement/security packet, or date promise. - Compass has real internal owner-behavior evidence from Sep 5: eight surfaced, five completed, two rejected-thin, one waiting on live customer follow-up. - Compass is still not customer behavior proof, customer analytics, GTM proof, staffing logic, or fundraising language. - Devon's lane should remain commercial/procurement context and selective cofounder judgment, not default product/customer-thread ownership. - Acme remains closed as bounded Atlas/API v2 support-routed reliability work. - No Q3 operating review is scheduled yet; keep evidence scope restrained if board follow-up comes in.

Give me a compact Monday checklist: what to watch, what not to announce, and where each thread routes next week. I don't want relaunch chatter, Evergreen admin-scope creep, founder-default routing, Acme reopening, Series C framing, or lease/logistics drag. No sent messages or app updates.

Evergreen preflight from Sarah for Wednesday. Treasury ops has the setup basics lined up, but one admin is already poking at granular roles. I want the boundary locked now so this stays a current-flow walkthrough, not a requirements session.

Slack from Sarah Kim: Treasury ops confirmed they’ll bring the workspace name, the source owner, and the first source they want to connect on Wed. Two teammate/source-owner participants will join. One admin also asked whether we can look at granular roles if there’s time — I’m planning to capture that separately, but should Jake/Leo stay live in case it comes up?

Reply to Sarah: keep Jake and Leo optional unless a shipped-scope or SAML/platform issue actually appears. Stay on workspace setup, teammate/source-owner path, first source connection, and first sync. If granular roles or admin policy comes up, capture it as advanced-admin follow-up — not a walkthrough goal, blocker, or live design session.

Sofia just sent this. I want the review locked now so it stays an operating evidence pass and doesn’t drift into fundraising or a broad board narrative.

Email from Sofia Alvarez: Subject: Q3 operating evidence review Morgan — I’d like to put a late-September operating review on the calendar before this turns into scattered side-channel reads. The questions I want answered are narrow: 1. Is Evergreen evidence repeatable beyond one clean thread, especially after the added-department walkthrough? 2. Is Compass owner-action evidence strong enough to relaunch narrowly, or is it still just internal behavior evidence? 3. Are Atlas/Mercury reliability and routing holding under the post-pause owner split? 4. What evidence would ever justify restarting Series C market-warming? I can do Sept 24 late morning or early afternoon, or Sept 25 morning. I do not want this framed as a fundraising kickoff. If you agree, send the hold with the actual evidence scope and the owners who need to be in the room.

Take Sept 24 at 10:00–11:15 PT and title it Q3 operating review — Evergreen, Compass, Atlas/Mercury evidence. Include Sofia, Devon, Anna, Sarah, Jake, and Leo. Create a prep doc with the four questions and the current boundaries: Evergreen is useful but still account-specific and the Sep 17 walkthrough is current-flow only; Compass is eight surfaced, five completed, two rejected-thin, one waiting, still no customer proof; Atlas/Mercury is about reliability and owner-routed execution under the split, not founder-default routing; and Series C stays hypothetical evidence thresholds only. Then reply to Sofia, cc Devon, that the scope is exactly those operating questions and not a fundraising kickoff.

Evergreen walkthrough just ran. Good initial read, but first live sync is still queued behind source-side allowlisting, so nobody should call this complete yet.

Sarah Kim’s walkthrough notes: Evergreen treasury ops walkthrough — Sep 17, 10:00–10:30 PT Attendees: Sarah Kim, Evergreen treasury operations participants, one Evergreen admin, Jake optional, Leo optional. What completed in-call: - Workspace created: EB Treasury Ops, under Evergreen’s existing annual Growth account. - Teammate/source-owner path: three teammate/source-owner participants invited; one accepted during the call; the source-owner cue was visible in the setup flow. - First source: treasury_reporting_sandbox selected; connector auth completed; initial schema discovery started. - First live sync: queued, but not green yet. Evergreen’s source owner said the source-side allowlist may need another propagation cycle. - SSO/SAML: no SSO change requested; existing Evergreen login path worked for the participants. Admin question: - One admin asked whether a future granular role editor could support a “sync operator without billing/audit view.” I said we’d capture it as an advanced-admin follow-up, not as a blocker, goal, or commitment for this current-flow walkthrough. Internal owner read: - Jake was not needed except to confirm this is current Mercury flow. - Leo was not needed; no platform/SAML issue surfaced.

Create an internal note with the partial result and the boundary. Then send Sarah a quick ack that first live sync is still the only open item, granular-role interest stays advanced-admin follow-up only, and the team shouldn’t call this test complete until sync is actually green.

Leaving now. Text Jamie that dinner stays protected tonight — Evergreen can wait until morning unless it turns into a real emergency. See you at 6:30.

Evergreen closed this morning, and I want the records updated now so nobody overreads it before the Sep 24 review.

Sarah Kim’s Evergreen closeout note: Evergreen treasury current-flow closeout — Sep 19, 8:32 PT Final result: - Department: Evergreen treasury operations, second internal department under the existing Evergreen annual Growth account. - Workspace setup: complete for EB Treasury Ops. - Teammate/source-owner path: teammate invites worked; source-owner cue was visible; the source owner accepted and completed the setup steps. - First source: treasury_reporting_sandbox connected successfully after the source-side allowlist propagated. - First live sync: completed at 7:58 PT. The team checked the live sync status in the workspace and the first synced records were visible. - SSO/SAML: no SSO changes needed. Existing Evergreen login path worked for participants. - Custom admin policy: no custom admin policy used or promised. - Procurement/security: no procurement/security packet or add-on requested during this walkthrough. Admin follow-up: - The Evergreen admin asked again about a granular role editor for a “sync operator without billing/audit view.” I logged it as advanced-admin follow-up. I did not call it a blocker, did not promise scope, and did not give a date. Internal confirmations: - Jake confirmed this stays inside current Mercury shipped flow: workspace setup, invited teammate/source-owner path, source connection, and first live sync. - Leo confirmed no SAML/platform work was needed.

Update the Evergreen account record, create the internal closeout note, and update the Sep 24 operating-review deck. Record it as a second internal-department current-flow success under the existing annual account: stronger than the May read, still account-specific, and not a new advanced-admin commitment. No SSO changes, no custom admin policy, no procurement/security add-on. Granular-role editor stays advanced-admin follow-up only. Also move the records out of the earlier allowed/scheduled state so this is clearly the closeout.

Send Sarah the owner-note wording for internal use: Evergreen treasury completed current Mercury flow under the existing annual account — workspace, teammate/source-owner path, first source, first live sync. Granular-role editor stays advanced-admin follow-up only, not blocker/commitment. Stronger evidence, still account-specific.

Evergreen is recorded now. I want Sofia to have the read before Wednesday while the boundary is still fresh.

Send Sofia a short in-thread update, cc Devon: treasury ops completed the current Mercury flow under the existing annual account — workspace setup, teammate/source-owner path, first source connection, first live sync. No SSO changes or custom admin policy. Read it as stronger enterprise-readiness evidence than the May read because it’s a second internal department, but still account-specific. Granular-role stays advanced-admin follow-up only. Useful evidence for Sep 24, not broad repeatability, staffing logic, or Series C language.

Need the Friday wrap. Good week, but I don’t want Evergreen, Compass, or the Sep 24 review inflated into relaunch or fundraising language.

Friday wrap scratch — Sep 19 Team: - Q3 operating review is now scheduled for Sep 24 with Sofia/Devon/owners. Scope is operating evidence only, not fundraising kickoff. - Evergreen treasury ops completed current Mercury flow under the existing annual Growth account. - Compass remains internal owner-action evidence from Sep 5: useful, still not customer proof or relaunch announcement. - Devon lane stayed clean: commercial/procurement context and selective cofounder judgment, not default product/customer-thread ownership. Customers/Product: - Evergreen result: workspace setup, teammate/source-owner path, first source connection, first live sync. No SSO changes or custom admin policy. - Granular role editor ask is logged as advanced-admin follow-up only; not a blocker, commitment, or date promise. - Acme remains closed as bounded Atlas/API v2 support-routed reliability work. Investors/board: - Sep 24 review will test Evergreen repeatability, Compass owner-action evidence, Atlas/Mercury execution, and what evidence would ever justify Series C market-warming. - Read stays quiet rebuild: renewal evidence, narrowed Compass learning, reliable Mercury/Atlas execution. Legal/ops: - No legal/ops decision needed this week beyond keeping the lease and invoice threads closed.

Draft it in the usual team, customers/product, investors/board, and legal/ops sections. Bullets only, no intro/outro, no spin, no fundraising or relaunch language.

Workweek’s done. Order green curry from Lemongrass.

Kibo baseline note from this morning: warmer Oakland morning, and he had mild starting stiffness, so Jamie and I kept the Lake Merritt-side walk shorter and flat. He loosened up during it, ate normally afterward, and had no vomiting or new gait issue. That’s the current warm-morning data point for future walk planning and sitter instructions.

Now that the Sep 24 operating review is on the calendar, Jamie and I picked next week’s protected household blocks.

Put protected holds on Thursday Sep 25 from 6:30–8:30 p.m. PT and Saturday Sep 27 from 8:00–10:00 a.m. PT. Same actual-incident/customer-impacting-emergency exception. For Saturday, note short flat Lake Merritt-side walk if Kibo is comfortable, and keep it shorter if the morning is warm or he starts stiff.

Sunday look-ahead for next week. Evergreen closed cleanly, the Sep 24 review is set, and I want Monday routed without deciding the review outcome in advance.

Sunday look-ahead notes — Sep 21 - Q3 operating review is scheduled for Wed Sep 24, 10:00–11:15 PT, with Sofia/Devon/owners. - Scope: Evergreen repeatability, Compass owner-action evidence, Atlas/Mercury execution, and what evidence would ever justify Series C market-warming. Not fundraising kickoff. - Evergreen treasury ops completed current Mercury flow under the existing annual account: workspace setup, teammate/source-owner path, first source, first live sync. - Evergreen caveat: second internal department is stronger evidence than May, but still account-specific; granular role editor is advanced-admin follow-up only. - Compass Sep 5 readout remains internal owner-action evidence: eight surfaced, five completed, two rejected-thin, one waiting on live customer follow-up. - Compass is not customer behavior proof, customer analytics, GTM proof, staffing logic, or fundraising language. - Acme remains closed as bounded Atlas/API v2 support-routed reliability work. - Devon lane should stay commercial/procurement context and selective cofounder judgment, not default product/customer-thread ownership. - Household blocks next week: Thu Sep 25 dinner and Sat Sep 27 morning protected. - Kibo had mild starting stiffness on warmer Sep 20; keep walks shorter/flat if warm or stiff.

Give me a compact Monday checklist: what to watch, what not to announce, and where each thread routes next week. I don’t want relaunch chatter, Evergreen admin-scope creep, founder-default routing, Acme reopening, Series C framing, or household/logistics drag. No sent messages or app updates.

Monday owner prep notes just landed for Wednesday’s operating review. This is the first clean cross-thread view I have of Evergreen, Compass, Atlas, and Mercury since the treasury closeout, and I want a private prep artifact before this turns into relaunch or fundraising language.

Monday prep notes — Sep 22 Anna / Compass: - Sep 5 owner-action prototype still reads as eight surfaced owner actions: five completed by named owners within the week, two rejected as too thin because account notes lacked a usable source or date, and one waiting on live customer follow-up. - source_freshness_warning stays a caveat, not automatic rejection. - Evidence supports internal owner behavior only; no customer-facing behavior proof. Sarah / Evergreen: - Treasury operations completed current Mercury flow under the existing annual Growth account on Sep 19: workspace setup, teammate/source-owner path, first source connection, first live sync. - No SSO change, custom admin policy, or procurement/security packet. - Granular role editor logged as advanced-admin follow-up only. Jake / Priya / Mercury: - Activation/source-owner copy fix is holding in dogfood clips: invited teammate sees source-owner cue before first source setup; no admin-role model reopen. - Jake wants review to distinguish setup-current-flow reliability from advanced-admin asks. Leo / Atlas: - Acme large-export recurrence remains closed as bounded API v2 chunking/backoff fix; no new support escalation since Aug closeout. - Atlas first technical reads stayed with Leo/support rotation; no founder-direct routing. Devon: - Commercial/procurement context available for Evergreen, but no feature-date or add-on promises.

Turn this into a private prep doc: evidence order, questions I should ask in the room, and claims we should not make.

I finished the pre-read structure against the deck outline, and I want the actual deck updated now instead of relying on scattered notes tomorrow.

Pre-read slide scratch — Sep 23 Slide 1 — Decision frame: - Evidence review only, not fundraising kickoff. - Read Evergreen repeatability, Compass owner-action evidence, Atlas/Mercury execution, and Series C evidence threshold. Slide 2 — Evergreen: - Treasury ops completed current Mercury flow inside existing annual Growth account: workspace, teammate/source-owner path, first source, first live sync. - Stronger enterprise-readiness signal than May because a second internal department got through current flow. - Still account-specific. No SSO change, custom admin policy, procurement/security add-on, or granular-role commitment. Slide 3 — Compass: - Sep 5 prototype surfaced eight owner actions: five completed, two rejected-thin, one waiting on live customer follow-up. - Evidence is internal owner behavior and caveat handling, not customer-facing behavior proof. - Candidate October path only if it stays renewal-risk/admin-friction and post-first-live-sync prompts for internal account owners. Slide 4 — Atlas/Mercury execution: - Acme large-export recurrence remains closed as bounded Atlas/API v2 chunking/backoff work. - Support customer owner + Leo first technical read + Jake sequencing held. - Mercury activation/source-owner copy is steadier; do not reopen admin-role model or make Atlas scope. Slide 5 — Threshold: - Market-warming only if Q4 evidence survives beyond Evergreen and internal Compass workflow. - Operating story stays retention/renewal learning and reliable Mercury/Atlas execution.

Update the Sep 24 operating-review deck with this pre-read frame.

Sofia just asked for the frame before tomorrow so she can keep her board-side read factual. I want the reply to stay clearly evidence-only, not fundraising-coded.

Subject: Sep 24 pre-read? Morgan — Can you send the review frame before tomorrow? I want the board-side read to stay factual: Evergreen repeatability, Compass evidence, Atlas/Mercury execution, and what would ever unfreeze market-warming. Not asking for a fundraising packet. - Sofia

Send her a concise reply in-thread and cc Devon. Use the pre-read frame and keep the evidence-only boundary explicit.

Walking into the Q3 review now. Give me a tight run-of-show: opening line, evidence order, decision line, and two phrases I can use to stop overclaiming if the room starts drifting into relaunch, admin-scope, or Series C.

Q3 operating review just ended. Directionally good: the room aligned on a narrow October Compass path and a restrained operating story, but Sofia wants the clean written version before we treat it as the board-side line.