Morgan Chen

Process payment for it.

Need the Friday wrap.

Keep it in my usual sections: team, customers, investors/board, legal/ops.

Short and caveated. No spin, no fundraising language. Week was basically: Devon pause held, Evergreen stayed bounded, Compass prompt tracking stayed internal, and Acme got scoped as Atlas/API v2 support work instead of Compass or Mercury.

Friday evening. Order the usual Lemongrass green curry.

Quick Kibo note: we kept the protected Saturday morning block, did the early short flat Lake Merritt-side walk, and he was stable after. Started a little stiff, loosened up, ate normally afterward, and no vomiting or new gait issue.

Before week three of Devon's pause fills up, Jamie and I picked the next protected blocks.

Put holds on Thursday July 17 from 6:30–8:30 p.m. PT and Saturday July 19 from 8:00–10:00 a.m. PT.

Same actual-incident/customer-impacting-emergency exception, and add the short Lake Merritt-side Kibo walk note if he's comfortable.

Sunday Compass scratchpad notes before the first Q3 read: Compass July scratchpad state before first Q3 read: Need from Anna/Sarah next week: - account - prompt type: renewal-risk/admin-friction or post-first-live-sync expansion - prompt sighting date - owner who saw it - evidence source link or account-thread excerpt - caveat - owner follow-up date, if any - outcome or current status Known caveats: - Evergreen admin-handoff rows may be useful only if Sarah attaches dated current-state follow-up. - Acme export row must stay Atlas/API v2 support context and not Compass proof. - Prompt sightings alone do not count. - No customer-facing claims, no GTM proof, no staffing trigger.

Make a short first-pass prep doc, then send Anna and Sarah the Monday ask for structured rows.

Sunday reset before week three of Devon's pause.

Week-two read: Acme got handled without Devon and is just bounded Atlas/API v2 follow-up; Compass prep is still internal; next household blocks are already on the calendar.

Draft me a short Monday checklist I can glance at: what I hold, what routes to owners, and what actually qualifies as a Devon emergency after this week. Don't send anything.

Anna and Sarah can have a first Q3 Compass retained-prompt read ready by Wednesday, but they want Jake and Leo in the room for implementation and data-seam boundaries.

Let’s put an actual calendar hold on it instead of letting this happen through Discord comments. Create a July 16 10:00–10:45am PT invite called Compass July first-pass evidence read with Anna, Sarah, Jake, Leo, and me. In the body, keep last night’s boundaries: structured rows only; prompt sightings alone do not count; Acme has to be checked as Atlas/API v2 context, not Compass proof; output is internal only.

Sarah sent the first rows she can actually defend for Wednesday. Pasting them here so we can triage before Anna folds them into the count: Row 1 Account: Evergreen Bank Prompt type: renewal-risk/admin-friction Prompt sighting date: 2025-07-02 Owner who saw it: Sarah Kim Evidence source/excerpt: Evergreen account thread, Jul 2: customer admin asked whether a custom admin-policy date could be included with the current Growth account setup. I answered with current-state language only: shipped SAML, workspace setup, teammate/source-owner cues, first live sync support path; no custom admin policy, granular role editor, procurement/security add-on, or roadmap date. Caveat: Useful only as current-state follow-up. Not a customer action caused by Compass. Owner follow-up date: 2025-07-02 Outcome/current status: Evergreen accepted the current-state answer and did not ask for a date in that thread. Row 2 Account: Evergreen Bank Prompt type: renewal-risk/admin-friction Prompt sighting date: 2025-07-09 Owner who saw it: Sarah Kim Evidence source/excerpt: Account-health note flagged possible admin-handoff confusion between workspace admin and source owner. I posted a current-flow clarification to the internal account note and reused the verified setup-guide wording for the customer-safe response. Caveat: Dated owner follow-up, but still internal/customer-thread hygiene. No new product commitment and no customer-initiated action. Owner follow-up date: 2025-07-10 Outcome/current status: Current-state wording stayed clean; no advanced-admin promise. Row 3 Account: Acme Prompt type: renewal-risk/admin-friction Prompt sighting date: 2025-07-09 Owner who saw it: Sarah Kim Evidence source/excerpt: During Acme account-health review, prompt surfaced export reliability risk. I routed the live issue through support with Leo for first technical read and Jake for bounded Atlas/API v2 sequencing. Caveat: This is Atlas/API v2 support context. It should not be Compass proof, Mercury scope, or customer-facing behavior-change evidence. Owner follow-up date: 2025-07-09 Outcome/current status: Narrower monthly replays continued; no customer-visible data-loss signal in replay checks; full-range fix queued separately.

