Morgan Chen

Draft a short reply to HR: no new req from Compass. It stays with the current owners. Nadia’s weekly customer-growth cadence and Sarah’s account-note hygiene are the operating model for now. We revisit only if v0.1 shows real behavior change or repeatable account follow-up, not because the workstream has a name.

Can you help me with Devon’s answer to Sarah? Keep it useful, not lawyerly. The posture should be: yes, the current SAML SSO path, certificate-rotation operational contacts, visible invite/source/admin audit lookup, and monthly active developer usage are available now. No, custom admin-role policy and a granular role editor should not be assumed in any baseline from this thread. If they want that later, it is separately scoped after the relevant work exists. Subject: Fwd: Evergreen follow-up on annual path / admin controls From: Devon Hayes To: Morgan Chen Cc: Sarah Kim Date: January 21, 2025 Morgan — Fresh procurement line from Evergreen below. Same issue as the worksheet last week: they are mixing current-state confirmations with annual-baseline language. Sarah still needs a clean reply posture that confirms what exists now without letting the admin-controls questions harden into assumed annual scope. Pasted excerpt: --- Evergreen procurement follow-up 1. Annual path / custom admin-role policy If the paid pilot moves toward an annual package, can Evergreen assume custom admin-role policy would be included? 2. Current baseline / granular role editor Is a granular role editor part of the current baseline? 3. Current SAML SSO path Please confirm that the current SAML SSO path is available now. 4. Certificate rotation process / operational contacts Please provide the operational contacts and process Evergreen should use for future certificate rotation. 5. Visible audit lookup Please confirm the visible audit lookup for teammate invitations, connected sources, and admin changes. 6. Monthly active developer usage visibility Please confirm whether monthly active developer usage is visible for review. --- Devon

Please create a doc titled “Compass v0.1 action-trigger checklist” from these notes. Make the body a compact owner checklist with signal, trigger, who sees it, evidence/caveat, source-quality requirement, and an explicit not-building line. Keep Anna, Nadia, Jake, Leo, and Sarah’s ownership clear, and keep the no-board-dashboard/no-new-hiring-lane boundary in it. Compass working session - rough notes Date: January 21, 2025 Participants: Morgan Chen, Anna Martinez, Nadia Singh, Jake, Leo Park, Sarah Kim Context for this session - Goal was to get Compass v0.1 out of abstract "useful signals" territory and into: what should actually happen when a signal appears. - Repeated boundary in the room: no board dashboard and no new hiring lane. - Jake repeated that January Mercury activation is still the center of gravity, so Compass cannot quietly turn into a dashboard/platform build while that work is active. Signals discussed 1. Renewal-risk / admin-friction - Morgan: this only matters if it causes a named person to do something for a real account. If it just labels an account as risky, it becomes internal theater. - Anna: definitions and caveats have to travel with the signal. "Renewal risk" by itself is too blunt and will be over-read. - Nadia: useful only if it points to a named account-owner follow-up and the specific admin friction causing the risk. - Sarah: account thread often mixes customer statement, support readout, and internal interpretation; if those are not separated, the signal will look more certain than it is. - Working shape: - signal should identify the specific admin friction, setup-control issue, or role confusion causing the apparent risk - should point to the account-owner follow-up, not just surface a category - should not collapse true product weakness, admin confusion, and procurement drag into one bucket - Open question: what is the minimum evidence package before Nadia will let this become an account-team script instead of an internal FYI? 2. Post-first-live-sync expansion prompt - Nadia: wants a customer-growth/account-team script, not another metrics view. - Jake: trigger cannot fire too early. It should happen only after first live sync is actually live and the teammate-invite/admin-role basics are visible. - Morgan: this should be about timely next action after first real traction, not generic upsell language. - Leo: before anything leaves the current team, he needs to check the data/platform seam and make sure the underlying event path is defendable. - Working shape: - trigger only after first live sync is live - teammate-invite/admin-role basics need to be visible enough that the follow-up is grounded in actual account state - evidence should distinguish observed usage from inferred readiness for broader usage - Open question: what is the smallest useful post-first-live-sync prompt that changes behavior without becoming a new product surface? 3. Account-note source quality - Sarah: source quality is uneven. Some thread notes are reliable and traceable; some are too thin to support follow-up. - Sarah can identify which thread notes are reliable and which are too thin. - Anna: caveats need to travel here too; weak notes should not be allowed to masquerade as a clean signal. - Nadia: does not want outreach based on mushy notes or internal inference dressed up as customer fact. - Working shape: - before a signal is used, Sarah should be able to say whether the underlying thread note is reliable, mixed, or too thin - provenance matters: customer statement vs observed usage vs support-derived fact vs internal interpretation - if note quality is weak, the caveat should be explicit or the signal should stay internal - Open question: what note fields or source tags are required before this can feed a real follow-up? Owner notes from discussion - Anna Martinez: keep definitions and caveats attached to each signal so they do not get over-read. - Nadia Singh: wants customer-growth/account-team scripts and follow-up logic, not a prettier metrics layer. - Jake: v0.1 cannot become a dashboard/platform build while January Mercury activation is still active. - Leo Park: needs a data/platform seam check before any signal is shown outside the current team. - Sarah Kim: can separate reliable account-thread notes from notes that are too thin; source hygiene is a gating input, not cleanup. Reminder boundaries captured again before wrap - no board dashboard - no new hiring lane - do not let Compass turn into a prettier internal dashboard - keep the first pass narrow enough to test whether signals actually produce action Loose follow-ups captured, not resolved - define what action each signal should trigger - define who sees each signal first and who should not see it yet - define the minimum evidence/caveat bundle - define the source-quality bar for using a signal outside the current team - define the explicit "not building" line for each v0.1 signal

