Morgan Chen

Maya texted that Mom was worried because I’d been sending only terse replies all week. I sent Mom a short “work was busy but okay” update with a Kibo apartment photo, then kept the rest of the afternoon quiet with Jamie instead of turning it into a whole work explanation.

Zoom true-up is still on hold. The admin export came back and the $5,120 invoice includes a few inactive host seats from old webinar rooms, so finance is asking Zoom for a corrected true-up instead of paying the full version.

Atlas rename ticket is contained. The customer saw the old workspace label in their integration view and thought webhooks were still tied to it, but Leo’s read was that delivery and signature verification are using the right workspace id. Jake didn’t change Atlas sequencing, and support sent the id-based explanation back.

Sarah forwarded Evergreen’s sandbox reviewer notes. Good news: the bounded SAML path is still clean and the admin vs billing-owner surface is landing clearly. The only product note is an audit-history table that looks out of order because the export is sorted in UTC while the UI shows local time. Procurement repeated the packet-timing question, but Devon put that in commercial/procurement context, not the beta validation result.

Acme reliability watch has two more normal rows. Greg sent Sarah the update: the API v2 export completed once Acme narrowed the big date range, and the statement preview that blanked earlier this month loaded on the new check. Jake added the timestamps to the watch notes, and Sarah kept the reply on the reliability thread without reopening the materials-boundary issue.

Nadia’s enterprise prep is getting useful — the Evergreen-style account reads are much sharper — but we had to reset the boundary today. Her draft mixed account patterns, source notes, customer follow-ups, and “roadmap implications,” and a few priority-account asks were written too much like commitments: SSO timing, audit-history completeness, procurement packet timing, admin-role exceptions. Devon and I pulled it back with Jake in the room. Nadia should own pattern capture, account prep, and a clearer conversation map. She does not own bespoke roadmap commitments. If an ask starts to look like custom scope, a feature-date promise, or a priority-account exception, it has to go through me or Devon and the relevant product owner before anyone uses it in customer follow-up.

Pinecone had a narrow connector-docs question from a partner proxy lowercasing `X-Scaffold-Signature`. Leo confirmed the verifier accepts the preserved header and fully lowercased `x-scaffold-signature` against the same raw body and workspace, but not underscore-style names or moving the signature somewhere else. The note stays limited to the header-only connector path; no Atlas contract change.

Mercury beta rerun was clean enough to give Evergreen a real validation update. Jake and Leo reran against last week’s sandbox notes: bounded SAML still passes, the admin vs billing-owner screenshots are still readable, and the audit-history table now follows the UI’s local-time order instead of the UTC export making it look scrambled. Sarah has the reviewer update, and Devon kept the procurement-packet question out of this readout.

Zoom came back with the corrected annual true-up. They removed the stale inactive hosts from the old webinar rooms, revised total is $4,360, and finance matched it to the current host list, so it’s no longer on manual-review hold.

Acme watch update: Greg sent Sarah the next rows. One API v2 export on a large date range hit a 27s timeout, then completed after they narrowed the range. The billing-dashboard statement preview loaded normally on the fresh check. Jake added trace IDs and timestamps to the notes, so Sarah has enough to answer in the existing reliability thread.

Nadia’s revised enterprise-conversation map is much cleaner after last week’s reset. She split source notes, repeatable Mercury patterns, owner routes, and customer-safe follow-up language. Two of the account snippets are actually usable now, and the priority-account ask is in the Morgan/Devon/product-owner routing column instead of being implied as a promise. Sarah can use the account-prep structure without changing who owns the customer threads.

Can you draft a short internal pricing reference for Nadia and Sarah for upcoming account prep? Use the existing Mercury budgetary guidance: Pilot is $2,500/month up to 50 monthly active developers, Growth is $7,500/month up to 200 monthly active developers, additional usage is $1,000 per extra 50 monthly active developers, and enterprise add-ons are quoted separately only after those features ship. Keep it clearly as reuse of current guidance, not a new price sheet or a one-off account exception.

