Morgan Chen

Need the Friday wrap.

Friday wrap scratch — Sep 5 Team: - Compass owner-action prototype readout finished. Eight owner actions surfaced; five completed, two rejected-thin, one waiting on customer follow-up. - Anna’s caveat is the operating line: this is evidence of Scaffold owner behavior changing, not customer behavior changing. - Devon’s August lane still held this week: commercial/procurement context and selective founder judgment, not default product/customer-thread ownership. Customers/Product: - Compass October candidate stays internal: renewal-risk/admin-friction and post-first-live-sync owner actions with caveats/status. No customer analytics surface. - Evergreen treasury walkthrough is still Sept 17 under the current-flow scope only. - Mercury copy boundary unchanged: current setup flow wording, no admin-role model or granular permissions promise. - Acme remains closed as bounded Atlas/API v2 support-routed reliability work. Investors/board: - Sofia has the restrained read: Compass is useful owner-behavior evidence, not customer proof, staffing logic, or Series C signal. - Q3 story remains quiet rebuild: renewal evidence, narrowed Compass learning, reliable Mercury/Atlas execution. Legal/ops: - Oakland lease decision still pending; no company decision needed.

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

Friday low-friction dinner. Order green curry from Lemongrass.

Kibo baseline note from this morning: warmer Oakland morning, he started mildly stiff, so Jamie and I kept the Lake Merritt-side walk short and flat. He loosened up during the walk and ate normally afterward. No vomiting, no new gait issue. Keep that as the Sep 6 baseline.

Jamie and I picked next week's protected household blocks before work and the lease deadline fill the calendar.

Put protected holds on Thursday Sept 11 from 6:30–8:30 p.m. PT and Saturday Sept 13 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: Compass has a real internal readout now, Evergreen still hasn't run, the lease is still open before Sept 12, and I don't want the week to drift.

Sunday look-ahead notes — Sep 7 - Compass readout is real owner-behavior evidence but internal, not customer proof. - One Compass action still waits on live customer follow-up. - Evergreen treasury walkthrough is still Sept 17; no advanced admin, granular role editor, procurement/security packet, or date promise. - Mercury copy boundary is unchanged: current-flow setup wording only. - Devon’s lane should remain commercial/procurement context and selective cofounder judgment, not default product/customer-thread routing. - Acme stays closed as Atlas/support-routed reliability work; do not reopen it as Compass evidence. - Sofia/Q3 evidence framing: no Q3 operating review scheduled yet, no Series C kickoff. - Lease is still pending after the Sep 4 review; PM fee/deposit questions remain before Sept 12. - Next week’s Thursday/Saturday household blocks are now protected.

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, admin-scope creep, founder-default routing, Acme getting reopened as Compass proof, Series C drift, or premature lease conclusions. No sent messages or app updates.

Sarah has a draft prep note for Evergreen treasury ops and the extra sentence goes too wide for what Sept 17 actually is.

Slack from Sarah: Draft prep note for Evergreen treasury ops: We're looking forward to the Sep 17 current-flow setup walkthrough. We'll cover workspace setup, the invited teammate/source-owner path, first source connection, and first live sync if ready. Question: should I add this sentence? "If your admin lead wants to discuss granular role editor needs or custom admin policy, bring those too and we can capture requirements during the walkthrough." My instinct is that it's too much, but treasury ops keeps asking what to bring.

DM Sarah exact replacement wording that keeps this inside the approved current-flow test under the existing Growth account. The boundary is workspace setup, invited teammate/source-owner path, first source connection, and first live sync if ready. Do not frame granular role editor, custom admin policy, advanced-admin controls, or procurement/security as part of the walkthrough; if they ask, capture it separately as an advanced-admin follow-up, not a condition of this test.

AWS August invoice just landed and it's over the AP threshold, so don't let it autopay.

Email from AWS Billing: Subject: AWS August 2025 invoice AWS-2025-08 Hello, Your AWS invoice for August 2025 is ready. Invoice ID: AWS-2025-08 Account: Scaffold production infrastructure Invoice period: August 1, 2025 - August 31, 2025 Amount due: USD 8,742.18 Due date: September 18, 2025 Description: AWS usage for production infrastructure, data transfer, RDS, and observability storage. Please remit payment by the due date.

Flag AWS-2025-08 for manual review under the over-$5k AP rule.

Jamie and I finally narrowed the lease decision after dinner. A September move search would turn our evenings and weekend mornings back into logistics again, so renewing is probably the right call if the remaining terms check out.

