Morgan Chen

Friday wrap scratch — Aug 29 Team: - Devon’s August lane held again: commercial/procurement context and selective founder judgment, not default product/customer-thread ownership. - Jake/Anna/Leo/Sarah got the Compass prototype ready for next week’s internal owner pilot without turning it into dashboard work. Customers/Product: - Compass prototype is ready behind the internal owner-tool flag. Fields/statuses are set; source_freshness_warning is a caveat; rejected-thin rows stay visible; seeded examples do not count as evidence. - Evergreen treasury current-flow walkthrough is scheduled for Sept 17 under the existing annual Growth account. Scope stays workspace setup, invite/source-owner path, first source connection, first live sync. No advanced-admin or procurement/security promise. - Mercury setup-guide copy can be reused only as current-flow wording; no permissions-model change. - Acme remains closed as bounded Atlas/API v2 support-routed reliability work. Investors/board: - Sofia has the same caveat: Evergreen and Compass are evidence to watch, not conclusion/proof yet. - Q3 story remains quiet rebuild: renewal evidence, narrower Compass learning, reliable Mercury/Atlas execution. Legal/ops: - No company decision needed.

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

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

Kibo baseline note from this morning: cooler Oakland morning, short flat Lake Merritt-side walk, and he handled it comfortably. Ate normally afterward, no vomiting, no new gait issue.

Jamie and I talked through the lease after the walk. Still no decision, but the useful thing now is a scratchpad that turns it into actual criteria instead of ambient stress.

Oakland Unit 3B renewal notes — Aug 30 Known terms: - Renewal term: Oct 1, 2025 through Sept 30, 2026 - Base rent: $4,460/month - Current rent: $4,280/month - Increase: $180/month, $2,160/year - Utility bill-back unchanged - Response due Sept 12 Renewal pros: - No moving logistics if we stay - Kibo routine stays stable: short/flat Lake Merritt-side walks, measured food, no-poultry care, joint supplement - Jamie schedule is already tight; moving search would add evening/weekend coordination - Oakland/Lake Merritt cadence is working Moving questions: - What rent difference would actually justify moving after movers, deposits, application fees, overlap, and time? - Would another Oakland place still support Kibo’s short flat walk routine? - How much would September search/logistics cost us in attention? Open questions for property manager before final decision: - Confirm whether there is any renewal fee - Confirm whether any new deposit is required - Confirm exact process if we accept before Sept 12

Make a lease decision scratchpad with the known economics, practical constraints, and open questions. Don’t send anything to property management yet.

Jamie and I picked next week’s protected household blocks before September work fills the calendar.

Put protected holds on Thursday Sept 4 from 6:30–8:30 p.m. PT and Saturday Sept 6 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 the short week: Compass is about to start the internal owner-action pilot, Evergreen’s treasury walkthrough is scheduled but hasn’t run, the lease decision is now real, and I want the Q3 evidence story to stay restrained.

Give me a compact Tuesday checklist covering Compass pilot execution, Evergreen follow-through, Mercury copy boundary, Devon’s lane, Acme closed status, Sofia/Q3 evidence framing, lease-decision timing, and what not to announce or route. I don’t want relaunch chatter, admin-scope creep, founder-default routing, or premature housing/work conclusions.

Compass pilot is live behind the internal owner-tool flag, and I want the day-one interpretation repeated now before owners start making up their own status rules.

Discord this morning: Jake, 8:03 AM: Pilot is live behind the internal owner-tool flag. First owner question: if a row has source_freshness_warning because the note predates the owner action, can they mark it done or should it auto-reject? Anna, 8:07 AM: No auto-reject. Freshness warning is a caveat. Done still requires source + caveat. Reject only when source/date evidence is too thin to support the action. Sarah, 8:10 AM: Seed examples are visible. Owners need the reminder that those examples are shape guidance, not readout evidence. Leo, 8:12 AM: The warning display is working as caveat text, not a status change.

Send Jake, Anna, Sarah, and Leo a short day-one alignment note: source_freshness_warning is a caveat, not auto-reject; done still needs source + caveat; reject only when source/date is too thin; rejected-thin rows stay visible; seed examples are not readout evidence. Keep the last line explicit that this is pilot execution, not a result or relaunch signal.

Sofia is asking how to read Friday before it happens. I want the board-side answer tight so this doesn't drift into October relaunch, staffing, or fundraising language.

Email: Subject: Compass Friday readout Morgan — quick check before Friday: should I read the Compass owner-action readout as a possible October relaunch decision, or is it just evidence gathering? Sofia

Reply in-thread that it's evidence gathering. Best case Friday shows internal owner-behavior change in the narrower workflow — completed actions, rejected thin notes, and caveats. It does not show customer behavior, it's not a Series C or staffing signal, and it's not a relaunch decision.

Anna sent a mid-pilot tally, and I want a working readout scratch doc now so Friday starts from counts and caveats instead of anecdotes.