Atlas ticket was less bad than it looked. Customer thought a connector import dropped archived records; Leo did the first read and API v2 was returning them correctly once the archive filter was removed. Their worker had copied a stale filter from a test import. Jake isn’t changing Atlas sequencing, and support already sent the corrected filter explanation.

Please send Sarah a concise clarification for the Evergreen pricing-counting reply: the bands are based on monthly active developer usage, not purchased seats or directory size. Scaffold/internal test users don’t count. Preview-only or sample usage should stay separate from activation reporting. Also keep the Evergreen-facing wording budgetary, not custom.

The Oakland portal posted the routine lease-renewal estimate — modest increase, response window is mid-September. Jamie flagged it for an actual decision after the long weekend, but we’re not deciding today. Please create a calendar reminder for Sep 3, 2024, 9:00–9:15am titled “Review Oakland lease renewal with Jamie.”

Can you draft a short note to the apartment office asking them to explain the utilities fee on the Oakland renewal estimate and confirm the exact response deadline? The rent increase itself looks manageable, but Jamie and I don’t want to decide until those two pieces are clear.

Kibo’s fall dental follow-up is booked for October 16 in Oakland. Jamie and I picked a late-morning slot so that day doesn’t start in chaos, and I added the no-poultry / boring-food notes to the prep so nobody gets creative with treats before or after.

Jake’s first post-holiday Mercury enterprise-readiness table is in. For the bounded v0.3 slice: SAML login passed in the staged test org, Priya’s role-separation language matches the current design frame, and the audit-event ordering issue from the UTC/local-time confusion is fixed. One seeded enterprise account still has a stale session after invite resend, so Jake is keeping the candidate in staging while Leo pulls traces for that row.

Atlas support had a customer-facing API v2 webhook signature ticket hit my queue for one workspace. Leo took the first read and found they were parsing and reserializing the JSON before verification instead of checking the signature against the raw request body. Support replied with that correction on the existing ticket, and Jake isn’t changing Atlas sequencing off this.

Jake and Leo finished the Mercury enterprise-readiness dry run and sent the short table: path, evidence, remaining risk, owner, release-language boundary. SAML login, the admin vs billing-owner surface, and audit-event emission are close enough for Monday review, but Leo still wants one clean actor-name trace attached to the audit-history row. Marcus did not run a Friday prod deploy; the candidate stays staged for the weekend.

Jamie’s hospital shift ran late, and the Trader Joe’s pickup window would have landed right in the middle of Saturday morning. I moved it out of the morning and kept Kibo’s walk plan boring so we don’t start tomorrow with another logistics pileup.

We actually kept the morning protected: coffee in Oakland, a short Lake Merritt loop with Kibo, and no work errand grafted onto it. After Jamie’s hospital week and my Scaffold week, ordinary and quiet was the whole point.

Apartment portal finally answered the renewal clarification. The utilities line is just their quarterly pass-through estimate for water, trash, and common-area service, and the response deadline is Monday Sept 16 at 5pm. Helpful, but Jamie and I still haven’t decided.

August AWS came in at $8,190 and is sitting in manual AP review. Marcus’s read is pretty boring: mostly normal prod compute, the old non-prod us-west-2 lines stayed flat, and he doesn’t see a runaway test runner or a new cleanup item in the detail.

Send Sarah a short pre-ship answer on Evergreen: if the Mercury slice ships this week, they can say the scoped SAML SSO and admin/audit capabilities shipped for scoped enterprise accounts. They should not treat that as the standalone procurement packet shipping too.

The Atlas “duplicate” API v2 webhook ticket was setup noise, not a replay bug. Leo found the same receiver endpoint registered in two workspaces during the customer’s sandbox test, so both deliveries were valid subscriptions. Support sent that explanation back, and Jake isn’t changing Atlas sequencing over it.