Please post in Discord #mercury-eng: “Keep this one in the January Mercury cut: invited-teammate/source-owner role visibility blocks the workspace → first source → first live sync path, so Jake/Leo should fix it as activation work. Do not pull in custom admin policy or granular role governance from Evergreen as part of this. Sarah only needs customer wording if the shipped basic-admin surface changes.”

Please DM Sarah Kim on Discord with this: “For the Evergreen follow-up, answer the current-state items plainly: shipped SAML SSO, certificate-rotation operational contacts, visible invite/source/admin audit lookup, and monthly-active-developer usage. Don’t call custom admin-role policy or a granular role editor part of any baseline; if Evergreen wants those later, Devon should scope/price them after the work exists. Please loop Devon before the customer reply so we don’t create a roadmap carve-out in a sentence.” Use these notes as the context: Sarah Kim — Evergreen procurement follow-up notes Date: January 23, 2025 Live Evergreen procurement follow-up. They are still mixing current Mercury state questions with one annual-baseline line, but the tone was not especially aggressive. Main read: they seem comfortable with a current-state answer as long as the boundaries are plain. Questions they raised: 1. SAML login - Asked whether SAML login is available in the current Mercury pilot. - Also framed it against a possible annual path, basically asking whether the same SAML login path is something they can reference if the pilot converts. - This sounded like a current-state confirmation request more than a new feature ask. 2. Certificate rotation / operational contact language - Asked what operational contact path Evergreen should use for future SAML certificate rotation. - They want language they can drop into the procurement summary. - This was asked as an operations/process item, not a broader security-package question. 3. Visible audit lookup - Asked whether the visible invite/source/admin audit lookup can be referenced in the procurement summary. - Specifically tied to teammate invitations, connected sources, and admin changes. - They appeared to want confirmation of what is visible now rather than an expansion of scope. 4. Monthly active developer usage - Asked for language on monthly-active-developer usage. - Procurement wants something simple they can use internally on how usage is counted / referenced for review. 5. Annual baseline line - One line in their follow-up asks whether custom admin-role policy and a granular role editor would be included in an annual baseline. - This is the only part that clearly tries to pull non-current admin controls into baseline language. - It read like they are trying to see whether they can package that assumption into the paperwork now. Read on customer posture: - They did not push back on the idea of a bounded current-state answer. - My take is they will accept a clean answer that separates what exists now from what is not part of any assumed baseline. - The risk is only if we answer too loosely and let a sentence turn into an annual-scope implication. Internal boundary from Devon: - No annual-baseline implication before paperwork. - No customer-specific roadmap carve-out. - Keep the answer on current-state Mercury items where we have clear support today. - Anything that sounds like custom admin-role policy or granular role-editor scope should stay outside the baseline and not get implied in procurement wording. Bottom line from the call: - Evergreen wants usable procurement-summary language. - They seem okay with a plain current-state answer on SAML login, certificate-rotation contacts, visible invite/source/admin audit lookup, and monthly-active-developer usage. - The only place we need to be especially careful is the annual-baseline question on custom admin-role policy and a granular role editor.