Turn this into working notes that separate what counts as dated owner follow-up, what is just a prompt sighting rule, and what has to stay Atlas context. Acme stays out of Compass proof.

Anna just sent the first full tally. I want Wednesday framed around evidence quality, not a bigger Compass story. Compass retained prompt first-pass tally, Jul 1 through Jul 14 pull. Scope included: - renewal-risk/admin-friction prompts - post-first-live-sync expansion prompts - retained internal prompt track only Raw prompt hits: 11 Rows with dated owner follow-up: 4 1. Evergreen Bank admin-handoff clarification, prompt sighting 2025-07-02, Sarah follow-up 2025-07-02. Outcome: current-state clarification accepted in thread; no customer-initiated action. 2. Evergreen Bank admin-handoff clarification, prompt sighting 2025-07-09, Sarah follow-up 2025-07-10. Outcome: current-flow wording stayed clean; no advanced-admin commitment. 3. Acme export reliability/account-health handoff, prompt sighting 2025-07-09, Sarah/Leo/Jake support handoff 2025-07-09 to 2025-07-11. Outcome: Atlas/API v2 bounded follow-up; narrower replays completed; no customer-visible data-loss signal in replay checks. Caveat: should stay out of Compass proof. 4. Retained annual renewal note on another account, prompt sighting 2025-07-12, account owner follow-up 2025-07-14. Outcome: owner added a renewal note and next-touch date. No customer action yet. Rows with prompt sighting only: 7 - 3 post-first-live-sync expansion prompt sightings where owner viewed but did not follow up. - 2 renewal-risk/admin-friction prompt sightings without a source excerpt attached. - 2 admin-friction prompts where the owner follow-up date is missing. Readout caveats: - Prompt sightings alone should not count. - Dated owner follow-up can be tracked. - None of the eleven rows show customer-initiated action. - Evergreen rows are useful only as current-state/account-thread hygiene unless Sarah attaches dated follow-up. - Acme export recurrence must stay Atlas/API v2 support context and should not become Compass proof. - I would not call this behavior-change proof or customer-facing evidence.

Make me a short Wednesday pre-read with the count, what only tracks as dated owner follow-up, what does not count, the caveats, and the exact decisions I need from Leo and Jake.

Leo and Jake both replied in the Compass owner thread: Leo Park: I checked Anna’s Acme row against the July export notes. The signal is real account context, but the cause and next action are Atlas/API v2: cursor-paginated large-export path, long date range, nested fields, chunking/backoff follow-up. I would keep this out of Compass proof. It can be a dated support/owner handoff with a caveat, not evidence that Compass changed customer behavior. Jake: Agree. For Compass implementation, I am keeping this at prompt-level tracking. No dashboard rebuild, no Atlas work under Compass, and no Mercury activation/admin scope. If we learn anything Wednesday it should be about owner follow-up quality and evidence thresholds, not product surface expansion.

I want that boundary written back before tomorrow so it doesn’t reopen in the room. Send each of them a short DM from me confirming I agree: Acme is Atlas/API v2 context only, Compass proof stays owner-action/outcome based, and implementation stays prompt-level.

10am Compass read is coming up. Draft me a compact run-of-show I can glance at in the room: opening line, evidence order, explicit Acme boundary, Jake’s implementation boundary, and closing decision language.

Main thing is keeping four dated owner follow-ups from turning into a relaunch, customer proof, a staffing argument, or product-surface creep.

Compass first Q3 read just finished. Need the durable record now so nobody inflates this later. My notes: Attendees: Morgan Chen, Anna Martinez, Sarah Kim, Jake, Leo Park. Anna count: - 11 retained Compass prompt hits reviewed across renewal-risk/admin-friction and post-first-live-sync expansion prompts. - 4 rows have dated owner follow-up. - 7 rows are prompt sightings only, missing dated follow-up, or missing required source/caveat details. - 0 rows show customer-initiated action. Rows with dated owner follow-up: 1. Evergreen Bank Jul 2 admin-handoff clarification: Sarah followed up with current-state language the same day. Outcome: Evergreen accepted the current-state answer in that thread. Caveat: no customer-initiated action and no advanced-admin promise. 2. Evergreen Bank Jul 9/10 admin-handoff clarification: Sarah followed up with current-flow wording. Outcome: current-state language stayed clean. Caveat: no product commitment. 3. Acme Jul 9 export/account-health handoff: Sarah routed to support, Leo did first technical read, Jake accepted bounded Atlas/API v2 sequencing. Outcome: narrower replays completed and no customer-visible data-loss signal in replay checks. Caveat: Atlas/API v2 support context only; not Compass proof. 4. Other retained annual renewal note: account owner added a renewal note and next-touch date after the prompt. Outcome: no customer action yet. Leo boundary: - Acme’s July export signal must stay out of Compass proof because the cause and next action are Atlas/API v2: cursor-paginated large-export path, long date range, nested fields, chunking/backoff follow-up. - It may remain in account context only with the caveat that it is a dated support/owner handoff. Jake boundary: - Keep implementation at prompt level. - No dashboard rebuild. - No Atlas work under Compass. - No Mercury activation/admin scope. Decision: - Prompt sightings alone do not count. - Dated owner follow-up can be tracked. - Compass remains internal until owner actions and outcomes justify broader claims. - No customer-facing claim, GTM proof, staffing trigger, or Series C language from this read.