BART ate the SF morning. I took the first call from Oakland and pushed office arrival later, so today is split remote/in-office instead of the clean in-person block I’d planned.

Mercury enterprise slice made the 3pm cutoff. Leo cleared the evidence review before any release language went out, and Jake/Marcus kept the deploy on the normal release path. The #eng-releases note is intentionally narrow: SAML SSO for scoped enterprise accounts, admin-side audit-history events for invite/source/admin changes, and clearer admin vs billing-owner separation. Sarah has Evergreen-safe wording on those shipped pieces. Devon is keeping the procurement/security packet separate because advanced admin controls and the standalone packet are still not done. Post-release framing: Devon owns commercial/procurement language, Sarah coordinates the customer thread, and we still should not make custom Evergreen promises or say Mercury is fully enterprise-ready.

Draft a short note to the apartment office asking them to send a corrected e-sign page before tomorrow’s response deadline. Jamie’s name is misspelled on one signature page, even though the portal shows it correctly elsewhere, so we didn’t sign tonight.

Can you sanity-check the corrected e-sign page against the rest of the renewal packet? Mostly Jamie’s name and any obvious signing blocker. The portal still has a 5 pm cutoff, so I want to catch anything weird before we sign. Resident Portal Lease Renewal Packet Status: Awaiting resident signatures Packet last updated: Monday, September 16, 2024, 11:41 AM PT Apartment: Unit 3B, Oakland, CA Residents: Morgan Chen; Jamie IMPORTANT RESPONSE CUTOFF Response required by: Monday, September 16, 2024, 5:00 PM PT If all required resident signatures are not completed by the response cutoff, this renewal offer may expire and alternate occupancy terms may apply under the existing lease and applicable law. Update posted Monday, September 16, 2024, 11:41 AM PT A corrected signature page has been added to this packet. Please review the updated page before signing. Packet contents 1. Renewal Offer Summary 2. Residential Lease Renewal Addendum 3. Community Policies Acknowledgment 4. Resident Signature Page (corrected) -------------------------------------------------- 1. RENEWAL OFFER SUMMARY -------------------------------------------------- Current lease end date: September 30, 2024 Offered renewal term: 12 months Renewal term dates: October 1, 2024 through September 30, 2025 Resident names on lease: Morgan Chen; Jamie Premises: Unit 3B, Oakland, CA Monthly charges for renewal term - Base rent: $4,280.00 - Reserved parking: Not included - Storage: Not included - Pet rent: $0.00 - Estimated utility bill-backs, if applicable: Billed separately under existing utility arrangements Move-in / deposit status - Security deposit currently on file: Carried forward under existing lease - Additional deposit due for renewal: $0.00 - One-time renewal fee: $0.00 - Amount due at signing: $0.00 Summary of offered changes - Lease term is extended for the period October 1, 2024 through September 30, 2025. - Monthly base rent changes to $4,280.00 beginning October 1, 2024. - All other terms of the original lease remain in effect except as specifically modified by this renewal packet. Resident action required - Review all packet documents. - Confirm resident names and premises information. - Complete all required signatures before Monday, September 16, 2024, 5:00 PM PT. -------------------------------------------------- 2. RESIDENTIAL LEASE RENEWAL ADDENDUM -------------------------------------------------- This Residential Lease Renewal Addendum ("Addendum") is entered into by and between the property owner/agent ("Owner") and the undersigned residents ("Residents") for the premises identified below. Premises Apartment: Unit 3B City: Oakland State: California Residents Resident 1: Morgan Chen Resident 2: Jamie Reference lease This Addendum renews and amends the existing residential lease for the above premises currently in effect through September 30, 2024. 1. Renewal term The lease term is renewed for a fixed term beginning October 1, 2024 and ending September 30, 2025. 2. Rent Beginning October 1, 2024, Residents agree to pay monthly base rent in the amount of $4,280.00. Rent is due in advance on the first day of each month at the place and in the manner stated in the original lease, unless Owner provides updated payment instructions in writing. 3. Other recurring charges Any utility reimbursement, late charges, returned payment charges, or other lawful recurring charges permitted under the original lease remain governed by the original lease unless expressly changed in this Addendum. No additional recurring charges are added by this Addendum beyond the rent stated above. 4. Security deposit Any security deposit currently held by Owner for the premises will remain on deposit and continue to secure performance under the renewed lease, subject to the terms of the original lease and applicable law. No additional deposit is required under this Addendum. 5. Occupancy Authorized residents under the renewed lease are limited to: - Morgan Chen - Jamie No additional occupants are authorized by this Addendum. 6. No other modifications Except as expressly set forth in this Addendum, all terms, conditions, rules, disclosures, addenda, and obligations contained in the original lease remain in full force and effect for the renewal term. 7. Insurance and legal compliance Residents remain responsible for maintaining any renter obligations required by the original lease, including compliance with applicable insurance, conduct, maintenance, notice, and legal requirements. 8. Entire renewal agreement This Addendum, together with the original lease and incorporated policies, constitutes the full renewal agreement for the renewal term described above. 9. Electronic signature consent Residents acknowledge that this renewal packet may be executed electronically and that electronic signatures shall have the same force and effect as original signatures to the extent permitted by law. Owner/Agent acknowledgment This offer is not fully executed until all required resident signatures are completed and Owner countersignature or confirmation is recorded, if required under the original lease or Owner workflow. -------------------------------------------------- 3. COMMUNITY POLICIES ACKNOWLEDGMENT -------------------------------------------------- Residents: Morgan Chen; Jamie Premises: Unit 3B, Oakland, CA Renewal term: October 1, 2024 through September 30, 2025 By signing the renewal packet, Residents acknowledge that the following community and lease-related policies continue to apply during the renewal term except to the extent prohibited by law or modified in writing by Owner: A. Quiet enjoyment and noise Residents will avoid unreasonable noise and disturbances, particularly during designated quiet hours and in shared common areas. B. Smoke-free restrictions Smoking and vaping restrictions for the premises and common areas remain as stated in the original lease and community rules. C. Maintenance and access Residents will promptly report maintenance issues and provide lawful access for repairs, inspections, and emergency response as required under the lease and applicable law. D. Waste, recycling, and common areas Residents will comply with posted waste, recycling, and disposal requirements and will keep hallways, entries, and common spaces clear of personal property except as expressly permitted. E. Alterations No material alterations, installations, or fixtures may be added without prior written approval when such approval is required under the original lease. F. Pets No change to pet status is made by this renewal packet. Any permitted pet obligations remain governed by the original lease and related addenda, if any. G. Rent payment and late charges Rent remains due on the first of each month. Any grace periods, late charges, and returned payment charges remain governed by the original lease and applicable law. H. Notices and contact information Residents are responsible for keeping contact information current in the resident portal so Owner may deliver notices regarding the tenancy, building access, maintenance, and billing. Resident acknowledgment Residents acknowledge review of these continuing policies as part of the renewal packet. -------------------------------------------------- 4. RESIDENT SIGNATURE PAGE (CORRECTED) -------------------------------------------------- Page status: Updated and ready for signature Page updated: Monday, September 16, 2024, 11:41 AM PT This signature page applies to: - Renewal Offer Summary - Residential Lease Renewal Addendum - Community Policies Acknowledgment Resident 1 Name: Morgan Chen Signature status: Not signed Date: ________ Resident 2 Name: Jamie Signature status: Not signed Date: ________ Owner / Agent Name: ____________________ Signature status: Pending after resident completion Date: ________ Electronic signing acknowledgment By selecting the sign action in the resident portal, each signing resident confirms that they have reviewed the renewal packet, agree to the renewal terms, and intend their electronic signature to bind them to the renewal documents to the extent permitted by law. Required completion notice All required resident signatures must be completed by Monday, September 16, 2024, 5:00 PM PT. Portal action buttons [Review documents] [Sign packet] [Decline renewal] Footer Lease Renewal Packet for Unit 3B, Oakland, CA Residents on packet: Morgan Chen; Jamie Status as of Monday, September 16, 2024, 11:41 AM PT: Awaiting resident signatures