Can you compare these two refill substitutes against Kibo’s care rules and tell me which, if either, is safe to order? I’m not guessing on poultry labels after the November treat mess. Pet-supply refill page - joint supplement substitutes for Kibo Captured: January 24, 2025 Current item - Vet-approved joint supplement tablet - Status: Out of stock until January 31 Your current supply - Enough on hand through the morning of January 28 Suggested substitute A - Listing name: Senior Joint Tabs - Flavor: beef-and-sweet-potato flavor - Active ingredients: - glucosamine - chondroitin - MSM - Inactive ingredients: - beef liver - sweet potato - rosemary extract - cellulose - Label review notes shown in screenshot: - no chicken - no turkey - no duck - no poultry meal - no chicken meal - no poultry fat - Estimated delivery: January 27 Suggested substitute B - Listing name: Dental Mobility Chews - Flavor: savory flavor - Active ingredients: - glucosamine - omega blend - Inactive ingredients include: - chicken meal - poultry fat - Estimated delivery: January 25 Refill page layout note - Substitute B is the faster delivery option. - Substitute A arrives later but before the current supply runs out if the estimate holds.

I ordered the non-poultry substitute from the refill page. Keep in your Kibo context that the dental chew was a no because of chicken meal and poultry fat. If shipping slips, Jamie and I should not improvise with poultry treats or chews.

Devon just got the Evergreen procurement packet. Help me write the internal note back to Devon and Sarah: hold standard Growth pricing as proposed — $7,500/month including up to 200 monthly active developers, plus $1,000 per additional 50 — but keep the support/procurement language current-state only: SAML login, cert-rotation operational contacts, visible invite/source/admin audit lookup, and MAD usage. Advanced admin controls and broader procurement/security packaging should stay separate unless the work exists later. Make it decisive, not triumphant; nothing is closed yet. Subject: Evergreen procurement packet for end-of-week routing From: Devon Hayes To: Morgan Chen Cc: Sarah Kim Date: January 27, 2025 Morgan — We have the next procurement packet from Evergreen. They want Scaffold to confirm the annual commercial structure before end-of-week paperwork can route. My commercial read is unchanged: - standard Growth at $7,500/month including up to 200 monthly active developers - $1,000 per additional 50 monthly active developers The packet is mostly workable if we keep the support/procurement language current-state and do not let the optional admin/security questions become assumed baseline scope. Sarah should own the customer-thread response once we have safe wording. Below is the packet summary with my notes. --- Evergreen procurement packet - January route 1. Annual commercial structure Evergreen request: Please confirm the annual commercial structure so paperwork can route by end of week. Devon note: We can hold standard Growth: $7,500/month including up to 200 monthly active developers, with $1,000 per additional 50 monthly active developers. 2. SAML login language Evergreen request: Please provide language confirming SAML login for the current Mercury state / annual packet summary. Devon note: Keep this current-state. Do not let it expand into a broader enterprise-readiness claim. 3. Certificate rotation operational contacts Evergreen request: Please provide the operational contacts / process Evergreen should use for certificate rotation. Devon note: Operational answer is fine. Keep it as contact/process language, not a larger procurement/security package answer. 4. Visible invite/source/admin audit lookup Evergreen request: Please provide language on the visible audit lookup for teammate invitations, connected sources, and admin changes. Devon note: Answer the visible current-state lookup plainly. 5. Monthly-active-developer usage language Evergreen request: Please confirm monthly-active-developer usage language for procurement review. Devon note: Fine to answer with the current MAD construct already used in the pilot. 6. Optional: advanced admin controls Evergreen request: Please indicate whether advanced admin controls are part of the annual package. Devon note: Keep separate. Do not imply inclusion. If relevant work exists later, it should be separately scoped/quoted. 7. Optional: broader procurement/security packaging Evergreen request: Please indicate whether broader procurement/security packaging is included. Devon note: Same line as above. Separate only if the work exists later. No customer-specific roadmap carve-out. --- Recommendation - confirm standard Growth commercial structure as above - keep support/procurement wording current-state only: SAML login, certificate-rotation operational contacts, visible invite/source/admin audit lookup, and MAD usage - keep advanced admin controls and broader procurement/security packaging separate - do not create a customer-specific roadmap carve-out in the answer Nothing is closed yet. This is just the posture I think we should hold before Sarah sends anything back. Devon