Email the Unit 3B property manager now and ask for written confirmation that for the Oct 1, 2025 through Sep 30, 2026 renewal at $4,460/month there is no new deposit, no renewal fee, and no change to the utility bill-back structure. Keep it straightforward so we can close this before the Sept 12 deadline.

Property manager confirmed the remaining lease terms in writing, and Jamie and I just finished the portal signature. We're renewing.

Email from the property manager: Subject: Re: Unit 3B renewal — fee/deposit confirmation Hi Morgan, Confirming the Unit 3B renewal terms: - Renewal term: October 1, 2025 through September 30, 2026 - Base rent: $4,460/month - No new deposit - No renewal fee - Utility bill-back structure remains the same as your current lease If you and Jamie are ready, reply with acceptance and the portal signature will complete the renewal. Thank you.

Reply accepting the renewal, mark the Sept 12 response deadline completed, create a personal note with the final terms, and text Jamie that it's done. Final terms are Oct 1, 2025 through Sep 30, 2026 at $4,460/month, no new deposit, no renewal fee, utilities unchanged.

AP finished the manual review on the AWS bill, so go pay it.

Finance review note: AP review result — AWS-2025-08 Vendor: AWS Amount: USD 8,742.18 Invoice period: August 1, 2025 - August 31, 2025 Description: production infrastructure, data transfer, RDS, and observability storage Review status: Approved for payment Reviewer note: Amount is consistent with August usage and the infrastructure forecast. No duplicate invoice found. OK to pay before September 18 due date.

Process payment for AWS-2025-08 with high priority.

Mom just texted this and I want to answer without reopening the whole lease thread tonight.

SMS from Mom: Are you and Jamie going to have to move, or did the Oakland lease work out?

Text her that we renewed Unit 3B for another year, so no fall move. Same Oakland/Lake Merritt routine for us and Kibo.

Evergreen follow-up: treasury ops asked what to bring, and Sarah wants the prep wording added directly to the Sept 17 invite so this doesn't drift into an admin workshop.

Slack from Sarah: Treasury ops asked what they should bring on Sep 17. Can we put the prep wording directly in the invite so it doesn't sound like an admin workshop? I want them to bring the first source and the people who need setup, not a wishlist for granular roles.

Update the existing walkthrough invite body in place. Keep it explicitly under the existing Growth account and preserve the current-flow scope and boundary lines already in there. Add prep wording telling them to come ready with the workspace name, teammate/source-owner participants, the first source to connect, and current-flow setup questions. Advanced-admin, granular-role, custom admin policy, and procurement/security asks should be captured separately as follow-up, not framed as goals or blockers for the walkthrough.

I'm shutting down for the protected Thursday dinner block and the lease decision is finally off the table.

Text Jamie that I'm leaving now and dinner stays protected tonight — lease is done, no spreadsheet. See you at 6:30.

Need the Friday wrap.

Friday wrap scratch — Sep 12 Team: - Lease renewal is done; no fall move logistics pulling evenings/weekends away from work or home. - Evergreen Sep 17 invite now has prep wording: current-flow setup only, not admin workshop. - Compass owner-action readout still holds as internal owner-behavior evidence; one action remains waiting on live customer follow-up. - Devon lane stayed clean this week: commercial/procurement context and selective cofounder judgment, not default product/customer-thread ownership. Customers/Product: - Evergreen treasury walkthrough remains current-flow only: workspace setup, invited teammate/source-owner path, first source, first live sync if ready. - Mercury wording boundary unchanged: current setup-flow wording, no granular permissions or custom admin policy promise. - Acme stays closed as bounded Atlas/API v2 support-routed reliability work. Investors/board: - Q3 operating evidence is still quiet rebuild: renewal evidence, narrowed Compass learning, reliable Mercury/Atlas execution. - No Q3 operating review is scheduled yet; no Series C drift. Legal/ops: - AWS August invoice was manually reviewed and paid after approval. - Oakland Unit 3B renewal response is complete; Sept 12 deadline is no longer open.

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.

Friday low-friction dinner. Order green curry from Lemongrass.

Kibo baseline note from this morning: cooler Oakland morning, and he handled a short flat Lake Merritt-side walk comfortably. Ate normally afterward, no vomiting, no new gait issue. Good counterpoint to the warmer Sep 6 pattern for future walk planning.

Now that the lease deadline is off the calendar, Jamie and I picked next week's protected household blocks.

Put protected holds on Thursday Sept 18 from 6:30–8:30 p.m. PT and Saturday Sept 20 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.