First short support digest after the Mercury enterprise slice is live came through from Jake. It’s the right shape so far: scoped SAML login attempts, admin audit-history lookups, and a few admin-vs-billing-owner questions. Leo called the one failed SAML attempt stale IdP metadata, not a regression, and Sarah kept the customer explanation tied to what actually shipped.

Atlas support escalation resolved: webhook retries were failing signature checks after a receiver-secret rotation because one customer worker was still verifying with the old secret. Leo did the first read, the customer fixed that worker config, and the next retry succeeded. Jake isn’t changing Atlas sequencing off this.

Kibo’s fall dental pre-visit intake came in, and the prep sheet had an optional chicken-flavored dental chew sample. Jamie caught it before we accepted anything; I marked the paperwork no poultry / no chicken meal so the clinic doesn’t hand that out around the visit.

Evergreen signed the paid Mercury Growth pilot. It starts Oct 1 on the standard Growth band Devon held: $7,500/month including up to 200 monthly active developers, then $1,000 per additional 50 MAD. No Evergreen-specific roadmap carveout. SAML SSO and admin-audit validation are included for the pilot through Dec 31, and anything longer-term on enterprise add-on pricing stays a separate quote once we have cleaner evidence. Sarah closed the customer thread, and Nadia’s prep really helped keep this framed as repeatable enterprise readiness instead of custom scope. Good outcome: commercially committed, not a bespoke Evergreen roadmap.