Kibo update: the non-poultry supplement substitute arrived this afternoon in Oakland, and the label matches the safe option. Jamie put it with his meds. Treat the refill scramble as closed; we’re staying no-poultry and not using the dental chews.

Can you give me two sentences from this: one cautious customer-safe sentence Sarah can use, and one internal sentence for Jake and Leo? Customer-safe should say basic teammate invites and admin-role visibility are in the January activation path once the current fix verifies; it is not custom admin policy. Internal should keep Jake and Leo on verification before Sarah says more. Subject: Mercury staging check - activation path / teammate-source-owner visibility From: Jake To: Morgan Chen Cc: Leo Park, Sarah Kim Date: January 28, 2025 Quick staging read from this morning. What is passing - Workspace creation through first-source connection is passing in staging. - First live sync succeeds when the source owner keeps admin visibility. What is still open - The invited-teammate/source-owner visibility bug has a candidate fix. - It still needs final verification before we treat it as settled. Scope boundary - No custom admin-role policy was built. - No granular role editor was built. - This is still the basic activation/admin-visibility path, not broader role-governance work. Leo is checking the platform seam on the candidate fix before we make a broader statement. Jake --- Reply from Sarah Kim Date: January 28, 2025 Thanks. If Evergreen asks about basic admin readiness before verification clears, what can I safely say? I want to stay accurate on the teammate-invite/admin-role basics without implying custom admin policy or a broader admin-controls story. Sarah

Jake and Leo cleared the Mercury admin visibility staging check. Need Sarah unstuck before she keeps waiting on the stale answer. Their staging verification note: The candidate fix for invited-teammate/source-owner role visibility completed final staging verification. Workspace creation through first-source connection and first live sync now works when the source owner is an invited teammate and retains the needed source/admin visibility. Leo’s platform-seam check did not surface a blocker. Jake still treats the change as January activation work. No custom admin-role policy was built. No granular role editor was built. Sarah can describe the verified current path as basic teammate invites and admin-role visibility in the January activation path, but should not describe it as custom admin policy, broader role governance, or a broader admin-controls story. Please DM Sarah Kim on Discord with this exact message: Verified: the invited-teammate/source-owner fix cleared staging for the January activation path. If Evergreen asks, keep the wording bounded to basic teammate invites and admin-role visibility; no custom admin policy, no granular role editor, and no broader admin-controls claim.

Sarah and Devon have a workable Evergreen reply, but one line is still too loose on future admin-control packaging. Can you rewrite it into something Sarah and Devon can actually use with the customer: keep standard Growth pricing, answer only current-state SAML, cert-rotation, audit lookup, and MAD usage, and remove anything that implies advanced admin controls or broader procurement/security packaging are in the annual baseline. Sarah’s draft with Devon’s commercial comments: The draft confirms Scaffold’s standard Mercury Growth annual structure at $7,500 per month including up to 200 monthly active developers, with $1,000 per additional 50 monthly active developers. It confirms current-state SAML login for Evergreen. It gives certificate-rotation operational-contact language as an operations path, not a broader security package. It confirms visible invite/source/admin audit lookup for teammate invitations, connected sources, and admin changes. It gives monthly-active-developer usage language for procurement review. It says advanced admin controls are not included in the annual baseline and would need separate scope after the work exists. It says broader procurement/security add-ons are not included in the annual baseline and would need separate scope after the work exists. Sarah remains the customer-thread owner. Devon owns commercial/procurement framing. Product requests continue through the standard Mercury roadmap. The risky draft sentence says future admin-control packaging can be discussed as part of annual planning, which Morgan thinks is too loose because it could imply the annual agreement includes future advanced-admin scope.