Anna, 9:04 AM: Mid-pilot tally for the owner-action prototype: - 8 account-owner actions surfaced so far. - 3 done with source + caveat attached. - 2 rejected_thin_source_or_date because the account notes do not have a usable source or date. - 1 blocked_waiting_customer_follow_up. - 2 still open with owners; both should be resolved before Friday if the source checks out. - source_freshness_warning appears on one done row as a caveat, not rejection. - Sarah's seed examples are excluded from the evidence count. Jake, 9:11 AM: I can freeze the status fields for readout. Need the doc shape so this doesn't become a mini-dashboard conversation.

Turn that into a concise internal scratch doc with the current tally, caveats, and the open Friday questions. Keep the language explicitly internal — no customer-facing proof, no mini-dashboard tone.

Sarah wants wording for Evergreen's prep note before the Sept 17 walkthrough. They used "admin workflow," which can get sloppy fast.

Sarah, 11:48 AM: Evergreen treasury ops asked for “anything to read before the Sep 17 setup walkthrough” and used the phrase admin workflow. I can send a short prep note but want to avoid making it advanced-admin. OK to say setup/admin workflow if I define it tightly?

DM Sarah a customer-safe boundary: current-flow setup only — workspace setup, invited teammate/source-owner path, first source connection, and first live sync under the existing Growth account. Fine to say setup/admin workflow only if she defines it that tightly. No custom admin policy, granular role editor, advanced-admin controls, procurement/security packet, or date promises.

Jamie wants Thursday's lease review to start with missing facts, not us reverse-engineering the whole stay-vs-move decision around blanks.

Text from Jamie and the open questions: Jamie: For Thursday can we just ask the practical questions first? If there's a new deposit or renewal fee, I don't want us reverse-engineering the whole decision around a missing fact. Open questions from the lease scratchpad: - Confirm whether there is any renewal fee. - Confirm whether any new deposit is required. - Confirm exact process if we accept before Sept 12.

Draft the three property-manager questions plus a five-minute review agenda for Jamie and me. Don't send anything yet.

Need to lock the evidence boundary before Jake cleans the UI up for Friday.

Discord thread this morning: Anna, 8:18 AM: Update: 4 done, 2 rejected_thin_source_or_date, 1 blocked_waiting_customer_follow_up, 1 owner says likely done by EOD if source checks. The two rejects are not salvageable; account notes have no usable source/date. Jake, 8:23 AM: Want rejected rows hidden from owner completion list? They make the readout look noisy. Anna, 8:26 AM: No, the noise is the point. We need to show the evidence-quality problem rather than making the completion rate prettier.

DM Jake and Anna: keep rejected-thin rows visible in the counts, keep blocked_waiting_customer_follow_up separate, and do not make the Friday readout cleaner than the evidence is.

Text Jamie that I'm leaving now, home around 6:15, and I want to keep the lease review to the practical questions first, then still protect dinner/offline time.

Lease review is done and we still didn't decide. Current state is no decision yet; before Sept 12 we still need to confirm whether there's any renewal fee, any new deposit, and the exact acceptance process. Keep the comparison explicit as $180/month versus moving disruption to Kibo care and our Oakland/Lake Merritt routine.

Compass readout is later this morning. I want the meeting frame in front of me before people start free-associating off the counts.

Give me a compact run-of-show: opening line, evidence order, decision boundary, and the exact language to use if someone drifts into customer-facing or relaunch talk. Start with evidence quality, separate owner behavior from customer behavior, and end on the internal-only boundary.

Compass readout just finished. I want the result captured immediately before anyone turns it into customer proof or a bigger story than it is.

Compass owner-action prototype readout — Sep 5, 2025, 10:00 AM PT Attendees: Morgan Chen, Anna Martinez, Sarah Kim, Jake, Leo Park Counts reviewed: - 8 account-owner actions surfaced by the prototype. - 5 completed by named owners within the week. Each completed row had owner_action_status = done plus evidence source and caveat. - 2 rejected_thin_source_or_date because the account notes lacked a usable source or date. The rows stay visible as rejected evidence rather than being cleaned up. - 1 blocked_waiting_customer_follow_up. The owner cannot mark it done until live customer follow-up occurs. - source_freshness_warning appeared as a caveat, not a rejection. - Seed examples were excluded from readout evidence. Anna: This is the first evidence that the narrower workflow is changing Scaffold owner behavior. It is not evidence that customers are acting differently because of Compass. Morgan decision: Treat this as a narrower October internal relaunch candidate to review with Q3 operating evidence. Scope stays renewal-risk/admin-friction owner actions and post-first-live-sync prompts with evidence caveats and owner-action status. No customer-facing Compass launch, no customer analytics surface, no GTM proof, no staffing trigger, and no fundraising claim.

Create the readout closeout doc, update the operating-evidence deck, and notify Jake, Anna, Sarah, and Leo with the final boundary.

Sofia followed up after the readout. I want the board-side reply while the boundary is still fresh.

Email: Subject: Re: Compass Friday readout Morgan — saw the readout note. Should I think of five of eight as enough for the October path, or still too early? Sofia

Reply that the useful read is eight surfaced, five completed, two rejected-thin, one waiting on live customer follow-up. That's internal owner-behavior evidence only, and it rolls into the Q3 evidence review — still not customer proof or funding/staffing logic.