Evergreen’s kickoff note is clean enough for Sarah to answer. They named two initial admin testers for the Oct 1 Mercury Growth pilot, asked if procurement can sit in on the first check-in, and asked whether SAML validation should use the same scoped enterprise account from the signed paperwork. Devon is treating procurement as optional commercial context, not a product participant, and Jake confirmed the shipped SSO/admin-audit surface is what we’re validating. No new roadmap promise needed.

BART made the SF timing silly this morning, so I bailed on the Embarcadero run plan. Did a short Lake Merritt loop from Oakland and took the first call from home instead of trying to stack commute + run + calls.

Send Kara the boundary Sarah and I aligned on: Kestrel can do maintenance copy that names the shipped SAML SSO, admin-audit, and admin-role-separation / admin-vs-billing-owner capabilities in generic product language. They should not use Evergreen’s name, customer logos, funding language, “enterprise-ready” proof claims, or any customer proof / case-study block unless Scaffold reviews that separately.

Board update is done. It landed better than June because the facts are more real now: Evergreen is a paid pilot, the SSO/admin-audit slice shipped, Atlas is handling normal issues on the post-Rishi split, and Nadia’s read is turning into stronger enterprise conversations.

We also said the less convenient part out loud. Nadia’s first stronger plan pulled too far toward bespoke asks, enterprise readiness is dragging roadmap gravity toward larger customers, and we’re not ready to scale GTM headcount. Devon and I told them Q4 stays constrained: no broad field-sales build, no RevOps/CS lane, and no second Mercury eng req until we see adoption, renewal/expansion signal, and account-source quality repeat. Good outcome overall — deliberate enterprise follow-through, not post-Series-B hiring acceleration, and enough board cover to say no when a one-account conversation tries to become roadmap.

Evergreen’s admin tester screenshot was a setup-path issue, not a scary Mercury regression. They got through SAML login and could see the admin-audit row, then got stuck trying to route a billing-contact invite through the workspace-admin surface. Leo and Jake both confirmed it wasn’t an SSO failure or audit-log bug. Sarah answered with the current workspace-admin path and kept the language tied to what’s actually shipped.