Jamie and I picked Saturday morning as the offline block this week: flat Kibo morning around Oakland/Lake Merritt. Evergreen follow-up and Compass cleanup do not get to sprawl over the whole weekend unless there’s a real incident.

Evergreen closed. Please update the existing Evergreen Bank CRM row now so it is not stuck in paid-pilot status. Close email / Devon commercial summary: Evergreen Bank converts from the paid Mercury Growth pilot to an annual Mercury Growth agreement. The annual term is February 1, 2025 through January 31, 2026. The commercial structure is Scaffold’s standard Growth terms. The price is $7,500 per month including up to 200 monthly active developers. Overage is $1,000 per additional 50 monthly active developers. The January closeout validated that SAML login works for the annual account. The January closeout validated that visible invite/source/admin audit lookup is sufficient for the annual deal. Advanced admin controls are not included in the annual baseline. Broader procurement/security add-ons are separately quoted only after the relevant work exists. Sarah Kim remains Evergreen customer-thread owner. Devon Hayes owns commercial/procurement framing. Nadia Singh captures repeatable customer-growth patterns. Product requests continue through the standard Mercury roadmap. Set status exactly to: annual_growth_customer Set tags exactly to: mercury, growth, annual-customer, evergreen Set trigger condition exactly to: Annual Growth agreement runs February 1, 2025 through January 31, 2026; advanced admin controls and broader procurement/security add-ons require separate quoting after relevant work exists. Set notes exactly to: Converted to annual Mercury Growth customer effective 2025-02-01 through 2026-01-31 on standard Growth terms: $7,500/month including up to 200 monthly active developers, plus $1,000 per additional 50 monthly active developers. January closeout validated SAML login and visible invite/source/admin audit lookup. Sarah Kim remains customer-thread owner; Devon Hayes owns commercial/procurement framing; Nadia Singh captures repeatable customer-growth patterns; product requests continue through the standard Mercury roadmap.

Friday, staying in. Please place the usual Friday Lemongrass order: green curry.

Kibo update from the flat Oakland/Lake Merritt walk: he started a little stiff, then settled into the shorter route. Non-poultry supplement routine was normal, and no appetite, vomiting, or gait issue came up.

AP sent the January Kestrel invoice. It matches the maintenance-copy line, but it’s over the manual-review threshold, so flag it before anything pays. AP email: Invoice ID: KEST-2025-01-MAINT. Vendor: Kestrel Marketing. Amount: $6,000.00. Service period: January 1, 2025 through January 31, 2025. Scope on invoice: Mercury page maintenance copy, lifecycle-copy maintenance, and routine copy QA. AP note: no additional January Kestrel charges are in queue. AP note: the invoice is over $5,000 and requires manual review before payment. Use this reason exactly: January maintenance-copy invoice exceeds Scaffold’s over-$5,000 manual-review threshold before payment.

Kestrel manual review looks fine: January maintenance-copy scope, no extra roadmap/customer-proof copy pass, no additional January charges. Give me one AP line I can paste back saying it passed manual review and can release on the normal payment run.

Compass owner fill-in is more concrete, but dashboard drift is trying to sneak back in. Give me a concise gap/risk read: what’s ready enough for owner follow-up, what still looks like dashboard drift, and what has to be settled before any limited discovery pass. Owner fill-in notes: Anna Martinez proposes that renewal-risk/admin-friction signals carry definitions, caveats, and confidence, and must not collapse true product weakness, admin confusion, and procurement drag into one bucket. Nadia Singh proposes that renewal/admin-friction follow-up should point to a named account-owner action and that the post-first-live-sync expansion prompt should produce a customer-growth or account-team script, not a generic upsell view. Jake says Compass v0.1 must remain narrow while January Mercury activation is active and must not become a dashboard or platform build. Leo Park says the data/platform seam can be checked for the renewal/admin-friction evidence path and the first-live-sync trigger, but anything shown outside the current team needs defendable event provenance first. Sarah Kim says account-thread notes need source tags that separate customer statement, observed usage, support-derived fact, and internal interpretation, and she can mark notes as reliable, mixed, or too thin. Open gaps are the minimum evidence bundle Nadia will accept before a script is used, who sees each signal first, which signals stay internal, and the exact not-building line for each v0.1 prompt.