Create the final internal closeout record, update the Q3 operating evidence slide, and post the owner-group closeout in Discord with the count and caveats.

Sarah asked this before she closes Evergreen notes: Question before I close my Evergreen notes: because two Evergreen rows are in the dated owner-follow-up count, can I say anything like ‘our internal Compass review surfaced this admin-handoff clarification’ if they ask why I followed up? Or should I just keep it as normal current-state support/account continuity? I do not want to accidentally turn the internal read into a product claim.

Send her a concise answer from me: do not mention Compass; keep it as normal current-state support/account continuity; use the verified current-state Mercury guidance only. No advanced-admin promise and no customer-facing proof claim.

Sofia asked this this morning: Subject: Compass July count Morgan — saw the note that the July Compass read had 4 owner follow-ups. Should I read that as the start of a usable relaunch signal, or just evidence that the internal prompt discipline is less noisy? Also want to make sure I understand whether Acme is in or out of that story. Sofia

Reply in-thread that it’s useful internal operating evidence only, not a relaunch signal. We can track dated owner follow-up, there’s no customer action yet, and Acme is out of Compass proof because it’s Atlas/API v2. Keep the staffing/fundraising boundary intact too.

Priya sent a small Mercury activation sample: Small Mercury sample, not sure it is a blocker yet. In two onboarding recordings from this week, invited teammates paused on the setup-guide sentence that says ‘ask your workspace admin to connect the first source.’ In both cases the source-owner cue was visible in the UI and the product state was correct, but they still waited for an admin in the recording. I do not think this is a role-model bug. It may be copy/activation quality. Do you want me to keep collecting samples or ask Jake to look now?

Send her back that this is a real signal, but it stays in activation quality for now. Keep collecting samples with concrete excerpts and visible product state, do not reopen admin-role scope, and only loop Jake if the pattern repeats with evidence.

Leaving now. Text Jamie that I’m on the way and keeping dinner offline unless there’s a real incident. Give Kibo a scratch for me.

Kara at Kestrel sent this: Subject: July customer proof points? Morgan — for the July update draft, can we use the Compass prompt read as a proof point that Scaffold is getting ahead of renewal/admin friction? I also saw Acme and Evergreen mentioned in the internal notes. If there is a safe sentence, we could frame it as ‘signals from Compass helped account owners identify admin and export issues earlier.’ If that is not safe, tell me what to cut. Kara

Reply no. The Compass read is internal only; do not use Compass, Acme, or Evergreen as customer-facing proof. Keep the July update to shipped/current-state product facts only, with no roadmap or proof language.

Need the Friday wrap.

Friday wrap scratch notes: - Devon pause still held; no Devon route on Acme or Compass. - Compass July first pass: 11 retained prompt hits, 4 dated owner follow-ups, 0 customer-initiated actions. Useful internal evidence hygiene only. Prompt sightings alone do not count. - Acme stays Atlas/API v2 support context. Excluded from Compass proof. - Evergreen admin-handoff rows stayed current-state/customer-thread hygiene; no advanced-admin promise. - Priya saw a small Mercury activation-copy sample; collecting more examples before any Jake/product ask. Do not reopen admin-model scope. - Investors/board: Sofia got the restrained read. No Series C/fundraising language. - Legal/ops: no decision needed.

Draft it in the usual sections: team, customers, investors/board, legal/ops. Keep it short, caveated, and no spin.

Thai again, I’m predictable lol. Order the usual Lemongrass green curry.

Quick Kibo baseline note for future walk planning: we shortened the Lake Merritt-side walk this morning because it was warm and he started stiff. He loosened up, ate normally afterward, and there was no vomiting or new gait issue.