HR is poking again because Evergreen converted and Compass has a name now. Draft a short internal reply for Nadia, Devon, and HR: Evergreen is a real annual conversion, not repeatability proof; Compass is still discovery; no Q1 customer-growth or Mercury hiring lane opens off this alone. Nadia’s weekly read plus HR follow-up: Nadia says Evergreen converting from the paid Mercury Growth pilot to annual Growth is the strongest current customer-growth signal. She notes that Sarah Kim’s Evergreen account notes are unusually clean and traceable compared with other account threads. She wants Compass to test whether renewal/admin-friction evidence and post-first-live-sync expansion prompts generalize beyond Evergreen. She says current account-source quality outside Sarah’s Evergreen thread is thinner and should not be treated as proof yet. HR asks whether Evergreen’s annual conversion plus Compass being named as a workstream means Scaffold should reopen customer-growth, RevOps, CS, SDR, field-sales, or the second Mercury engineering requisition. Devon’s comment is that the current model should hold unless the team sees repeatable behavior-change evidence, not just one clean annual conversion.

Friday. Please place a Lemongrass order for one green curry.

New Atlas support intake, and I want the routing clean before this turns into founder-direct triage or a random pull-Jake/Rishi loop. Give me a short internal routing note: support owner keeps customer comms, Leo does the first technical read, Jake only if sequencing changes. Support rotation intake note: The customer support thread reports that archived records did not appear as expected during an API v2 webhook replay. The support rotation has a named customer owner for the thread, and that support owner remains responsible for customer communication. The initial note does not yet identify root cause. The current request is for Leo Park to do the first technical read on archive cursor, replay/backfill, and auth/platform-boundary behavior. Jake should be pulled in only if the technical read changes Atlas product priority or sequencing. The support rotation doc remains the routing source of truth. Rishi is no longer the default Atlas customer-thread owner.

Leo has a likely cause and reset is in motion, but no one gets to call this closed until the customer confirms replay works. Prepare a short customer-safe status line plus internal close criteria. Leo’s technical update with Jake’s sequencing comment: Leo traced the archived-records/API v2 webhook replay issue to an expired archive cursor plus a receiver-side retry assumption. The customer expected the replay to recover automatically on the receiver side, but the current read is that the archive cursor needed a reset. The cursor reset has been initiated for the affected replay path. Support remains the customer-thread owner. Jake reviewed the technical read and says this does not change Atlas product priority or sequencing. There is no new Atlas owner or priority rule from this issue. Customer confirmation that the replay works after the cursor reset has not arrived yet.

Atlas archived-records/API v2 replay thread is closed. Support kept the customer owner, Leo traced it to the expired archive cursor plus the receiver-side retry assumption, Jake said no sequencing change, and the customer confirmed replay works after the reset. Normal post-Rishi split held. No new Atlas owner or priority rule.

HR is asking for the Q1 all-hands hold before calendars fill up. HR scheduling note: Requested date: March 6, 2025. Requested time: 10:00 AM to 11:00 AM Pacific. Meeting should be the Q1 quarterly all-hands. Format should be the current structured default: short company update plus pre-collected questions. No open-mic Q&A block unless Morgan separately chooses it. HR will collect questions in advance and route out-of-scope questions asynchronously or to named owners. Create this calendar event: Title: Q1 company update + collected Q&A Time: March 6, 2025, 10:00 AM–11:00 AM Pacific Attendees: Scaffold team Body: Structured quarterly all-hands: short company update, pre-collected questions, live answers only on approved current topics, async or named-owner routing for the rest. No open-mic Q&A block.

Friday. Please place a Lemongrass order for: green curry.

Kibo update from the shorter Oakland/Lake Merritt-style walk with Jamie: slightly stiff at the start, then he settled into the flat route. Ate normally afterward. No vomiting, appetite change, or gait weirdness.

Compass v0.1 is close enough for limited preview planning, but I want the Evergreen and Acme paths separated cleanly before anyone starts treating the same material as reusable. Internal Compass limited-preview prep notes: Compass v0.1 signal views are ready for limited preview planning. Evergreen Bank can review current-state Compass signals tied to its annual Mercury account, procurement/admin follow-up, renewal-risk/admin-friction evidence, and post-first-live-sync expansion prompts. Acme should participate only through a live review of its own account-health, reliability, and renewal-risk signals with Greg Shipman, Sarah Kim, Nadia Singh, and Jake. No Evergreen-derived examples, written Mercury packet, screenshots, customer-specific briefing materials, or design-partner materials should be sent to Acme. The preview goal is to observe whether the signal tells a customer or account owner what action to take. Anna owns definitions, caveats, and confidence. Nadia owns scripts and customer-growth use cases. Sarah owns account-thread source quality and customer-thread hygiene. Jake owns keeping v0.1 narrow. Leo owns data/platform seam and event-provenance checks before anything is shown beyond the current team. The boundary remains no board dashboard and no new hiring lane. Give me a concise internal guardrail note and checklist: separate Evergreen written/current-state review from Acme live-only review, name the no-materials boundary for Acme, and keep the center question on what action each signal should trigger.

Evergreen could read the Compass surface, but the useful part is the action ambiguity, not “customer understood chart.” Turn this into follow-up questions, not proof. Evergreen Compass preview notes from Sarah and Nadia: Evergreen reviewed current-state Compass signal views tied to the annual Mercury Growth account, visible admin/procurement follow-up, renewal-risk/admin-friction evidence, and a post-first-live-sync expansion prompt. The Evergreen side understood the labels and could follow the signal surface. They asked whether a renewal-risk/admin-friction signal should trigger Sarah Kim to schedule an admin follow-up, Devon Hayes to update procurement/commercial framing, Nadia Singh to prepare an account-team script, or some other account-owner action. They wanted the evidence and caveat visible with the signal. No custom admin-policy request, granular role-editor request, or advanced-admin commitment was made in this preview note. Sarah noted that the Evergreen account-thread notes are unusually clean and traceable. Nadia noted that this is still one account and should not be treated as repeatability proof. Summarize this into a short internal set of action-trigger questions for Nadia, Anna, Sarah, and Jake. Explicitly avoid product-proof or repeatable-GTM-proof language.

Need the Acme opener to sound normal, not like we’re reading a legal disclaimer. Keep Greg and our side inside the materials boundary. Acme live-only Compass prep note: The Acme preview will be a live review only. Greg Shipman, Sarah Kim, Nadia Singh, and Jake will review Acme’s own account-health, reliability, and renewal-risk signals. Scaffold should not send Acme Evergreen-derived examples, a written Mercury packet, screenshots, customer-specific briefing materials, design-partner materials, or a post-call packet from Compass. Sarah will keep customer-thread continuity. Nadia will listen for whether the signal changes account-team follow-up. Jake will answer current product facts only if needed. The session should be framed as discovery on Acme’s own signals, not a Mercury materials review or a roadmap conversation. Draft a short live-call opener and an internal reminder for Sarah, Nadia, and Jake: live-only, limited to Acme’s own signals, and not a written-materials or roadmap-sharing session.

This week’s offline household time is the quiet weeknight dinner with Jamie plus a weekend morning Kibo walk on the flatter Oakland/Lake Merritt route. Same rule as before, just applying it for the week.

Compass v0.1 is now in limited preview/discovery. Evergreen is reviewing current-state Compass signals tied to its annual Mercury account and procurement/admin follow-up. Acme is live-only with Greg, Sarah, Nadia, and Jake, limited to Acme’s own account-health, reliability, and renewal-risk signals. No Evergreen-derived examples, written Mercury packet, screenshots, or customer-specific briefing materials went to Acme through Compass. First read: customers can read the surface, but they keep asking what action the signal is supposed to trigger. That’s the thing to track, not dashboard polish.

Compass week done enough. Please place a Lemongrass order for: green curry.

HR is ready to collect Q1 all-hands questions. I want the prompt to reinforce structured Q&A, not accidentally invite open mic. HR follow-up note: The Q1 company update plus collected Q&A calendar hold is on calendars for March 6, 2025 from 10:00 AM to 11:00 AM Pacific. HR wants to start collecting questions this week. The collection note should tell the Scaffold team that the meeting will use the structured quarterly all-hands format: 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 Q&A block. HR will collect and organize the questions before the meeting. Draft a short internal question-collection prompt for HR that matches that format and does not imply there will be an open-mic Q&A block.

For the first Compass read, I want behavior change separated from legibility. Do not let this turn into “nice dashboard, customers understood it.” Post-preview working notes from the Compass owner group: Evergreen could read the current-state signals and asked who should act on renewal-risk/admin-friction signals and what evidence should travel with the signal. Acme stayed inside the live-only review boundary and discussed only its own account-health, reliability, and renewal-risk signals with Greg Shipman, Sarah Kim, Nadia Singh, and Jake; no written Mercury packet, screenshots, Evergreen examples, or customer-specific Compass materials were sent to Acme. Greg asked what the account team would do next when a signal was red. Anna wants definitions, caveats, and confidence kept attached. Nadia wants to distinguish signal legibility from whether an account-team script or customer-growth follow-up changes. Sarah wants account-thread notes separated by source quality. Jake wants v0.1 kept narrow and not turned into a dashboard or platform build. Leo wants event provenance checked before any broader use. Create a concise internal readout scaffold for the first Compass preview read: separate legibility from behavior change, list the concrete next-action evidence to look for, preserve the Acme live-only boundary, and avoid board-proof or GTM-proof language.

Compass guardrail for the week: the preview is discovery, not proof. The owner group is still separating signal legibility from whether Evergreen or Acme actually changed a customer/account-team action. I don’t have the final read yet, and for board, operating-read, or staffing context the safe framing is still: legible surface, unproven behavior change.

Update slide 4 in Q1 2025 Board Operating Read to: Customer growth / Mercury proof points: Evergreen converted from paid pilot to annual Mercury Growth customer effective 2025-02-01 through 2026-01-31 on standard Growth terms; Compass v0.1 is in limited preview/discovery and is not yet behavior-change or GTM proof; current customer-growth staffing remains lightweight while the March operating read tests for Compass behavior change, account-source quality beyond Evergreen, and owner-routed enterprise-readiness intake.

Tonight is the protected offline dinner with Jamie. Kibo is fine; still keeping walks flatter when he’s stiff. Ordinary Scaffold catch-ups don’t get to eat the evening just because the calendar has space.

Friday brain is done. Please place a Lemongrass order for my usual green curry.

HR sent the first organized Q1 all-hands batch. I want this sorted for the structured format, not turned into open mic. HR’s batch contains these submitted questions: 1. “Evergreen converted to an annual Growth agreement — does that mean the enterprise motion is working enough to hire CS, RevOps, SDR, or field sales?” 2. “Is Project Compass becoming a customer-facing product this quarter, or is it still discovery?” 3. “What Mercury proof points matter most for Q1: first live sync, admin roles, SSO/admin-audit adoption, or expansion after live sync?” 4. “How should people talk about Acme in Compass previews if Acme can only do live review of its own signals?” 5. “Are we opening the second Mercury engineering req now that Evergreen is annual?” 6. “Does the Evergreen deal change the roadmap for advanced admin controls or procurement/security packaging?” 7. “After Rishi left, is Atlas support still routed through support/Leo/Jake or should people escalate directly to founders?” 8. “What should teams do with enterprise-readiness requests that do not clearly belong to Mercury release work?” HR’s note says the all-hands is still the March 6, 2025 structured quarterly format: 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 Q&A block. Sort the question batch into live-answer topics, async or named-owner topics, and items to defer; keep the wording consistent with the structured all-hands format and avoid implying open mic.