id: '181'
narrative_anchor_date: '2026-09-14'
test: Create a historical note about the early-April 2023 API v1 billing and inbound-event
  routes and their authentication. Do not present them as current guidance.
load_bearing_facts:
- 35
- 43
- 44
expected_tool_calls:
- create_doc
grade:
  type: tool_trace
  config:
    check_version: 2
    today: '2026-09-14'
    assertions:
    - type: field_equals
      tool: create_doc
      path: result.ok
      value: true
      check_id: morgan_181_00
      action_id: morgan_181_create_doc
    - type: field_llm_judge
      path: result.document.body
      criterion: Records /charges and /refunds wired to billing using the basic-auth
        token, and POST /v1/webhooks using the same basic-auth setup. Keeps it historical
        API v1, not current v2 JWT guidance. Token-creation sprint detail is unnecessary.
      tool: create_doc
      check_id: morgan_181_01
      action_id: morgan_181_create_doc
mock_state:
  calendar:
  - attendees:
    - Devon
    end: '2023-01-11T10:30:00-08:00'
    id: cal_000004_1
    start: '2023-01-11T10:00:00-08:00'
    title: Numbers slide review with Devon
  - attendees:
    - Marcus
    end: '2023-01-11T11:05:00-08:00'
    id: cal_000004_2
    start: '2023-01-11T10:35:00-08:00'
    title: Support rotation doc review
  - attendees:
    - Priya
    end: '2023-01-12T10:20:00-08:00'
    id: evt_20230111130000000
    start: '2023-01-12T10:00:00-08:00'
    title: Review onboarding flow mocks
  - attendees: []
    end: '2023-01-13T07:05:00-08:00'
    id: evt_20230112170000000
    start: '2023-01-13T07:00:00-08:00'
    title: 'Reminder: review Priya''s design spec before standup'
  - attendees: []
    end: '2023-01-14T17:35:00-08:00'
    id: evt_20230114140000000
    start: '2023-01-14T17:30:00-08:00'
    title: 'Reminder: grab the Trader Joe''s order before 6'
  - attendees: []
    end: '2023-01-27T09:05:00-08:00'
    id: evt_20230126173000000
    start: '2023-01-27T09:00:00-08:00'
    title: 'Reminder: submit December expenses'
  - attendees:
    - Devon
    end: '2023-02-06T11:30:00-08:00'
    id: cal_000094_1
    start: '2023-02-06T11:00:00-08:00'
    title: 1:1 with Devon
  - attendees:
    - Devon
    end: '2023-02-23T16:00:00-08:00'
    id: evt_20230222140000000
    start: '2023-02-23T14:00:00-08:00'
    title: Working session on the H2 plan
  - attendees: []
    end: '2023-02-27T09:05:00-08:00'
    id: evt_20230224153000000
    start: '2023-02-27T09:00:00-08:00'
    title: 'Reminder: send the board pre-read'
  - attendees:
    - Devon
    end: '2023-03-08T10:00:00-08:00'
    id: cal_000198_1
    start: '2023-03-08T09:00:00-08:00'
    title: Q3 planning check-in
  - attendees:
    - Devon
    body: No interrupting.
    end: '2023-03-08T12:00:00-08:00'
    id: evt_20230307140000004
    start: '2023-03-08T10:00:00-08:00'
    title: Conversation with Devon about the prior month
  - attendees:
    - reservations@pennyroma-test.com
    end: '2023-03-19T21:00:00-07:00'
    id: cal_000260_1
    start: '2023-03-19T19:30:00-07:00'
    title: Dinner reservation at Penny Roma
  - attendees: []
    end: '2023-04-28T11:00:00-07:00'
    id: evt_20230421093000000
    start: '2023-04-28T10:00:00-07:00'
    title: All-hands -- Q&A format
  - attendees: []
    end: '2023-04-28T15:00:00-07:00'
    id: evt_20230421100000000
    start: '2023-04-28T14:00:00-07:00'
    title: quarterly all-hands
  - attendees:
    - Priya
    end: '2023-04-22T15:30:00-07:00'
    id: evt_20230421140000000
    start: '2023-04-22T15:00:00-07:00'
    title: Sync w/ Priya
  - attendees: []
    end: '2023-05-08T12:00:00-07:00'
    id: evt_1784911051711
    start: '2023-05-08T10:00:00-07:00'
    title: 'Protected time — Mercury operating work: Jake''s weekly agenda + blockers'
  - attendees:
    - Morgan Chen
    - Devon Hayes
    - Jake
    - Priya
    - Anna Martinez
    end: '2023-05-12T16:00:00-07:00'
    id: evt_1784911056457
    start: '2023-05-12T10:00:00-07:00'
    title: Mercury product offsite — decisions, owners, launch blockers
  - attendees:
    - Morgan Chen
    - Anna Martinez
    - Devon Hayes
    end: '2023-05-17T11:45:00-07:00'
    id: evt_1784920497852
    start: '2023-05-17T11:00:00-07:00'
    title: Mercury retention package review — weekly cuts + board view
  - attendees: []
    end: '2023-05-18T11:05:00-07:00'
    id: evt_1784920499960
    start: '2023-05-18T09:05:00-07:00'
    title: Travel buffer — SFO airport arrival for AS 16
  - attendees: []
    end: '2023-05-18T19:41:00-04:00'
    id: evt_1784920500387
    start: '2023-05-18T11:05:00-07:00'
    title: Flight AS 16 — SFO to JFK (Alaska RK7Q2M)
  - attendees: []
    end: '2023-05-20T11:00:00-04:00'
    id: evt_1784920500820
    start: '2023-05-18T16:00:00-04:00'
    title: Hotel stay — Ace Hotel Brooklyn (88417326)
  - attendees: []
    end: '2023-05-20T15:30:00-04:00'
    id: evt_1784920501254
    start: '2023-05-20T13:30:00-04:00'
    title: Travel buffer — JFK airport arrival for AS 23
  - attendees: []
    end: '2023-05-20T18:58:00-07:00'
    id: evt_1784920501700
    start: '2023-05-20T15:30:00-04:00'
    title: Flight AS 23 — JFK to SFO (Alaska RK7Q2M)
  - attendees: []
    body: Protected hold for Mercury operating follow-through.
    end: '2023-05-22T12:00:00-07:00'
    id: evt_1785100219582
    start: '2023-05-22T10:00:00-07:00'
    title: Protected time — Mercury operating follow-through
  - attendees:
    - Morgan Chen
    - Anna Martinez
    - Devon Hayes
    body: Review the suspect Mercury activation mapping before any board or external
      use.
    end: '2023-05-24T13:30:00-07:00'
    id: evt_1785100220511
    start: '2023-05-24T13:00:00-07:00'
    title: Mercury activation mapping review
  - attendees: []
    body: October 12–22, 2023 Tokyo trip hold is postponed/canceled before buying
      flights. No replacement hold or booked date is being created; revisit only after
      Mercury follow-through, Jamie’s hospital schedule, and H2 fundraising timing
      are clearer.
    end: '2023-09-20T09:19:00-07:00'
    id: evt_1785100222856
    start: '2023-09-20T09:18:00-07:00'
    title: Postponed — Tokyo trip (no active October hold)
  - attendees:
    - ops@bluelinehq.com
    - morgan@atlas-test.com
    end: '2023-06-06T17:45:00-07:00'
    id: evt_morgan_20260529_blueline_offsite
    notes: Contractor touchpoint; preserve the existing invitation when rescheduling.
    start: '2023-06-06T17:15:00-07:00'
    title: Blueline contractor offsite touchpoint
  - attendees: []
    body: Protected hold for Mercury operating follow-through before Jake's weekly
      turns into scattered follow-ups.
    end: '2023-06-05T12:00:00-07:00'
    id: evt_1785104285741
    start: '2023-06-05T10:00:00-07:00'
    title: Protected time — Mercury operating work
  - attendees:
    - morgan@atlas-test.com
    - jake@atlas-test.com
    - rishi@atlas-test.com
    body: Short Mercury auth v0.2 readout with Morgan, Jake, and Rishi.
    end: '2023-06-08T11:00:00-07:00'
    id: evt_1785104290048
    start: '2023-06-08T10:30:00-07:00'
    title: Mercury auth v0.2 readout
  - attendees: []
    body: Protected hold for Mercury operating work.
    end: '2023-06-12T12:00:00-07:00'
    id: evt_1785105380282
    start: '2023-06-12T10:00:00-07:00'
    title: Protected time — Mercury operating work
  - attendees:
    - morgan@atlas-test.com
    - priya@atlas-test.com
    - jake@atlas-test.com
    - marcus@atlas-test.com
    body: Session for resolving activation-surface QA blockers before the next Mercury
      readout.
    end: '2023-06-27T15:15:00-07:00'
    id: evt_1785127165403
    start: '2023-06-27T14:30:00-07:00'
    title: Mercury activation surface bug bash
  - attendees:
    - Morgan Chen
    - Leo Park
    body: CEO welcome and Mercury context on Leo’s first morning.
    end: '2023-07-10T10:30:00-07:00'
    id: evt_1785127681379
    start: '2023-07-10T10:00:00-07:00'
    title: Leo Park — CEO welcome and Mercury context
  - attendees:
    - Morgan Chen
    - Priya
    - Marcus
    - Leo Park
    body: 'Figma: https://www.figma.com/file/7mQvR1aH2k9p4LxM3Yc8nR/Mercury-activation-v0.2?node-id=1842%3A9912


      Priya''s context: Review the latest Mercury failed-sync and small-width frames.
      Focus on whether the 320px source-unavailable clipping follow-up is resolved;
      whether the failed-sync states still preserve the neutral warning-circle direction
      and normalized error buckets cleanly at small widths; and whether anything under
      setup-guide copy or icon polish has crossed from nonblocking follow-up into
      a release-readiness blocker. Do not reopen the settled CTA or failed-state icon
      decisions. Use the review to confirm the frames are good enough for the next
      dogfood pass and that Marcus and Leo can tie remaining evidence questions back
      to MER-1279.'
    end: '2023-07-26T15:00:00-07:00'
    id: evt_1785179885099
    start: '2023-07-26T14:00:00-07:00'
    title: Mercury failed-sync / small-width review
  - attendees:
    - Morgan Chen
    - Devon Hayes
    - Anna Martinez
    - Sofia Alvarez
    - Northstar partner group
    body: 'Agenda: September/October Mercury cohort package; Evergreen enterprise-readiness
      signal; hybrid pricing. Boundaries: focused diligence readout only; no term-sheet
      implication, no lead designation for Northstar, and no weekly activation cuts
      in the deck.'
    end: '2024-01-11T11:30:00-08:00'
    id: evt_1785306027016
    start: '2024-01-11T10:00:00-08:00'
    title: Northstar Mercury partner readout
  - attendees: []
    body: 'Protected local reset with Jamie and Kibo: Dec. 24 through Jan. 1 stays
      local and travel-free, with Oakland/Lake Merritt plans and no Tokyo or substitute-trip
      hold. Exception only for work directly required for the already-scheduled Jan.
      11 Northstar readout.'
    end: '2024-01-02T00:00:00-08:00'
    id: evt_1785307426116
    start: '2023-12-24T00:00:00-08:00'
    title: Holiday local reset — Oakland/Lake Merritt
  - attendees: []
    body: 'Booked Tokyo trip for Morgan Chen and Jamie, Thu Mar 7 through Tue Mar
      12, 2024. Flights: JAL 1 San Francisco to Tokyo Haneda, departs Mar 7 at 12:40
      PM PST and arrives Mar 8 at 4:55 PM JST; JAL 2 Tokyo Haneda to San Francisco,
      departs Mar 12 at 6:25 PM JST and arrives Mar 12 at 11:10 AM PDT. Flight confirmation
      H7K4Q2. Hotel: Trunk Hotel Shibuya, check-in Mar 8 and check-out Mar 12, confirmation
      54188231. Kibo care confirmed locally in Oakland. Devon Hayes owns non-urgent
      investor close-out follow-up while Morgan is away.'
    end: '2024-03-13T00:00:00-07:00'
    id: evt_1785523421608
    start: '2024-03-07T00:00:00-08:00'
    title: Protected travel window — Tokyo trip
  - id: evt_1786405354514
    title: Evergreen enterprise-readiness review
    start: '2024-07-11T10:00:00-07:00'
    end: '2024-07-11T11:00:00-07:00'
    attendees:
    - Evergreen procurement and security reviewers
    - Sarah Kim
    - Devon Hayes
    - Nadia Singh
    - Morgan Chen
    body: 'Enterprise-readiness review centered on current-state evidence, SSO/SAML
      evaluation framing, admin-side audit history, admin vs. billing-owner separation,
      and what a standalone procurement/security packet would need to include.


      Role boundaries:

      - Sarah keeps the customer thread.

      - Devon owns the commercial/procurement framing without feature-date promises.

      - Nadia listens for repeatable customer-growth patterns.'
  - id: evt_1786564591567
    title: Review Oakland lease renewal with Jamie
    start: '2024-09-03T09:00:00-07:00'
    end: '2024-09-03T09:15:00-07:00'
    attendees: []
  - id: evt_1786933546919
    title: Oakland maintenance — window leak reseal
    start: '2025-01-06T10:00:00-08:00'
    end: '2025-01-06T12:00:00-08:00'
    attendees: []
    body: Living-room window lower-frame reseal for Unit 3B. Keep towel setup until
      done; keep Kibo out of the work area while sealant is applied/cures.
  - id: evt_1786933939856
    title: Kibo routine senior-dog recheck
    start: '2025-04-11T10:00:00-07:00'
    end: '2025-04-11T10:30:00-07:00'
    attendees: []
    body: 'Routine senior-dog recheck after stable Jan. 10 gait visit; go sooner if
      appetite, vomiting, or gait problems recur.


      Prep notes for Apr 11: short flat Lake Merritt-side walks have been okay; Apr
      5 had mild starting stiffness, then Kibo loosened up; eating normally; no vomiting;
      no new gait issue. Current baseline: measured food, strict no-poultry care,
      vet-approved non-poultry joint supplement, and shorter or flatter walks when
      stiff.'
  - id: evt_1739468760000
    title: Q1 company update + collected Q&A
    start: '2025-03-06T10:00:00-08:00'
    end: '2025-03-06T11:00:00-08:00'
    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.'
  - id: evt_1741655100003
    title: Protected evening — Morgan + Jamie anniversary
    start: '2025-03-19T18:00:00-07:00'
    end: '2025-03-19T22:00:00-07:00'
    attendees: []
    body: Protected anniversary evening in Oakland. Only an actual incident or similarly
      customer-impacting emergency should override it; route routine investor, board,
      customer, and internal catch-ups around this hold.
  - id: evt_1742229720003
    title: Evergreen SAML certificate rotation prep
    start: '2025-04-01T11:00:00-07:00'
    end: '2025-04-01T11:30:00-07:00'
    attendees:
    - Sarah Kim
    - Leo Park
    - Devon Hayes
    body: Prep for Evergreen’s April 3 SAML certificate rotation on the annual Mercury
      Growth account. Keep this to shipped SAML operational readiness and workspace-admin
      support path; no advanced-admin, procurement/security add-on, or roadmap commitments.
  - id: evt_1744247220000
    title: Offline household morning — Jamie/Kibo
    start: '2025-04-12T08:30:00-07:00'
    end: '2025-04-12T11:00:00-07:00'
    attendees: []
    body: Protected Oakland household block with Jamie and Kibo. Route routine Scaffold
      work, investor follow-ups, customer check-ins, and internal catch-ups around
      it unless there is an actual incident or customer-impacting emergency.
  - id: evt_1744766580001
    title: Offline household dinner — Morgan/Jamie
    start: '2025-04-17T18:30:00-07:00'
    end: '2025-04-17T20:30:00-07:00'
    attendees: []
    body: Protected weeknight household block. Route routine Scaffold work, investor
      follow-ups, customer check-ins, and internal catch-ups around it unless there
      is an actual incident or customer-impacting emergency.
  - id: evt_1745335920000
    title: Compass April prompt evidence review
    start: '2025-04-25T10:00:00-07:00'
    end: '2025-04-25T10:45:00-07:00'
    attendees:
    - Morgan Chen
    - Anna Martinez
    - Nadia Singh
    - Jake
    - Leo Park
    - Sarah Kim
    body: 'Review the April Compass action-prompt trial evidence. Anna brings definitions,
      evidence sources, dates, and caveats. Sarah brings account-thread evidence within
      Evergreen annual-account and Acme live-only boundaries. Leo covers data/platform
      seam and source-recency checks. Jake confirms prompt-level implementation only,
      no dashboard rebuild. Nadia covers account-team scripts and whether behavior
      changed. Decision boundaries: no customer-facing proof, no board-dashboard framing,
      no hiring implication before the May board-cycle evidence gate.'
  - id: evt_1745457120004
    title: Offline household morning — Jamie/Kibo
    start: '2025-04-26T08:30:00-07:00'
    end: '2025-04-26T10:30:00-07:00'
    attendees: []
    body: Protected Oakland household block with Jamie and Kibo. Short flat Lake Merritt-side
      walk if Kibo is moving comfortably. Route routine Scaffold work, investor follow-ups,
      customer check-ins, and internal catch-ups around it unless there is an actual
      incident or customer-impacting emergency.
  - id: evt_1745888520009
    title: Offline household dinner — Morgan/Jamie
    start: '2025-05-01T18:30:00-07:00'
    end: '2025-05-01T20:30:00-07:00'
    attendees: []
    body: Protected weeknight household block. Route routine Scaffold work, investor
      follow-ups, customer check-ins, and internal catch-ups around it unless there
      is an actual incident or customer-impacting emergency.
  - id: evt_1746061440003
    title: Offline household morning — Jamie/Kibo
    start: '2025-05-03T08:30:00-07:00'
    end: '2025-05-03T10:30:00-07:00'
    attendees: []
    body: Protected Oakland household block with Jamie and Kibo. Short flat Lake Merritt-side
      walk if Kibo is moving comfortably. Route routine Scaffold work, investor follow-ups,
      customer check-ins, and internal catch-ups around it unless there is an actual
      incident or customer-impacting emergency.
  - id: evt_1746112560004
    title: Evergreen annual account operating read — current state + repeatability
    start: '2025-05-05T10:00:00-07:00'
    end: '2025-05-05T10:50:00-07:00'
    attendees:
    - Morgan Chen
    - Devon Hayes
    - Sarah Kim
    - Nadia Singh
    - Anna Martinez
    body: 'Operating read for Evergreen’s annual Mercury Growth account.


      Agenda:

      - Current-state evidence: shipped SAML rotation, audit lookup, workspace-admin
      support, monthly-active-developer usage.

      - Commercial/procurement boundary: standard Growth terms; no advanced-admin
      add-on claim unless Devon confirms a shipped/quotable package.

      - Customer-growth question: what, if anything, repeats beyond Evergreen?

      - Staffing boundary: no RevOps/CS/SDR/field-sales/customer-growth support or
      second Mercury engineering req unless May board-cycle evidence gate changes.


      Not a customer-facing packet, not a board-dashboard session, and not a hiring
      meeting.'
  - id: evt_1746496020011
    title: Offline household dinner — Morgan/Jamie
    start: '2025-05-07T18:30:00-07:00'
    end: '2025-05-07T20:30:00-07:00'
    attendees: []
    body: Protected weeknight household block. Route routine Scaffold work, investor
      follow-ups, customer check-ins, and internal catch-ups around it unless there
      is an actual incident or customer-impacting emergency.
  - id: evt_1746675780002
    title: Offline household morning — Jamie/Kibo
    start: '2025-05-10T08:30:00-07:00'
    end: '2025-05-10T10:30:00-07:00'
    attendees: []
    body: Protected Oakland household block with Jamie and Kibo. Short flat Lake Merritt-side
      walk if Kibo is moving comfortably. Route routine Scaffold work, investor follow-ups,
      customer check-ins, and internal catch-ups around it unless there is an actual
      incident or customer-impacting emergency.
  - id: evt_1746750120005
    title: May board-cycle evidence review — staffing gate
    start: '2025-05-13T11:00:00-07:00'
    end: '2025-05-13T11:45:00-07:00'
    attendees:
    - Morgan Chen
    - Devon Hayes
    - Sofia Alvarez
    body: 'Focused May board-cycle evidence review. Agenda: Compass prompt behavior-change
      evidence; account-source quality beyond Evergreen; owner-routed enterprise-readiness
      intake. Boundary: evidence review only, not a default staffing decision or fundraising
      narrative.'
  - id: evt_1747098660012
    title: Offline household dinner — Morgan/Jamie
    start: '2025-05-15T18:30:00-07:00'
    end: '2025-05-15T20:30:00-07:00'
    attendees: []
    body: Protected weeknight household block during May board-cycle week. Route routine
      Scaffold work, investor follow-ups, customer check-ins, and internal catch-ups
      around it unless there is an actual incident or customer-impacting emergency.
  - id: evt_1747238760004
    title: Compass June closeout — narrow evidence read
    start: '2025-06-04T10:00:00-07:00'
    end: '2025-06-04T10:45:00-07:00'
    attendees:
    - Morgan Chen
    - Devon Hayes
    - Anna Martinez
    - Nadia Singh
    - Jake
    - Leo Park
    - Sarah Kim
    body: 'Narrow Compass closeout after the May board-cycle review.


      Agenda:

      - Did either action prompt change customer or account-team behavior beyond internal
      owner follow-up?

      - What account-source quality is reliable beyond Sarah Kim’s Evergreen Bank
      thread?

      - Is enterprise-readiness intake still owner-routed, and where did routing break
      down?

      - What remains worth keeping as internal prompt evidence work?


      Exclusions: no customer-facing Compass launch, no board dashboard, no GTM proof
      claim, no staffing trigger, and no Series C narrative.'
  - id: evt_1747271760005
    title: Offline household morning — Jamie/Kibo
    start: '2025-05-17T08:30:00-07:00'
    end: '2025-05-17T10:30:00-07:00'
    attendees: []
    body: Protected Oakland household block with Jamie and Kibo. Short flat Lake Merritt-side
      walk if Kibo is moving comfortably. Route routine Scaffold work, investor follow-ups,
      customer check-ins, and internal catch-ups around it unless there is an actual
      incident or customer-impacting emergency.
  - id: evt_1747703220008
    title: Offline household dinner — Morgan/Jamie
    start: '2025-05-22T18:30:00-07:00'
    end: '2025-05-22T20:30:00-07:00'
    attendees: []
    body: Protected weeknight household block. Route routine Scaffold work, investor
      follow-ups, customer check-ins, and internal catch-ups around it unless there
      is an actual incident or customer-impacting emergency.
  - id: evt_1747789860003
    title: Offline household morning — Jamie/Kibo
    start: '2025-05-24T08:30:00-07:00'
    end: '2025-05-24T10:30:00-07:00'
    attendees: []
    body: Protected Oakland household block with Jamie and Kibo. Short flat Lake Merritt-side
      walk if Kibo is moving comfortably. Route routine Scaffold work, investor follow-ups,
      customer check-ins, and internal catch-ups around it unless there is an actual
      incident or customer-impacting emergency.
  - id: evt_1748306280011
    title: Offline household dinner — Morgan/Jamie
    start: '2025-05-29T18:30:00-07:00'
    end: '2025-05-29T20:30:00-07:00'
    attendees: []
    body: Protected weeknight household block. Route routine Scaffold work, investor
      follow-ups, customer check-ins, and internal catch-ups around it unless there
      is an actual incident or customer-impacting emergency.
  - id: evt_1748394360001
    title: Offline household morning — Jamie/Kibo
    start: '2025-05-31T08:30:00-07:00'
    end: '2025-05-31T10:30:00-07:00'
    attendees: []
    body: Protected Oakland household block with Jamie and Kibo. Short flat Lake Merritt-side
      walk if Kibo is moving comfortably. Route routine Scaffold work, investor follow-ups,
      customer check-ins, and internal catch-ups around it unless there is an actual
      incident or customer-impacting emergency.
  - id: evt_1748913180008
    title: Offline household dinner — Morgan/Jamie
    start: '2025-06-05T18:30:00-07:00'
    end: '2025-06-05T20:30:00-07:00'
    attendees: []
    body: Protected weeknight household block during Compass closeout week. Route
      routine Scaffold work, investor follow-ups, customer check-ins, and internal
      catch-ups around it unless there is an actual incident or customer-impacting
      emergency.
  - id: evt_1748999040001
    title: Offline household morning — Jamie/Kibo
    start: '2025-06-07T08:30:00-07:00'
    end: '2025-06-07T10:30:00-07:00'
    attendees: []
    body: Protected Oakland household block with Jamie and Kibo. Short flat Lake Merritt-side
      walk if Kibo is moving comfortably. Route routine Scaffold work, investor follow-ups,
      customer check-ins, and internal catch-ups around it unless there is an actual
      incident or customer-impacting emergency.
  - id: evt_1749494820011
    title: Customer Growth role calibration — current phase alignment
    start: '2025-06-10T10:30:00-07:00'
    end: '2025-06-10T11:15:00-07:00'
    attendees:
    - Morgan Chen
    - Devon Hayes
    - Nadia Singh
    body: 'Private conversation about whether the Head of Customer Growth role matches
      Scaffold''s current phase after the Compass closeout. Boundary: role fit and
      next-step discussion only; no blame framing, no replacement-search assumption,
      and no final transition terms in the invite.'
  - id: evt_1749518340013
    title: Offline household dinner — Morgan/Jamie
    start: '2025-06-11T18:30:00-07:00'
    end: '2025-06-11T20:30:00-07:00'
    attendees: []
    body: Protected weeknight household block. Route routine Scaffold work, investor
      follow-ups, customer check-ins, and internal catch-ups around it unless there
      is an actual incident or customer-impacting emergency.
  - id: evt_1749580860001
    title: Customer Growth role-fit follow-up — next steps
    start: '2025-06-12T10:00:00-07:00'
    end: '2025-06-12T10:30:00-07:00'
    attendees:
    - Morgan Chen
    - Devon Hayes
    - Nadia Singh
    body: Private follow-up after the June 10 role-fit conversation. Discuss next
      steps only; do not use replacement-search, final-transition, or broad communications
      framing in the invite.
  - id: evt_1749689760005
    title: Offline household morning — Jamie/Kibo
    start: '2025-06-14T08:30:00-07:00'
    end: '2025-06-14T10:30:00-07:00'
    attendees: []
    body: Protected Oakland household block with Jamie and Kibo. Short flat Lake Merritt-side
      walk if Kibo is moving comfortably. Route routine Scaffold work, investor follow-ups,
      customer check-ins, and internal catch-ups around it unless there is an actual
      incident or customer-impacting emergency.
  - id: evt_1749763560009
    title: Nadia / Sarah handoff — scripts + account-thread hygiene
    start: '2025-06-16T09:00:00-07:00'
    end: '2025-06-16T09:30:00-07:00'
    attendees:
    - Nadia Singh
    - Sarah Kim
    body: 'Private transition handoff. Scope: customer-growth scripts, account-prep
      language, account-thread hygiene, and Evergreen/Acme boundaries. Not a customer-facing
      owner-story change and not a roadmap or procurement commitment.'
  - id: evt_1749763560010
    title: Nadia / Anna handoff — Compass behavior read + caveats
    start: '2025-06-16T13:00:00-07:00'
    end: '2025-06-16T13:30:00-07:00'
    attendees:
    - Nadia Singh
    - Anna Martinez
    body: 'Private transition handoff. Scope: behavior-read context, Compass prompt
      caveats, evidence quality, and what not to claim. Compass remains internal prompt
      work, not customer-facing proof, GTM proof, a board dashboard, or a hiring trigger.'
  - id: evt_1750122420016
    title: Offline household dinner — Morgan/Jamie
    start: '2025-06-19T18:30:00-07:00'
    end: '2025-06-19T20:30:00-07:00'
    attendees: []
    body: Protected weeknight household block during Nadia's final transition week.
      Route routine Scaffold work, investor follow-ups, customer check-ins, and internal
      catch-ups around it unless there is an actual incident or customer-impacting
      emergency.
  - id: evt_1750122420017
    title: Offline household morning — Jamie/Kibo
    start: '2025-06-21T08:00:00-07:00'
    end: '2025-06-21T10:00:00-07:00'
    attendees: []
    body: Protected Oakland household block with Jamie and Kibo. Short flat Lake Merritt-side
      walk if Kibo is moving comfortably. Route routine Scaffold work, investor follow-ups,
      customer check-ins, and internal catch-ups around it unless there is an actual
      incident or customer-impacting emergency.
  - id: evt_1750813380001
    title: Offline household dinner — Morgan/Jamie
    start: '2025-06-26T18:30:00-07:00'
    end: '2025-06-26T20:30:00-07:00'
    attendees: []
    body: Protected weeknight household block during Q2 board-cycle week. Route routine
      Scaffold work, investor follow-ups, customer check-ins, and internal catch-ups
      around it unless there is an actual incident or customer-impacting emergency.
  - id: evt_1750813380002
    title: Offline household morning — Jamie/Kibo
    start: '2025-06-28T08:00:00-07:00'
    end: '2025-06-28T10:00:00-07:00'
    attendees: []
    body: Protected Oakland household block with Jamie and Kibo. Short flat Lake Merritt-side
      walk if Kibo is moving comfortably. Route routine Scaffold work, investor follow-ups,
      customer check-ins, and internal catch-ups around it unless there is an actual
      incident or customer-impacting emergency.
  - id: evt_1751152680010
    title: Devon July pause planning — private
    start: '2025-06-29T09:30:00-07:00'
    end: '2025-06-29T10:15:00-07:00'
    attendees:
    - Morgan Chen
    - Devon Hayes
    body: Private founder conversation after Q2 board-cycle close. Discuss whether
      Devon takes a real July pause from day-to-day work, emergency-only boundary,
      owner coverage, and what not to announce before Morgan and Devon agree.
  - id: evt_1751296980012
    title: Devon away from day-to-day Scaffold work — emergency-only
    start: '2025-07-01T00:00:00-07:00'
    end: '2025-08-01T00:00:00-07:00'
    attendees:
    - Morgan Chen
    - Devon Hayes
    body: 'Devon is away from day-to-day Scaffold work July 1–31, 2025. Only true
      emergencies route to him. July owner split: Jake owns Mercury sequencing; Leo
      Park owns platform seams and Atlas first technical reads; Priya owns activation/onboarding
      quality; Anna Martinez owns retention and Compass evidence quality; Sarah Kim
      owns Evergreen customer-thread continuity; Morgan Chen owns board/customer narrative
      without Devon as the default second brain.'
  - id: evt_1751330760020
    title: Offline household dinner — Morgan/Jamie
    start: '2025-07-03T18:30:00-07:00'
    end: '2025-07-03T20:30:00-07:00'
    attendees: []
    body: Protected weeknight household block during the first week of Devon's July
      pause. Route routine Scaffold work, investor follow-ups, customer check-ins,
      and internal catch-ups around it unless there is an actual incident or customer-impacting
      emergency.
  - id: evt_1751330760021
    title: Offline household morning — Jamie/Kibo
    start: '2025-07-05T08:00:00-07:00'
    end: '2025-07-05T10:00:00-07:00'
    attendees: []
    body: Protected Oakland household block with Jamie and Kibo. Short flat Lake Merritt-side
      walk if Kibo is moving comfortably. Route routine Scaffold work, investor follow-ups,
      customer check-ins, and internal catch-ups around it unless there is an actual
      incident or customer-impacting emergency.
  - id: evt_1751851320012
    title: Offline household dinner — Morgan/Jamie
    start: '2025-07-10T18:30:00-07:00'
    end: '2025-07-10T20:30:00-07:00'
    attendees: []
    body: Protected weeknight household block during Devon's July pause. Route routine
      Scaffold work, investor follow-ups, customer check-ins, and internal catch-ups
      around it unless there is an actual incident or customer-impacting emergency.
  - id: evt_1751851320013
    title: Offline household morning — Jamie/Kibo
    start: '2025-07-12T08:00:00-07:00'
    end: '2025-07-12T10:00:00-07:00'
    attendees: []
    body: Protected Oakland household block with Jamie and Kibo. Short flat Lake Merritt-side
      walk if Kibo is moving comfortably. Route routine Scaffold work, investor follow-ups,
      customer check-ins, and internal catch-ups around it unless there is an actual
      incident or customer-impacting emergency.
  - id: evt_1752454560024
    title: Offline household dinner — Morgan/Jamie
    start: '2025-07-17T18:30:00-07:00'
    end: '2025-07-17T20:30:00-07:00'
    attendees: []
    body: Protected weeknight household block during Devon's July pause. Route routine
      Scaffold work, investor follow-ups, customer check-ins, and internal catch-ups
      around it unless there is an actual incident or customer-impacting emergency.
  - id: evt_1752454560025
    title: Offline household morning — Jamie/Kibo
    start: '2025-07-19T08:00:00-07:00'
    end: '2025-07-19T10:00:00-07:00'
    attendees: []
    body: Protected Oakland household block with Jamie and Kibo. Short flat Lake Merritt-side
      walk if Kibo is moving comfortably. Route routine Scaffold work, investor follow-ups,
      customer check-ins, and internal catch-ups around it unless there is an actual
      incident or customer-impacting emergency.
  - id: evt_1752507360000
    title: Compass July first-pass evidence read
    start: '2025-07-16T10:00:00-07:00'
    end: '2025-07-16T10:45:00-07:00'
    attendees:
    - Morgan Chen
    - Anna Martinez
    - Sarah Kim
    - Jake
    - Leo Park
    body: 'First Q3 read of retained Compass prompt usage. Bring structured rows only:
      account, prompt type, sighting date, owner, source/excerpt, caveat, owner follow-up
      date, outcome/current status. Boundaries: prompt sightings alone do not count;
      dated owner follow-up can be tracked; Acme export signal must be checked as
      Atlas/API v2 support context, not Compass proof; no customer-facing claims,
      GTM proof, staffing trigger, or Devon route during the July pause.'
  - id: evt_1753058760014
    title: Offline household dinner — Morgan/Jamie
    start: '2025-07-24T18:30:00-07:00'
    end: '2025-07-24T20:30:00-07:00'
    attendees: []
    body: Protected weeknight household block during Devon's July pause. Route routine
      Scaffold work, investor follow-ups, customer check-ins, and internal catch-ups
      around it unless there is an actual incident or customer-impacting emergency.
  - id: evt_1753058760015
    title: Offline household morning — Jamie/Kibo
    start: '2025-07-26T08:00:00-07:00'
    end: '2025-07-26T10:00:00-07:00'
    attendees: []
    body: Protected Oakland household block with Jamie and Kibo. Short flat Lake Merritt-side
      walk if Kibo is moving comfortably, and keep it shorter if the morning is warm
      or he starts stiff. Route routine Scaffold work, investor follow-ups, customer
      check-ins, and internal catch-ups around it unless there is an actual incident
      or customer-impacting emergency.
  - id: evt_1753660680020
    title: Offline household dinner — Morgan/Jamie
    start: '2025-07-31T18:30:00-07:00'
    end: '2025-07-31T20:30:00-07:00'
    attendees: []
    body: Protected weeknight household block during the final day of Devon's July
      pause. Route routine Scaffold work, investor follow-ups, customer check-ins,
      and internal catch-ups around it unless there is an actual incident or customer-impacting
      emergency.
  - id: evt_1753660680021
    title: Offline household morning — Jamie/Kibo
    start: '2025-08-02T08:00:00-07:00'
    end: '2025-08-02T10:00:00-07:00'
    attendees: []
    body: Protected Oakland household block with Jamie and Kibo. Short flat Lake Merritt-side
      walk if Kibo is moving comfortably, and keep it shorter if the morning is warm
      or he starts stiff. Route routine Scaffold work, investor follow-ups, customer
      check-ins, and internal catch-ups around it unless there is an actual incident
      or customer-impacting emergency.
  - id: evt_1753715460000
    title: Devon pause re-entry conversation — August lane shape
    start: '2025-07-29T16:30:00-07:00'
    end: '2025-07-29T17:15:00-07:00'
    attendees:
    - Morgan Chen
    - Devon Hayes
    body: Private founder conversation at the end of Devon's July pause. Discuss August
      re-entry shape, what should not snap back, and which July owner lanes stay intact
      until Morgan and Devon explicitly agree otherwise. Not a broad operating announcement.
  - id: evt_1753919040018
    title: Mercury activation-copy review — July samples and source-owner cue
    start: '2025-08-05T10:00:00-07:00'
    end: '2025-08-05T10:45:00-07:00'
    attendees:
    - Morgan Chen
    - Priya
    - Jake
    - Leo Park
    body: 'Review Priya''s July activation-copy sample packet. Focus: clip evidence,
      source-owner cue visibility, product state correctness, and whether setup-guide/admin
      copy is confusing invited teammates. Boundaries: no admin-role model reopen,
      no custom admin policy, no granular permissions scope, no Atlas scope. Outcome
      should be a bounded copy/product-state read, not a product escalation by default.'
  - id: evt_1754265120025
    title: Offline household dinner — Morgan/Jamie
    start: '2025-08-07T18:30:00-07:00'
    end: '2025-08-07T20:30:00-07:00'
    attendees: []
    body: Protected weeknight household block during the first full August workweek
      after Devon's pause. Route routine Scaffold work, investor follow-ups, customer
      check-ins, and internal catch-ups around it unless there is an actual incident
      or customer-impacting emergency.
  - id: evt_1754265120026
    title: Offline household morning — Jamie/Kibo
    start: '2025-08-09T08:00:00-07:00'
    end: '2025-08-09T10:00:00-07:00'
    attendees: []
    body: Protected Oakland household block with Jamie and Kibo. Short flat Lake Merritt-side
      walk if Kibo is moving comfortably; keep it shorter if the morning is warm or
      he starts stiff. Route routine Scaffold work, investor follow-ups, customer
      check-ins, and internal catch-ups around it unless there is an actual incident
      or customer-impacting emergency.
  - id: evt_1754869200028
    title: Offline household dinner — Morgan/Jamie
    start: '2025-08-14T18:30:00-07:00'
    end: '2025-08-14T20:30:00-07:00'
    attendees: []
    body: Protected weeknight household block. Route routine Scaffold work, investor
      follow-ups, customer check-ins, and internal catch-ups around it unless there
      is an actual incident or customer-impacting emergency.
  - id: evt_1754869200029
    title: Offline household morning — Jamie/Kibo
    start: '2025-08-16T08:00:00-07:00'
    end: '2025-08-16T10:00:00-07:00'
    attendees: []
    body: Protected Oakland household block with Jamie and Kibo. Short flat Lake Merritt-side
      walk if Kibo is moving comfortably; keep it shorter if the morning is warm or
      he starts stiff. Route routine Scaffold work, investor follow-ups, customer
      check-ins, and internal catch-ups around it unless there is an actual incident
      or customer-impacting emergency.
  - id: evt_1755015480004
    title: Compass owner-action prototype scope decision
    start: '2025-08-13T10:00:00-07:00'
    end: '2025-08-13T10:45:00-07:00'
    attendees:
    - Morgan Chen
    - Anna Martinez
    - Sarah Kim
    - Jake
    - Leo Park
    body: 'Decision meeting: whether to approve a small internal Compass owner-action
      prototype. Proposed scope: renewal-risk/admin-friction and post-first-live-sync
      prompts; next action + evidence source + caveat in one place; owner-action status.
      Boundaries: no dashboard, no customer-facing surface, no GTM/customer-proof/staffing
      claim, and Acme export signals stay Atlas/API v2 support context.'
  - id: evt_1755473700025
    title: Offline household dinner — Morgan/Jamie
    start: '2025-08-21T18:30:00-07:00'
    end: '2025-08-21T20:30:00-07:00'
    attendees: []
    body: Protected weeknight household block. Route routine Scaffold work, investor
      follow-ups, customer check-ins, and internal catch-ups around it unless there
      is an actual incident or customer-impacting emergency.
  - id: evt_1755473700026
    title: Offline household morning — Jamie/Kibo
    start: '2025-08-23T08:00:00-07:00'
    end: '2025-08-23T10:00:00-07:00'
    attendees: []
    body: Protected Oakland household block with Jamie and Kibo. Short flat Lake Merritt-side
      walk if Kibo is moving comfortably; keep it shorter if the morning is warm or
      he starts stiff. Route routine Scaffold work, investor follow-ups, customer
      check-ins, and internal catch-ups around it unless there is an actual incident
      or customer-impacting emergency.
  - id: evt_1756077720028
    title: Offline household dinner — Morgan/Jamie
    start: '2025-08-28T18:30:00-07:00'
    end: '2025-08-28T20:30:00-07:00'
    attendees: []
    body: Protected weeknight household block. Route routine Scaffold work, investor
      follow-ups, customer check-ins, and internal catch-ups around it unless there
      is an actual incident or customer-impacting emergency.
  - id: evt_1756077720029
    title: Offline household morning — Jamie/Kibo
    start: '2025-08-30T08:00:00-07:00'
    end: '2025-08-30T10:00:00-07:00'
    attendees: []
    body: Protected Oakland household block with Jamie and Kibo. Short flat Lake Merritt-side
      walk if Kibo is moving comfortably; keep it shorter if the morning is warm or
      he starts stiff. Route routine Scaffold work, investor follow-ups, customer
      check-ins, and internal catch-ups around it unless there is an actual incident
      or customer-impacting emergency.
  - id: evt_1756310760007
    title: Evergreen treasury current-flow setup walkthrough
    start: '2025-09-17T10:00:00-07:00'
    end: '2025-09-17T10:30:00-07:00'
    attendees:
    - Sarah Kim
    - Jake
    - Leo Park
    - Evergreen treasury operations department
    body: 'Current-flow setup walkthrough under Evergreen''s existing annual Growth
      account. Sarah leads the customer thread. Scope: workspace setup, invited teammate/source-owner
      path, first source connection, and first live sync if ready. Jake optional for
      Mercury product-scope questions; Leo optional for SAML/platform questions only.
      Excludes custom admin policy, granular role editor, advanced-admin controls,
      and procurement/security commitments.


      Prep note for Evergreen treasury operations: come ready with the workspace name,
      teammate/source-owner participants, the first source to connect, and any current-flow
      setup questions. If advanced-admin or granular-role questions come up, Scaffold
      will capture them separately as follow-up, not as blockers or commitments for
      this walkthrough.'
  - id: evt_1756326120009
    title: Compass owner-action prototype readout — actions, caveats, rejected-thin
      rows
    start: '2025-09-05T10:00:00-07:00'
    end: '2025-09-05T10:45:00-07:00'
    attendees:
    - Morgan Chen
    - Anna Martinez
    - Sarah Kim
    - Jake
    - Leo Park
    body: Internal readout for the September Compass owner-action prototype. Bring
      counts by owner_action_status; completed owner actions with evidence source
      and caveat; rejected_thin_source_or_date rows; blocked_waiting_customer_follow_up
      rows; and source_freshness_warning caveats. This is not a customer-facing Compass
      launch, GTM proof, staffing trigger, or fundraising claim.
  - id: evt_1756395660010
    title: Review Oakland Unit 3B lease renewal decision
    start: '2025-09-04T18:00:00-07:00'
    end: '2025-09-04T18:30:00-07:00'
    attendees: []
    body: 'Review pending Unit 3B renewal offer before response deadline. Terms: Oct
      1, 2025–Sept 30, 2026; $4,460/month base rent; utility bill-back unchanged;
      response due Sept 12. Decision frame: renewal increase versus moving cost/disruption,
      Kibo senior-care routine, Jamie schedule, and Oakland/Lake Merritt cadence.
      Do not assume decision yet.'
  - id: evt_1756395660011
    title: Completed — Oakland Unit 3B lease renewal response sent
    start: '2025-09-12T09:00:00-07:00'
    end: '2025-09-12T09:15:00-07:00'
    attendees: []
    body: Renewal response sent September 10, 2025. Unit 3B renewed for October 1,
      2025 through September 30, 2026 at $4,460/month; no new deposit, no renewal
      fee, and utility bill-back unchanged. No action needed on the September 12 deadline.
  - id: evt_1756683360017
    title: Offline household dinner — Morgan/Jamie
    start: '2025-09-04T18:30:00-07:00'
    end: '2025-09-04T20:30:00-07:00'
    attendees: []
    body: Protected weeknight household block. Route routine Scaffold work, investor
      follow-ups, customer check-ins, and internal catch-ups around it unless there
      is an actual incident or customer-impacting emergency.
  - id: evt_1756683360018
    title: Offline household morning — Jamie/Kibo
    start: '2025-09-06T08:00:00-07:00'
    end: '2025-09-06T10:00:00-07:00'
    attendees: []
    body: Protected Oakland household block with Jamie and Kibo. Short flat Lake Merritt-side
      walk if Kibo is comfortable; keep it shorter if the morning is warm or he starts
      stiff. Route routine Scaffold work, investor follow-ups, customer check-ins,
      and internal catch-ups around it unless there is an actual incident or customer-impacting
      emergency.
  - id: evt_1757287680018
    title: Offline household dinner — Morgan/Jamie
    start: '2025-09-11T18:30:00-07:00'
    end: '2025-09-11T20:30:00-07:00'
    attendees: []
    body: Protected weeknight household block. Route routine Scaffold work, investor
      follow-ups, customer check-ins, and internal catch-ups around it unless there
      is an actual incident or customer-impacting emergency.
  - id: evt_1757287680019
    title: Offline household morning — Jamie/Kibo
    start: '2025-09-13T08:00:00-07:00'
    end: '2025-09-13T10:00:00-07:00'
    attendees: []
    body: Protected Oakland household block with Jamie and Kibo. Short flat Lake Merritt-side
      walk if Kibo is comfortable; keep it shorter if the morning is warm or he starts
      stiff. Route routine Scaffold work, investor follow-ups, customer check-ins,
      and internal catch-ups around it unless there is an actual incident or customer-impacting
      emergency.
  - id: evt_1757892840012
    title: Offline household dinner — Morgan/Jamie
    start: '2025-09-18T18:30:00-07:00'
    end: '2025-09-18T20:30:00-07:00'
    attendees: []
    body: Protected weeknight household block. Route routine Scaffold work, investor
      follow-ups, customer check-ins, and internal catch-ups around it unless there
      is an actual incident or customer-impacting emergency.
  - id: evt_1757892840013
    title: Offline household morning — Jamie/Kibo
    start: '2025-09-20T08:00:00-07:00'
    end: '2025-09-20T10:00:00-07:00'
    attendees: []
    body: Protected Oakland household block with Jamie and Kibo. Short flat Lake Merritt-side
      walk if Kibo is comfortable; keep it shorter if the morning is warm or he starts
      stiff. Route routine Scaffold work, investor follow-ups, customer check-ins,
      and internal catch-ups around it unless there is an actual incident or customer-impacting
      emergency.
  - id: evt_1758038820001
    title: Q3 operating review — Evergreen, Compass, Atlas/Mercury evidence
    start: '2025-09-24T10:00:00-07:00'
    end: '2025-09-24T11:15:00-07:00'
    attendees:
    - Morgan Chen
    - Devon Hayes
    - Sofia Alvarez
    - Anna Martinez
    - Sarah Kim
    - Jake
    - Leo Park
    body: 'Evidence review only, not a fundraising kickoff. Questions: (1) whether
      Evergreen evidence is repeatable beyond one clean thread; (2) whether Compass
      owner-action evidence is strong enough to relaunch narrowly; (3) whether Atlas/Mercury
      reliability is holding under the post-pause owner split; (4) what evidence would
      ever justify restarting Series C market-warming. Bring actual evidence, caveats,
      owner boundaries, and what not to claim.'
  - id: evt_1758497820013
    title: Offline household dinner — Morgan/Jamie
    start: '2025-09-25T18:30:00-07:00'
    end: '2025-09-25T20:30:00-07:00'
    attendees: []
    body: Protected weeknight household block. Route routine Scaffold work, investor
      follow-ups, customer check-ins, and internal catch-ups around it unless there
      is an actual incident or customer-impacting emergency.
  - id: evt_1758497820014
    title: Offline household morning — Jamie/Kibo
    start: '2025-09-27T08:00:00-07:00'
    end: '2025-09-27T10:00:00-07:00'
    attendees: []
    body: Protected Oakland household block with Jamie and Kibo. Short flat Lake Merritt-side
      walk if Kibo is comfortable; keep it shorter if the morning is warm or he starts
      stiff. Route routine Scaffold work, investor follow-ups, customer check-ins,
      and internal catch-ups around it unless there is an actual incident or customer-impacting
      emergency.
  - id: evt_1759102260020
    title: Offline household dinner — Morgan/Jamie
    start: '2025-10-02T18:30:00-07:00'
    end: '2025-10-02T20:30:00-07:00'
    attendees: []
    body: Protected weeknight household block. Route routine Scaffold work, investor
      follow-ups, customer check-ins, and internal catch-ups around it unless there
      is an actual incident or customer-impacting emergency.
  - id: evt_1759102260021
    title: Offline household morning — Jamie/Kibo
    start: '2025-10-04T08:00:00-07:00'
    end: '2025-10-04T10:00:00-07:00'
    attendees: []
    body: Protected Oakland household block with Jamie and Kibo. Short flat Lake Merritt-side
      walk if Kibo is comfortable; keep it shorter if the morning is warm or he starts
      stiff. Route routine Scaffold work, investor follow-ups, customer check-ins,
      and internal catch-ups around it unless there is an actual incident or customer-impacting
      emergency.
  - id: evt_1759176720003
    title: Q4 operating lanes decision — Morgan/Devon
    start: '2025-09-30T09:30:00-07:00'
    end: '2025-09-30T10:00:00-07:00'
    attendees:
    - Devon Hayes
    body: 'Private founder decision after Q3 review closeout: whether July/August
      owner lanes become the durable Q4 operating model. Decision frame: Devon handles
      commercial/procurement context and selective cofounder judgment; avoid snapping
      back to Devon as default board/customer cleanup or loose-owner route.'
  - id: evt_1762543080000
    title: Q4 operating review
    start: '2025-12-12T10:00:00-08:00'
    end: '2025-12-12T11:30:00-08:00'
    attendees:
    - Sofia Alvarez
    - Devon Hayes
    - Anna Martinez
    - Sarah Kim
    - Jake
    - Leo Park
    - Morgan Chen
    body: 'Review whether Q4 evidence survives beyond Evergreen and the internal Compass
      workflow, whether Acme is normal support again, and whether Series C market-warming
      or hiring posture changes.


      Hard stop at 11:30 PT. Please read the Evergreen usage/overage note, Compass
      November behavior read, and Acme support-routing summary before the meeting.
      This is an operating-evidence review, not a fundraising kickoff or default staffing-decision
      meeting.'
  - id: evt_1763088360000
    title: Oakland household time — no normal Scaffold scheduling
    start: '2025-12-24T00:00:00-08:00'
    end: '2025-12-29T00:00:00-08:00'
    attendees: []
    body: Morgan and Jamie are local in Oakland with Kibo for protected household
      time. There is no normal Scaffold scheduling during Dec 24-28; owner lanes and
      the support rotation handle normal work. Pull Morgan in only for an actual customer-impacting
      incident or a founder-level decision. Evergreen's normal admin follow-up stays
      on Jan 6. If Kibo is stiff, walks should stay short and flat.
  - id: evt_1765426260002
    title: Family call
    start: '2025-12-14T16:30:00-08:00'
    end: '2025-12-14T17:00:00-08:00'
    attendees: []
    body: Keep it light; mention local holiday plans and Kibo.
  - id: evt_1765483560003
    title: Q4 review opening notes final pass
    start: '2025-12-12T08:15:00-08:00'
    end: '2025-12-12T08:45:00-08:00'
    attendees: []
    body: 'Use bounded language: Evergreen strong but one account; Compass internal
      workflow; Acme normal support; no pre-review staffing decision.'
  - id: evt_1765842900001
    title: Offline household dinner
    start: '2025-12-18T18:30:00-08:00'
    end: '2025-12-18T20:30:00-08:00'
    attendees: []
    body: Normal Scaffold scheduling routes around it unless there is an actual incident.
  - id: evt_1765842900002
    title: Kibo flat walk and coffee
    start: '2025-12-21T09:00:00-08:00'
    end: '2025-12-21T10:30:00-08:00'
    attendees: []
    body: Short flat route if Kibo is stiff and no work catch-ups.
  - id: evt_1767212640001
    title: Jan 2 re-entry — owner-lane cleanup only
    start: '2026-01-02T08:30:00-08:00'
    end: '2026-01-02T09:15:00-08:00'
    attendees: []
    body: route Q4 closeout cleanup to owners; Evergreen January 6 stays with Sarah
      and Devon; Leo owns Atlas/webhook follow-up unless there is renewed customer
      impact; Priya/Jake stay on OAuth-cancel activation fix; do not reopen Series
      C, Head of Customer Growth, or second Mercury engineering req from the first-hour
      sweep.
  - id: evt_1768009200003
    title: Family call
    start: '2026-01-11T16:30:00-08:00'
    end: '2026-01-11T17:00:00-08:00'
    attendees: []
    body: Keep it short; no hosting plan.
  - id: evt_1768786500001
    title: Evergreen redline review hold
    start: '2026-01-20T08:30:00-08:00'
    end: '2026-01-20T09:15:00-08:00'
    attendees: []
    body: Review Evergreen renewal redlines; keep standard Growth/current-state admin
      line; no roadmap or overage concession.
  - id: evt_1769995320002
    title: Mercury empty source-list review — no scope creep
    start: '2026-02-02T08:30:00-08:00'
    end: '2026-02-02T09:00:00-08:00'
    attendees: []
    body: Review Priya/Jake empty source-list options. Keep focus on explanation after
      canceled auth or no connected sources. No invite-link status, admin roles, granular
      roles, or growth-metric claims.
  - id: evt_1770845160003
    title: Compass evidence review — internal owner actions only
    start: '2026-02-13T10:00:00-08:00'
    end: '2026-02-13T10:45:00-08:00'
    attendees:
    - morgan@scaffold.com
    - anna@scaffold.com
    - sarah@scaffold.com
    - jake@scaffold.com
    - leo@scaffold.com
    body: Review January/early-Feb owner-action rows. Classify completed dated owner
      outcomes vs accepted prompts/planned follow-ups/thin signals. No customer-facing
      Compass claims, GTM proof, or Q1 repeatability conclusion in the agenda.
  - id: evt_1771279500001
    title: Evergreen admin review prep — current-state only
    start: '2026-02-18T11:30:00-08:00'
    end: '2026-02-18T12:00:00-08:00'
    attendees:
    - Sarah Kim
    - Devon Hayes
    body: 'Internal prep before Evergreen''s later current-state/admin review. Procurement
      may join the customer session, so align on bounded language first.


      Scope:

      - SAML login hygiene

      - Visible invite/source/admin audit lookup

      - Department usage snapshot

      - How to answer the granular sync-operator roadmap question as later advanced-admin
      research only


      Boundary:

      - Current-state/admin controls only

      - No advanced-admin package

      - No granular sync-operator commitment

      - No custom admin package

      - No renewal obligation'
  - id: evt_1772567280001
    title: Q1 Board Durability Review — operating evidence only
    start: '2026-03-27T10:00:00-07:00'
    end: '2026-03-27T11:30:00-07:00'
    attendees:
    - Morgan Chen
    - Sofia Alvarez
    - Devon Hayes
    - Anna Martinez
    - Sarah Kim
    - Jake
    - Leo Park
    body: 'Scope:

      - standard-term Evergreen retention and usage

      - Acme support posture

      - Mercury activation quality

      - Compass repeatability limits

      - Atlas owner-lane reliability

      - margin discipline

      - whether H1 Series C market-warming remains off


      Non-goals:

      - not a fundraising kickoff

      - not a hiring meeting

      - not a customer-facing Compass decision by default'
  - id: evt_1772758020000
    title: Q1 durability evidence-owner checkpoint
    start: '2026-03-12T09:00:00-07:00'
    end: '2026-03-12T09:30:00-07:00'
    attendees:
    - Morgan Chen
    - Sofia Alvarez
    - Devon Hayes
    - Anna Martinez
    - Sarah Kim
    - Jake
    - Leo Park
    body: 'Purpose: check evidence rows and open questions only before the March 27
      durability review. This is not a fundraising kickoff, hiring meeting, or customer-facing
      Compass decision.'
  - id: evt_1773775680002
    title: Kibo short flat walk
    start: '2026-03-17T12:50:00-07:00'
    end: '2026-03-17T13:15:00-07:00'
    attendees: []
    body: Use the ramp/runner if the entry is damp.
  - id: evt_1775489280002
    title: Evergreen current-state/admin review
    start: '2026-04-16T10:00:00-07:00'
    end: '2026-04-16T10:45:00-07:00'
    attendees:
    - Sarah Kim
    - Devon Hayes
    - Evergreen's admin team
    body: 'Current-state/admin review under standard Growth terms only.


      In scope:

      - shipped SAML login

      - visible invite/source/admin audit lookup

      - workspace-admin support

      - March closed usage under standard Growth mechanics


      Out of scope:

      - no custom admin-policy discussion

      - no granular-role or sync-operator roadmap commitment

      - no procurement or add-on negotiation

      - no overage forecast

      - no department carveout


      This event schedules the review only; it does not imply the review is already
      completed.'
  - id: evt_1776699360001
    title: Kibo vet recheck
    start: '2026-04-22T11:30:00-07:00'
    end: '2026-04-22T12:00:00-07:00'
    attendees: []
    body: Repeated damp side-entry stair hesitation twice in one week; normal eating
      and normal on flat sidewalk; use ramp and non-slip runner when damp or stiff
      until the vet result; do not test damp steps as proof he is fine.
  - id: evt_1777581120001
    title: Manager Q&A — Q2 operating focus
    start: '2026-05-05T09:00:00-07:00'
    end: '2026-05-05T09:30:00-07:00'
    attendees:
    - managers@scaffold.dev
    - hr@scaffold.dev
    body: This session is for manager language on Q2 execution, retention, margin
      discipline, standard customer work, owner lanes, and avoiding fundraising or
      staffing speculation.
  - id: evt_1779204240002
    title: May board deck dry run — overclaim pass
    start: '2026-05-21T14:00:00-07:00'
    end: '2026-05-21T14:45:00-07:00'
    attendees:
    - devon@scaffold.dev
    - jake@scaffold.dev
    - priya@scaffold.dev
    - sarah@scaffold.dev
    - leo@scaffold.dev
    body: 'Working pass before packet freeze. Check April close, Evergreen standard
      mechanics, Mercury docs/support scope, vendor hygiene, and no-H1-market-warming
      language. This is a factual overclaim pass, not a strategy reset.


      Leo is needed from 2:00 to 2:15 PM PT only for the Compass/Atlas overclaim boundary.'
  - id: evt_1779981360000
    title: May close hygiene pass — vendor/customer overclaim check
    start: '2026-06-03T11:00:00-07:00'
    end: '2026-06-03T11:30:00-07:00'
    attendees:
    - Devon Hayes
    - Sarah Kim
    body: AWS should stay rightsizing/vendor hygiene. Pinecone should stay monthly
      unless sustained baseline usage changes the picture. Evergreen May usage should
      stay under standard Growth mechanics. No expansion, financing, or admin-commitment
      language.
  - id: evt_1781709840000
    title: Q2 durability read
    start: '2026-06-24T10:00:00-07:00'
    end: '2026-06-24T11:00:00-07:00'
    attendees:
    - Sofia Alvarez
    - Devon Hayes
    - Anna Martinez
    - Sarah Kim
    - Jake
    - Leo Park
    body: 'Purpose: bounded internal read before H1 closes.


      Scope:

      - Q2 operating evidence

      - July market-warming posture

      - Whether any staffing revisit is actually justified


      Out of scope:

      - not a data-room refresh

      - not an investor packet

      - not a customer-facing Compass decision

      - not a default hiring-reopen meeting'
  - id: evt_1782401520002
    title: Evergreen Q3 current-state/admin review — bounded scope
    start: '2026-07-16T10:00:00-07:00'
    end: '2026-07-16T10:45:00-07:00'
    attendees:
    - Sarah Kim
    - Devon Hayes
    - Evergreen admin team
    body: 'Quarterly current-state/admin review under standard Growth scope.


      In scope:

      - shipped SAML login

      - visible invite/source/admin audit lookup

      - workspace-admin support

      - standard Growth usage mechanics

      - questions on current-state admin controls


      Out of scope:

      - custom admin policy scoping

      - granular sync-operator roadmap commitments

      - procurement/security add-ons

      - overage caps

      - department carveouts

      - renewal conditions

      - Q3 expansion motion'
  - id: evt_1783443960003
    title: Mercury setup-copy/support-quality lane kickoff
    start: '2026-07-09T11:00:00-07:00'
    end: '2026-07-09T11:30:00-07:00'
    attendees:
    - Priya
    - Jake
    - Sarah Kim
    body: 'One-time kickoff for the Mercury setup-copy/support-quality lane.


      Scope:

      - empty source-list copy

      - admin labels during teammate invitations

      - first-sync support wording

      - where source-specific caveats belong


      Out of scope:

      - activation metrics

      - enterprise-readiness claims

      - advanced admin scope

      - staffing evidence'
  - id: evt_1783723500001
    title: Private engagement logistics check-in
    start: '2026-07-12T18:30:00-07:00'
    end: '2026-07-12T19:15:00-07:00'
    attendees:
    - Jamie
    body: Private and limited to what to defer plus family-message boundaries, with
      no date, venue, guest-list, social-post, or family scheduling decisions.
  - id: evt_1784935500001
    title: Private engagement logistics check-in
    start: '2026-07-27T20:15:00-07:00'
    end: '2026-07-27T21:00:00-07:00'
    attendees:
    - Jamie
    body: Compare what we're deferring and how to keep family messaging calm; no date-picking,
      venue search, guest list, social post, or family weekend scheduling.
  - id: evt_1786333260003
    title: Fill water before building shutoff
    start: '2026-08-11T08:15:00-07:00'
    end: '2026-08-11T09:00:00-07:00'
    attendees: []
    body: Building water is off from 9:00 AM to noon. Fill the kettle and Kibo's water
      bowl before calls.
  - id: evt_1787599320003
    title: Oakland lease renewal — compare options
    start: '2026-08-25T19:30:00-07:00'
    end: '2026-08-25T20:00:00-07:00'
    attendees: []
    body: Review $4,620 renewal offer, no new deposit/fee, unchanged utility and pet
      terms, ramp/runner okay. Compare against moving disruption; no decision required
      in the calendar item.
  crm:
  - added_at: '2023-07-18T14:27:00-07:00'
    id: crm_1689715620138
    name: Pinecone
    notes: 'July 2026 prepay offer declined: 6% discount on $60k annual prepay was
      not worth creating prepaid capacity or vendor-risk framing while June was about
      $4.0k and July is tracking about $4.1k with no replay spike.'
    tags:
    - vendor
    - integration
    - monthly-hygiene
    - no-prepaid
    - july2026-prepay-declined
    updated_at: '2026-07-22T08:20:00-07:00'
    trigger_condition: revisit only after August close if sustained Pinecone usage
      materially exceeds the normal monthly hygiene range
    status: monthly_hygiene_no_july_prepay
    next_touch_date: '2026-08-31'
  - added_at: '2023-08-02T10:56:00-07:00'
    id: crm_1785189091939
    name: Evergreen Bank
    notes: 'November 2025 usage closed at 223 monthly active developers; treasury
      and risk operations are active alongside the original department; Evergreen
      is processing the standard first Growth overage band of $1,000 under existing
      terms; no seat carveout, custom department package, or custom commercial exception.


      Jan 27, 2026: annual Mercury Growth renewal signed for Feb 1, 2026 through Jan
      31, 2027 on standard terms: $7,500 per month including up to 200 monthly active
      developers, plus $1,000 per additional 50 monthly active developers. Quarterly
      current-state/admin reviews are included for then-current admin controls only.
      The signed renewal does not include a granular sync-operator commitment, custom
      admin package, overage cap, department carveout, roadmap appendix, delivery
      date, or advanced-admin renewal obligation. Treat this as a standard Growth
      renewal, not a custom package or founder-owned follow-up.


      Apr 16, 2026: first included 2026 current-state/admin review closed inside standard
      Growth mechanics. Covered shipped SAML login, visible invite/source/admin audit
      lookup, workspace-admin support, and March usage under standard Growth. No custom
      admin policy, overage cap, granular-role date or package, procurement-security
      item, add-on, or department carveout commitment. Sync-operator interest remains
      later advanced-admin research only, with no committed date. Sarah Kim owns the
      customer thread and Devon Hayes covers commercial/procurement context.'
    status: q3_2026_admin_review_closed_current_scope
    tags:
    - mercury
    - growth
    - annual-customer
    - evergreen
    - current-state-admin-review-closed
    - granular-sync-operator-logged-input
    - no-commercial-exception
    updated_at: '2026-07-16T11:35:00-07:00'
    trigger_condition: new standard-term account health or a customer question; not
      April overage as an expansion signal
    next_touch_date: normal Q2 account check-in only
  - added_at: '2023-08-02T10:56:00-07:00'
    id: crm_1690998960154
    name: Acme
    notes: 'Aug 8, 2025: July API v2 large-export recurrence closed as bounded Atlas/API
      v2 chunking/backoff fix. Patched path chunks long export ranges and backs off
      before cursor path timeout. Acme reran the same 90-day export in production;
      export completed and row counts matched narrower monthly replay/workaround checks.
      No customer-visible data loss identified. Routing stayed support customer owner
      + Leo Park first technical read + Jake product sequencing; not Compass, Mercury,
      Devon, or founder-direct scope.'
    updated_at: '2026-06-08T14:46:00-07:00'
    status: normal_q2_atlas_api_v2_support_no_founder_route
    tags:
    - atlas
    - api_v2
    - support-routed
    - normal-q2-2026
    - no-founder-route
  - added_at: '2023-10-25T13:26:00-07:00'
    id: crm_1785284617707
    name: Northstar Ventures
    notes: 'Aug 21: Sofia declined the September 9 AI-infrastructure breakfast/update
      ask. No data room, no September hold, no customer-facing Compass packet, and
      no Series C market-warming from the owner-lane read. Sep 11: Northstar asked
      whether to reserve an early diligence slot or get a lightweight data-room touch
      before partners travel after hearing there is a Sep 18 Q3 operating-posture
      read. Keep warm-later only. No active September process, no data-room touch,
      and no diligence slot reservation unless re-engagement is explicitly chosen
      after the read.'
    status: warm_later_after_sep18_read_no_active_process
    tags:
    - investor
    - b-round
    - northstar
    - narrow-short-list
    - no-data-room
    - aug21-panel-declined
    - no-september-hold
    trigger_condition: Re-engage only if explicitly chosen after the Sep 18 operating-posture
      read; until then there is no active process, no data-room touch, and no diligence
      slot reservation.
    updated_at: '2026-09-11T14:36:00-07:00'
    next_touch_date: after the Sep 18 read, only if re-engagement is explicitly chosen
  deck_edits:
  - applied_at: '2023-05-18T07:44:00-07:00'
    change: 'Update this slide using Anna''s quarterly cohort view only. Keep weekly
      operating cuts out of the board-facing chart.


      Content:

      - Chart/table title: Mercury retention — quarterly first-paid cohorts.

      - Use quarterly cohorts, not weekly signup-week cuts.


      | First paid quarter | Start accounts | M3 logo retention | M6 logo retention
      | M12 logo retention | Net revenue retention at latest mature point | Notes
      |

      | --- | ---: | ---: | ---: | ---: | --- | --- |

      | 2022 Q1 | 21 | 86% | 81% | 71% | 108% @ M12 | Raw is 121% if the oversized
      early expansion customer stays untrimmed; do not headline raw number. |

      | 2022 Q2 | 24 | 88% | 82% | 74% | 110% @ M12 | First cohort with cleaner onboarding
      path reflected consistently. |

      | 2022 Q3 | 29 | 89% | 84% | — | 113% @ M9 | Okay to show through current maturity;
      not enough age for M12 claim. |

      | 2022 Q4 | 32 | 91% | 85% | — | 116% @ M6 | Reads as flattening after onboarding
      improvements; too early to overclaim durability. |

      | 2023 Q1 | 35 | 90% | — | — | 118% @ M3 | Early only; include only if clearly
      marked as immature. |


      Main read:

      - Quarterly cohorts are materially cleaner than weekly cohorts and show better
      flattening after onboarding changes.

      - Revenue retention improves even after trimming the oversized early expansion
      customer from the sensitivity read.

      - External wording: improving quarterly cohort shape, not retention is solved.


      Footnote:

      Quarterly first-paid cohorts; latest quarter shown only through available maturity;
      top-1 expansion outlier trimmed in companion sensitivity view.'
    deck: board note
    id: deck_edit_1784920499112
    slide: Mercury retention — quarterly cohort view
  - applied_at: '2023-06-28T16:38:00-07:00'
    change: 'Slide title: Late-Q2 operating update


      - Anna’s retention package is board-safe quarterly cohort reporting; weekly
      operating cuts are omitted from the board chart.

      - Mercury has real internal progress on auth and onboarding, but Q3 still needs
      to produce external-ready proof on activation and retention.

      - Jake’s weekly Mercury cadence remains the operating spine, and Priya owns
      activation/onboarding UX through launch for clear launch accountability.

      - Leo Park starts July 10 as the staff-engineer anchor for release discipline,
      platform seams, and launch readiness.

      - The B-round remains an H2 conversation; this is operating progress, not a
      rushed summer fundraising restart.'
    deck: board deck
    id: deck_edit_1785127166793
    slide: Late-Q2 operating narrative
  - applied_at: '2023-06-29T09:12:00-07:00'
    change: 'Slide title: Late-Q2 operating update


      - Anna’s retention package is now board-safe quarterly cohort reporting; weekly
      cuts stay out of the board chart.

      - Mercury has real internal progress on auth and onboarding, but Q3 still needs
      to produce external-ready proof on activation and retention.

      - Jake’s weekly Mercury cadence remains the operating spine, with Priya owning
      activation/onboarding UX through launch for clear Mercury launch accountability.

      - Leo Park starts July 10 as the staff-engineer anchor for release discipline,
      platform seams, and launch readiness.

      - The B-round remains an H2 conversation after Mercury produces external-ready
      proof.'
    deck: board deck
    id: deck_edit_1785127167252
    slide: Late-Q2 operating narrative
  - id: deck_edit_1740684060000
    deck: Q1 2025 Board Operating Read
    slide: 4
    change: '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.'
    applied_at: '2025-02-27T11:21:00-08:00'
  - id: deck_edit_1741813560000
    deck: Q1 2025 Board Operating Read
    slide: 4
    change: 'Slide 4 — Customer growth: Evergreen signal + Compass preview


      Slide language:

      - Evergreen Bank converted from paid Mercury Growth pilot to annual Mercury
      Growth customer on standard terms. This is real customer proof and a stronger
      signal than October.

      - Compass v0.1 preview is active with Evergreen and Acme, but it is not yet
      repeatability proof or behavior-change proof.

      - Evergreen can review its annual-account signals; Acme remains live-only review
      of Acme’s own account-health, reliability, and renewal-risk signals. Do not
      use written Acme materials, screenshots, packet excerpts, or Evergreen-derived
      examples.

      - Spring staffing is not a board-deck next step. RevOps, CS, SDR, field sales,
      and a second Mercury engineering req remain out of this slide until the operating
      read changes the plan.


      Speaker notes:

      - Hold the line: Evergreen annual conversion is real customer proof, not repeatable
      customer-growth proof by itself.

      - Compass v0.1 is legible operating input but has not changed customer or account-team
      behavior yet.

      - Nadia Singh and Sarah Kim’s account-source input is early evidence quality
      work, not a hiring trigger.

      - The operating read should decide whether staffing is revisited; this deck
      should not pre-decide RevOps, CS, SDR, field sales, or Mercury engineering headcount.'
    applied_at: '2025-03-12T14:06:00-07:00'
  - id: deck_edit_1746487920010
    deck: May_2025_Board_Review_Working
    slide: 7
    change: 'Replace Evergreen line with: "Evergreen is useful current-state enterprise
      evidence inside the annual Growth account: shipped SAML rotation, audit lookup,
      workspace-admin support path, and monthly-active-developer usage. Treat it as
      an account-read proof point while Anna/Nadia test repeatability; do not use
      it by itself as customer-growth motion, staffing trigger, or Series C narrative."'
    applied_at: '2025-05-05T16:32:00-07:00'
  - id: deck_edit_1746733440004
    deck: May_2025_board_review_working
    slide: 4
    change: 'Replace the Evergreen section with: ''Evergreen is current-state enterprise
      evidence inside the annual Growth account: shipped Apr 3 SAML rotation, visible
      invite/source/admin audit lookup, workspace-admin support, and monthly-active-developer
      usage are cleanly evidenced in Sarah''s thread. Devon has no separate advanced-admin
      add-on ready to quote; any advanced-admin package remains separately scoped
      only after the work exists. Anna and Nadia are still testing whether this repeats
      beyond Evergreen, so do not frame it as a growth motion, staffing trigger, or
      Series C narrative.'''
    applied_at: '2025-05-08T12:44:00-07:00'
  - id: deck_edit_1747064220011
    deck: May_2025_board_review_working
    slide: 3
    change: 'Evidence gate slide: Compass prompts have produced a few account-team
      follow-ups, but no customer behavior change yet. Account-source quality is strongest
      in the clean Evergreen thread and uneven elsewhere. Enterprise-readiness intake
      remains owner-routed: Sarah for customer-thread continuity, Devon for commercial/procurement
      framing, Nadia for pattern capture, Jake/Leo for product and seam input. Staffing
      decision remains pending the May board-cycle review; do not present Evergreen
      or Compass as a hiring trigger.'
    applied_at: '2025-05-12T08:37:00-07:00'
  - id: deck_edit_1747164720001
    deck: May_2025_Board_Cycle_Evidence
    slide: 4
    change: 'Replace evidence-gate slide with: Decision: keep RevOps, CS, SDR, field-sales,
      customer-growth support, and the second Mercury engineering req closed through
      Q2. Evidence: Compass prompts produced a few account-team follow-ups but no
      customer behavior change; account-source quality is strong in Sarah Kim’s Evergreen
      Bank thread and uneven elsewhere; enterprise-readiness intake remains owner-routed.
      Framing: Evergreen is annual-account and enterprise-readiness evidence, not
      repeatable customer-growth proof or a Series C story. Compass remains an experiment.
      Next: narrow June closeout, not a staffing or fundraising narrative.'
    applied_at: '2025-05-13T12:32:00-07:00'
  - id: deck_edit_1749060180004
    deck: May/June Board Evidence Gate
    slide: '12'
    change: 'Replace Compass framing with: June closeout confirmed a false start.
      Renewal-risk/admin-friction and post-first-live-sync prompts helped internal
      owners prepare, but did not produce repeatable customer action; Evergreen treated
      signals as account appendix context and Acme still required live human follow-up.
      Decision: cut H1 customer-facing Compass plan; keep narrow internal prompt track
      only. No GTM proof, staffing trigger, or Series C narrative.'
    applied_at: '2025-06-04T11:03:00-07:00'
  - id: deck_edit_1750692660010
    deck: Q2_2025_Board_Prep
    slide: 3
    change: 'Revise Evergreen framing: describe Evergreen Bank as a real annual Growth
      account win and current-state enterprise-readiness evidence source. Explicitly
      remove or avoid language that says Evergreen by itself proves repeatable customer
      growth, justifies new customer-growth headcount, or authorizes bespoke roadmap
      commitments. Keep Sarah Kim as customer-thread owner and Devon Hayes as commercial/procurement
      owner.'
    applied_at: '2025-06-23T08:31:00-07:00'
  - id: deck_edit_1750692660011
    deck: Q2_2025_Board_Prep
    slide: 5
    change: 'Revise Compass framing: June closeout cut the customer-facing plan down
      to retained internal action prompts on renewal-risk/admin-friction and post-first-live-sync
      expansion. Anna Martinez owns definitions/caveats/evidence quality; Sarah Kim
      supplies account-thread evidence and handed-off scripts; Jake owns implementation;
      Leo Park owns data/platform seams; Morgan Chen keeps board/customer narrative
      restrained. Compass is not a customer-facing launch, GTM proof, behavior-change
      proof, board dashboard, or hiring trigger.'
    applied_at: '2025-06-23T08:31:00-07:00'
  - id: deck_edit_1750692660012
    deck: Q2_2025_Board_Prep
    slide: 7
    change: 'Revise operating-owner split: Mercury sequencing stays with Jake; platform
      seams and Atlas first technical reads stay with Leo Park; urgent customer-facing
      Atlas issues enter through support rotation with a named support owner and immediate
      next step; Sarah Kim keeps Evergreen/customer-thread continuity; Anna Martinez
      owns evidence quality; Devon Hayes provides commercial/procurement context where
      needed; Morgan Chen owns board/customer narrative. Do not describe this as a
      new hiring plan or Series C setup.'
    applied_at: '2025-06-23T08:31:00-07:00'
  - id: deck_edit_1750879560004
    deck: Q2_2025_Board_Prep
    slide: 8
    change: 'Revise Q3 evidence-test language: Evergreen is a real annual-account
      win and current-state enterprise evidence, but Q3 repeatability requires renewal/expansion
      evidence beyond one clean account thread. Compass remains narrow internal prompt
      learning only if evidence shows dated owner follow-up or behavior change; cleaner
      prompts alone are not enough. Remove any Series C, hiring-trigger, or customer-facing
      Compass implication.'
    applied_at: '2025-06-25T12:26:00-07:00'
  - id: deck_edit_1750951980006
    deck: Q2_2025_Board_Prep
    slide: 12
    change: 'Replace financing-launch language with: Q3 is a quiet rebuild around
      retention, renewal evidence, narrowed Compass learning, and reliable Mercury/Atlas
      execution. Evergreen Bank is a real annual-account proof point, not repeatable
      customer-growth proof by itself. Compass remains cut down to retained internal
      action prompts. Do not frame this slide as a Series C setup, investor-coffee
      loop, hiring trigger, or bespoke-roadmap expansion.'
    applied_at: '2025-06-26T08:33:00-07:00'
  - id: deck_edit_1751053320008
    deck: Q2_2025_Board_Prep
    slide: 2
    change: 'Final closeout summary: choose quiet Q3 rebuild over early Series C chatter.
      Operating story is retention, renewal evidence, narrowed Compass learning, and
      reliable Mercury/Atlas execution. Evergreen is a real annual-account win, not
      repeatable customer-growth proof by itself. Compass remains internal prompt
      learning. Remove fundraising-push, broad investor-coffee, hiring-trigger, and
      bespoke-roadmap implications.'
    applied_at: '2025-06-27T12:42:00-07:00'
  - id: deck_edit_1751489160007
    deck: Q3 operating evidence scratch deck
    slide: 4
    change: 'Add July 2 note: Evergreen asked whether custom admin policy for an additional
      admin group could be folded into the existing annual Growth baseline. Answer:
      no commitment; current-state support remains shipped SAML login, visible invite/source/admin
      audit lookup, workspace-admin support, and basic admin-role setup. Treat as
      enterprise-readiness evidence, not repeatable growth proof, staffing trigger,
      custom roadmap promise, or Devon route during July pause.'
    applied_at: '2025-07-02T13:46:00-07:00'
  - id: deck_edit_1752250320020
    deck: Q3_2025_operating_evidence_grid
    slide: 4
    change: 'Add/update Acme Atlas row: July API v2 large-export recurrence stayed
      in support -> Leo first technical read -> Jake bounded Atlas/API v2 sequencing.
      Scope is cursor-paginated large-export path on long ranges with nested fields;
      narrower replays completed; no customer-visible data loss identified. Queue
      chunking/backoff follow-up. Do not use as Compass proof, Mercury scope, Series
      C narrative, or Devon/founder-direct escalation.'
    applied_at: '2025-07-11T09:12:00-07:00'
  - id: deck_edit_1752689880006
    deck: Q3_operating_evidence
    slide: Compass July evidence
    change: 'Replace any prompt-volume framing with: July first pass reviewed 11 retained
      Compass prompt hits; 4 produced dated owner follow-up and 7 did not meet the
      evidence threshold; none produced customer-initiated action. Track dated owner
      follow-up and outcome only. Note explicitly: Acme export recurrence is Atlas/API
      v2 context and excluded from Compass proof. No customer-facing claim, GTM proof,
      staffing trigger, or Series C language.'
    applied_at: '2025-07-16T11:18:00-07:00'
  - id: deck_edit_1753900680009
    deck: Q3_2025_Operating_Evidence
    slide: Leadership operating model
    change: 'Replace the July-pause wording with: Devon returns in the first full
      August workweek for commercial/procurement context and true cofounder judgment
      calls. Day-to-day operating lanes remain with Jake/Mercury sequencing, Leo/platform
      seams and Atlas first technical reads, Priya/activation quality, Anna/retention
      and Compass evidence quality, Sarah/Evergreen customer-thread continuity, and
      Morgan/board + customer narrative. Do not frame this as a reorg, full snapback,
      or Devon-as-default-second-brain model.'
    applied_at: '2025-07-30T11:38:00-07:00'
  - id: deck_edit_1754667720024
    deck: Q3_2025_operating_evidence
    slide: 6
    change: 'Acme API v2 large-export recurrence: closed Aug 8 as bounded Atlas/API
      v2 chunking/backoff fix. Same 90-day export reran successfully; row counts matched
      monthly replay checks; no customer-visible data loss identified. Evidence is
      reliability/support-routing execution: support customer owner + Leo technical
      read + Jake sequencing. Not Compass proof, Mercury scope, Devon route, or fundraising
      signal.'
    applied_at: '2025-08-08T08:42:00-07:00'
  - id: deck_edit_1755109920007
    deck: Q3_2025_Operating_Evidence
    slide: 6
    change: 'Compass: September target is a narrow internal owner-action prototype,
      not a dashboard or customer-facing analytics surface. Scope is renewal-risk/admin-friction
      and post-first-live-sync prompts, with next action, evidence/caveat drawer,
      and owner-action status. Owners: Jake prototype, Anna evidence threshold, Sarah
      account-thread examples, Leo data seams. Interpretation: test whether owners
      complete better follow-up actions; no customer-facing proof or Series C/staffing
      implication.'
    applied_at: '2025-08-13T11:32:00-07:00'
  - id: deck_edit_1755273360017
    deck: Q3_2025_Operating_Evidence
    slide: 5
    change: 'Mercury activation quality: Priya completed a copy-only setup-guide fix
      clarifying that invited source owners can connect the first source from the
      current step. Jake confirmed product state is correct; Leo confirmed no platform
      mismatch. Interpretation: concrete activation-quality improvement without admin-model
      change, custom admin policy, granular role editor, or Atlas scope.'
    applied_at: '2025-08-15T08:56:00-07:00'
  - id: deck_edit_1755791640019
    deck: Q3 Operating Evidence
    slide: 4
    change: 'Evergreen Aug 21 update: second internal department may test current
      Mercury flow under the existing annual Growth account. Interpret as repeatability
      signal inside one annual customer, not commercial expansion or advanced-admin
      proof. Test commitments are workspace setup, teammate invite/source-owner path,
      first source connection, and first live sync only. Exclude custom admin-policy
      date, granular role editor, broader advanced-admin controls, procurement/security
      add-on, SSO change, and Devon product/customer-thread ownership.'
    applied_at: '2025-08-21T08:54:00-07:00'
  - id: deck_edit_1757096580011
    deck: Q3 Operating Evidence — Sep 2025
    slide: Compass evidence
    change: 'Update Compass section: September owner-action prototype surfaced 8 account-owner
      actions: 5 completed by named owners, 2 rejected_thin_source_or_date because
      account notes lacked usable source/date, 1 blocked_waiting_customer_follow_up.
      Interpretation: first evidence the narrow workflow changed Scaffold owner behavior,
      not customer behavior. October candidate remains internal owner-action workflow
      only; no customer-facing proof, GTM proof, staffing trigger, or fundraising
      claim.'
    applied_at: '2025-09-05T11:23:00-07:00'
  - id: deck_edit_1758296880009
    deck: Q3_Operating_Review_Sep24
    slide: '3'
    change: 'Evergreen evidence update: second internal department completed current
      Mercury shipped flow under existing annual Growth account — workspace setup,
      teammate/source-owner path, first source connection, first live sync. No SSO
      changes or custom admin policy. Granular role editor logged as advanced-admin
      follow-up only. Operating read: stronger enterprise-readiness evidence inside
      one annual customer, still account-specific and not a new advanced-admin commitment.'
    applied_at: '2025-09-19T08:48:00-07:00'
  - id: deck_edit_1758645060001
    deck: Q3_Operating_Review_Sep24
    slide: 1
    change: 'Decision frame: evidence review only, not a fundraising kickoff. Read
      Evergreen repeatability, Compass owner-action evidence, Atlas/Mercury execution,
      and what evidence would ever justify Series C market-warming.'
    applied_at: '2025-09-23T09:31:00-07:00'
  - id: deck_edit_1758645060002
    deck: Q3_Operating_Review_Sep24
    slide: 2
    change: 'Evergreen: treasury ops completed current Mercury flow inside the existing
      annual Growth account — workspace, teammate/source-owner path, first source,
      first live sync. Stronger enterprise-readiness evidence than May because a second
      internal department completed current flow, but still account-specific. No SSO
      change, custom admin policy, procurement/security add-on, or granular-role commitment.'
    applied_at: '2025-09-23T09:31:00-07:00'
  - id: deck_edit_1758645060003
    deck: Q3_Operating_Review_Sep24
    slide: 3
    change: 'Compass: Sep 5 prototype surfaced eight owner actions — five completed,
      two rejected-thin, one waiting on live customer follow-up. Evidence is internal
      owner behavior and caveat handling, not customer-facing behavior proof. Candidate
      October path only if it stays renewal-risk/admin-friction and post-first-live-sync
      prompts for internal account owners.'
    applied_at: '2025-09-23T09:31:00-07:00'
  - id: deck_edit_1758645060004
    deck: Q3_Operating_Review_Sep24
    slide: 4
    change: 'Atlas/Mercury execution: Acme large-export recurrence remains closed
      as bounded Atlas/API v2 chunking/backoff work. Support customer owner + Leo
      first technical read + Jake sequencing held. Mercury activation/source-owner
      copy is steadier; do not reopen admin-role model or make Atlas scope.'
    applied_at: '2025-09-23T09:31:00-07:00'
  - id: deck_edit_1758645060005
    deck: Q3_Operating_Review_Sep24
    slide: 5
    change: 'Threshold: Series C market-warming only if Q4 evidence survives beyond
      Evergreen and the internal Compass workflow. Operating story stays retention/renewal
      learning and reliable Mercury/Atlas execution.'
    applied_at: '2025-09-23T09:31:00-07:00'
  - id: deck_edit_1758738960008
    deck: Q3_Operating_Review_Sep24
    slide: 6
    change: 'Working conclusion after Sep 24 review: narrow October Compass path only
      for internal account-owner work — renewal-risk/admin-friction owner actions,
      post-first-live-sync expansion prompts, and admin-workflow evidence. Evergreen
      repeatability is real inside one annual account, not a broad market pattern.
      Acme is closed as bounded Atlas/API v2 work. Series C market-warming remains
      on hold unless Q4 evidence survives beyond Evergreen and internal Compass workflow.
      Sofia written confirmation pending before final board-side line.'
    applied_at: '2025-09-24T11:36:00-07:00'
  - id: deck_edit_1758901920013
    deck: Q3_Operating_Review_Sep24
    slide: 6
    change: 'Final Q3 operating-review conclusion: Evergreen shows current-flow repeatability
      inside one annual customer, not broad market repeatability. Acme is closed and
      no longer a live Atlas emergency. October Compass path is narrow internal account-owner
      work — renewal-risk/admin-friction owner actions, post-first-live-sync expansion
      prompts, and admin-workflow evidence only. Compass has no customer-facing behavior
      proof. Series C market-warming remains on hold until Q4 evidence survives beyond
      Evergreen and the internal Compass workflow. Operating story: retention/renewal
      learning and reliable Mercury/Atlas execution, not a fundraising push.'
    applied_at: '2025-09-26T08:52:00-07:00'
  - id: deck_edit_1759252680005
    deck: Q3_2025_Operating_Evidence
    slide: Leadership operating model
    change: 'Final Q4 operating model: July-pause coverage becomes durable post-pause
      operating model, not temporary leave coverage. Devon handles commercial/procurement
      context and selective cofounder judgment calls. Morgan keeps board/customer
      narrative. Jake owns Mercury operating work; Leo owns Atlas/platform seams and
      Atlas first technical reads; Priya owns activation/onboarding quality; Anna
      owns retention/evidence quality/Compass; Sarah owns Evergreen continuity. Loose
      owner questions route to named owners first, not Devon by default. Do not frame
      as a reorg or a return to the pre-July founder pattern.'
    applied_at: '2025-09-30T10:18:00-07:00'
  - id: deck_edit_1759432920001
    deck: Q4_2025_Operating_Evidence
    slide: Compass internal owner queue
    change: 'Add Oct 2 update: Compass is live as an internal Q4 account-owner queue,
      not a customer-facing product. Default owner queue shows proposed, accepted,
      completed, and blocked_waiting_customer_follow_up rows. rejected_thin_source_or_date
      rows stay out of the default owner action queue but remain visible to Anna Martinez
      for evidence/caveat audit. source_freshness_warning renders as caveat text,
      not automatic rejection. Scope remains renewal-risk/admin-friction owner actions
      and post-first-live-sync expansion prompts only. No GTM proof, staffing trigger,
      customer analytics surface, or fundraising language.'
    applied_at: '2025-10-02T12:22:00-07:00'
  - id: deck_edit_1764867120003
    deck: Q4_2025_Operating_Evidence
    slide: Compass November behavior read
    change: 42 owner actions surfaced; 30 completed with evidence and caveats; 7 rejected
      as too thin; 5 blocked on customer follow-up; 9 completed owner actions had
      dated account-team outcomes; named examples are Evergreen standard-overage/customer-thread
      prep, Evergreen source-side allowlist follow-up, and Acme renewal-risk documentation
      clarification; Jake confirmed prompt-level only; Leo found no data/platform
      reason to broaden exposure; conclusion is internal operating workflow evidence,
      not customer-facing analytics or GTM proof.
    applied_at: '2025-12-04T08:52:00-08:00'
  - id: deck_edit_1765569120004
    deck: Q4_2025_Operating_Evidence
    slide: Q4 operating review outcome
    change: steady retention and expansion through owner lanes; Evergreen is strong
      but still one annual customer with standard overage; Compass remains internal
      account-owner workflow for renewal-risk/admin-friction, post-first-live-sync
      expansion prompts, and internal admin-workflow evidence; Acme is stable in normal
      Atlas/API v2 support; no Q1 Series C market-warming; no Head of Customer Growth
      backfill or second Mercury engineering req reopened from this review.
    applied_at: '2025-12-12T11:52:00-08:00'
  - id: deck_edit_1768263840004
    deck: January_2026_Board_CEO_Pulse
    slide: 3
    change: 'CEO pulse metrics — January working packet


      - Q4 closeout: steady owner-lane progress.

      - Evergreen: standard Growth/current-state admin; renewal signature still pending.

      - Acme: normal API v2 support.

      - Atlas: webhook retry concurrency and jitter guardrail live; normal support
      routing.

      - Compass: internal owner-workflow evidence only.

      - Mercury: OAuth-cancel fix still in QA and not shipped.

      - No Series C market-warming, Head of Customer Growth reopen, or second Mercury
      engineering req reopen.'
    applied_at: '2026-01-12T16:24:00-08:00'
  - id: deck_edit_1768435500007
    deck: January_2026_Board_CEO_Pulse
    slide: 3
    change: 'CEO pulse metrics — January working packet


      - Mercury: scoped OAuth-cancel activation-quality fix shipped Jan 14; successful
      OAuth path unchanged; no admin/granular-role scope.

      - Atlas: closed out through Leo/support.

      - Evergreen: standard Growth/current-state admin; renewal signature pending.

      - Compass: internal evidence only.

      - No Series C market-warming, Head of Customer Growth reopen, or second Mercury
      engineering req reopen.'
    applied_at: '2026-01-14T16:05:00-08:00'
  - id: deck_edit_1769014200003
    deck: January_2026_Board_CEO_Pulse
    slide: 3
    change: 'Replace slide 3 with:


      CEO pulse metrics — January working packet


      - Evergreen: counter sent; standard Growth usage terms remain in place. Quarterly
      current-state/admin review is allowed. Granular sync-operator work remains later
      research with no date, package, renewal obligation, or overage concession. Renewal
      signature is still pending.

      - Atlas: webhook retry concurrency and jitter guardrail is live through Leo/support;
      single-workspace endpoint failures remain normal support routing.

      - Mercury: scoped OAuth-cancel activation-quality fix shipped Jan 14; successful
      OAuth path unchanged; no admin/granular-role scope.

      - Compass: internal evidence only.

      - No Series C market-warming, Head of Customer Growth reopen, or second Mercury
      engineering req reopen.'
    applied_at: '2026-01-21T08:50:00-08:00'
  - id: deck_edit_1769195160000
    deck: January_2026_Board_CEO_Pulse
    slide: 3
    change: 'Replace slide 3 with:


      CEO pulse metrics — January working packet


      - Evergreen: renewal clause narrowed to standard Growth/current-state admin;
      renewal signature still pending.

      - Mercury: OAuth-cancel activation-quality fix shipped; successful OAuth/admin
      scope unchanged.

      - Atlas: webhook retry concurrency and jitter guardrail live through Leo/support.

      - Compass: internal evidence only.

      - Acme: normal support.

      - No Series C market-warming or financing process, and no closed hiring loops
      reopened.'
    applied_at: '2026-01-23T11:06:00-08:00'
  - id: deck_edit_1769618520003
    deck: January_2026_Board_CEO_Pulse
    slide: 3
    change: 'Replace slide 3 with:


      CEO pulse metrics — January working packet


      - Evergreen: signed annual Mercury Growth renewal for Feb 1, 2026 through Jan
      31, 2027 on standard terms; quarterly current-state/admin reviews only; no granular
      sync-operator commitment, custom admin package, overage cap, or department carveout.

      - Mercury: OAuth-cancel activation-quality fix shipped; successful OAuth/admin
      scope unchanged.

      - Atlas: webhook retry concurrency and jitter guardrail live through Leo/support.

      - Compass: internal evidence only.

      - Acme: normal support.

      - No Series C market-warming or financing process, and no closed hiring loops
      reopened.'
    applied_at: '2026-01-28T08:42:00-08:00'
  - id: deck_edit_1769707560000
    deck: January_2026_Board_CEO_Pulse
    slide: 3
    change: 'Replace slide 3 with:


      CEO pulse metrics — January working packet


      - Evergreen: signed annual Mercury Growth renewal for Feb 1, 2026 through Jan
      31, 2027 on standard terms; quarterly current-state/admin reviews only; no granular
      sync-operator commitment, custom admin package, overage cap, or department carveout.

      - Mercury: OAuth-cancel activation-quality fix is validated by the first mature
      read; abandoned setup sessions tied to OAuth cancellation fell from 41 to 14
      and support tickets fell from 12 to 2. Treat this as activation-quality evidence,
      not a conversion-lift or enterprise-readiness claim. Next focus is empty source-list
      explanation. Invite-link status and granular admin roles remain out of the January/early-February
      commitment.

      - Atlas: webhook retry concurrency and jitter guardrail live through Leo/support.

      - Compass: internal evidence only.

      - Acme: normal support.

      - No Series C market-warming or financing process, and no closed hiring loops
      reopened.'
    applied_at: '2026-01-29T09:26:00-08:00'
  - id: deck_edit_1770405480000
    deck: Q1_2026_Board_File_Working
    slide: 2
    change: 'Title: January closeout: retention and margin discipline


      - Evergreen closed January at 241 monthly active developers on standard Growth
      overage handling with no custom admin package or cap.

      - Mercury activation-quality improved through the validated OAuth-cancel work
      and empty source-list polish without new headcount or custom scope.

      - Atlas guardrail/support posture is contained and Acme stayed normal API v2
      support.

      - AWS is below the December support-spike run rate and Pinecone remains monthly
      usage.

      - Message: standard-term retention plus owner-lane durability, not growth-at-any-cost
      or a Series C preface.'
    applied_at: '2026-02-06T11:18:00-08:00'
  - id: deck_edit_1771364100002
    deck: Q1_2026_Board_File_Working
    slide: Compass evidence
    change: 'Replace any language or speaker note that says ''five non-core completed
      rows broaden Compass repeatability.''


      New slide language:

      - Queue: 36 surfaced actions; 21 completed with evidence and caveats.

      - 5 completed actions are outside Evergreen and Acme, but only 2 of those have
      dated account-team outcomes and none are approved to be named.

      - Conclusion: Compass remains an internal account-owner workflow. Broader board
      or customer claims require at least 2 nameable non-Evergreen/non-Acme accounts
      with completed owner actions and dated outcomes.


      Speaker note / boundary:

      - Anonymous or non-nameable rows may remain in the internal evidence tracker,
      but they cannot support repeatability, fundraising, customer-facing product,
      or staffing claims.'
    applied_at: '2026-02-17T13:35:00-08:00'
  - id: deck_edit_1771523880000
    deck: Q1_2026_Board_File_Working
    slide: Compass evidence
    change: 'Replace the overclaim with this stricter wording:

      - Queue: 36 surfaced actions; 21 completed with evidence/caveats.

      - 5 completed actions are outside Evergreen and Acme, but only 2 of those have
      dated account-team outcomes and none are approved to be named.

      - Conclusion: Compass remains an internal account-owner workflow. Broader board
      or customer claims require at least 2 nameable non-Evergreen/non-Acme accounts
      with completed owner actions and dated outcomes.'
    applied_at: '2026-02-19T09:58:00-08:00'
  - id: deck_edit_1773245520002
    deck: Q1_2026_Board_File_Working
    slide: Acme support posture
    change: 'Acme Q1 2026 support posture: six routine API v2 export/docs questions
      in Q1; zero large-export timeout recurrences; no data-loss findings; no renewed
      request for customer-facing Compass material; no new Atlas product-priority
      item. All items stayed in the normal support route, with Sarah Kim and Leo Park
      owning the account and technical reads. Use as Atlas/API v2 owner-lane durability
      evidence only, not Compass proof, Mercury scope, founder-direct routing, or
      a new product-priority claim.'
    applied_at: '2026-03-11T09:12:00-07:00'
  - id: deck_edit_1773353100000
    deck: Q1_2026_Board_File_Working
    slide: 1
    change: 'Title: Q1 durability review: operating evidence, not market-warming


      - Evergreen: standard Growth usage mechanics only; no custom admin/procurement
      scope.

      - Acme: normal API v2 support route and owner-lane evidence only; no Compass
      proof or product-priority claim.

      - Mercury: activation-quality and support-discovery signals; no broadened scope
      or headcount ask.

      - Compass: internal rows stay gated unless two nameable non-Evergreen/non-Acme
      outcomes exist.

      - Margin: AWS/Pinecone posture is discipline and hygiene, not financing theater.

      - H1 Series C market-warming remains a question for the review, not a packet
      launch.'
    applied_at: '2026-03-12T15:05:00-07:00'
  - id: deck_edit_1773875100005
    deck: Q1_2026_Board_File_Working
    slide: Margin discipline
    change: 'Title: Margin discipline


      - AWS finished February at $18.6k versus the December support-spike run rate
      of $26.9k.

      - Pinecone finished February at $4.3k, including the $420 one-off support-ticket
      backfill, and remains monthly usage.

      - No prepaid minimum or contract change.

      - Read this as contained operating discipline and monthly hygiene, not a vendor-negotiation
      win or a Series C efficiency story.'
    applied_at: '2026-03-18T16:05:00-07:00'
  - id: deck_edit_1773940680001
    deck: Q1_2026_Board_File_Working
    slide: Margin discipline
    change: 'Title: Contained run-rate discipline and monthly vendor hygiene


      Footnote:

      AWS finished February at $18.6k versus the December support-spike run-rate of
      $26.9k. Pinecone finished at $4.3k including the $420 one-off support-ticket
      backfill. Read this as contained operating discipline and monthly hygiene, not
      fundraising efficiency, vendor-negotiation leverage, prepaid-capacity discussion,
      or Series C setup.'
    applied_at: '2026-03-19T10:18:00-07:00'
  - id: deck_edit_1774369080002
    deck: Q1_2026_Board_File_Working
    slide: 1
    change: 'Title: Q1 durability review: operating evidence, not market-warming


      - Evergreen: standard Growth usage mechanics only; no custom admin/procurement
      scope.

      - Acme: normal API v2 support route and owner-lane evidence only; no Compass
      proof or product-priority claim.

      - Mercury: activation-quality and support-discovery signals; no broadened scope
      or headcount ask.

      - Compass: internal rows do not support repeatability unless at least two nameable
      non-Evergreen/non-Acme accounts have completed owner actions and dated outcomes.

      - Margin: AWS/Pinecone posture is discipline and hygiene, not financing theater.

      - Question for the review: is the current operating evidence durable enough
      to keep H1 Series C market-warming off?'
    applied_at: '2026-03-24T09:18:00-07:00'
  - id: deck_edit_1774538280000
    deck: Q1_2026_Board_File_Working
    slide: Compass evidence
    change: 'Replace the stale appendix language that says two additional non-Evergreen/non-Acme
      rows are pending naming. New wording: Additional internal owner-action rows
      outside Evergreen and Acme may be tracked in the internal evidence appendix,
      but there is no naming permission before the March 27 review and no dated account-team
      outcome that clears the repeatability gate. Compass therefore remains internal-only.
      Broader board or customer claims still require at least two nameable non-Evergreen/non-Acme
      accounts with completed owner actions and dated outcomes. Explicit non-goals:
      these internal rows do not support repeatability, customer-facing claims, staffing,
      or H1 market-warming.'
    applied_at: '2026-03-26T08:18:00-07:00'
  - id: deck_edit_1774562520001
    deck: Q1_2026_Board_File_Working
    slide: Margin discipline
    change: 'Title: Contained run-rate discipline and monthly vendor hygiene


      Speaker note: AWS finished February at $18.6k versus the December support-spike
      run rate of $26.9k. Pinecone finished at $4.3k including the $420 one-off support-ticket
      backfill. No prepaid minimum or contract change. Read this as contained operating
      discipline and monthly vendor hygiene, not H1 financing optionality, vendor
      negotiation, prepaid capacity, or Series C efficiency leverage.'
    applied_at: '2026-03-26T15:02:00-07:00'
  - id: deck_edit_1778598720002
    deck: May_2026_Board_Operating_Working
    slide: 5
    change: 'Title: April close: standard mechanics and hygiene, not a new motion


      - Evergreen April usage locked at 214 MAD: one standard $1,000 Growth overage;
      March 199 does not offset April and does not create a cap, carveout, or rolling
      credit.

      - AWS held around $18.7k and Pinecone around $4.3k; Pinecone remains monthly
      through Q2.

      - Readout: retention/account health plus margin hygiene, not Compass proof,
      custom admin scope, staffing change, or H1 market-warming.'
    applied_at: '2026-05-12T08:12:00-07:00'
  - id: deck_edit_1778859120001
    deck: May_2026_Board_Operating_Working
    slide: 6
    change: 'Title: Mercury source-type questions: docs/support scope


      - Generic source-support questions stayed lower after the source-type docs link,
      but the latest seven tickets are source-specific caveats: Salesforce sandbox
      and NetSuite variants.

      - Decision: keep the brand-new-workspace empty state as a narrow docs-discovery
      surface; do not turn it into a connector promise list.

      - Action: put source-specific caveats in supported-source-types docs and the
      support macro. This is support deflection and setup clarity, not activation-lift
      proof or a reason to widen Mercury scope.'
    applied_at: '2026-05-15T08:32:00-07:00'
  - id: deck_edit_1779401040001
    deck: May_2026_Board_Operating_Working
    slide: 7
    change: 'Compass owner-action read: internal usefulness, not product proof


      - Useful internal cases: Evergreen admin-review prompt helped standard usage/admin
      follow-up before April invoice questions escalated; Acme API/JWT prompt routed
      support to updated clock-skew docs for Acme''s audit file.

      - Eight other owner actions completed internally, but none are nameable non-Evergreen/non-Acme
      proof with permission and dated account-team outcomes.

      - Readout: Q2 evidence grid tracks owner outcomes only; no claim for broader
      repeatability, customer-facing product, GTM/fundraising, staffing, or Atlas
      platform exposure.'
    applied_at: '2026-05-21T15:04:00-07:00'
  - id: deck_edit_1781105160000
    deck: May_2026_Board_Operating_Working
    slide: 6
    change: 'Slide 6 — Final May close: operating discipline, not a new motion


      - Evergreen Bank finished May at 221 monthly active developers, representing
      one standard Growth overage band under the existing terms.

      - AWS closed at about $18.8k after the final allocation cleanup.

      - Pinecone closed at about $4.2k.

      - There is no contract change, prepaid capacity, vendor-risk issue, or custom
      commercial exception after declining Pinecone''s annual/prepaid offer.

      - Conclusion: March-May evidence supports standard Growth usage and monthly
      vendor hygiene. Do not frame this as financing efficiency or an expansion/custom-scope
      story.'
    applied_at: '2026-06-10T08:26:00-07:00'
  - id: deck_edit_1782240120002
    deck: Q2_Durability_Read_Working
    slide: 1
    change: 'Title: Q2 durability read — evidence boundaries


      What we can assess

      - Q2 operating evidence before H1 closes

      - July market-warming posture as a question, not a conclusion

      - Whether any staffing revisit is actually justified


      What we are not deciding

      - Not a data-room refresh

      - Not an investor packet

      - Not a customer-facing Compass decision

      - Not a default hiring-reopen meeting


      Owner inputs

      - Devon: final May close and current June hygiene language

      - Sarah: Evergreen standard account language and account-language risks

      - Jake: Mercury setup/support-quality evidence without activation overclaiming

      - Leo: Atlas owner-lane support evidence

      - Sofia and Anna: keep the July posture question framed as a question, not a
      decision'
    applied_at: '2026-06-23T11:42:00-07:00'
  - id: deck_edit_1782834720005
    deck: Q2_Durability_Read_Working
    slide: 2
    change: 'Title: Q2 read outcome — Q3 posture


      Evidence read

      - Q2 evidence supports durability and evidence discipline.


      Q3 operating posture

      - Retention

      - Margin discipline

      - Standard-term customer work

      - Mercury/Atlas owner lanes

      - Internal Compass evidence quality


      What is not changing

      - No July market-warming process

      - No data-room refresh

      - No Head of Customer Growth backfill

      - No second Mercury engineering req

      - No customer-facing Compass claim


      Director action

      - No director action required.'
    applied_at: '2026-06-30T08:52:00-07:00'
  - id: deck_edit_1783351980002
    deck: Q2 working board deck
    slide: June final close — standard Growth/vendor hygiene
    change: 'Title: June final close — standard Growth/vendor hygiene


      - Evergreen Bank finished June at 219 monthly active developers, representing
      one standard Growth overage band under the existing terms.

      - AWS closed at about $19.2k after allocation cleanup.

      - Pinecone closed at about $4.0k with no replay spike.

      - No contract change, prepaid capacity, vendor-risk issue, or custom commercial
      exception.

      - Interpretation: standard Growth usage and monthly vendor hygiene only; do
      not frame this as financing efficiency, expansion ARR reclassification, or a
      staffing trigger.'
    applied_at: '2026-07-06T08:33:00-07:00'
  - id: deck_edit_1785512160002
    deck: Q3_2026_Operating_Evidence_Working
    slide: July bounded operating evidence
    change: '- Mercury: supported-source docs/support macros are the stable source-caveat
      home; empty state remains generic docs discovery, not activation or enterprise-readiness
      proof.

      - Evergreen: Q3 current-state/admin review closed inside included scope; granular
      sync-operator interest remains logged advanced-admin input only, not expansion
      or Compass repeatability.

      - Atlas: support-contract examples are internal owner-lane clarity; do not use
      as roadmap, reliability-roadmap, or customer-facing product proof.'
    applied_at: '2026-07-31T08:36:00-07:00'
  - id: deck_edit_1786030380000
    deck: Q3_2026_Operating_Evidence_Working
    slide: July bounded operating evidence
    change: '- Evergreen Bank finished at 228 monthly active developers, still one
      standard Growth overage band.

      - AWS closed at about $19.5k.

      - Pinecone closed at about $4.1k with no replay spike.

      - No contract change, prepaid-capacity need, vendor-risk issue, or custom commercial
      exception.

      - July supports standard usage and monthly vendor hygiene, not market-warming,
      an expansion package, or headcount reopening.'
    applied_at: '2026-08-06T08:33:00-07:00'
  - id: deck_edit_1786735200000
    deck: Q3_2026_Operating_Evidence_Working
    slide: First owner-lane read — Aug 14
    change: 'Aug 14 first owner-lane read

      - Mercury: source-specific tickets fell from 7 in the two weeks before the supported-source
      docs/support macro update to 3 in the two weeks after; first-sync completion
      did not materially change.

      - Atlas/API v2: new examples handled repeat webhook, cursor, and JWT questions
      without new defect evidence.

      - Compass: owner-action evidence remains useful only around Evergreen Bank and
      Acme.

      - Conclusion: Q3 stays narrow. This is support-quality and internal evidence-quality
      improvement, not activation-lift proof, customer-facing Compass proof, or a
      hidden Atlas reliability-roadmap claim.'
    applied_at: '2026-08-14T12:20:00-07:00'
  discord_dm_log:
  - id: discord_dm_1784911046993
    message: Posted the tighter Friday-wrap version. The connective tissue is useful,
      but the board-style narrative belongs in a separate launch/board context, not
      in the Friday wrap.
    sent_at: '2023-05-05T09:27:00-07:00'
    user: Devon Hayes
  - id: discord_dm_1785100222384
    message: Devon — no board-note patch from this corrected weekly cut. Use it for
      internal operating decisions, and keep board-facing retention/activation on
      the appropriate cohort view until we have a cleaner external-ready cut.
    sent_at: '2023-05-24T13:49:00-07:00'
    user: Devon Hayes
  - id: discord_dm_1785100223802
    message: Priya — can you find a 30-minute slot with Jake next week for Mercury
      rollout blockers and the corrected activation definition? Please coordinate
      the slot; I’m not pinging Jake directly yet.
    sent_at: '2023-05-25T11:12:00-07:00'
    user: Priya
  - id: discord_dm_1785101686057
    message: Priya — the design review invite looks like it’s missing the review link
      and presenter context. Can you send the Figma link and a one-sentence read on
      who’s presenting what before the review?
    sent_at: '2023-05-30T08:44:00-07:00'
    user: Priya
  - id: discord_dm_1785101686515
    message: Absolutely — no speech and no special public moment. Just keep doing
      normal Mercury work, and be explicit when the activation/onboarding call is
      yours.
    sent_at: '2023-05-31T09:28:00-07:00'
    user: Priya
  - id: discord_dm_1785101687937
    message: Jake — for Mercury launch work, Priya is the formal owner of Mercury
      activation/onboarding UX through the Q3 launch. Please treat those activation/onboarding
      UX calls as hers in the normal Mercury workstream.
    sent_at: '2023-05-31T10:18:00-07:00'
    user: Jake
  - id: discord_dm_1785104286692
    message: 'Priya — confirming the Mercury activation/onboarding QA path from the
      weekly: empty states, source-connect prompts, and first-live-sync copy. Normal
      workstream tone; just keep any blockers in the weekly thread.'
    sent_at: '2023-06-05T09:39:00-07:00'
    user: Priya
  - id: discord_dm_1785104287635
    message: Priya — before I accept the Mercury activation review, can you send the
      Figma link and a short context note on what we’re deciding / who is walking
      through what?
    sent_at: '2023-06-06T08:53:00-07:00'
    user: Priya
  - id: discord_dm_1785104288103
    message: 'Until the deploy is green, keep the draft notes in #eng-releases. Not
      #eng-all pre-green.'
    sent_at: '2023-06-06T11:06:00-07:00'
    user: Marcus
  - id: discord_dm_1785104289563
    message: Priya — can you route the usual calendar path for a 30-minute Thursday
      morning slot with Jake and Rishi for the Mercury auth readout, if there’s an
      opening?
    sent_at: '2023-06-07T10:18:00-07:00'
    user: Priya
  - id: discord_dm_1785105382650
    message: Priya — activation/onboarding design calls are yours. Keep the decision
      path clean in Figma; if implementation risk requires a change, we’ll link it
      back to the exact frame instead of relitigating in side threads.
    sent_at: '2023-06-13T14:27:00-07:00'
    user: Priya
  - id: discord_dm_1785105383119
    message: Marcus — release-readiness and dogfood gating are your checklist lane.
      Those concerns can block ship, but they should live in the implementation checklist/release
      review rather than being litigated in Figma comments.
    sent_at: '2023-06-13T14:27:00-07:00'
    user: Marcus
  - id: discord_dm_1785122055370
    message: Jake — Acme can keep informing customer/blocker context, but while the
      NDA scope is muddy they should not get fresh Mercury materials and should not
      be in the first design-partner wave.
    sent_at: '2023-06-16T08:36:00-07:00'
    user: Jake
  - id: discord_dm_1785122056317
    message: Rishi — Pinecone’s headers matched the agreed contract. The code-side
      thing to inspect is the signing/timestamp path around `signed_at` versus send/receive
      time; the failure looks like timestamp skew.
    sent_at: '2023-06-16T09:39:00-07:00'
    user: Rishi
  - id: discord_dm_1785122059111
    message: Rishi — staging work is fine, but Friday-after-3 production is blocked
      unless the full on-call roster is online and I explicitly approve it. `rp/mercury-org-invite-edges`
      should stay out of production scope for now.
    sent_at: '2023-06-21T16:27:00-07:00'
    user: Rishi
  - id: discord_dm_1785122060553
    message: 'Priya — can you route a late-July checkpoint for me, Jake, and Devon
      through the usual calendar path? Purpose: revisit Mercury engineering headcount
      after July launch-readiness feedback.'
    sent_at: '2023-06-22T09:54:00-07:00'
    user: Priya
  - id: discord_dm_1785127163550
    message: Sarah — I saved `Leo Park — Mercury onboarding brief`. It’s ready for
      HR onboarding logistics.
    sent_at: '2023-06-23T08:58:00-07:00'
    user: Sarah Kim
  - id: discord_dm_1785127164010
    message: Rishi — keep `rp/mercury-org-invite-edges` out of production before the
      weekend. Please keep the staging evidence together for Monday, but I’m not approving
      a Friday production exception.
    sent_at: '2023-06-23T16:28:00-07:00'
    user: Rishi
  - id: discord_dm_1785127682341
    message: 'Rishi — Pinecone’s rerun isolated the casing issue: preserved `X-Scaffold-Signature`
      passed, but lowercased `x-scaffold-signature` failed with signature mismatch/reject
      on the same body and workspace. Can you look at the verifier side?'
    sent_at: '2023-06-30T10:18:00-07:00'
    user: Rishi
  - id: discord_dm_1785173820591
    message: 'Please keep the Pinecone issue framed as verifier/debugging work, not
      a contract change. The boundary stays header-only: `X-Scaffold-Workspace` plus
      `X-Scaffold-Signature`, with no query-parameter fallback while they trace the
      casing mismatch.'
    sent_at: '2023-07-03T08:32:00-07:00'
    user: Rishi
  - id: discord_dm_1785173823008
    message: No Friday production exception for polish. Keep the failed-state icon
      cleanup on the normal follow-up path, and don’t reopen the dogfood gate.
    sent_at: '2023-07-07T15:49:00-07:00'
    user: Marcus
  - id: discord_dm_1785177269341
    message: Useful internally, but too early externally. Leo gives us more Mercury
      launch-readiness leverage; he is not a fundraising proof point. The activation
      dogfood gate is still internal pressure-testing, and the round stays deferred
      until Q3 Mercury data is credible.
    sent_at: '2023-07-10T14:26:00-07:00'
    user: Devon Hayes
  - id: discord_dm_1785177270812
    message: Leo asked for 30 minutes with Jake before Friday, Jul 14, to sanity-check
      the Mercury platform-seam parts of his release-risk readout — mostly org-invite
      / role-state edges and where they touch activation branches. Since you run Jake’s
      calendar, can you route that instead of me pinging Jake directly?
    sent_at: '2023-07-12T09:34:00-07:00'
    user: Priya
  - id: discord_dm_1785178393812
    message: Query-param fallback is off the table; we’re keeping Pinecone on the
      header-only contract.
    sent_at: '2023-07-17T11:29:00-07:00'
    user: Rishi
  - id: discord_dm_1785178395769
    message: 'Concrete asks for Friday’s Mercury readout:

      - Keep it tied to launch-readiness verification, not a broader platform memo.

      - Treat `source unavailable` as improved in the current build.

      - Do not cite `unknown / retry` as closed without a screenshot set.

      - Call out that queued-sync retry still has only one end-to-end dogfood run.

      - Separate verified closure from thin evidence.'
    sent_at: '2023-07-19T13:48:00-07:00'
    user: Leo Park
  - id: discord_dm_1785179884575
    message: Useful progress, but let's keep Leo's readout and MER-1279 as launch-readiness
      operating evidence for now. I don't want it used as a board/investor proof claim
      or a B-round reopening point yet — still internal.
    sent_at: '2023-07-24T11:16:00-07:00'
    user: Devon Hayes
  - id: discord_dm_1785189093860
    message: I’ve sent `rp/mercury-org-invite-edges` through the standard Mercury
      staging path only. Treat this as staging validation only — not production approval
      and not a Clerk/Auth0/provider decision.
    sent_at: '2023-08-02T14:20:00-07:00'
    user: Rishi
  - id: discord_dm_1785189094336
    message: 'Can you find a separate 30-minute prep slot on Jake’s calendar with
      me and Devon Hayes before next week’s Mercury weekly? Scope: first-wave boundaries
      — Evergreen Bank as the admin/security stress case without bespoke work, Acme
      staying out while the NDA scope is muddy, and what Acme’s prior feedback can
      inform internally. No external materials off this.'
    sent_at: '2023-08-03T09:28:00-07:00'
    user: Priya
  - id: discord_dm_1785189094813
    message: Yes — please place the Tava Kitchen meal hold for 14. HR still owns the
      budget path. The listed vegetarian / gluten-free needs don’t require switching
      vendors since Tava can label the gluten-free trays separately and keep the vegetarian
      options distinct.
    sent_at: '2023-08-04T10:35:00-07:00'
    user: Sarah Kim
  - id: discord_dm_1785192080739
    message: 'Use the corrected activation definition for launch-week operating reads:
      activated = real_source_connected or first_live_sync_completed within 7 days;
      sample_import_completed stays out. I’d keep this weekly cut directional/internal
      only for now, and not turn the early numbers into board or external chart material.'
    sent_at: '2023-08-08T08:51:00-07:00'
    user: Anna Martinez
  - id: discord_dm_1785271735730
    message: Non-urgent, but can you check the non-prod NAT gateway egress spike in
      us-west-2 from the AWS Budgets alert? Forecasted August spend is up to $18.7k
      vs. the $15k budget, with about $1.9k week-over-week from non-prod NAT gateway
      egress. Please confirm there isn’t a production incident behind it and report
      back by EOD before anyone makes a spend or architecture decision.
    sent_at: '2023-08-21T08:44:00-07:00'
    user: Marcus
  - id: discord_dm_1785274728052
    message: 'Good with deleting the non-prod runner now and adding the narrow non-prod
      egress guardrail alert. Let’s treat this as non-prod only: production wasn’t
      involved, prod traffic and alarms looked normal, and we’re not turning this
      into architecture or spend-plan work unless the next cost report still shows
      leakage.'
    sent_at: '2023-08-28T08:52:00-07:00'
    user: Marcus
  - id: discord_dm_1785275709749
    message: Non-prod egress spike looks contained. Please keep the narrow guardrail
      alert, but don’t turn this into architecture work or spend-plan work unless
      the next report regresses.
    sent_at: '2023-09-05T15:06:00-07:00'
    user: Marcus
  - id: discord_dm_1785276675661
    message: 'Safer board-note version:


      “Evergreen’s procurement follow-up is commercial packaging and enterprise-readiness
      work around the current Mercury design-partner scope. The September metrics
      package stays inside its operating bounds: activation/admin friction has improved,
      expansion remains uneven, and this is not proof that enterprise readiness, retention,
      or expansion is solved. It should not be framed as a B-round restart.”'
    sent_at: '2023-09-14T09:48:00-07:00'
    user: Devon Hayes
  - id: discord_dm_1785277492460
    message: 'Quick answer on the board follow-up: the corrected cut is activation/onboarding,
      not retention. Evergreen’s packet is commercial packaging plus enterprise-readiness
      gap work, not enterprise-readiness or expansion proof. H2 fundraising prep does
      not mean we’re restarting a September B-round process.'
    sent_at: '2023-09-19T11:07:00-07:00'
    user: Devon Hayes
  - id: discord_dm_1785277492944
    message: 'Quick answer on the board follow-up: the corrected cut is activation/onboarding,
      not retention. Evergreen’s packet is commercial packaging plus enterprise-readiness
      gap work, not enterprise-readiness or expansion proof. H2 fundraising prep does
      not mean we’re restarting a September B-round process.'
    sent_at: '2023-09-19T11:07:00-07:00'
    user: Anna Martinez
  - id: discord_dm_1785277493922
    message: 'Final Evergreen procurement walkthrough run-of-show (internal; do not
      forward)


      Objective:

      - Walk Evergreen through the current Mercury pilot, commercial framework, and
      follow-up handling.

      - Keep live scope separate from next-phase enterprise-readiness gaps.

      - Sarah coordinates the customer conversation and follow-up thread.


      0:00–0:03 — Sarah: opening / expectations

      - Frame this as a walkthrough of current Mercury pilot scope and commercial
      framing, not a launch-scope expansion or custom Evergreen commitment.

      - State that follow-up questions will be captured and routed through Sarah’s
      thread.


      0:03–0:10 — Jake: current product facts only

      - Current access path: Clerk-backed sessions, magic links, and org invites.

      - Preview/sample data is preview-only and non-activating.

      - Activation = real source connected or first live sync completed within 7 days.

      - Current known gaps may be named, but no feature sequencing, dates, or commitment
      language.


      0:10–0:17 — Devon: commercial/procurement framing

      - Use standard Mercury hybrid pricing: Pilot is a $2,500/month platform minimum
      including up to 50 monthly active developers; Growth is a $7,500/month platform
      minimum including up to 200 monthly active developers; overage is $1,000 per
      additional 50 monthly active developers.

      - Pricing is based on monthly active developers, not seats, directory size,
      invited users, or a custom Evergreen carveout.

      - Scaffold/internal test users do not count.

      - Keep it budgetary and directional; enterprise add-ons are separate only after
      they ship.


      0:17–0:23 — Sarah-led follow-up capture, with Jake/Devon answering only inside
      scope

      - Questions about SSO, audit history, admin/billing-owner separation, or deeper
      procurement detail should be captured as next-phase follow-up.

      - No dates, bespoke commitments, or “roadmap” framing in the live meeting.


      0:23–0:30 — Q&A / next steps

      - Sarah manages time and records follow-up items for the external thread.

      - Devon answers commercial/procurement and pricing questions.

      - Jake answers current product facts and known gaps only.

      - Anything beyond shipped scope is captured for next-phase follow-up, not improvised.


      Backup answers:

      - Preview/sample data counts as activation? No. Activation is real source connected
      or first live sync completed within 7 days.

      - Pricing by seat? No. Pricing maps to monthly active developer usage.

      - SSO available in current pilot? Not in current live scope; capture for next-phase
      follow-up.

      - Audit history for admin changes available now? Not in current live scope;
      capture for next-phase follow-up.

      - Admin vs billing-owner separation fully available today? Not fully; it is
      a known enterprise-readiness gap for follow-up.

      - Full standalone procurement/security packet ready now? We can share current
      commercial framing and live product scope; fuller procurement detail is next-phase
      follow-up.


      Do not include a roadmap-labeled slide. If a backup appendix is needed, title
      it “Next-phase follow-up topics” and keep it date-free and commitment-free.'
    sent_at: '2023-09-20T09:18:00-07:00'
    user: Sarah Kim
  - id: discord_dm_1785277494449
    message: 'Final Evergreen procurement walkthrough run-of-show (internal; do not
      forward)


      Objective:

      - Walk Evergreen through the current Mercury pilot, commercial framework, and
      follow-up handling.

      - Keep live scope separate from next-phase enterprise-readiness gaps.

      - Sarah coordinates the customer conversation and follow-up thread.


      0:00–0:03 — Sarah: opening / expectations

      - Frame this as a walkthrough of current Mercury pilot scope and commercial
      framing, not a launch-scope expansion or custom Evergreen commitment.

      - State that follow-up questions will be captured and routed through Sarah’s
      thread.


      0:03–0:10 — Jake: current product facts only

      - Current access path: Clerk-backed sessions, magic links, and org invites.

      - Preview/sample data is preview-only and non-activating.

      - Activation = real source connected or first live sync completed within 7 days.

      - Current known gaps may be named, but no feature sequencing, dates, or commitment
      language.


      0:10–0:17 — Devon: commercial/procurement framing

      - Use standard Mercury hybrid pricing: Pilot is a $2,500/month platform minimum
      including up to 50 monthly active developers; Growth is a $7,500/month platform
      minimum including up to 200 monthly active developers; overage is $1,000 per
      additional 50 monthly active developers.

      - Pricing is based on monthly active developers, not seats, directory size,
      invited users, or a custom Evergreen carveout.

      - Scaffold/internal test users do not count.

      - Keep it budgetary and directional; enterprise add-ons are separate only after
      they ship.


      0:17–0:23 — Sarah-led follow-up capture, with Jake/Devon answering only inside
      scope

      - Questions about SSO, audit history, admin/billing-owner separation, or deeper
      procurement detail should be captured as next-phase follow-up.

      - No dates, bespoke commitments, or “roadmap” framing in the live meeting.


      0:23–0:30 — Q&A / next steps

      - Sarah manages time and records follow-up items for the external thread.

      - Devon answers commercial/procurement and pricing questions.

      - Jake answers current product facts and known gaps only.

      - Anything beyond shipped scope is captured for next-phase follow-up, not improvised.


      Backup answers:

      - Preview/sample data counts as activation? No. Activation is real source connected
      or first live sync completed within 7 days.

      - Pricing by seat? No. Pricing maps to monthly active developer usage.

      - SSO available in current pilot? Not in current live scope; capture for next-phase
      follow-up.

      - Audit history for admin changes available now? Not in current live scope;
      capture for next-phase follow-up.

      - Admin vs billing-owner separation fully available today? Not fully; it is
      a known enterprise-readiness gap for follow-up.

      - Full standalone procurement/security packet ready now? We can share current
      commercial framing and live product scope; fuller procurement detail is next-phase
      follow-up.


      Do not include a roadmap-labeled slide. If a backup appendix is needed, title
      it “Next-phase follow-up topics” and keep it date-free and commitment-free.'
    sent_at: '2023-09-20T09:18:00-07:00'
    user: Devon Hayes
  - id: discord_dm_1785277494962
    message: 'Final Evergreen procurement walkthrough run-of-show (internal; do not
      forward)


      Objective:

      - Walk Evergreen through the current Mercury pilot, commercial framework, and
      follow-up handling.

      - Keep live scope separate from next-phase enterprise-readiness gaps.

      - Sarah coordinates the customer conversation and follow-up thread.


      0:00–0:03 — Sarah: opening / expectations

      - Frame this as a walkthrough of current Mercury pilot scope and commercial
      framing, not a launch-scope expansion or custom Evergreen commitment.

      - State that follow-up questions will be captured and routed through Sarah’s
      thread.


      0:03–0:10 — Jake: current product facts only

      - Current access path: Clerk-backed sessions, magic links, and org invites.

      - Preview/sample data is preview-only and non-activating.

      - Activation = real source connected or first live sync completed within 7 days.

      - Current known gaps may be named, but no feature sequencing, dates, or commitment
      language.


      0:10–0:17 — Devon: commercial/procurement framing

      - Use standard Mercury hybrid pricing: Pilot is a $2,500/month platform minimum
      including up to 50 monthly active developers; Growth is a $7,500/month platform
      minimum including up to 200 monthly active developers; overage is $1,000 per
      additional 50 monthly active developers.

      - Pricing is based on monthly active developers, not seats, directory size,
      invited users, or a custom Evergreen carveout.

      - Scaffold/internal test users do not count.

      - Keep it budgetary and directional; enterprise add-ons are separate only after
      they ship.


      0:17–0:23 — Sarah-led follow-up capture, with Jake/Devon answering only inside
      scope

      - Questions about SSO, audit history, admin/billing-owner separation, or deeper
      procurement detail should be captured as next-phase follow-up.

      - No dates, bespoke commitments, or “roadmap” framing in the live meeting.


      0:23–0:30 — Q&A / next steps

      - Sarah manages time and records follow-up items for the external thread.

      - Devon answers commercial/procurement and pricing questions.

      - Jake answers current product facts and known gaps only.

      - Anything beyond shipped scope is captured for next-phase follow-up, not improvised.


      Backup answers:

      - Preview/sample data counts as activation? No. Activation is real source connected
      or first live sync completed within 7 days.

      - Pricing by seat? No. Pricing maps to monthly active developer usage.

      - SSO available in current pilot? Not in current live scope; capture for next-phase
      follow-up.

      - Audit history for admin changes available now? Not in current live scope;
      capture for next-phase follow-up.

      - Admin vs billing-owner separation fully available today? Not fully; it is
      a known enterprise-readiness gap for follow-up.

      - Full standalone procurement/security packet ready now? We can share current
      commercial framing and live product scope; fuller procurement detail is next-phase
      follow-up.


      Do not include a roadmap-labeled slide. If a backup appendix is needed, title
      it “Next-phase follow-up topics” and keep it date-free and commitment-free.'
    sent_at: '2023-09-20T09:18:00-07:00'
    user: Jake
  - id: discord_dm_1785280873493
    message: 'Your read matches the logs: Clerk revalidation succeeds and rotates
      to session_version 27 / rt_4b22, but the inline retry starts before the cookie/session
      write lands and pulls cached v26 / rt_4b21, so refresh_exchange rejects on session_version_mismatch.
      Before calling the patch green, can you verify: (1) retry uses the freshly revalidated
      auth context rather than cache, (2) cookie/session write ordering can’t race
      the retry, (3) expired-mid-flight API v2 requests pass without hard reload,
      and (4) clean login/clean refresh still pass? Keeping this scoped to the retry
      failure mode, not a broader auth redesign.'
    sent_at: '2023-10-02T09:32:00-07:00'
    user: Marcus
  - id: discord_dm_1785280874363
    message: 'Prep for Elena:

      - Keep this as calibration, not a process launch.

      - Use the September Mercury package as operating evidence: activation/admin
      friction improved, expansion still uneven.

      - Pricing frame: Pilot $2,500/mo up to 50 monthly active developers; Growth
      $7,500/mo up to 200; $1,000 per extra 50.

      - Evergreen is a regulated procurement / enterprise-readiness signal, not proof
      enterprise readiness is solved.

      - Pressure-test: credible vs February, repeatable vs anecdotal, pricing discipline,
      and how cleanly we explain uneven expansion before widening.

      - No random investor coffees off this package.'
    sent_at: '2023-10-03T08:18:00-07:00'
    user: Devon Hayes
  - id: discord_dm_1785280874807
    message: Month-open AWS cost email has non-prod snapshots running about $1,860
      above the September run rate. Can you check the cause and send back one recommended
      cleanup? Please keep it narrow — I do not want this turning into a broader infra
      project.
    sent_at: '2023-10-03T09:04:00-07:00'
    user: Marcus
  - id: discord_dm_1785280875667
    message: 'Please keep the JWT retry patch announcement to #eng-releases only.
      Do not post it in #eng-all.'
    sent_at: '2023-10-03T14:38:00-07:00'
    user: Marcus
  - id: discord_dm_1785280876959
    message: '- Elena: materially more credible than February.

      - Biggest push: prove Evergreen can be repeatable, not anecdotal.

      - Do not widen beyond a short list yet.

      - Next: tighten uneven-expansion explanation before any step.

      - Park random coffees; keep evidence-focused calibration only.'
    sent_at: '2023-10-04T14:16:00-07:00'
    user: Devon Hayes
  - id: discord_dm_1785280877818
    message: 'Approved for the narrow cleanup: delete forgotten non-prod snapshots
      older than 14 days from the auth-rewrite load test, with the estimated ~$1,200/month
      savings. Please send me a one-line confirmation after it’s done. This is not
      approval for new tooling or broader infrastructure work.'
    sent_at: '2023-10-05T10:21:00-07:00'
    user: Marcus
  - id: discord_dm_1785280878849
    message: 'Cleaned-up version:


      Quick two-minute observability demo: trace an “invite accepted, then sync looked
      stuck” report end to end across API v2, auth, and Mercury. The goal is to show
      how we move from a vague symptom to the failing retry branch without turning
      this into a vendor pitch.


      Suggested flow:

      1. Start with the invite-accepted / sync-looked-stuck trace.

      2. Filter by workspace + endpoint to narrow the trace set.

      3. Open the auth handoff where the retry path fans out.

      4. Use derived columns/breakdown to isolate the error bucket.

      5. Click the offending trace and show the malformed retry reason.

      6. Close with what we learned, not “reliability is solved.”'
    sent_at: '2023-10-05T11:33:00-07:00'
    user: Jordan
  - id: discord_dm_1785280879719
    message: Thanks for getting the Acme API v2 export timeout patch live and through
      Greg’s test export.
    sent_at: '2023-10-06T16:21:00-07:00'
    user: Jake
  - id: discord_dm_1785280880150
    message: After Elena’s calibration, we are not putting random coffees on the calendar.
      Only short-list, evidence-focused calibration stays open. Anything that turns
      October into a broad process gets parked.
    sent_at: '2023-10-06T16:58:00-07:00'
    user: Devon Hayes
  - id: discord_dm_1785282144511
    message: For Evergreen’s second-admin-group prep, you own the budgetary and commercial
      questions. Please keep that separate from the bounded product test so the customer
      agenda does not read like expansion approval.
    sent_at: '2023-10-09T08:46:00-07:00'
    user: Devon Hayes
  - id: discord_dm_1785282144950
    message: 'For Evergreen prep, keep customer-facing product facts limited to the
      current Mercury test flow: magic links, org invites, preview-only sample data,
      real-source connection, and first live sync. No SSO/admin/procurement promises.'
    sent_at: '2023-10-09T08:46:00-07:00'
    user: Jake
  - id: discord_dm_1785282145378
    message: 'Decision from the usability notes: keep the already selected low-pressure
      empty-state direction, but make the repo task clearer. Let’s simplify to:


      Headline: “Connect your first repo”

      Support line: “Finish setup now or come back later from workspace settings.”


      The issue looks like clarity of the next step, not resistance to the relaxed
      tone. Let’s not bring back trial-activation language.'
    sent_at: '2023-10-09T09:37:00-07:00'
    user: Priya
  - id: discord_dm_1785282145809
    message: 'Marcus — the billing retry digest shows four Stripe renewal rows still
      stuck after webhook replay: ren_44181 replay_seen_not_requeued, ren_44197 lock_held_after_replay,
      ren_44206 replay_applied_waiting_worker, and ren_44212 manual_review_required.


      The digest shows no duplicate-charge signal: same payment_intents, 0 new charge
      objects, access still grace_active, and no extra dunning email. Please confirm
      the current retry state, replay only these stuck renewals if safe/no second-collect
      risk, and send me one customer-support sentence in case anyone asks. Keep this
      contained to these Stripe renewals.'
    sent_at: '2023-10-09T10:08:00-07:00'
    user: Marcus
  - id: discord_dm_1785282147016
    message: 'Remaining go/no-go questions before release wording:


      1. Who is the canary owner, and what is the exact 30-minute watch window?

      2. Has the rollback toggle been exercised end-to-end in prod-like config, including
      already-warm pods / mixed auth state?

      3. During canary, are we agreed that sustained auth failures, sticky 401 loops,
      or org-context mismatches are stop/rollback triggers, while a one-request 401
      blip is not?

      4. For the release note, can we keep it provider-neutral?


      Recommended #eng-releases wording once the go/no-go items are closed: “API v2
      auth now revalidates expired sessions more consistently in the background. No
      customer action is expected.”'
    sent_at: '2023-10-11T08:58:00-07:00'
    user: Marcus
  - id: discord_dm_1785282148508
    message: 'Rishi — thanks for keeping AT-3419 and AT-3427 from sitting. The support
      rotation doc is still the source of truth for Atlas intake and ownership.


      You should not become the default bypass for old side threads. If an urgent
      Atlas issue comes in directly, it needs to be handed into the rotation with
      an explicit owner named. Please keep redirecting direct Atlas items rather than
      absorbing them by default.'
    sent_at: '2023-10-11T10:14:00-07:00'
    user: Rishi
  - id: discord_dm_1785282149400
    message: 'Evergreen’s second admin group is now in the bounded Mercury test, and
      their first live sync completed. The admins asked again about SSO, admin-change
      audit history, and admin-vs-billing-owner separation. Customer stance: testing
      can continue under current scope; those asks stay next-phase enterprise-readiness,
      not v0.2 promises or Evergreen exceptions. You own the commercial/budgetary
      framing.'
    sent_at: '2023-10-12T10:54:00-07:00'
    user: Devon Hayes
  - id: discord_dm_1785282149937
    message: 'Evergreen’s second admin group is now in the bounded Mercury test, and
      their first live sync completed. For any customer-facing follow-up, stay limited
      to current product facts: magic links, org invites, preview-only sample data,
      real-source connection, and first live sync. SSO, admin-change audit history,
      and admin-vs-billing-owner separation stay next-phase — no commitments.'
    sent_at: '2023-10-12T10:54:00-07:00'
    user: Jake
  - id: discord_dm_1785282150837
    message: 'Tighter version for the board note:


      Evergreen’s second admin group is useful additional evidence that the bounded
      Mercury path is worth testing beyond the first admin cohort, but it is still
      bounded evidence. The second group helps us observe whether the current flow
      — magic links, org invites, preview-only sample data, real-source connection,
      and first live sync — holds up with more enterprise users inside one account.
      It does not prove enterprise readiness, repeatable expansion, or resolution
      of the remaining gaps around SSO, auditability, admin controls, billing-owner
      separation, or procurement packaging. For October, the right framing is selective
      calibration: we can use Evergreen to sharpen the Mercury story and pressure-test
      what still needs to harden, but we are not launching a broad B-round process
      off this signal alone.'
    sent_at: '2023-10-13T09:41:00-07:00'
    user: Devon Hayes
  - id: discord_dm_1785283360885
    message: Thanks for getting the auth-rewrite rollout over the line and posting
      the clean completion note. Appreciate the careful watch on 401s and rollback.
    sent_at: '2023-10-17T14:16:00-07:00'
    user: Marcus
  - id: discord_dm_1785283361313
    message: We replayed the affected renewal safely, and our checks show no duplicate
      charge on the account.
    sent_at: '2023-10-17T15:34:00-07:00'
    user: Rishi
  - id: discord_dm_1785283361742
    message: The Stripe renewal remediation thread can close unless a customer reports
      a duplicate charge.
    sent_at: '2023-10-17T15:34:00-07:00'
    user: Marcus
  - id: discord_dm_1785283362664
    message: '- Friday room decisions: Mercury hardening cutline — keep Q4 to invited-member
      handoff, failed-sync legibility, and setup-to-first-sync reliability, or open
      a parallel enterprise-readiness lane now.

      - Friday room decisions: onboarding scope — decide whether workspace-switcher
      / extra branching belongs in this pass or stays deferred until there’s evidence.

      - Owner follow-through: auth rewrite cleanup stays with Jake + Rishi unless
      leadership wants to reopen the provider/commercial piece.

      - Owner follow-through: API v2 docs stay with Rishi unless docs need to jump
      ahead of Mercury/onboarding hardening in the same window.

      - Framing: I’d keep this as an operating cutline for Friday, not investor packaging.'
    sent_at: '2023-10-18T17:22:00-07:00'
    user: Devon Hayes
  - id: discord_dm_1785283363527
    message: The Acme NDA issue remains active and unresolved. Acme is excluded from
      fresh Mercury materials because of the legal scope issue, not because there’s
      no interest.
    sent_at: '2023-10-19T10:48:00-07:00'
    user: Devon Hayes
  - id: discord_dm_1785283363961
    message: The Acme NDA issue remains active and unresolved. Acme is excluded from
      fresh Mercury materials because of the legal scope issue, not because there’s
      no interest.
    sent_at: '2023-10-19T10:48:00-07:00'
    user: Jake
  - id: discord_dm_1785283364393
    message: 'I’d use this tightened version:


      | Evidence row | Current read | How to use it in the note | Caveat |

      | --- | --- | --- | --- |

      | Wave-1 aggregate | Activation and admin friction look improved inside the
      design-partner wave, but expansion is still uneven. | Use as the honest Mercury
      progress topline. | Not a claim that retention or expansion is solved. |

      | Evergreen Bank | Second admin group testing stays inside the bounded current
      Mercury flow: magic links, org invites, preview-only sample data, real-source
      connection, and first live sync. | Use as bounded enterprise-admin evidence
      for the current path, not as proof of full enterprise readiness. | SSO, admin-change
      audit history, and admin-vs-billing-owner separation remain follow-up items,
      not v0.2 promises or Evergreen exceptions. |

      | Metrics framing | Quarterly cohort view is the board-facing context; corrected
      weekly activation cuts are internal operating input only. | Keep the board note
      anchored on the cohort view and use weekly cuts only as directional operating
      context. | Avoid making weekly cuts sound board-grade by themselves. |

      | October fundraise calibration | Mercury can support narrow October prep only
      if uneven expansion and enterprise-readiness caveats stay explicit. | Use as
      the framing row above the table. | No new investor names and no broad B-round
      reopening claim. |


      Deleted/parked: Acme. Do not use Acme as Mercury evidence or as pending fresh-material
      access while the NDA scope remains unresolved. The Acme exclusion is legal-scope
      driven, not a demand-signal judgment.'
    sent_at: '2023-10-20T08:57:00-07:00'
    user: Devon Hayes
  - id: discord_dm_1785283364851
    message: Atlas support intake should follow the support rotation doc as the source
      of truth. If an Atlas issue comes in through a side thread and needs urgent
      help, the handoff should name the support owner and the immediate next step
      before it lands in rotation. “Send to Rishi” is not the default route for Atlas
      issues; pull Rishi in when there is a specific Atlas question or code-path reason,
      while keeping a named support owner responsible for tracking and driving the
      issue.
    sent_at: '2023-10-20T09:12:00-07:00'
    user: Rishi
  - id: discord_dm_1785284615952
    message: 'Good news that the header-casing clarification got Pinecone past verification.
      Before we add a language-specific Go example, can you grab one concrete failing
      repro where the current docs are still insufficient? Keep the docs scope narrow:
      no env-var/header-location variants, no alternate signature locations, and no
      broader connector-docs rewrite.'
    sent_at: '2023-10-24T11:58:00-07:00'
    user: Rishi
  - id: discord_dm_1785284617285
    message: 'Good first call with Sofia. Next actions: assemble the cleaned Mercury
      cohort package, Evergreen enterprise-readiness context, and hybrid pricing model;
      keep the caveats intact; and don’t turn this into fundraising theater.'
    sent_at: '2023-10-25T13:26:00-07:00'
    user: Devon Hayes
  - id: discord_dm_1785284618131
    message: Sounds good that the auth rewrite is still quiet. Remove the two staging-only
      Clerk toggles after you confirm there are no production references. Leave the
      rollback flag in place until Friday, 2023-11-03. No new release note — customer
      behavior didn’t change.
    sent_at: '2023-10-25T15:08:00-07:00'
    user: Marcus
  - id: discord_dm_1785284618574
    message: 'Agree this should stay targeted. Support should use the current GraphQL
      API v2 quickstart: https://docs.atlas-test.com/api/v2/graphql-quickstart, and
      avoid the legacy v1 search result. Treat this as a docs/search pinning fix,
      not a reopening of the API migration project. If screenshots help pin the exact
      result ordering, grab them, but don’t let this expand.'
    sent_at: '2023-10-26T09:36:00-07:00'
    user: Rishi
  - id: discord_dm_1785284619076
    message: 'Here’s the replacement I’d use:


      Section: selective financing update


      Northstar Ventures has been added to the narrow B-round short list through Sofia
      Alvarez after Elena’s introduction and our first context call. The first thread
      is a selective review of the real Mercury evidence: the cleaned cohort package,
      Evergreen Bank context on current product scope versus enterprise-readiness
      follow-up, the hybrid pricing model, and the caveats around expansion and enterprise
      readiness. Sofia engaged with the actual story rather than asking for a glossier
      fundraising version, which makes Northstar worth focused follow-up while keeping
      the financing path narrow and evidence-led.


      Board-call note:

      - Follow-up requested: cleaned Mercury cohort package, Evergreen context, hybrid
      pricing model

      - Read-through: Northstar is now on the narrow short list through Sofia, with
      follow-up focused on current Mercury evidence, pricing, Evergreen context, and
      caveats.'
    sent_at: '2023-10-27T08:07:00-07:00'
    user: Devon Hayes
  - id: discord_dm_1785284619514
    message: 'Planning cutline: keep Mercury hardening bug fixes in the sprint, and
      let Rishi pull in the targeted API v2 docs/search cleanup now. Defer onboarding
      tooltip polish. Auth cleanup should stay to must-do housekeeping only.


      For Northstar, we should not borrow product/eng owner time for investor packaging
      unless the work also improves the actual product evidence. Real materials, minimally
      cleaned up, beat a packaging lane that weakens the sprint.'
    sent_at: '2023-10-27T08:48:00-07:00'
    user: Devon Hayes
  - id: discord_dm_1785285807055
    message: Devon — for the Evergreen follow-up, please own the commercial/procurement
      framing. Keep it separate from the bounded Mercury v0.2 scope/current-state
      reply.
    sent_at: '2023-10-30T13:31:00-07:00'
    user: Devon Hayes
  - id: discord_dm_1785285807489
    message: Jake — for Evergreen, please only supply current product facts. Stay
      on the bounded current-state description; no roadmap language or v0.2/enterprise
      promises.
    sent_at: '2023-10-30T13:31:00-07:00'
    user: Jake
  - id: discord_dm_1785285808804
    message: Jordan — October close has Honeycomb ingest about $740 over expected
      monthly run rate, mostly retained demo/debug traces. Can you confirm whether
      those traces can be sampled or archived, send me one sentence on the expected
      recurring run rate after cleanup, and keep this as cost hygiene rather than
      a new observability-tooling project?
    sent_at: '2023-10-31T14:18:00-07:00'
    user: Jordan
  - id: discord_dm_1785285809247
    message: Marcus — October close has Honeycomb ingest about $740 over expected
      monthly run rate, mostly retained demo/debug traces. Can you confirm whether
      those traces can be sampled or archived, send me one sentence on the expected
      recurring run rate after cleanup, and keep this as cost hygiene rather than
      a new observability-tooling project?
    sent_at: '2023-10-31T14:18:00-07:00'
    user: Marcus
  - id: discord_dm_1785285810578
    message: 'Anna — final October Mercury cut rule: close the month at Oct. 31; compare
      real-source/live-sync activation against May; use Evergreen’s second admin group
      only as a bounded enterprise-pattern example for admin-friction improvement;
      keep weekly cuts and sample-preview diagnostics internal; leave expansion described
      as uneven.'
    sent_at: '2023-11-01T10:11:00-07:00'
    user: Anna Martinez
  - id: discord_dm_1785285811018
    message: 'Devon — same cut rule for the October Mercury package: close the month
      at Oct. 31; compare real-source/live-sync activation against May; use Evergreen’s
      second admin group only as a bounded enterprise-pattern example; weekly cuts
      and sample-preview diagnostics stay internal; expansion remains uneven.'
    sent_at: '2023-11-01T10:11:00-07:00'
    user: Devon Hayes
  - id: discord_dm_1785285812382
    message: Marcus — approved to remove the staging-only Clerk toggles and the rollback
      flag after one final production-reference check. No new release note; customer
      behavior didn’t change.
    sent_at: '2023-11-03T11:08:00-07:00'
    user: Marcus
  - id: discord_dm_1785287792763
    message: 'Final practical terms for the senior engineer offer: expires Monday,
      2023-11-13 at 5:00 p.m. PT. Preferred start date is Monday, 2023-11-27; Monday,
      2023-12-04 is acceptable if needed. Please do not reopen the existing comp or
      equity language in this pass, and keep the required legal-clearance path before
      sending.'
    sent_at: '2023-11-06T16:10:00-08:00'
    user: HR
  - id: discord_dm_1785287795496
    message: 'Suggested revision:


      After the October reset, the B-round work remains selective prep rather than
      active diligence. Northstar Ventures, through Sofia Alvarez, remains on the
      narrow short list, but that is not a lead commitment or an active diligence
      step yet. On the product side, Evergreen is useful bounded evidence from the
      current Mercury path: activation and admin-friction signals are cleaner, and
      the design-partner feedback is helping us identify enterprise-readiness gaps.
      It is not proof that enterprise readiness or expansion is solved. We’re still
      being selective about where we spend time, and the work remains focused prep
      around the evidence and caveats.'
    sent_at: '2023-11-08T09:04:00-08:00'
    user: Devon Hayes
  - id: discord_dm_1785300763646
    message: 'Final caveat pass: the Sofia send stays limited to the cleaned cohort
      view, bounded Evergreen context, and Devon’s pricing appendix. I left out weekly
      cuts/raw customer movement and kept the caveats explicit: activation = real
      source/live sync within 7 days, preview/sample excluded, and expansion/enterprise
      readiness not solved. Next conversation remains a selective Mercury evidence
      review, not a lead process or term-sheet conversation.'
    sent_at: '2023-11-13T10:14:00-08:00'
    user: Anna Martinez
  - id: discord_dm_1785300764127
    message: 'Final caveat pass: the Sofia send stays limited to Anna’s cleaned cohort
      view, bounded Evergreen context, and your pricing appendix. I left out weekly
      cuts/raw customer movement and kept the caveats explicit: activation = real
      source/live sync within 7 days, preview/sample excluded, and expansion/enterprise
      readiness not solved. Next conversation remains a selective Mercury evidence
      review, not a lead process or term-sheet conversation.'
    sent_at: '2023-11-13T10:14:00-08:00'
    user: Devon Hayes
  - id: discord_dm_1785300765063
    message: 'Evergreen split to preserve: SSO timing, audit-history, and admin-versus-billing-owner
      questions stay next-phase enterprise-readiness, not v0.2 promises or Evergreen-specific
      exceptions. Please keep commercial/procurement framing with you; Jake should
      stick to current product facts.'
    sent_at: '2023-11-13T10:39:00-08:00'
    user: Devon Hayes
  - id: discord_dm_1785300765532
    message: 'Evergreen split to preserve: SSO timing, audit-history, and admin-versus-billing-owner
      questions are next-phase enterprise-readiness, not v0.2 promises or Evergreen-specific
      exceptions. Please stick to current product facts if this comes up; Devon owns
      commercial/procurement framing.'
    sent_at: '2023-11-13T10:39:00-08:00'
    user: Jake
  - id: discord_dm_1785300766475
    message: 'Mercury triage: prioritize the recurring admin-setup “Billing owner”
      mislabel (MER-1746) and the live-sync retry cluster (MER-1749, with MER-1751
      tied to the parent if cheap). Keep SSO, admin-change audit history, and admin-vs-billing-owner
      separation out of v0.2; those stay enterprise-readiness follow-up. Any customer-facing
      wording should be limited to current product facts.'
    sent_at: '2023-11-14T14:32:00-08:00'
    user: Leo Park
  - id: discord_dm_1785300766945
    message: 'Mercury triage: prioritize the recurring admin-setup “Billing owner”
      mislabel (MER-1746) and the live-sync retry cluster (MER-1749, with MER-1751
      tied to the parent if cheap). Keep SSO, admin-change audit history, and admin-vs-billing-owner
      separation out of v0.2; those stay enterprise-readiness follow-up. Any customer-facing
      wording should be limited to current product facts.'
    sent_at: '2023-11-14T14:32:00-08:00'
    user: Jake
  - id: discord_dm_1785300767415
    message: 'Please keep this as targeted pinning/suppression cleanup: suppress the
      stale API v1 refund-webhook cache result at `/api/v1/webhooks/refunds`, and
      pin the current API v2 quickstart for that support path: https://docs.atlas-test.com/api/v2/graphql-quickstart.


      Support-facing sentence: “For refund webhook auth, use the current GraphQL API
      v2 quickstart and its auth/header model: https://docs.atlas-test.com/api/v2/graphql-quickstart.”


      No broader API migration cleanup.'
    sent_at: '2023-11-14T14:51:00-08:00'
    user: Rishi
  - id: discord_dm_1785300768853
    message: 'Prep for Sofia’s Friday 9 a.m. PT Northstar session:


      • You own the cohort walkthrough: use the external activation definition — real
      source connected or first live sync within 7 days; sample/preview excluded;
      invite sent is supporting only.

      • Be precise on activation versus expansion: show where real-source/live-sync
      activation improved, and where expansion remains uneven or failure modes still
      show up.

      • Bring a quarterly-view caveat only if it materially changes the read; no weekly
      operating cuts unless necessary.

      • Evergreen: frame what the bounded flow validated versus what it exposed as
      later enterprise-readiness follow-up around SSO timing, audit history, admin/billing-owner
      separation, and procurement packaging. Morgan will keep the process label narrow.'
    sent_at: '2023-11-15T08:46:00-08:00'
    user: Anna Martinez
  - id: discord_dm_1785300769328
    message: 'Prep for Sofia’s Friday 9 a.m. PT Northstar session:


      • You own hybrid pricing: Pilot/Growth structure, monthly active developer usage
      as the honest ramp measure, and why this is not directory-size or purchased-seat
      pricing.

      • Keep Evergreen budgetary and non-custom: no custom Evergreen exception, and
      enterprise add-ons only after they ship.

      • Be ready for pricing questions where teams activate but expansion stays uneven.

      • Morgan will keep the process label narrow: current Mercury evidence review,
      not a broader process deck.'
    sent_at: '2023-11-15T08:46:00-08:00'
    user: Devon Hayes
  - id: discord_dm_1785300769793
    message: 'One crosslink is fine only if it points back to the canonical header-only
      path: `X-Scaffold-Workspace` and `X-Scaffold-Signature` on the incoming webhook.
      Do not add a Python example without a concrete failing repro. No alternate signature
      locations, no query-param/env-var forms, and no broader connector rewrite.'
    sent_at: '2023-11-15T10:59:00-08:00'
    user: Rishi
  - id: discord_dm_1785300770266
    message: 'Approved for the narrow AWS cleanup after you confirm production log
      retention is untouched: move non-prod log groups from 90-day to 14-day retention.
      Please send one confirmation after it’s done. This is not approval for new logging
      tooling or broader infra work.'
    sent_at: '2023-11-16T15:04:00-08:00'
    user: Marcus
  - id: discord_dm_1785300771702
    message: 'Recap from Sofia session: your cohort walkthrough landed as intended
      — activation improvement = real-source/live-sync, preview/sample excluded; expansion
      still uneven. Devon’s pricing framing also landed — MAU usage is the honest
      ramp measure, not directory-seat pricing. Sofia asked for a December partner-level
      readout. Boundary stays explicit: Northstar is active diligence through Sofia,
      not a declared lead, not a term-sheet process, and not proof Evergreen or Mercury
      expansion is solved.'
    sent_at: '2023-11-17T10:18:00-08:00'
    user: Anna Martinez
  - id: discord_dm_1785300772179
    message: 'Recap from Sofia session: Anna’s cohort walkthrough landed as intended
      — activation improvement = real-source/live-sync, preview/sample excluded; expansion
      still uneven. Your pricing framing also landed — MAU usage is the honest ramp
      measure, not directory-seat pricing. Sofia asked for a December partner-level
      readout. Boundary stays explicit: Northstar is active diligence through Sofia,
      not a declared lead, not a term-sheet process, and not proof Evergreen or Mercury
      expansion is solved.'
    sent_at: '2023-11-17T10:18:00-08:00'
    user: Devon Hayes
  - id: discord_dm_1785300772653
    message: 'Cleaned owner note draft:


      Mercury hardening: Keep this in motion inside the sprint, limited to launch-confidence
      bugs: live-sync retry behavior, retry-state visibility, admin setup/handoff
      rough edges, and UI/admin mislabels that materially muddy clean Mercury evidence.
      No feature-shaped work under “hardening.” Owners: Jake / Marcus / Leo, with
      Priya only where UI wording is part of the fix.


      Onboarding rollout: Treat as monitored rollout, not a new scope lane. Priya/Jake
      keep watching repo-first completion, invite-order confusion, and support volume.
      No separate polish pass unless rollout data clearly worsens.


      API v2 support-path cleanup: Keep the targeted support-path work in motion:
      pin https://docs.atlas-test.com/api/v2/graphql-quickstart, demote stale API
      v1 hits, and tighten support macro/auth-error routing so support stops sending
      users into deprecated docs. Owner: Rishi.


      Pinecone connector docs: Narrow docs follow-through only: canonical header-only
      path, one Go example if it lands cleanly, and at most one small crosslink back
      to the canonical auth section. No alternate header forms/locations and no broader
      connector-page expansion. Owner: Rishi.


      Diligence-response work: Keep Northstar/similar follow-up with the small business/data
      group. Pull product/engineering help only where it improves actual product evidence;
      do not create an engineering-owned investor packaging lane.'
    sent_at: '2023-11-17T15:58:00-08:00'
    user: Devon Hayes
  - id: discord_dm_1785302122368
    message: Devon — Evergreen compliance is asking for v0.2 labels and rough timing
      on SSO, audit history, and admin-vs-billing-owner separation. Please keep owning
      the commercial/procurement framing; we’re keeping those asks as next-phase enterprise-readiness,
      not Evergreen-specific exceptions or rough-date commitments.
    sent_at: '2023-11-20T09:49:00-08:00'
    user: Devon Hayes
  - id: discord_dm_1785302122873
    message: 'Jake — Evergreen compliance is pressing on SSO, audit history, and admin-vs-billing-owner
      timing. Please stick to current product facts only: current bounded admin-test
      flow, what is live, and known next-phase gaps. No v0.2 promises, Evergreen-specific
      exceptions, or rough-date language.'
    sent_at: '2023-11-20T09:49:00-08:00'
    user: Jake
  - id: discord_dm_1785302123428
    message: Thanks for closing this out. No release note—customer behavior didn’t
      change. Let’s close it as narrow cost hygiene unless the AWS budget line jumps
      again.
    sent_at: '2023-11-20T10:44:00-08:00'
    user: Marcus
  - id: discord_dm_1785302123907
    message: 'Approved from my side if the Go snippet and SDK crosslink stay exactly
      on the canonical header-only path: incoming `X-Scaffold-Workspace` + `X-Scaffold-Signature`,
      with preserved `X-Scaffold-Signature` and lowercased `x-scaffold-signature`
      both accepted. No alternate signature locations, no query fallback, no Python/example
      expansion, and no broader connector rewrite.'
    sent_at: '2023-11-20T11:31:00-08:00'
    user: Rishi
  - id: discord_dm_1785302127449
    message: 'Suggested replacement:


      “Thursday and Friday coverage is for genuinely customer-impacting issues only.
      Atlas issues should go through the support owner on duty; if the question is
      clearly about the verifier/auth path or the current docs/search behavior, tag
      Rishi on that specific code path while support keeps the thread and names the
      next step. Mercury issues should go through the named Mercury owner on call,
      especially live-sync or admin-setup problems on an active design-partner account;
      the handoff should include the owner, customer impact, and immediate next action.
      If an issue is ambiguous between Atlas and Mercury, keep it with the support/on-call
      owner and choose the next named owner rather than defaulting to Morgan or Rishi.
      Anything non-urgent or purely internal can wait until Monday.”'
    sent_at: '2023-11-22T09:19:00-08:00'
    user: Rishi
  - id: discord_dm_1785302128887
    message: 'Thanks for catching this. Narrow holiday fix only: for coverage, point
      support to https://docs.atlas-test.com/api/v2/graphql-quickstart and use this
      customer-safe sentence: “For current API authentication and webhook-related
      setup, please use our GraphQL API v2 quickstart here: https://docs.atlas-test.com/api/v2/graphql-quickstart;
      it reflects the current auth/header model we support now.” On Monday, suppress
      or patch the old refund-webhook macro so it stops steering people to `/api/v1/webhooks/refunds`.
      Do not reopen the API migration project.'
    sent_at: '2023-11-24T10:29:00-08:00'
    user: Rishi
  - id: discord_dm_1785303389872
    message: 'Evergreen admin-test questions are staying in the current thread for
      now: no dates, no v0.2 promises, and no Evergreen-specific exceptions. Please
      keep your side to the commercial/procurement framing.'
    sent_at: '2023-11-27T08:58:00-08:00'
    user: Devon Hayes
  - id: discord_dm_1785303390343
    message: 'Evergreen admin-test questions are staying in the current thread for
      now: no dates, no v0.2 promises, and no Evergreen-specific exceptions. Please
      stick to current product facts only.'
    sent_at: '2023-11-27T08:58:00-08:00'
    user: Jake
  - id: discord_dm_1785303390825
    message: 'Based on your Nov. 27 RC pass, take MER-1746 and MER-1751 only if the
      listed tests stay green: the admin-setup relabel/helper-text fix and the narrow
      live-sync retry CTA in-flight guard. Keep MER-1749’s broader state-reconcile
      work out of the RC, and keep SSO and audit history out of v0.2. Please attach
      the rc5 replay notes/evidence to MER-1279/current launch-readiness ledger instead
      of leaving it in chat. No customer-facing language should imply Mercury is enterprise-ready.'
    sent_at: '2023-11-27T09:37:00-08:00'
    user: Leo Park
  - id: discord_dm_1785303391313
    message: 'RC guidance: take only MER-1746 and MER-1751 if the listed tests are
      green. Hold MER-1749’s broader reconcile fix, and keep SSO/audit history out
      of v0.2. Please make sure the current launch-readiness ledger gets the evidence,
      and keep any customer-facing language to current product facts only — nothing
      implying Mercury is enterprise-ready.'
    sent_at: '2023-11-27T09:37:00-08:00'
    user: Jake
  - id: discord_dm_1785303391791
    message: 'Customer-safe sentence for support: “For current API authentication
      and webhook-related setup, please use our GraphQL API v2 quickstart here: https://docs.atlas-test.com/api/v2/graphql-quickstart;
      it reflects the current auth/header model we support now.” The macro fix can
      close after support confirms that this current API v2 support-path link is actually
      in the path. Do not reopen the API migration project.'
    sent_at: '2023-11-27T09:55:00-08:00'
    user: Rishi
  - id: discord_dm_1785303392372
    message: 'Private Northstar ownership checklist: you own the cohort read and activation-versus-expansion
      caveats for Sofia’s consolidated questions. Devon owns the hybrid pricing logic
      and Evergreen context. Please send answer snippets first; nobody should turn
      this into partner-readout prep, lead status, a term-sheet step, or a launched
      process.'
    sent_at: '2023-11-27T10:08:00-08:00'
    user: Anna Martinez
  - id: discord_dm_1785303392843
    message: 'Private Northstar ownership checklist: Anna owns the cohort read and
      activation-versus-expansion caveats; you own the hybrid pricing logic and Evergreen
      context. Please send answer snippets first; nobody should turn this into partner-readout
      prep, lead status, a term-sheet step, or a launched process.'
    sent_at: '2023-11-27T10:08:00-08:00'
    user: Devon Hayes
  - id: discord_dm_1785303394704
    message: 'I looked at the two annual renewal rows. Both show Stripe payment succeeded
      and BillingOrchestrator recorded the renewal payment, but the entitlement renewal
      dates stayed at the prior annual end instead of rolling forward to the Stripe
      next annual end. Please keep remediation narrow: reconcile the entitlement renewal
      dates without replaying charges, confirm there is no duplicate-charge path,
      and give Rishi this customer-safe sentence in case either account writes in:
      “Your renewal payment succeeded; we’re reconciling the entitlement renewal date
      to match Stripe, and our checks do not indicate a duplicate charge.”'
    sent_at: '2023-11-28T10:43:00-08:00'
    user: Marcus
  - id: discord_dm_1785303395170
    message: 'Here’s the safer replacement for the board-note section:


      Section: selective financing update


      Northstar remains active diligence through Sofia Alvarez against the current
      Mercury evidence package. Sofia’s written follow-up, and any narrow data-partner
      clarification, are useful for testing whether the activation, Evergreen-context,
      and pricing answers hold up; they should not be framed as a lead process, launched
      financing path, or term-sheet step.


      Evergreen remains the clearest recurring enterprise-pattern signal inside Mercury,
      but it needs careful scope. The current bounded admin flow is working without
      customer-specific exceptions and continues to surface repeat questions around
      SSO timing, audit history, admin-versus-billing-owner separation, and procurement
      packaging. Those questions help define next-phase enterprise-readiness work;
      they do not prove enterprise readiness, solve expansion, or create v0.2 commitments.


      The December board discussion should stay selective and caveated: current package,
      current evidence, clear gaps, no broad process language.


      Supporting bullets:

      - Northstar: active diligence through Sofia on Mercury evidence, Evergreen context,
      and hybrid pricing

      - Current external work: written follow-up on activation sources, expansion
      failure modes, Evergreen context, and pricing logic

      - Read-through: Evergreen is a recurring enterprise-pattern signal that needs
      careful scoping, not proof that enterprise readiness or expansion is solved

      - Risk: if we let the packet sprawl, we create packaging work instead of keeping
      the discussion anchored to the real Mercury evidence'
    sent_at: '2023-11-29T09:42:00-08:00'
    user: Devon Hayes
  - id: discord_dm_1785303396104
    message: 'Customer-safe line if either account writes in: “The renewal payment
      succeeded, the entitlement renewal date has been reconciled to match Stripe,
      and there was no duplicate charge.”'
    sent_at: '2023-11-29T14:38:00-08:00'
    user: Rishi
  - id: discord_dm_1785303396578
    message: Thanks — if the two rows are reconciled, there are no duplicate charges,
      and the entitlement dates now match Stripe, we can close the thread unless either
      account reports a billing discrepancy.
    sent_at: '2023-11-29T14:38:00-08:00'
    user: Marcus
  - id: discord_dm_1785303397625
    message: 'Evergreen compliance follow-up: no owner names or dates yet, keep the
      questions in the current admin-test thread, ask for exact examples next week
      for scoping, and do not treat any of this as v0.2 commitments. Please keep your
      side to commercial/procurement framing.'
    sent_at: '2023-11-30T09:06:00-08:00'
    user: Devon Hayes
  - id: discord_dm_1785303398096
    message: 'Evergreen compliance follow-up: no owner names or dates yet, keep the
      questions in the current admin-test thread, ask for exact examples next week
      for scoping, and do not treat any of this as v0.2 commitments. Please stick
      to current product facts only.'
    sent_at: '2023-11-30T09:06:00-08:00'
    user: Jake
  - id: discord_dm_1785303399049
    message: 'Cleaned-up owner note:


      Product-owner focus stays on real product evidence:

      - Mercury hardening: launch-confidence bugs only — sync reliability, retry behavior,
      admin handoff rough edges, and bugs that materially affect clean Mercury evidence.
      No feature-shaped work under a hardening label.

      - API v2 support cleanup: targeted support-path cleanup around the GraphQL quickstart
      and stale v1 suppression; not a migration reopen.

      - Onboarding: monitor the current rollout; no tooltip, help, or checklist pass
      unless the rollout data clearly worsens.

      - Evergreen: collect enterprise-readiness questions for scoping, but this is
      not sprint scope yet.

      - Northstar / board materials: keep with Morgan, Devon, and Anna unless a narrow
      clarification directly improves actual product evidence. Engineering should
      not pick up broad investor-packaging work.'
    sent_at: '2023-12-01T15:57:00-08:00'
    user: Devon Hayes
  - id: discord_dm_1785303399981
    message: Thanks for driving the November infra-cost close. Since the non-prod
      log-retention cleanup held and Honeycomb ingest stayed near the expected run
      rate, no all-hands mention and no release note — customer behavior did not change.
      Let’s close it as cost hygiene unless the December run rate jumps.
    sent_at: '2023-12-01T16:48:00-08:00'
    user: Marcus
  - id: discord_dm_1785303400450
    message: Thanks for the November infra-cost close. Since the cleanup held and
      Honeycomb ingest stayed near the expected run rate, no all-hands mention and
      no release note — customer behavior did not change. Let’s close it as cost hygiene
      unless the December run rate jumps.
    sent_at: '2023-12-01T16:48:00-08:00'
    user: Jordan
  - id: discord_dm_1785304503834
    message: Leo — thanks for the Dec. 4 pass. Please keep these rows as internal
      readiness evidence only. For MER-1279/current readiness, the only rows I would
      attach if the final launch call stays clear are MER-1746 (Workspace admin relabel/helper
      text, no permissions behavior change) and MER-1751 (retry CTA disabled while
      a retry is in flight). MER-1749 stays out of the current RC. MER-1754, MER-1756,
      and MER-1757 are real enterprise-readiness follow-up, not v0.2, and should not
      leak into customer-facing wording.
    sent_at: '2023-12-04T10:47:00-08:00'
    user: Leo Park
  - id: discord_dm_1785304504322
    message: Jake — for Sarah/Evergreen, keep anything customer-facing to current
      product facts only after release status is actually clear. Do not use Leo’s
      rows as external proof that v0.2 is enterprise-ready, and do not pull SSO/SAML
      timing, admin-change audit history, admin-vs-billing-owner separation, procurement-packet
      status, or other enterprise-readiness claims into v0.2. MER-1746 and MER-1751
      can stay internal readiness evidence; MER-1749 and the enterprise rows stay
      out.
    sent_at: '2023-12-04T10:47:00-08:00'
    user: Jake
  - id: discord_dm_1785304504796
    message: 'Evergreen scoping huddle close: we’re moving the repeated procurement/security
      asks out of the support-question loop and into a bounded next-phase enterprise-readiness
      backlog outside Mercury v0.2: SSO timing, admin-change audit history, admin-vs-billing-owner
      separation, and a standalone procurement packet.


      Ownership:

      - Devon: commercial/procurement framing.

      - Jake + Leo: current product facts and seam-risk input.

      - Sarah: customer thread.

      - Morgan: guardrail — no dates, no custom Evergreen promises, and no enterprise-add-on
      quotes until those features actually ship.


      Customer-thread-ready language for Sarah:

      “For the current Mercury review, the bounded product answer is the current admin
      test flow: magic-link access, org invites, preview-only sample data, real-source
      connection, and first live sync. The questions on SSO/SAML timing, admin-change
      audit history, admin-versus-billing-owner separation, and a standalone procurement/security
      packet are the right next-phase enterprise-readiness follow-up areas, but they
      are outside Mercury v0.2 and we are not attaching dates, Evergreen-specific
      commitments, or enterprise-add-on quotes until the relevant capabilities ship.”'
    sent_at: '2023-12-05T11:33:00-08:00'
    user: Devon Hayes
  - id: discord_dm_1785304505265
    message: 'Evergreen scoping huddle close: we’re moving the repeated procurement/security
      asks out of the support-question loop and into a bounded next-phase enterprise-readiness
      backlog outside Mercury v0.2: SSO timing, admin-change audit history, admin-vs-billing-owner
      separation, and a standalone procurement packet.


      Ownership:

      - Devon: commercial/procurement framing.

      - Jake + Leo: current product facts and seam-risk input.

      - Sarah: customer thread.

      - Morgan: guardrail — no dates, no custom Evergreen promises, and no enterprise-add-on
      quotes until those features actually ship.


      Customer-thread-ready language for Sarah:

      “For the current Mercury review, the bounded product answer is the current admin
      test flow: magic-link access, org invites, preview-only sample data, real-source
      connection, and first live sync. The questions on SSO/SAML timing, admin-change
      audit history, admin-versus-billing-owner separation, and a standalone procurement/security
      packet are the right next-phase enterprise-readiness follow-up areas, but they
      are outside Mercury v0.2 and we are not attaching dates, Evergreen-specific
      commitments, or enterprise-add-on quotes until the relevant capabilities ship.”'
    sent_at: '2023-12-05T11:33:00-08:00'
    user: Jake
  - id: discord_dm_1785304505730
    message: 'Evergreen scoping huddle close: we’re moving the repeated procurement/security
      asks out of the support-question loop and into a bounded next-phase enterprise-readiness
      backlog outside Mercury v0.2: SSO timing, admin-change audit history, admin-vs-billing-owner
      separation, and a standalone procurement packet.


      Ownership:

      - Devon: commercial/procurement framing.

      - Jake + Leo: current product facts and seam-risk input.

      - Sarah: customer thread.

      - Morgan: guardrail — no dates, no custom Evergreen promises, and no enterprise-add-on
      quotes until those features actually ship.


      Customer-thread-ready language for Sarah:

      “For the current Mercury review, the bounded product answer is the current admin
      test flow: magic-link access, org invites, preview-only sample data, real-source
      connection, and first live sync. The questions on SSO/SAML timing, admin-change
      audit history, admin-versus-billing-owner separation, and a standalone procurement/security
      packet are the right next-phase enterprise-readiness follow-up areas, but they
      are outside Mercury v0.2 and we are not attaching dates, Evergreen-specific
      commitments, or enterprise-add-on quotes until the relevant capabilities ship.”'
    sent_at: '2023-12-05T11:33:00-08:00'
    user: Leo Park
  - id: discord_dm_1785304506190
    message: 'Evergreen scoping huddle close: we’re moving the repeated procurement/security
      asks out of the support-question loop and into a bounded next-phase enterprise-readiness
      backlog outside Mercury v0.2: SSO timing, admin-change audit history, admin-vs-billing-owner
      separation, and a standalone procurement packet.


      Ownership:

      - Devon: commercial/procurement framing.

      - Jake + Leo: current product facts and seam-risk input.

      - Sarah: customer thread.

      - Morgan: guardrail — no dates, no custom Evergreen promises, and no enterprise-add-on
      quotes until those features actually ship.


      Customer-thread-ready language for Sarah:

      “For the current Mercury review, the bounded product answer is the current admin
      test flow: magic-link access, org invites, preview-only sample data, real-source
      connection, and first live sync. The questions on SSO/SAML timing, admin-change
      audit history, admin-versus-billing-owner separation, and a standalone procurement/security
      packet are the right next-phase enterprise-readiness follow-up areas, but they
      are outside Mercury v0.2 and we are not attaching dates, Evergreen-specific
      commitments, or enterprise-add-on quotes until the relevant capabilities ship.”'
    sent_at: '2023-12-05T11:33:00-08:00'
    user: Sarah Kim
  - id: discord_dm_1785304507126
    message: 'Northstar follow-up recap: Sofia got the focused diligence pass on October
      activation sources, the 19/27 vs 16/27 read, expansion failure modes, bounded
      Evergreen context, and hybrid pricing. I kept the caveat visible that activation/admin-friction
      progress is not proof downstream expansion is clean. Any narrow follow-up from
      either of you routes through me. Please keep this as active diligence through
      Sofia on the current Mercury package — not a partner readout, lead process,
      or term-sheet step.'
    sent_at: '2023-12-05T15:09:00-08:00'
    user: Anna Martinez
  - id: discord_dm_1785304507594
    message: 'Northstar follow-up recap: Sofia got the focused diligence pass on October
      activation sources, the 19/27 vs 16/27 read, expansion failure modes, bounded
      Evergreen context, and hybrid pricing. I kept the caveat visible that activation/admin-friction
      progress is not proof downstream expansion is clean. Any narrow follow-up from
      either of you routes through me. Please keep this as active diligence through
      Sofia on the current Mercury package — not a partner readout, lead process,
      or term-sheet step.'
    sent_at: '2023-12-05T15:09:00-08:00'
    user: Devon Hayes
  - id: discord_dm_1785304509986
    message: 'Board recap: aligned on the narrow version. Selective B-round prep is
      real enough to discuss, but December is not a launched broad process. Elena
      calibration is complete, Northstar is active diligence through Sofia, and the
      list is still narrowing. Keep caveats beside progress: stronger Mercury activation/admin
      friction, cleaner hybrid pricing, Evergreen enterprise pull, but expansion remains
      uneven and enterprise-readiness gaps remain open.'
    sent_at: '2023-12-08T11:38:00-08:00'
    user: Devon Hayes
  - id: discord_dm_1785304510461
    message: 'Board recap: aligned on the narrow version. Selective B-round prep is
      real enough to discuss, but December is not a launched broad process. Elena
      calibration is complete, Northstar is active diligence through Sofia, and the
      list is still narrowing. Keep caveats beside progress: stronger Mercury activation/admin
      friction, cleaner hybrid pricing, Evergreen enterprise pull, but expansion remains
      uneven and enterprise-readiness gaps remain open.'
    sent_at: '2023-12-08T11:38:00-08:00'
    user: Anna Martinez
  - id: discord_dm_1785306020372
    message: 'Agree with your instinct. Keep the board framing caveated: we should
      not build weekly activation cuts into investor material or widen the default
      Mercury deck. If a bounded Northstar readout is actually scheduled and they
      ask for a narrower read, use the September/October Mercury cohort package with
      the caveats intact; weekly cuts stay internal unless we make a separate call.'
    sent_at: '2023-12-11T09:27:00-08:00'
    user: Devon Hayes
  - id: discord_dm_1785306020859
    message: 'For the Northstar appendix question: keep investor materials anchored
      to the bounded Mercury package. No proactive weekly activation cuts in the deck.
      If a specific bounded readout gets scheduled, use the September/October Mercury
      cohort package with caveats intact; weekly operating cuts should stay internal
      unless we explicitly decide on a narrow backup read.'
    sent_at: '2023-12-11T09:27:00-08:00'
    user: Anna Martinez
  - id: discord_dm_1785306021382
    message: Please keep this to a narrow reconciliation pass on the two downgrade
      credit-memo rows. Reconcile Stripe vs. BillingOrchestrator applied-credit state
      before any retry reruns, and do not issue manual or duplicate credits. acct_01J7M4QK
      looks like Stripe applied cm_01J7N0A1 while BillingOrchestrator is behind; acct_01J7MB2T
      looks like BillingOrchestrator marked applied while Stripe has not applied cm_01J7N4F8.
      Please confirm there is no customer-visible over-credit path and give Rishi
      one safe support sentence in case either customer writes in.
    sent_at: '2023-12-11T11:19:00-08:00'
    user: Marcus
  - id: discord_dm_1785306021849
    message: 'Pre-green guidance: hold release wording until the deploy is actually
      green. If and when it is green, only the admin-setup mislabel fix and the live-sync
      retry in-flight guard can become release-note material, and the note belongs
      in #eng-releases, not #eng-all. Keep SSO, audit history, admin-vs-billing-owner,
      and enterprise-readiness claims out.'
    sent_at: '2023-12-12T09:39:00-08:00'
    user: Leo Park
  - id: discord_dm_1785306022311
    message: 'Pre-green guidance: hold any release note until the deploy is actually
      green. If it goes green, the note should be short and live in #eng-releases,
      not #eng-all. The only release-note material is the admin-setup mislabel fix
      and the live-sync retry in-flight guard. Keep SSO, audit history, admin-vs-billing-owner,
      and enterprise-readiness claims out.'
    sent_at: '2023-12-12T09:39:00-08:00'
    user: Jake
  - id: discord_dm_1785306023240
    message: I sent Sarah a date-free Evergreen version. It keeps current Mercury
      facts separate from next-phase enterprise-readiness and avoids custom Evergreen
      commitments, enterprise add-on quotes, or target windows.
    sent_at: '2023-12-12T10:08:00-08:00'
    user: Devon Hayes
  - id: discord_dm_1785306023731
    message: 'I sent Sarah a safer Evergreen version. Boundary: current product facts
      only for the bounded flow; SSO/SAML, admin-side audit history, and admin-vs-billing-owner
      separation stay next-phase with no dates or Evergreen-specific commitments.'
    sent_at: '2023-12-12T10:08:00-08:00'
    user: Jake
  - id: discord_dm_1785306025128
    message: Can we protect Jan. 11 from 10:00–11:30 a.m. PT for the possible Northstar
      readout? Agenda should stay to the September/October Mercury cohort package,
      the Evergreen enterprise-readiness signal, and hybrid pricing. Pull weekly activation
      cuts out of any Northstar deck path, and don’t send anything externally until
      the hold is confirmed.
    sent_at: '2023-12-13T09:29:00-08:00'
    user: Devon Hayes
  - id: discord_dm_1785306025594
    message: Can we protect Jan. 11 from 10:00–11:30 a.m. PT for the possible Northstar
      readout? Please keep the package to the September/October Mercury cohort view,
      Evergreen enterprise-readiness signal, and hybrid pricing. Pull weekly activation
      cuts out of the deck path, and don’t send anything externally until the hold
      is confirmed.
    sent_at: '2023-12-13T09:29:00-08:00'
    user: Anna Martinez
  - id: discord_dm_1785306026064
    message: 'If either account writes in, safe sentence: “The downgrade credit state
      has been reconciled against Stripe, and no duplicate credit was issued. Please
      let us know if you see any balance discrepancy.” Keep it precautionary and route
      any reported discrepancy back to us.'
    sent_at: '2023-12-13T13:07:00-08:00'
    user: Rishi
  - id: discord_dm_1785306026553
    message: Thanks. If the two rows are reconciled, no duplicate credits were issued,
      and Rishi has the precautionary support line, we can close this unless either
      account reports a balance discrepancy.
    sent_at: '2023-12-13T13:07:00-08:00'
    user: Marcus
  - id: discord_dm_1785306027938
    message: 'Northstar readout is being held for Jan. 11, 10:00–11:30 a.m. PT. Prep
      stays bounded: September/October Mercury cohort package, Evergreen enterprise-readiness
      signal, and hybrid pricing. No term-sheet implication, don’t treat Northstar
      as lead, and keep weekly activation cuts out of the deck.'
    sent_at: '2023-12-14T08:58:00-08:00'
    user: Devon Hayes
  - id: discord_dm_1785306028394
    message: Northstar readout is being held for Jan. 11, 10:00–11:30 a.m. PT. Prep
      stays bounded to the September/October Mercury cohort package, Evergreen enterprise-readiness
      signal, and hybrid pricing. No term-sheet implication, don’t treat Northstar
      as lead, and keep weekly activation cuts out of the deck.
    sent_at: '2023-12-14T08:58:00-08:00'
    user: Anna Martinez
  - id: discord_dm_1785306029351
    message: 'Posted the #eng-releases note only. Please keep follow-up wording tight:
      the shipped changes are the “Billing owner” → “Workspace admin” admin-setup
      wording and the retry CTA in-flight guard only. Do not name Evergreen, and don’t
      imply SSO, audit history, admin-vs-billing-owner separation, broader state reconcile,
      or enterprise readiness shipped.'
    sent_at: '2023-12-14T10:48:00-08:00'
    user: Jake
  - id: discord_dm_1785306029824
    message: 'Support wording should stay generic and not name Evergreen. Safe line:
      “No action required; this is a UI/guardrail cleanup, not a change to auth or
      admin permissions.” If you mention the deploy, limit it to clearer Workspace
      admin wording and the retry CTA disabled while a retry is already in flight;
      nothing here implies SSO, audit history, admin-vs-billing-owner separation,
      broader state reconcile, or enterprise readiness shipped.'
    sent_at: '2023-12-14T10:48:00-08:00'
    user: Rishi
  - id: discord_dm_1785306030294
    message: 'Evergreen is asking who evaluates SSO/SAML and admin-side audit history.
      Keep the customer answer at functional-area level only: auth/login plus commercial/procurement
      framing for SSO; admin/product surface plus procurement/security packaging for
      audit history. No committed individual owners, owner/date pairs, delivery dates,
      or Evergreen-specific promises. Both stay next-phase backlog; live examples
      next week are fine.'
    sent_at: '2023-12-14T11:21:00-08:00'
    user: Devon Hayes
  - id: discord_dm_1785306030774
    message: 'For Evergreen’s owner-routing question, please keep it at functional-area
      level only. SSO/SAML: auth/login surface plus commercial/procurement framing.
      Admin-side audit history: admin/product surface plus procurement/security packaging.
      No named owner/date commitments, no delivery dates, and no Evergreen-specific
      promises; both remain next-phase backlog items.'
    sent_at: '2023-12-14T11:21:00-08:00'
    user: Jake
  - id: discord_dm_1785307420479
    message: 'Evergreen follow-up boundary: stay on commercial/procurement framing
      only when needed. Sarah owns the customer thread; Jake and Leo should stay on
      current product facts and seam risk. The useful output is concrete examples
      Evergreen can circulate, not named commitments: no dates, no owner/date pairs,
      no custom Evergreen promises, no enterprise add-on quotes, and no roadmap commitments.
      Keep procurement/security packaging as next-phase follow-up, not a completed
      current asset.'
    sent_at: '2023-12-18T15:44:00-08:00'
    user: Devon Hayes
  - id: discord_dm_1785307420946
    message: 'Evergreen follow-up boundary: stick to current Mercury product facts
      and seam risk. Current flow is magic-link access, org invites, preview-only
      sample data, real-source connection, and first live sync; no Evergreen-specific
      branch. Do not imply SSO/SAML, standalone admin-change audit history, separated
      admin/billing-owner roles, or fuller procurement/security packaging is current
      or shipped. Useful examples only, not named commitments.'
    sent_at: '2023-12-18T15:44:00-08:00'
    user: Jake
  - id: discord_dm_1785307421415
    message: 'Evergreen follow-up boundary: keep your input to current product facts
      and seam risk. The customer-ready answer should use concrete examples from the
      bounded current flow, with no Evergreen-specific exception path. Do not imply
      SSO/SAML, standalone admin-change audit history, separated admin/billing-owner
      roles, procurement/security packaging, or enterprise readiness has shipped.
      Useful examples only, not named commitments.'
    sent_at: '2023-12-18T15:44:00-08:00'
    user: Leo Park
  - id: discord_dm_1785307421892
    message: 'Northstar Jan. 11 prep: before the holiday break, freeze only the agenda
      and evidence index. Keep the package bounded to Mercury evidence, Evergreen
      signal, and pricing. Pull weekly activation cuts out, do not chase new data
      over the holidays, and resume actual package work on Jan. 2.'
    sent_at: '2023-12-18T16:08:00-08:00'
    user: Anna Martinez
  - id: discord_dm_1785307422363
    message: 'Northstar Jan. 11 prep: before the holiday break, freeze only the agenda
      and evidence index. Keep the package bounded to Mercury evidence, Evergreen
      signal, and pricing. Pull weekly activation cuts out, do not chase new data
      over the holidays, and resume actual package work on Jan. 2.'
    sent_at: '2023-12-18T16:08:00-08:00'
    user: Devon Hayes
  - id: discord_dm_1785307423310
    message: 'Safer support wording: the Mercury hardening release included only the
      scoped admin-setup wording fix and the live-sync retry guard. Do not mention
      Evergreen, and do not imply SSO, audit history, admin-versus-billing-owner separation,
      or enterprise readiness shipped.'
    sent_at: '2023-12-19T11:31:00-08:00'
    user: Rishi
  - id: discord_dm_1785307423793
    message: 'Same Mercury hardening boundary Rishi is getting: the release included
      only the scoped admin-setup wording fix and the live-sync retry guard. Do not
      mention Evergreen, and do not imply SSO, audit history, admin-versus-billing-owner
      separation, or enterprise readiness shipped.'
    sent_at: '2023-12-19T11:31:00-08:00'
    user: Jake
  - id: discord_dm_1785307425189
    message: 'For holiday Honeycomb alerts: keep the existing alert thresholds, page
      the named on-call owner first, and escalate to me only for confirmed customer
      impact or an unreachable owner after the documented path. If the week stays
      quiet, send a Monday digest instead.'
    sent_at: '2023-12-21T10:18:00-08:00'
    user: Marcus
  - id: discord_dm_1785308067577
    message: Keep the current Honeycomb thresholds. Page the named on-call owner first;
      escalate to me only for confirmed customer impact or an unreachable owner after
      the documented path. Otherwise put the noise in the Monday digest. Any non-urgent
      cleanup can wait for January.
    sent_at: '2023-12-26T15:18:00-08:00'
    user: Marcus
  - id: discord_dm_1785308068511
    message: Don’t pull weekly activation cuts or chase new data over the break. Prep
      resumes from the bounded agenda after January 2, 2024.
    sent_at: '2023-12-27T10:52:00-08:00'
    user: Anna Martinez
  - id: discord_dm_1785308068985
    message: Don’t pull weekly activation cuts or chase new data over the break. Prep
      resumes from the bounded agenda after January 2, 2024.
    sent_at: '2023-12-27T10:52:00-08:00'
    user: Devon Hayes
  - id: discord_dm_1785308069914
    message: Evergreen’s examples are useful, and current product facts are okay in
      January. No delivery dates, owner/date commitments, roadmap commitments, custom
      Evergreen promises, or enterprise add-on quotes now.
    sent_at: '2023-12-28T09:41:00-08:00'
    user: Devon Hayes
  - id: discord_dm_1785308070383
    message: Evergreen’s examples are useful, and current product facts are okay in
      January. No delivery dates, owner/date commitments, roadmap commitments, custom
      Evergreen promises, or enterprise add-on quotes now.
    sent_at: '2023-12-28T09:41:00-08:00'
    user: Jake
  - id: discord_dm_1785308070860
    message: Evergreen’s examples are useful, and current product facts are okay in
      January. No delivery dates, owner/date commitments, roadmap commitments, custom
      Evergreen promises, or enterprise add-on quotes now.
    sent_at: '2023-12-28T09:41:00-08:00'
    user: Leo Park
  - id: discord_dm_1785474166539
    message: Counsel can get ready on the standard legal/diligence cleanup and governance-doc
      workstreams, but we should not frame Northstar as accepted or lead until there
      is formal paper and Devon and I have said yes. Keeping this narrow — no broad
      process narrative.
    sent_at: '2024-01-17T13:06:00-08:00'
    user: Sarah Kim
  - id: discord_dm_1785474167870
    message: Priya — you can close the remaining Figma monitoring comments and move
      this back to normal support/product metrics. The shipped headline stays “Connect
      your first repo,” the teammate-invite clarification stays support-only, and
      new product-copy work needs a real metric or support-volume regression.
    sent_at: '2024-01-19T09:22:00-08:00'
    user: Priya
  - id: discord_dm_1785485378739
    message: 'Close-readiness note before the long weekend: remaining close-path items
      are board consent; Sofia/Northstar board-seat mechanics; written-consent structure;
      signature authority; holder list; notice schedules; and final signature packets.
      Feb. 22 stays a target, not a promise. No extra fundraising asks, no price-shopping
      thread, and no new diligence lane.'
    sent_at: '2024-02-16T10:02:00-08:00'
    user: Devon Hayes
  - id: discord_dm_1785485379169
    message: 'Close-readiness note before the long weekend: remaining close-path items
      are board consent; Sofia/Northstar board-seat mechanics; written-consent structure;
      signature authority; holder list; notice schedules; and final signature packets.
      Feb. 22 stays a target, not a promise. No extra fundraising asks, no price-shopping
      thread, and no new diligence lane.'
    sent_at: '2024-02-16T10:02:00-08:00'
    user: Sarah Kim
  - id: discord_dm_1785523420734
    message: You and Devon own the commercial/procurement packaging lane. Jake and
      Leo stay the source of truth for current product facts. Nothing in the reset
      creates Evergreen-specific roadmap promises, feature dates, or custom scope.
    sent_at: '2024-02-27T12:38:00-08:00'
    user: Sarah Kim
  - id: discord_dm_1785523422477
    message: While I’m away Mar 7–12, please own non-urgent investor close-out follow-up.
      If something truly material appears, flag me; otherwise keep it moving and avoid
      travel-time noise.
    sent_at: '2024-02-28T15:22:00-08:00'
    user: Devon Hayes
  - id: discord_dm_1785540287245
    message: 'Rishi — thanks for tightening the Atlas coverage note. The line stays:
      you remain Atlas owner; this is coverage cleanup, not a resignation workflow.


      By Fri Apr 5, please name backups for verifier/auth, the API v2 docs/search
      support path, and recurring support handoff edges that still default to you.
      Jake covers product-priority, sequencing, and cut decisions if you’re unavailable.
      Leo shadows verifier/auth implementation seams now and can help pull the PR-1187
      verifier note.


      Customer-facing ownership stays with the support rotation doc: urgent Atlas
      issues go to the named weekly owner with an immediate next step, not direct
      bypasses to you. For docs/search confusion, use the current GraphQL API v2 quickstart
      link: https://docs.atlas-test.com/api/v2/graphql-quickstart. No broad support
      announcement unless the routing rules themselves change.'
    sent_at: '2024-03-29T08:57:00-07:00'
    user: Rishi
  - id: discord_dm_1786405353077
    user: Devon Hayes
    message: The BART single-tracking alert is still active, so I’m starting remote
      from Oakland. Please treat my first in-person window as tentative, not late.
    sent_at: '2024-05-13T07:44:00-07:00'
  - id: discord_dm_1786405353554
    user: Rishi
    message: Anna Rao called and said Tessl is making you a real database-internals/platform
      offer. I’m not starting a counteroffer circus, but I do need transition impact
      by Atlas path before this gets any further. Please use the ownership map and
      the support/code-path notes you already wrote down, especially the areas that
      still depend on you.
    sent_at: '2024-05-17T16:21:00-07:00'
  - id: discord_dm_1786405354027
    user: Devon Hayes
    message: 'Private note: Anna’s intro may cost us someone we rely on more than
      I’d been admitting.'
    sent_at: '2024-05-17T16:21:00-07:00'
  - id: discord_dm_1786563123637
    user: Priya
    message: Priya, please pull Jake and Leo into a quick design review on the Mercury
      v0.3 role-label mismatch before implementation copy lands. The ticket cut is
      otherwise split cleanly across bounded SAML SSO login, admin audit events, and
      admin vs billing-owner surface cleanup; this is just the wording seam you flagged.
    sent_at: '2024-07-29T15:42:00-07:00'
  - id: discord_dm_1786564591091
    user: Sarah Kim
    message: '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. Please keep the Evergreen-facing wording budgetary, not
      custom.'
    sent_at: '2024-08-31T11:24:00-07:00'
  - id: discord_dm_1786565626376
    user: Sarah Kim
    message: 'Short pre-ship answer for 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.'
    sent_at: '2024-09-10T14:18:00-07:00'
  - id: discord_dm_1786940695403
    user: Sarah Kim
    message: '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.'
    sent_at: '2025-01-23T11:36:00-08:00'
  - id: discord_dm_1738174440000
    user: Sarah Kim
    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.'
    sent_at: '2025-01-29T10:14:00-08:00'
  - id: discord_dm_1743611640001
    user: Sarah Kim
    message: 'Suggested safer Evergreen pre-rotation wording:


      Evergreen team — we’re set for the April 3 SAML certificate rotation on the
      current annual Mercury Growth account. We’ll verify the shipped SAML login path
      during the window and confirm once the rotation is complete. For any workspace-admin
      support questions, please continue through this account thread and we’ll route
      the right technical owner.


      I’d keep procurement/admin follow-up out of this rotation note so we don’t imply
      new scope.'
    sent_at: '2025-04-02T09:34:00-07:00'
  - id: discord_dm_1744820760002
    user: Sarah Kim
    message: 'Please keep this as a prewrite only for now. We still need Leo’s clean
      end-to-end pass after Jake’s cache fix. If you need a placeholder internally,
      use: “Scaffold is verifying basic invited-teammate/source-owner visibility in
      the current activation path.” No date, no custom admin policy, no granular role
      editor, no advanced admin controls.'
    sent_at: '2025-04-16T09:26:00-07:00'
  - id: discord_dm_1744918080005
    user: Sarah Kim
    message: 'Use this version for your check, not for customer send until you confirm
      it’s needed: “In the current Mercury activation path, Scaffold has verified
      the basic invited-teammate/source-owner cues needed for a workspace teammate
      to move from setup guidance to source connection and first live sync.” Keep
      out: custom admin policy, granular role editor, advanced admin controls, SAML/procurement
      timing.'
    sent_at: '2025-04-17T12:28:00-07:00'
  - id: discord_dm_1745271120010
    user: Sarah Kim
    message: 'Yes, you can use the verified line now if it helps the Evergreen support
      note: “The basic invited-teammate/source-owner cues in Mercury’s current activation
      path are verified for setup guidance, source connection, and first live sync.”
      Keep it there. Do not add custom admin policy, granular role editor, advanced
      admin controls, or procurement/security language.'
    sent_at: '2025-04-21T14:32:00-07:00'
  - id: discord_dm_1746127320005
    user: Nadia Singh
    message: 'For Monday: join the Evergreen read for pattern capture, not as a new
      account owner. Sarah keeps live customer-thread continuity; Devon keeps commercial/procurement;
      product facts stay current-state only. Useful question for you is what, if anything,
      looks repeatable beyond Evergreen.'
    sent_at: '2025-05-01T12:22:00-07:00'
  - id: discord_dm_1746635880001
    user: Sarah Kim
    message: For the Evergreen account note, use current-state annual-account evidence,
      not repeatable customer-growth proof. Keep it to shipped SAML rotation, audit
      lookup, workspace-admin support, and usage; no advanced-admin/procurement or
      staffing language.
    sent_at: '2025-05-07T09:38:00-07:00'
  - id: discord_dm_1747756080000
    user: Sarah Kim
    message: 'Acme API v2 export timeout should stay in the support rotation. Please
      keep customer-thread ownership and give them a narrow status: we''re investigating
      the export timeout and will route the technical read through Leo. No founder
      side thread unless this becomes customer-impacting beyond the export path.'
    sent_at: '2025-05-20T08:48:00-07:00'
  - id: discord_dm_1747756080001
    user: Leo Park
    message: Can you take first technical read on the Acme API v2 export timeout?
      Start with the large export path and the support request IDs/timestamps, then
      hand back a concise finding plus any safe workaround. Support keeps customer
      ownership.
    sent_at: '2025-05-20T08:48:00-07:00'
  - id: discord_dm_1747756080002
    user: Jake
    message: 'Heads-up: Acme API v2 export timeout is coming through support. Leo
      has first technical read. Please keep any follow-up as bounded Atlas/API v2
      product sequencing once scoped — not Compass or Mercury unless evidence says
      otherwise.'
    sent_at: '2025-05-20T08:48:00-07:00'
  - id: discord_dm_1747847880005
    user: Sarah Kim
    message: 'Safe line for Acme: we isolated the timeout to the large API v2 export
      path, and they can continue the review using the narrower replay while we scope
      the bounded export follow-up. Please keep it date-free and support-owned; no
      full-export fix promise yet.'
    sent_at: '2025-05-21T10:18:00-07:00'
  - id: discord_dm_1747868160006
    user: Jake
    message: 'Agree with the lane: bounded Atlas/API v2 export-path follow-up after
      Acme can continue via narrower replay. Support keeps customer ownership, Leo
      owns first technical read, you own product sequencing. Let''s keep it out of
      Compass/Mercury and out of founder-direct routing.'
    sent_at: '2025-05-21T15:56:00-07:00'
  - id: discord_dm_1747928520007
    user: Sarah Kim
    message: 'For Acme: recommend they proceed with the narrower replay for the renewal-risk
      review. We should not ask them to keep retrying the full export today; the full
      export-path timeout is our bounded Atlas/API v2 follow-up. Keep it date-free
      and support-owned.'
    sent_at: '2025-05-22T08:42:00-07:00'
  - id: discord_dm_1748981220000
    user: Jake
    message: 'For tomorrow: do not reserve Mercury capacity for broader Compass work.
      The closeout may keep narrow prompt learning, but it does not authorize a dashboard,
      platform build, or Mercury sequencing change unless I explicitly reopen scope
      after the evidence read.'
    sent_at: '2025-06-03T13:07:00-07:00'
  - id: discord_dm_1749068520006
    user: Sarah Kim
    message: 'Customer-safe Compass line after the closeout: we are using internal
      prompt learning to improve account follow-up. Do not describe Compass as a customer-facing
      workflow, launch, roadmap item, GTM proof, or source of new customer materials.
      Evergreen stays current-state/account-thread context; Acme stays live-only on
      its own signals and gets no Evergreen-derived examples or written customer-specific
      materials.'
    sent_at: '2025-06-04T13:22:00-07:00'
  - id: discord_dm_1749141360007
    user: Nadia Singh
    message: 'Keep the scripts, but only as internal prompt/prep learning for now.
      The closeout was clear: they improved account-team prep, but they did not create
      a sales wedge or repeatable customer action. In the weekly read, please label
      them as internal behavior-read inputs and keep any stronger GTM/customer-facing
      claim out until the evidence changes.'
    sent_at: '2025-06-05T09:36:00-07:00'
  - id: discord_dm_1749594480002
    user: Sarah Kim
    message: 'Keep Evergreen routing unchanged for now: you own the customer thread,
      Devon owns commercial/procurement framing, and customer-facing follow-up should
      stay on current product facts only. Do not mention the private role-fit conversation
      or imply any owner-story change while Morgan/Devon/Nadia are still working through
      it.'
    sent_at: '2025-06-10T15:28:00-07:00'
  - id: discord_dm_1750115880015
    user: Devon Hayes
    message: 'Status after today''s Nadia handoffs: Sarah has the scripts/account-thread
      hygiene pieces; Anna has the behavior-read and evidence-caveat context. Nadia
      is still here through Jun 20. Remaining work: Sarah thin-note pass, HR closeout,
      final team note. I want the narrative restrained — role fit / next phase, not
      villain story, not Compass/GTM proof language, and no replacement-search loop.'
    sent_at: '2025-06-16T16:18:00-07:00'
  - id: discord_dm_1750175520001
    user: Sarah Kim
    message: Saved the thin-note pass. Use the marked scripts for account-thread hygiene
      only; anything undated/source-thin stays internal prep. Evergreen stays current-state/account-specific,
      Acme stays live-only. No customer-facing Compass material or owner-story change.
    sent_at: '2025-06-17T08:52:00-07:00'
  - id: discord_dm_1750263600004
    user: Nadia Singh
    message: I saved the final handoff packet. The scripts and behavior-read context
      are preserved with Sarah/Anna, and we’ll keep the narrative role-fit / next
      phase — not blame, not Compass proof, and not a new customer-owner story.
    sent_at: '2025-06-18T09:20:00-07:00'
  - id: discord_dm_1750724280014
    user: Devon Hayes
    message: 'Appreciate it, but don’t take an overnight board-cleanup pass. I’m routing
      nonurgent cleanup by owner this week: Jake/Mercury, Leo/Atlas + seams, Anna/evidence,
      Sarah/account thread, you only for commercial/procurement context where it’s
      actually needed. I’ll hold the board/customer narrative.'
    sent_at: '2025-06-23T17:18:00-07:00'
  - id: discord_dm_1750895340005
    user: Devon Hayes
    message: 'Thanks for offering the overnight cleanup pass. Please don’t take it
      tonight. I’m routing the remaining board-cycle cleanup by owner: Jake/Mercury,
      Leo/Atlas seams, Anna/evidence, Sarah/account threads, you only for commercial/procurement
      context where it’s actually needed. I’ll hold the board/customer narrative.'
    sent_at: '2025-06-25T16:49:00-07:00'
  - id: discord_dm_1751296980014
    user: Devon Hayes
    message: I put the July pause and owner split in writing. You’re away from day-to-day
      July 1–31; true emergencies only. I’ll hold board/customer narrative instead
      of using you as the default second brain.
    sent_at: '2025-06-30T08:23:00-07:00'
  - id: discord_dm_1751296980015
    user: Jake
    message: 'July coverage note while Devon is fully away from day-to-day: you own
      Mercury sequencing. Keep decisions in the normal Mercury lane and escalate only
      if a true emergency genuinely needs Devon.'
    sent_at: '2025-06-30T08:23:00-07:00'
  - id: discord_dm_1751296980016
    user: Leo Park
    message: 'July coverage note while Devon is fully away from day-to-day: you own
      platform seams and Atlas first technical reads. Support still keeps customer
      ownership; Jake owns product priority/sequencing.'
    sent_at: '2025-06-30T08:23:00-07:00'
  - id: discord_dm_1751296980017
    user: Priya
    message: 'July coverage note while Devon is fully away from day-to-day: you own
      Mercury activation/onboarding quality. This is coverage clarity, not a reorg
      or new scope.'
    sent_at: '2025-06-30T08:23:00-07:00'
  - id: discord_dm_1751296980018
    user: Anna Martinez
    message: 'July coverage note while Devon is fully away from day-to-day: you own
      retention and Compass evidence quality, including definitions, caveats, and
      what not to overclaim.'
    sent_at: '2025-06-30T08:23:00-07:00'
  - id: discord_dm_1751296980019
    user: Sarah Kim
    message: 'July coverage note while Devon is fully away from day-to-day: you own
      Evergreen customer-thread continuity. Keep customer wording current-state; route
      commercial/procurement context to Devon only if it is truly needed.'
    sent_at: '2025-06-30T08:23:00-07:00'
  - id: discord_dm_1751382720000
    user: Sarah Kim
    message: Keep Evergreen questions in your thread during Devon's July pause. If
      something asks for custom scope or dates, bring it to me + Jake; don't route
      to Devon unless it's a true founder-level emergency.
    sent_at: '2025-07-01T08:12:00-07:00'
  - id: discord_dm_1751382720001
    user: Leo Park
    message: For July Atlas reads, keep support as intake. Take the first technical
      read once support has a named owner + immediate next step; loop Jake only when
      there is a product sequencing question. Devon stays emergency-only.
    sent_at: '2025-07-01T08:12:00-07:00'
  - id: discord_dm_1751470860003
    user: Sarah Kim
    message: 'Hold this in the July owner split: you keep the Evergreen thread; no
      Devon route. Please don''t answer custom admin policy yet. I''m asking Jake
      for product-scope confirmation, then we''ll give current-state wording only.'
    sent_at: '2025-07-02T08:41:00-07:00'
  - id: discord_dm_1751470860004
    user: Jake
    message: 'Evergreen is asking whether granular custom admin policy for an additional
      admin group can be folded into the annual Growth baseline. Can you confirm current
      Mercury scope? My read: current shipped SAML, invite/source/admin audit lookup,
      workspace-admin support, basic admin-role setup; no custom admin policy commitment.'
    sent_at: '2025-07-02T08:41:00-07:00'
  - id: discord_dm_1751476680005
    user: Sarah Kim
    message: 'Customer-safe line: current annual Growth baseline covers shipped SAML
      login, visible invite/source/admin audit lookup, workspace-admin support, and
      basic admin-role setup. We are not committing granular custom admin policy or
      an advanced role editor into the annual baseline. Log the ask as Q3 enterprise-readiness
      evidence, not a blocker to current Mercury use. Devon stays out of this route
      unless there is a true emergency.'
    sent_at: '2025-07-02T10:18:00-07:00'
  - id: discord_dm_1751567760008
    user: Leo Park
    message: Push vague Atlas/API v2 side-channel reports back through support first.
      Once support has a named owner + immediate next step, you take the first technical
      read. Jake comes in only for bounded product sequencing. Devon is not the default
      route.
    sent_at: '2025-07-03T11:36:00-07:00'
  - id: discord_dm_1751902080000
    user: Anna Martinez
    message: Use the July scratchpad, but split sightings from evidence. Raw prompt
      sightings can be logged as observations. For the Q3 read, a row only counts
      if it has dated owner follow-up, evidence source, caveat, and outcome. No owner
      action = not proof, not staffing input.
    sent_at: '2025-07-07T08:28:00-07:00'
  - id: discord_dm_1751902080001
    user: Sarah Kim
    message: 'For July Compass rows: log raw sightings if useful, but only dated owner
      follow-up with source, caveat, and outcome counts for the Q3 evidence read.
      Account-thread context stays bounded; no customer-facing proof language.'
    sent_at: '2025-07-07T08:28:00-07:00'
  - id: discord_dm_1751922960002
    user: Jake
    message: Keep Acme export weirdness out of Mercury unless it changes the activation/admin
      path. Route it support first; Leo takes the first technical read once support
      has an owner + next step; you come in only for bounded Atlas/API v2 sequencing.
      Devon is true-emergency-only.
    sent_at: '2025-07-07T14:16:00-07:00'
  - id: discord_dm_1751988180004
    user: Sarah Kim
    message: Keep Acme in the support/customer thread. Acknowledge the two API v2
      large-export timeouts, say we're checking the export path and narrower replay
      option, and do not promise a fix date or route through Devon. Pull Leo for first
      technical read.
    sent_at: '2025-07-08T08:23:00-07:00'
  - id: discord_dm_1751988180005
    user: Leo Park
    message: 'Acme reported two more API v2 large-export timeouts from the 90-day
      nested-field export path. Please take the first technical read through support:
      isolate path, check whether narrower replay completes, and say explicitly if
      you see any data-integrity signal. Not a broad Atlas memo.'
    sent_at: '2025-07-08T08:23:00-07:00'
  - id: discord_dm_1751988180006
    user: Jake
    message: 'Heads-up only: Acme has a July recurrence of API v2 large-export timeouts.
      Keep out of Mercury/Compass for now. Leo is doing first technical read; I''ll
      pull you in only for bounded Atlas/API v2 sequencing once scoped.'
    sent_at: '2025-07-08T08:23:00-07:00'
  - id: discord_dm_1751994360007
    user: Sarah Kim
    message: 'Safe line for Greg: ‘We saw the two 90-day API v2 export timeouts and
      are checking the large-export path now. For the account-health review, keep
      using the narrower replay/export path while we verify the full-range behavior.
      We have not identified a data-loss issue from the report so far, but we are
      still validating and will update you through this thread.’ No fix date yet.'
    sent_at: '2025-07-08T10:06:00-07:00'
  - id: discord_dm_1752081480010
    user: Sarah Kim
    message: 'Acme-safe update: ‘We traced the failures to the large-export path for
      the long date range with nested fields. The narrower replay completed, and our
      checks did not identify corrupt exported data in those replay results. Keep
      using the narrower replay while we finish scoping the full-range timeout follow-up.
      We’re not promising a fix date yet.’'
    sent_at: '2025-07-09T10:18:00-07:00'
  - id: discord_dm_1752081480011
    user: Jake
    message: 'Leo’s first read: Acme recurrence is cursor-paginated large-export timeout
      on long range + nested fields; auth/webhook/connector not implicated; narrower
      replay completed with no corrupt data found. Can you take this as a bounded
      Atlas/API v2 export-path sequencing item if chunking/backoff holds? Not Mercury/Compass.'
    sent_at: '2025-07-09T10:18:00-07:00'
  - id: discord_dm_1752098580012
    user: Anna Martinez
    message: Log the Acme row only as ‘prompt sighting + dated support handoff’ if
      Sarah attaches the source/date/caveat. Caveat must say the live issue is Atlas/API
      v2 export timeout, not Compass proof. It should not count as customer-initiated
      Compass action.
    sent_at: '2025-07-09T15:03:00-07:00'
  - id: discord_dm_1752098580013
    user: Sarah Kim
    message: 'For the Acme Compass row, attach the support handoff source/date if
      useful, but keep the caveat explicit: Atlas/API v2 export issue, live handling
      through support + Leo, not customer-facing Compass proof or a new customer material.'
    sent_at: '2025-07-09T15:03:00-07:00'
  - id: discord_dm_1752165240014
    user: Jake
    message: Yes — take Acme as bounded Atlas/API v2 export-path sequencing if Leo’s
      chunking/backoff confirmation holds. Keep it out of Mercury/Compass and no ship-date
      promise to Acme yet.
    sent_at: '2025-07-10T09:34:00-07:00'
  - id: discord_dm_1752165240015
    user: Leo Park
    message: Jake is aligned to a bounded Atlas/API v2 export-path follow-up if your
      chunking/backoff confirmation holds. Please finish the replay/verification note
      with the data-integrity line explicit.
    sent_at: '2025-07-10T09:34:00-07:00'
  - id: discord_dm_1752165240016
    user: Sarah Kim
    message: 'Owner line for Acme: support/customer thread stays with you, Leo owns
      technical verification, Jake owns bounded Atlas/API v2 sequencing once confirmed.
      No Mercury/Compass framing and no ship-date promise yet.'
    sent_at: '2025-07-10T09:34:00-07:00'
  - id: discord_dm_1752250320021
    user: Sarah Kim
    message: 'Final Acme support-safe line: ‘We traced the July failures to the API
      v2 large-export path for long ranges with nested fields. The narrower replay
      completed, and our checks did not identify customer-visible data loss or corrupt
      exported data. We’ve queued a bounded chunking/backoff follow-up for the full-range
      export path; no ship date to promise yet.’'
    sent_at: '2025-07-11T09:12:00-07:00'
  - id: discord_dm_1752458880027
    user: Anna Martinez
    message: 'For Monday’s Compass first pass, use the structured rows: account, prompt
      type/date, owner, evidence source, caveat, dated owner follow-up, outcome. Sightings
      alone stay raw observations. Acme export stays Atlas context.'
    sent_at: '2025-07-13T19:08:00-07:00'
  - id: discord_dm_1752458880028
    user: Sarah Kim
    message: For Monday’s Compass first pass, please attach source/date/caveat to
      any Evergreen or Acme rows. Evergreen stays current-state account-thread context;
      Acme export stays Atlas/API v2 support context. No customer-facing Compass proof
      language.
    sent_at: '2025-07-13T19:08:00-07:00'
  - id: discord_dm_1752615060003
    user: Leo Park
    message: 'Agree with your read. For tomorrow: Acme can stay in the table only
      as a dated support/owner handoff with caveats. It is Atlas/API v2 context, not
      Compass proof or customer behavior-change evidence.'
    sent_at: '2025-07-15T14:31:00-07:00'
  - id: discord_dm_1752615060004
    user: Jake
    message: Agree. Keep Compass implementation at prompt-level tracking for tomorrow's
      read. No dashboard rebuild, no Atlas work under Compass, and no Mercury activation/admin
      scope from the Acme row.
    sent_at: '2025-07-15T14:31:00-07:00'
  - id: discord_dm_1752700140008
    user: Sarah Kim
    message: 'Keep Evergreen customer-facing language as normal current-state support/account
      continuity. Do not mention Compass or the internal evidence read. You can say
      we are keeping the current setup guidance clear: shipped SAML, workspace setup,
      teammate/source-owner cues, first live sync support path. No advanced-admin
      promise, no product claim, no ''Compass surfaced this'' line.'
    sent_at: '2025-07-16T14:09:00-07:00'
  - id: discord_dm_1752784980010
    user: Priya
    message: Treat this as activation/onboarding quality for now, not an admin-role
      model bug. Please collect a few concrete excerpts with the visible product state
      and exact copy they paused on. Do not reopen custom admin policy or role-editor
      scope. Loop Jake if the pattern repeats with evidence; no product change ask
      yet.
    sent_at: '2025-07-17T13:43:00-07:00'
  - id: discord_dm_1753121160002
    user: Priya
    message: This is a real signal, but keep it in activation quality for now. Please
      keep collecting concrete excerpts plus the visible product state for each clip.
      Do not reopen admin-role scope. Do not loop Jake yet unless the pattern repeats
      with enough evidence that we can ask a bounded copy/product-state question rather
      than an admin-model question.
    sent_at: '2025-07-21T11:06:00-07:00'
  - id: discord_dm_1753136520003
    user: Anna Martinez
    message: Keep this as evidence quality, not a dashboard pass. The July read gave
      us owner follow-up hygiene, not behavior proof. If the row shape is hard to
      use, note what is hard and what an owner needs in one place; do not ask Jake
      for implementation or a new view yet.
    sent_at: '2025-07-21T15:22:00-07:00'
  - id: discord_dm_1753296480008
    user: Sarah Kim
    message: 'Use the narrow version: Evergreen accepted the current setup/admin-support
      path for now, and the July admin-policy question stayed contained without a
      roadmap promise. Useful account-thread hygiene and enterprise-readiness context;
      not repeatable customer-growth proof, not an advanced-admin commitment, and
      not a staffing trigger.'
    sent_at: '2025-07-23T11:48:00-07:00'
  - id: discord_dm_1753379820013
    user: Jake
    message: 'Yes. The line is: Mercury remains important, but the second eng req
      stays closed because the current owner split is holding and we do not have stronger
      September operating evidence yet. Do not frame it as deprioritizing Mercury
      or asking Leo to absorb everything; keep asks bounded to sequencing, platform
      seams, and activation quality.'
    sent_at: '2025-07-24T10:57:00-07:00'
  - id: discord_dm_1753456680017
    user: Priya
    message: 'Yes — preserve this as a tighter sample packet. Current boundary: activation-copy
      evidence, not an admin-model bug. Do not reopen admin-role scope, and do not
      loop Jake as a product escalation yet. If we bring him in, it should be a bounded
      copy/product-state review with the clips and excerpts attached.'
    sent_at: '2025-07-25T08:18:00-07:00'
  - id: discord_dm_1753733220004
    user: Priya
    message: 'Yes — keep these as activation-copy evidence. The packet should stay
      anchored on: source-owner cue visible, product state correct, pause happens
      at the setup-guide/admin sentence. No admin-model change and no immediate Jake
      escalation. If we bring Jake in, it should be a bounded copy/product-state review
      with clips/excerpts attached.'
    sent_at: '2025-07-28T13:07:00-07:00'
  - id: discord_dm_1753803960006
    user: Anna Martinez
    message: This cleanup works as structured evidence rows, not a dashboard request.
      Keep rows 1, 2, and 5 as usable dated owner follow-up with caveats; reject 3
      and 6 as thin unless Sarah can attach source/date/owner; keep Acme as Atlas/API
      v2 context only. No product implementation scope from this pass.
    sent_at: '2025-07-29T08:46:00-07:00'
  - id: discord_dm_1753900680010
    user: Devon Hayes
    message: 'Captured the re-entry shape: first full August workweek, narrow lane
      — commercial/procurement context and true cofounder judgment calls. Not a snapback
      to you as default second brain for board cleanup, customer narrative, or every
      owner ambiguity. I’ll keep the owner DMs boring and clear.'
    sent_at: '2025-07-30T11:38:00-07:00'
  - id: discord_dm_1753900680011
    user: Jake
    message: 'Devon’s August return shape is set: he’s back next week in a narrow
      commercial/procurement + true cofounder-judgment lane, not as a default tiebreaker.
      Please keep owning Mercury sequencing for operating work; route to Devon only
      if the question genuinely needs founder/commercial judgment.'
    sent_at: '2025-07-30T11:38:00-07:00'
  - id: discord_dm_1753900680012
    user: Leo Park
    message: Devon’s August return is narrow, not a reset of the Atlas split. Please
      keep owning platform seams and Atlas first technical reads for operating work;
      Devon is for commercial/procurement context or true cofounder judgment calls,
      not normal technical triage.
    sent_at: '2025-07-30T11:38:00-07:00'
  - id: discord_dm_1753900680013
    user: Priya
    message: Devon’s August return shape is set and does not change your activation/onboarding
      quality lane. Keep the Mercury activation-copy work with you; if Jake/Leo join,
      it’s for bounded review, not a Devon-routed admin-model reopen.
    sent_at: '2025-07-30T11:38:00-07:00'
  - id: discord_dm_1753900680014
    user: Anna Martinez
    message: Devon’s August return is narrow and does not change your retention/Compass
      evidence-quality lane. Keep Compass in structured evidence rows with caveats;
      Devon is not the default second brain for evidence cleanup or dashboard/product-scope
      questions.
    sent_at: '2025-07-30T11:38:00-07:00'
  - id: discord_dm_1753900680015
    user: Sarah Kim
    message: 'Devon’s August return shape is set: narrow commercial/procurement context
      plus true cofounder judgment calls. You keep Evergreen customer-thread continuity
      for operating work. Loop Devon when the question is genuinely commercial/procurement
      framing, not for routine current-state support wording.'
    sent_at: '2025-07-30T11:38:00-07:00'
  - id: discord_dm_1753910160017
    user: Sarah Kim
    message: 'For Acme: safe line is ‘we’re validating the bounded API v2 large-export
      reliability follow-up; the Acme-shaped replay is improving but not clean enough
      for a customer-ready statement yet.’ Please do not say we expect to ship this
      week or give a fix date.'
    sent_at: '2025-07-30T14:16:00-07:00'
  - id: discord_dm_1754061840021
    user: Sarah Kim
    message: Please wait for the first full August workweek and keep the lane narrow.
      You keep Evergreen customer-thread continuity; loop Devon next week only for
      real commercial/procurement framing or true cofounder judgment, not routine
      current-state support wording.
    sent_at: '2025-08-01T08:24:00-07:00'
  - id: discord_dm_1754061840022
    user: Jake
    message: 'Do not turn today into a quiet snapback. Keep Mercury sequencing with
      you. Devon’s return starts in the first full August workweek and stays narrow:
      commercial/procurement context + true cofounder judgment calls, not routine
      sequencing cleanup.'
    sent_at: '2025-08-01T08:24:00-07:00'
  - id: discord_dm_1754068260023
    user: Sarah Kim
    message: 'Acme wording: ‘We’re seeing improved staging results on the bounded
      API v2 large-export reliability path, including completed Acme-shaped replays
      with matching row counts. We still have one validation case and log review open,
      so we’re not calling it fixed or giving a production date yet.’'
    sent_at: '2025-08-01T10:11:00-07:00'
  - id: discord_dm_1754320140000
    user: Jake
    message: Keep Mercury sequencing and tomorrow’s activation-copy review in the
      Jake/Priya/Leo lane. Devon’s back in a narrow August lane, not as the default
      tiebreaker. Pull him only if there’s a true cofounder judgment call or commercial/procurement
      context Morgan/Devon need to hold.
    sent_at: '2025-08-04T08:09:00-07:00'
  - id: discord_dm_1754320140001
    user: Sarah Kim
    message: Keep Evergreen customer-thread continuity with you. If procurement/security
      asks about advanced admin, use current-state/basic admin wording and pull Devon
      only for commercial/procurement framing — no feature-date promise, no Devon-as-default-route.
    sent_at: '2025-08-04T08:09:00-07:00'
  - id: discord_dm_1754328360003
    user: Sarah Kim
    message: 'Acme wording for now: Monday staging validation completed cleanly and
      row counts matched replay checks. Still say production ship and Acme rerun are
      pending. Don’t call it fixed/closed yet, don’t promise a date, and keep it in
      the support + Leo + Jake Atlas route.'
    sent_at: '2025-08-04T10:26:00-07:00'
  - id: discord_dm_1754341500005
    user: Anna Martinez
    message: 'Accepted the Aug 4 cleanup as evidence-row hygiene: 5 usable internal
      rows, 2 rejected/thin. Boundary stays the same — no dashboard, no customer-facing
      proof, no GTM/staffing implication, and no prototype decision from today’s pass.
      Acme stays Atlas context.'
    sent_at: '2025-08-04T14:05:00-07:00'
  - id: discord_dm_1754417220007
    user: Priya
    message: 'Captured Aug 5 outcome: likely setup-guide/admin copy confusion; product
      state correct; no platform mismatch. Next step is copy-only alternate tested
      against the July clips. No shipped-fix language yet and no admin-model/custom-policy/granular-permissions
      scope.'
    sent_at: '2025-08-05T11:07:00-07:00'
  - id: discord_dm_1754417220008
    user: Jake
    message: 'Mercury review record is bounded: product state correct, likely copy
      hierarchy issue, Priya owns copy-only alternate. No admin-model reopen and no
      sequencing escalation unless the copy test finds a real product-state mismatch.'
    sent_at: '2025-08-05T11:07:00-07:00'
  - id: discord_dm_1754417220009
    user: Leo Park
    message: 'Captured your read: no Atlas/platform mismatch visible in the activation-copy
      samples. Keeping this out of Atlas scope unless Priya’s copy-only test exposes
      a real platform/product-state mismatch.'
    sent_at: '2025-08-05T11:07:00-07:00'
  - id: discord_dm_1754434920012
    user: Sarah Kim
    message: 'Safe Acme wording: ‘We’ve shipped a bounded API v2 change for the long-range
      export path and would like you to rerun the same 90-day export when convenient.
      We’ll compare completion + row counts against the replay checks before calling
      this closed.’ Don’t say fixed yet; keep Leo/Jake internal.'
    sent_at: '2025-08-05T16:02:00-07:00'
  - id: discord_dm_1754494020013
    user: Sarah Kim
    message: 'Yes: tell Greg to treat Thursday as the validation rerun of the same
      90-day export. Ask them to keep the narrower monthly workaround until the run
      completes and row counts are compared. We’re not calling it fixed/closed until
      completion + counts are confirmed.'
    sent_at: '2025-08-06T08:27:00-07:00'
  - id: discord_dm_1754584560017
    user: Sarah Kim
    message: 'Acme status: rerun completed, but counts are pending. Please don’t close
      the support thread or say no data loss until their row-count output matches
      the replay/monthly checks.'
    sent_at: '2025-08-07T09:36:00-07:00'
  - id: discord_dm_1754584560018
    user: Leo Park
    message: 'Captured: prod rerun completed and telemetry clean, but closure waits
      for row-count comparison. No no-data-loss statement until counts match.'
    sent_at: '2025-08-07T09:36:00-07:00'
  - id: discord_dm_1754584560019
    user: Jake
    message: Keeping Acme as completed-rerun/counts-pending. No closure language yet;
      once counts match, we can close as bounded Atlas/API v2 fix.
    sent_at: '2025-08-07T09:36:00-07:00'
  - id: discord_dm_1754596320020
    user: Priya
    message: 'Finish the copy-only alternate + side-by-side against the July clips
      first. Don’t ship the wording this week just because the direction looks right.
      Boundary stays: clarify source-owner action, no admin-model/custom-policy/granular-permissions
      change.'
    sent_at: '2025-08-07T12:52:00-07:00'
  - id: discord_dm_1754936040002
    user: Priya
    message: 'Good direction. For the review, bring the side-by-side clips, the exact
      old/new sentence, and whether the source-owner cue was visible in each clip.
      Keep it copy-only: no admin-model, custom-policy, granular-permissions, or Atlas
      scope.'
    sent_at: '2025-08-11T11:14:00-07:00'
  - id: discord_dm_1755109920008
    user: Jake
    message: 'Approved scope: internal Compass owner-action prototype for September.
      Only renewal-risk/admin-friction + post-first-live-sync prompts; next action,
      evidence/caveat drawer, owner-action status. No dashboard or customer surface.'
    sent_at: '2025-08-13T11:32:00-07:00'
  - id: discord_dm_1755109920009
    user: Anna Martinez
    message: 'You own the Compass evidence threshold for the September prototype.
      Please keep thin-note rejection explicit: no source/date/caveat means no usable
      owner action, not a prettier row.'
    sent_at: '2025-08-13T11:32:00-07:00'
  - id: discord_dm_1755109920010
    user: Sarah Kim
    message: For Compass September prototype prep, please supply account-thread examples
      for the two approved prompt families only. Keep examples tied to source/excerpt/caveat;
      no customer-facing Compass wording.
    sent_at: '2025-08-13T11:32:00-07:00'
  - id: discord_dm_1755109920011
    user: Leo Park
    message: 'Please check the Compass data/platform seams before the September readout:
      source recency, caveat visibility, and whether owner-action status can be trusted.
      Acme export stays Atlas context, not Compass proof.'
    sent_at: '2025-08-13T11:32:00-07:00'
  - id: discord_dm_1755188640014
    user: Priya
    message: 'This is the right bounded fix. Please make the setup-guide copy-only
      change with Jake/Leo’s confirmations attached. Keep the final note explicit:
      product state correct, no platform mismatch, no admin-model or granular-permissions
      scope.'
    sent_at: '2025-08-14T09:24:00-07:00'
  - id: discord_dm_1755273360019
    user: Priya
    message: 'Recorded the Mercury copy fix as activation-quality improvement: source-owner
      action clarity only, no admin-model change. Nice tight closeout.'
    sent_at: '2025-08-15T08:56:00-07:00'
  - id: discord_dm_1755273360020
    user: Jake
    message: 'Mercury copy-fix record is updated with your boundary: product state
      correct, basic invite/source-owner/admin path unchanged, no custom admin policy
      or granular role scope.'
    sent_at: '2025-08-15T08:56:00-07:00'
  - id: discord_dm_1755273360021
    user: Leo Park
    message: 'Mercury copy-fix record includes your confirmation: no platform mismatch
      and no Atlas/auth change. Treat this as setup-guide wording clarity only.'
    sent_at: '2025-08-15T08:56:00-07:00'
  - id: discord_dm_1755284880023
    user: Sarah Kim
    message: 'Customer-safe wording: the setup-guide copy now makes the current source-owner
      action clearer for invited teammates. Product/admin model did not change: basic
      invite/source-owner/admin path only; no custom admin policy, granular role editor,
      advanced-admin commitment, or procurement/security add-on promise.'
    sent_at: '2025-08-15T12:08:00-07:00'
  - id: discord_dm_1755530640001
    user: Jake
    message: 'Compass prototype criteria for today: keep it internal; fields are account,
      prompt_type, owner, next_action, evidence_source, caveat, owner_action_status.
      Use statuses not_started / done / rejected_thin_source_or_date / blocked_waiting_customer_follow_up.
      Keep rejected-thin rows visible so Anna can count weak evidence. No due-date
      field unless there is a real dated owner follow-up. No dashboard or customer-facing
      surface.'
    sent_at: '2025-08-18T08:24:00-07:00'
  - id: discord_dm_1755530640002
    user: Anna Martinez
    message: 'I wrote the Compass prototype execution criteria. Key point for your
      lane: rejected-thin rows stay visible and countable; missing source/date should
      be a rejected evidence row, not silently dropped. September readout stays owner-action
      quality/completion with caveats, not customer behavior proof.'
    sent_at: '2025-08-18T08:24:00-07:00'
  - id: discord_dm_1755530640003
    user: Sarah Kim
    message: For Compass examples this week, please keep rows to account, prompt type,
      source/date excerpt, caveat, owner, next action, and current status. If source/date
      is too thin, mark it that way; do not rescue the row with narrative. Acme export
      stays Atlas/API v2 context, not Compass proof.
    sent_at: '2025-08-18T08:24:00-07:00'
  - id: discord_dm_1755530640004
    user: Leo Park
    message: 'Compass prototype criteria are written. For your seam check: internal
      owner tool only, evidence source/caveat visible, rejected-thin rows preserved.
      No dashboard, customer-facing surface, or new data-platform scope unless you
      see a real seam blocker.'
    sent_at: '2025-08-18T08:24:00-07:00'
  - id: discord_dm_1755548220006
    user: Sarah Kim
    message: Cleaned the Compass examples. Evergreen Aug 14 post-first-live-sync row
      is usable with the caveat visible. Acme export should stay Atlas/API v2 context,
      not Compass proof. The Evergreen admin-policy note is too thin until you attach
      the actual customer source/date/excerpt — keep it rejected-thin rather than
      smoothing it over.
    sent_at: '2025-08-18T13:17:00-07:00'
  - id: discord_dm_1755618480008
    user: Anna Martinez
    message: 'Turned your Compass threshold into the reference note. I agree: completed
      owner action needs owner + dated next action + evidence source + caveat + status.
      Rejected-thin rows should count visibly; customer behavior proof is not expected
      from this prototype.'
    sent_at: '2025-08-19T08:48:00-07:00'
  - id: discord_dm_1755618480009
    user: Jake
    message: For Compass implementation, please make rejected-thin a first-class owner_action_status,
      not a hidden note. September readout needs completed / rejected-thin / waiting
      separated. This is still internal owner-action evidence only, no dashboard or
      customer-facing proof.
    sent_at: '2025-08-19T08:48:00-07:00'
  - id: discord_dm_1755704280013
    user: Sarah Kim
    message: 'Do not answer Evergreen yet. Split the ask: (1) whether treasury ops
      can test current Mercury flow under the existing annual Growth account, and
      (2) custom admin-policy date. We can only answer current shipped path after
      Jake confirms scope and Devon confirms commercial framing. No admin-policy date
      or advanced-admin promise.'
    sent_at: '2025-08-20T08:38:00-07:00'
  - id: discord_dm_1755704280014
    user: Jake
    message: 'Evergreen asks if a second internal department can test the Mercury
      path under the existing annual Growth account, plus they again ask for a custom
      admin-policy date. Please confirm current product commitments only: workspace
      setup, teammate invite/source-owner path, first source connection, first live
      sync. No custom admin policy, granular role editor, or broader advanced-admin
      scope.'
    sent_at: '2025-08-20T08:38:00-07:00'
  - id: discord_dm_1755704280015
    user: Devon Hayes
    message: Evergreen wants a second internal department to test current Mercury
      flow under the existing annual Growth account, and separately asks for a custom
      admin-policy date. Can you give commercial framing only on whether the test
      can sit under the existing annual Growth account? Product/date boundary stays
      with Jake/current shipped scope; no advanced-admin package or date promise.
    sent_at: '2025-08-20T08:38:00-07:00'
  - id: discord_dm_1755714420016
    user: Sarah Kim
    message: 'Customer-safe line for Evergreen: treasury operations can test the current
      Mercury setup flow under the existing annual Growth account, limited to workspace
      setup, teammate invite/source-owner path, first source connection, and first
      live sync. The current setup-guide wording clarifies source-owner action, but
      the product/admin model has not changed. We are not providing a custom admin-policy
      date, granular role editor, broader advanced-admin controls, or procurement/security
      add-on commitment. Devon''s input is commercial framing only; Jake owns product
      scope.'
    sent_at: '2025-08-20T11:27:00-07:00'
  - id: discord_dm_1755791640020
    user: Sarah Kim
    message: 'Evergreen closeout recorded. Customer-safe boundary going forward: treasury
      ops can test current Mercury flow under the existing annual Growth account —
      setup, invite/source-owner path, first source, first live sync only. No custom
      admin-policy date, granular role editor, advanced-admin controls, or procurement/security
      promise.'
    sent_at: '2025-08-21T08:54:00-07:00'
  - id: discord_dm_1755791640021
    user: Jake
    message: 'Evergreen second-department closeout is recorded with your scope line:
      current shipped Mercury path only — workspace setup, teammate invite/source-owner
      path, first source connection, first live sync. No admin-policy or granular-role
      scope reopened.'
    sent_at: '2025-08-21T08:54:00-07:00'
  - id: discord_dm_1755791640022
    user: Devon Hayes
    message: Evergreen closeout is recorded with you in commercial framing only. Second
      department can test current flow under the existing annual Growth account; no
      paid expansion package, advanced-admin quote, custom admin-policy date, or product/customer-thread
      ownership shift.
    sent_at: '2025-08-21T08:54:00-07:00'
  - id: discord_dm_1755876780025
    user: Jake
    message: Compass prototype shape looks right. Please add Leo's source-freshness
      warning when account note is older than owner action. Keep rejected_thin_source_or_date
      visible in readout counts. This is implementation progress only — not a prototype
      result, dashboard, or customer-facing proof.
    sent_at: '2025-08-22T08:33:00-07:00'
  - id: discord_dm_1756135140001
    user: Jake
    message: Good progress on the owner-action prototype. Please treat Sarah's seeded
      rows as flow-test data only, add Leo's source-freshness warning before owner
      use, and keep rejected_thin_source_or_date rows visible. Do not call this a
      readout result yet.
    sent_at: '2025-08-25T08:19:00-07:00'
  - id: discord_dm_1756143840002
    user: Sarah Kim
    message: 'For Evergreen treasury ops, keep the setup note to current Mercury flow
      only: workspace setup, invited teammate/source-owner path, first source connection,
      and first live sync under the existing Growth account. Do not include a granular
      role-editor date, custom admin policy, advanced-admin controls, or procurement/security
      add-on language. If they ask, say those remain separate roadmap/commercial topics,
      not part of this current-flow test.'
    sent_at: '2025-08-25T10:44:00-07:00'
  - id: discord_dm_1756223520005
    user: Jake
    message: 'Use Leo''s version: source_freshness_warning when the evidence source
      predates the owner-action timestamp. Treat it as a caveat, not auto-reject.
      Rejected_thin_source_or_date is only for rows where the source/date is too thin
      to support the action.'
    sent_at: '2025-08-26T08:52:00-07:00'
  - id: discord_dm_1756235760006
    user: Sarah Kim
    message: Yes, you can reuse the updated Mercury setup-guide wording for Evergreen
      treasury ops, but keep it to the current invited teammate/source-owner flow.
      Do not describe it as a permissions-model change, granular role editor, custom
      admin policy, or Atlas/platform commitment.
    sent_at: '2025-08-26T12:16:00-07:00'
  - id: discord_dm_1756310760008
    user: Sarah Kim
    message: 'Scheduled Sept 17 at 10 PT. I kept the body to current-flow setup under
      the existing Growth account: workspace setup, invited teammate/source-owner
      path, first source connection, and first live sync. Jake/Leo are optional support
      only. No custom admin policy, granular role editor, advanced-admin, or procurement/security
      commitment in the invite.'
    sent_at: '2025-08-27T09:06:00-07:00'
  - id: discord_dm_1756481820014
    user: Jake
    message: 'Looks ready for next week''s internal owner pilot. Please keep the instructions
      explicit: seed examples are not evidence, done requires source + caveat, source_freshness_warning
      is a caveat, and rejected-thin rows stay visible. Still not a readout result.'
    sent_at: '2025-08-29T08:37:00-07:00'
  - id: discord_dm_1756826280000
    user: Jake
    message: 'Compass pilot day-one boundary: source_freshness_warning is a caveat,
      not an auto-reject; done still needs source + caveat; reject only when source/date
      are too thin; seed examples are not readout evidence; rejected-thin rows stay
      visible. This is pilot execution, not a result or relaunch claim.'
    sent_at: '2025-09-02T08:18:00-07:00'
  - id: discord_dm_1756826280001
    user: Anna Martinez
    message: 'Compass pilot day-one boundary: source_freshness_warning is a caveat,
      not an auto-reject; done still needs source + caveat; reject only when source/date
      are too thin; seed examples are not readout evidence; rejected-thin rows stay
      visible. This is pilot execution, not a result or relaunch claim.'
    sent_at: '2025-09-02T08:18:00-07:00'
  - id: discord_dm_1756826280002
    user: Sarah Kim
    message: 'Compass pilot day-one boundary: source_freshness_warning is a caveat,
      not an auto-reject; done still needs source + caveat; reject only when source/date
      are too thin; seed examples are not readout evidence; rejected-thin rows stay
      visible. This is pilot execution, not a result or relaunch claim.'
    sent_at: '2025-09-02T08:18:00-07:00'
  - id: discord_dm_1756826280003
    user: Leo Park
    message: 'Compass pilot day-one boundary: source_freshness_warning is a caveat,
      not an auto-reject; done still needs source + caveat; reject only when source/date
      are too thin; seed examples are not readout evidence; rejected-thin rows stay
      visible. This is pilot execution, not a result or relaunch claim.'
    sent_at: '2025-09-02T08:18:00-07:00'
  - id: discord_dm_1756926360006
    user: Sarah Kim
    message: 'For the Sep 17 Evergreen prep note, keep it to current flow: workspace
      setup, invited teammate/source-owner path, first source connection, and first
      live sync under the existing annual Growth account. It is fine to call that
      setup/admin workflow if defined that tightly. Do not promise custom admin policy,
      granular role editor, advanced-admin controls, procurement/security packet,
      or dates.'
    sent_at: '2025-09-03T12:06:00-07:00'
  - id: discord_dm_1757000640007
    user: Jake
    message: Keep rejected-thin rows visible in the readout counts. Don't clean them
      out of the owner list; the evidence-quality problem is part of the result. Keep
      blocked_waiting_customer_follow_up separate from done or rejected.
    sent_at: '2025-09-04T08:44:00-07:00'
  - id: discord_dm_1757000640008
    user: Anna Martinez
    message: 'Agree with your read: rejected-thin rows stay visible, and blocked_waiting_customer_follow_up
      stays separate. The readout should show completed owner actions plus the evidence-quality
      failures, not a prettier completion rate.'
    sent_at: '2025-09-04T08:44:00-07:00'
  - id: discord_dm_1757096580012
    user: Anna Martinez
    message: 'Compass readout captured: 8 actions surfaced, 5 done, 2 rejected_thin_source_or_date,
      1 blocked_waiting_customer_follow_up. Your interpretation is the official boundary:
      evidence of Scaffold owner-behavior change, not customer behavior. Internal-only
      until Q3 operating evidence review.'
    sent_at: '2025-09-05T11:23:00-07:00'
  - id: discord_dm_1757096580013
    user: Jake
    message: 'Compass readout captured. October candidate stays narrow/internal: renewal-risk/admin-friction
      owner actions + post-first-live-sync prompts with evidence caveats/status. No
      dashboard, no customer analytics surface, no customer-facing launch claim.'
    sent_at: '2025-09-05T11:23:00-07:00'
  - id: discord_dm_1757096580014
    user: Sarah Kim
    message: 'Compass readout captured: rejected-thin rows stay visible, seed examples
      excluded, and one action remains waiting on live customer follow-up. Please
      keep customer/account wording internal and avoid customer-facing Compass proof
      language.'
    sent_at: '2025-09-05T11:23:00-07:00'
  - id: discord_dm_1757096580015
    user: Leo Park
    message: Compass readout captured. source_freshness_warning stayed a caveat, not
      rejection. Final interpretation remains internal owner-action evidence only,
      with no customer-facing proof or broader platform claim.
    sent_at: '2025-09-05T11:23:00-07:00'
  - id: discord_dm_1759159260000
    user: Jake
    message: 'For the Oct Compass workback: keep the row as `blocked_waiting_customer_follow_up`
      until there is an actual customer reply. A Sarah nudge is owner follow-up, not
      customer behavior proof, and it should not become a provisional customer-signal
      bucket.'
    sent_at: '2025-09-29T08:21:00-07:00'
  - id: discord_dm_1759159260001
    user: Sarah Kim
    message: Please nudge through the normal account thread if useful, but keep the
      Compass row labeled `blocked_waiting_customer_follow_up` until there is an actual
      customer reply. Your nudge is owner follow-up, not customer behavior proof.
    sent_at: '2025-09-29T08:21:00-07:00'
  - id: discord_dm_1759165440002
    user: Sarah Kim
    message: 'Use this instead for Evergreen treasury ops:


      Thanks again for the walkthrough. The current shipped flow is available for
      workspace setup, teammate/source-owner path, first source connection, and first
      live sync under the existing annual account. We captured the granular role editor
      ask as separate advanced-admin follow-up; it is not a blocker for the current
      flow and we are not attaching a Q4 date or custom admin-policy commitment to
      it.


      Please keep Devon only on commercial/procurement framing if needed, not product
      timing.'
    sent_at: '2025-09-29T10:04:00-07:00'
  - id: discord_dm_1759252680006
    user: Devon Hayes
    message: 'Captured the Q4 decision: no snapback to pre-July. You stay on commercial/procurement
      context and selective cofounder judgment calls; routine board/customer cleanup
      and loose-owner routing do not default back to you. I’ll keep board/customer
      narrative.'
    sent_at: '2025-09-30T10:18:00-07:00'
  - id: discord_dm_1759252680007
    user: Jake
    message: 'Q4 operating lane is explicit now: Mercury operating work stays with
      you. Loose-owner questions should route to named owners first, not to Devon
      by default. This is durable Q4 model, not temporary leave coverage.'
    sent_at: '2025-09-30T10:18:00-07:00'
  - id: discord_dm_1759252680008
    user: Leo Park
    message: 'Q4 operating lane is explicit now: Atlas/platform seams and Atlas first
      technical reads stay with you. Loose-owner questions route to named owners first,
      not back to Devon by default.'
    sent_at: '2025-09-30T10:18:00-07:00'
  - id: discord_dm_1759252680009
    user: Priya
    message: 'Q4 operating lane is explicit now: activation/onboarding quality stays
      with you. This is part of the durable post-pause model, not temporary leave
      coverage or Devon snapback.'
    sent_at: '2025-09-30T10:18:00-07:00'
  - id: discord_dm_1759252680010
    user: Anna Martinez
    message: 'Q4 operating lane is explicit now: retention, evidence quality, and
      Compass caveats stay with you. Loose-owner questions route to named owners first,
      not to Devon by default.'
    sent_at: '2025-09-30T10:18:00-07:00'
  - id: discord_dm_1759252680011
    user: Sarah Kim
    message: 'Q4 operating lane is explicit now: Evergreen continuity and customer-thread
      hygiene stay with you. Devon remains commercial/procurement context where needed,
      not default customer-thread owner.'
    sent_at: '2025-09-30T10:18:00-07:00'
  - id: discord_dm_1759267080012
    user: Jake
    message: 'For the Oct Compass implementation: rejected-thin rows can stay out
      of the default owner action queue, but they must remain visible in Anna’s evidence/caveat
      view. `source_freshness_warning` is a caveat, not automatic rejection; only
      use `rejected_thin_source_or_date` when source/date evidence is too thin to
      support the action. Keep the surface internal owner-action workflow only — no
      customer-facing analytics or proof framing.'
    sent_at: '2025-09-30T14:18:00-07:00'
  discord_log:
  - channel: '#eng-team'
    id: discord_1784911046569
    message: 'Friday wrap — May 4


      Team

      - Shipped the standing-rules pass.

      - Agent workflow is now in the normal loop, not just a draft/runbook.


      Customers

      - Product moved, but blockers are still concentrated in activation and admin.

      - Activation still has invite/setup dead ends for some new accounts.

      - Admin invite failures remain unresolved in a couple of account shapes.

      - Account-level permissions are still muddy enough to block rollout and confuse
      admins.


      Investors

      - Deck stays deferred while we tighten launch work first.'
    sent_at: '2023-05-05T09:27:00-07:00'
  - channel: '#eng-team'
    id: discord_1784911054310
    message: 'Mercury weekly owner list:

      - Anna: retention freshness.

      - Priya: activation UX.

      - Jake: admin sequencing.


      Open blockers: admin invites, activation instrumentation, account-level permissions.'
    sent_at: '2023-05-09T12:07:00-07:00'
  - channel: '#eng-team'
    id: discord_1784911056888
    message: 'Mercury offsite prep: use the saved agenda as the source of truth. Come
      with cuts you will actually make, blockers you need decided, and owner proposals.'
    sent_at: '2023-05-11T15:09:00-07:00'
  - channel: '#eng-team'
    id: discord_1784920499536
    message: 'Mercury decision note for next weekly:


      - Use the fresh weekly retention signals with control bands for activation,
      expansion, and admin decisions. Treat them as internal operating signal.

      - Quarterly cohorts stay for board reporting.

      - Keep this in operating mode, not narrative polish.


      Current blockers + owners from the offsite closeout:

      - Billing gate timing: Priya + Jake bring the post-value usage-cap rule and
      product/implementation implications; Morgan only for the actual scope call if
      needed.

      - Activation instrumentation definitions: Anna owns the definition/success cut;
      Jake needs exact event names before wiring.

      - Feature-flag rollout owner/criteria: Jake owns named owner, merge criteria,
      rollback note, and target date.

      - Admin audit-log minimum scope: Jake owns launch-mandatory audit events/surfaces;
      Anna keeps severity/frequency signal attached.'
    sent_at: '2023-05-18T08:02:00-07:00'
  - channel: '#eng-team'
    id: discord_1785100221911
    message: 'Mercury activation reporting direction from Anna’s May 24 correction:


      - Activation within 7 days now means real_source_connected or first_live_sync_completed.

      - Do not count sample_import_completed.

      - Treat invite_sent as supporting evidence only, not activation.

      - Use this corrected weekly cut as internal directional operating input only.

      - Do not use it on board/external charts; keep board/investor framing on the
      sturdier cohort view.'
    sent_at: '2023-05-24T13:38:00-07:00'
  - channel: '#eng-team'
    id: discord_1785101685136
    message: 'May 26 weekly wrap is up: https://loom.test/scaffold/may-26-wrap


      Mercury activation cleanup and launch follow-through.'
    sent_at: '2023-05-26T10:06:00-07:00'
  - channel: '#eng-team'
    id: discord_1785104283847
    message: 'Scaffold Friday wrap — Jun 2 recording is up: https://www.loom.com/share/6e4e4b0866d348ed9dd9e2fd20d7d67d'
    sent_at: '2023-06-02T10:07:00-07:00'
  - channel: '#eng-team'
    id: discord_1785105378409
    message: 'Mercury auth v0.2 decision: Clerk is the baseline for sessions, magic
      links, and organization invites for the next internal dogfood build. SSO and
      deeper admin/org controls stay out of this scope.'
    sent_at: '2023-06-09T10:22:00-07:00'
  - channel: '#eng-team'
    id: discord_1785105378872
    message: 'Mercury auth follow-up: no Friday-after-3 exception without the full
      on-call roster. Keep `rishi/mercury-admin-org-invite-settings` on the standard
      Monday pipeline.'
    sent_at: '2023-06-09T15:43:00-07:00'
  - channel: '#eng-team'
    id: discord_1785105379345
    message: 'June 9 Friday update recording is up: https://www.loom.com/share/8d0e9604c2d84e4da1f6a4f0c6c9c5bf'
    sent_at: '2023-06-09T17:12:00-07:00'
  - channel: '#eng-team'
    id: discord_1785105382164
    message: 'Mercury review decision path: design calls for activation/onboarding
      stay with Priya in Figma; release-readiness and dogfood gating stay with Marcus
      in the implementation checklist/release review. If a checklist blocker needs
      a design change, link the exact Figma frame and reopen only that decision. Discord
      threads should point back to the frame or checklist, not become a third system.
      This gives us a cleaner path; it does not mean every tension is solved.'
    sent_at: '2023-06-13T14:04:00-07:00'
  - channel: '#eng-team'
    id: discord_1785105384571
    message: 'Mercury operating update — no meeting:


      - Auth dogfood: Clerk-backed build is functionally holding up; sessions are
      solid, invite accept/revoke worked, magic links are acceptable but a little
      slow, and org-invite copy is the must-fix before the next pass.

      - Release-readiness owners: Rishi on session persistence and invite/audit plumbing;
      Marcus on magic-link telemetry, invite-copy implementation, support note, and
      rollback checklist; Jake on dogfood org seed/pending invites; Priya remains
      the Figma owner for flow/copy decisions.

      - Monday open questions: are the telemetry/audit event names final enough to
      measure the next dogfood pass, and are we keeping SSO/deeper admin controls
      out of v0.2 while the invite/settings branch stays on the standard pipeline?'
    sent_at: '2023-06-15T16:18:00-07:00'
  - channel: '#eng-team'
    id: discord_1785127682814
    message: 'The board update is done, Mercury remains the operating focus, and there’s
      no long written recap; recording: https://loom.com/share/mercury-q2-close-20230630'
    sent_at: '2023-06-30T16:42:00-07:00'
  - channel: '#eng-team'
    id: discord_1785173822527
    message: '- Mercury activation surface v0.2 is cleared for the next internal dogfood
      under the corrected activation definition (`real_source_connected` or `first_live_sync_completed`
      within 7 days; sample imports excluded).

      - Priya’s Figma four-state surface remains the UX source; Marcus’s Linear checklist
      carries the implementation gates.

      - Anna confirmed definition alignment; setup-guide copy, small-width spacing,
      and icon polish are follow-up, not launch gates.'
    sent_at: '2023-07-06T10:03:00-07:00'
  - channel: '#eng-team'
    id: discord_1785177268235
    message: 'Leo’s first useful Mercury output should be a release-risk readout grounded
      in evidence: where launch risk is hiding, what proof is thin, and what needs
      direct verification. Please keep his ramp tied to Mercury release discipline,
      platform seams, and launch readiness — not abstract platform recommendations
      or a parallel process.'
    sent_at: '2023-07-10T11:36:00-07:00'
  - channel: '#eng-team'
    id: discord_1785177271779
    message: '- Leo’s first Mercury readout stayed scoped to release risk and evidence,
      not a platform roadmap or owner-split launch ledger.

      - Main risk areas: org-invite role/source-state seam, thin dogfood evidence,
      and failed-sync bucket verification.

      - Next checks: invited-member permutations, queue -> retry -> recovery trace,
      and no raw vendor strings or activated-looking sample states.

      - Setup-guide copy and icon polish stay later unless they cause wrong actions,
      clipping, or regressions.'
    sent_at: '2023-07-14T13:22:00-07:00'
  - channel: '#eng-team'
    id: discord_1785179884094
    message: MER-1279 is the working source for Mercury launch readiness. Marcus owns
      implementation gates + dogfood blockers; Priya's Figma remains the design source
      of truth; Leo owns cross-service platform-seam risk notes; Jake will run the
      weekly from the ledger instead of collecting separate owner narratives.
    sent_at: '2023-07-24T09:44:00-07:00'
  - channel: '#eng-releases'
    id: discord_1785189095295
    message: 'Mercury staging: org-invite edge retries now log workspace/signature
      casing; queued-sync retry telemetry added; no prod rollout yet; deploy status
      yellow pending smoke tests.'
    sent_at: '2023-08-04T11:18:00-07:00'
  - channel: '#eng-team'
    id: discord_1785192081708
    message: 'Mercury Aug 10 operating boundary:


      - Wave 1 is Evergreen Bank only.

      - Live scope stays the current Mercury path: Clerk-backed sessions, magic links,
      org invites, corrected activation surface, and preview-only sample data.

      - Out of scope: SSO, deeper admin-control promises, one-off enterprise/custom
      work, or bespoke side commitments.

      - Priya owns final activation/onboarding UX calls from Figma; settled failed-sync,
      CTA, queued-sync, and sample-data directions stay settled unless clarity regresses.

      - Marcus owns implementation gates and dogfood blockers in MER-1279; Leo owns
      cross-service seam risk notes there.

      - Anna uses corrected activation only: real_source_connected or first_live_sync_completed
      within 7 days. sample_import_completed is out; weekly cuts stay directional/internal.

      - Jake runs the Aug 10 cadence and keeps the Evergreen boundary narrow.

      - Call Morgan only for scope widening, launch/no-launch decisions, or a watch
      item becoming an actual blocker.

      - Keep evidence operating/internal — no board, investor, or generic proof-claim
      language.'
    sent_at: '2023-08-09T17:58:00-07:00'
  - channel: '#eng-team'
    id: discord_1785192083218
    message: 'Mercury wave 1 is live for Evergreen Bank on the bounded current product
      path: Clerk-backed sessions, magic links, org invites, corrected activation
      surface, and preview-only sample data.


      MER-1279 is green for launch-blocking gates; invited-member coverage and queued-sync
      retry remain watch items in the ledger, not stop signs. Leo has no launch-blocking
      platform-seam risk in scope. Priya has UX signoff on the shipped frames. Anna’s
      launch-week activation read uses corrected activation only: real_source_connected
      or first_live_sync_completed within 7 days; sample_import_completed is excluded.


      Keep launch evidence operating/internal. No board, investor, customer-proof,
      custom-work, SSO/admin-depth, or scope-expansion language. If Evergreen asks
      about later-scope admin/security or SSO, log it as feedback and keep the wave
      bounded.'
    sent_at: '2023-08-10T09:43:00-07:00'
  - channel: '#eng-releases'
    id: discord_1785271739667
    message: 'Mercury preview-copy clarification is green: this is a copy-only change
      to clarify preview versus real-source setup. The activation definition stays
      unchanged, and this does not expand auth, SSO, or admin scope.'
    sent_at: '2023-08-23T10:34:00-07:00'
  - channel: '#eng-team'
    id: discord_1785274732942
    message: 'Quick Mercury pricing/counting clarification so this doesn’t stay buried:
      pricing bands are based on monthly active developer usage in Mercury, not purchased
      seats or directory size. Scaffold/internal test users don’t count. Preview/sample-only
      activity stays separate from activation reporting; activation remains real_source_connected
      or first_live_sync_completed within 7 days. Any Evergreen-facing answer should
      stay budgetary and non-custom. Please don’t reopen the MAU-vs-seat debate or
      invent enterprise exceptions in customer emails.'
    sent_at: '2023-08-31T10:06:00-07:00'
  - channel: '#eng-team'
    id: discord_1785276671686
    message: '@Anna Martinez @Devon Hayes — please relabel the Looker/board-prep tile
      before the next export as corrected activation/onboarding, not retention. The
      cut should stay tied to real_source_connected OR first_live_sync_completed within
      7 days, with sample-preview-only sessions excluded. For the board layer, keep
      this operating-only and leave weekly movement plus sample-preview diagnostics
      out of the board package.'
    sent_at: '2023-09-11T10:39:00-07:00'
  - channel: '#eng-team'
    id: discord_1785276672702
    message: '@Devon Hayes @Jake — Evergreen packet ownership/boundary: Devon owns
      the commercial/procurement packet. Jake should only supply current product facts
      and open enterprise-readiness gaps. Use the hybrid pricing model as the commercial
      baseline. SSO, audit history, and deeper admin controls stay roadmap-dependent
      add-ons, not launch promises, and nobody should make Evergreen-specific roadmap
      commitments.'
    sent_at: '2023-09-12T09:39:00-07:00'
  - channel: '#eng-releases'
    id: discord_1785277495944
    message: 'Release note: the expired-magic-link helper text now clarifies retry
      guidance for expired magic links. This does not change the Mercury activation
      definition, and it does not expand auth-provider, SSO, admin, or procurement
      scope.'
    sent_at: '2023-09-21T14:37:00-07:00'
  - channel: '#eng-team'
    id: discord_1785278549388
    message: 'Marcus, Leo, Sarah — the new MER-1279 Evergreen rows are monitor/not
      launch blockers. The launch-readiness ledger remains the source of truth. Customer-safe
      sentence Sarah can use: bounded testing can continue while admin/billing-owner
      separation remains an enterprise-readiness gap. No SSO, audit, admin-control,
      or procurement promises.'
    sent_at: '2023-09-26T09:47:00-07:00'
  - channel: '#eng-releases'
    id: discord_1785280875238
    message: API v2 auth refresh retry fix is live. No customer action is needed.
    sent_at: '2023-10-03T14:38:00-07:00'
  - channel: '#eng-team'
    id: discord_1785282146364
    message: 'Thanks Jordan for the Honeycomb walkthrough. The concrete win: starting
      from the repo-connect latency alert, the query path got us from “latency is
      up” to a suspect deploy / worker shape in roughly two minutes, without the usual
      dashboard → logs → grep loop first.


      Useful caveat: this does not solve reliability by itself. It shortens time-to-understand;
      we still need to fix the underlying deploy/worker issues and keep instrumentation
      hygiene strong.'
    sent_at: '2023-10-10T12:06:00-07:00'
  - channel: '#eng-releases'
    id: discord_1785283360452
    message: API v2 auth rewrite rollout is complete. The updated JWT auth path is
      now at 100% of API v2 traffic; monitoring shows no elevated 401s, the rollback
      flag was not used, and no customer action is needed.
    sent_at: '2023-10-17T14:16:00-07:00'
  - channel: '#eng-team'
    id: discord_1785284614665
    message: 'Devon/Jake — Evergreen second-admin follow-up: Devon owns the commercial
      framing. Jake, please stick to current product facts only: magic links, org
      invites, preview-only sample data, real-source connection, and first live sync.
      SSO, admin-change audit history, and admin-vs-billing-owner separation stay
      as next-phase enterprise-readiness follow-up, not Mercury v0.2 promises or Evergreen-specific
      exceptions.'
    sent_at: '2023-10-23T08:47:00-07:00'
  - channel: '#eng-team'
    id: discord_1785285811463
    message: 'Anna, Jake, Leo, Devon — consolidated pass on October Mercury package
      v0.7:


      - Keep the center of gravity: activation is stronger than May on the corrected
      real-source/live-sync definition. Keep the metric definition attached wherever
      the activation table travels.

      - Use Evergreen’s second admin group only as bounded enterprise-pattern evidence:
      org invite, magic-link access, preview/sample data, real-source connection,
      and first live sync are less brittle. Do not turn the audit/history, SSO, or
      admin-vs-billing questions into near-term promises.

      - Remove any language that says retention or expansion is solved. Mature cohorts
      can be described as tracking better than spring with windowing explicit; expansion
      remains uneven.

      - Mark weekly cuts, sample-preview diagnostics, small-n Evergreen movement,
      and MER-1279 / non-external launch-readiness rows as internal-only.

      - Short-list-diligence version should be narrative caveats + monthly activation
      trend + mature-cohort week-4 retention + bounded Evergreen example + enterprise-readiness
      gaps/commercial framing. No ticket-by-ticket appendix.'
    sent_at: '2023-11-02T10:18:00-07:00'
  - channel: '#eng-team'
    id: discord_1785285811928
    message: 'Anna, Jake, Leo, Devon — final package-use boundary from owner review:


      The October Mercury package is usable for short-list diligence only under my
      caveats. Quarterly cohort and board-operating views can be shared selectively;
      weekly cuts, sample-preview diagnostics, and small-n Evergreen movement stay
      internal.


      The package can say activation is holding better than May and admin friction
      is improving, with Evergreen’s second admin group as the bounded enterprise-pattern
      example. Expansion remains uneven. This is not broad external proof that Mercury
      has solved retention or enterprise expansion.'
    sent_at: '2023-11-03T09:34:00-07:00'
  - channel: '#eng-team'
    id: discord_1785287791436
    message: '@Devon @Jake quick Evergreen split to preserve: Devon owns commercial/procurement
      framing. Jake should stay limited to current product facts in the bounded Mercury
      flow — no SSO timing, audit-history roadmap, admin/billing separation commitments,
      or Evergreen-specific exceptions.'
    sent_at: '2023-11-06T13:27:00-08:00'
  - channel: '#eng-team'
    id: discord_1785287791880
    message: '@Jordan @Marcus approving the narrow Honeycomb ingest cleanup: sample
      retained demo/debug traces at 10% and archive older demo traces. Please send
      one updated run-rate sentence by Friday, 2023-11-10. Keep this framed as cost
      hygiene, not a new observability-tooling project.'
    sent_at: '2023-11-06T14:05:00-08:00'
  - channel: '#eng-team'
    id: discord_1785287792328
    message: '@Devon for Friday: decision material = Mercury hardening and API v2
      stale-doc/search cleanup. Onboarding is a ramp guardrail and owner follow-through,
      not new scope. Pinecone Go snippet is acceptable only as a narrow docs fix if
      we take it; don’t let it turn into broader connector-doc work.'
    sent_at: '2023-11-06T14:22:00-08:00'
  - channel: '#eng-team'
    id: discord_1785287793757
    message: '@Rishi keep the Pinecone docs PR narrow: one Go snippet is fine only
      for the canonical header-only request path using `X-Scaffold-Workspace` and
      `X-Scaffold-Signature`. Please remove the query-param fallback and any alternate
      signature-location language; do not add underscore/env-var variants like `X_SCAFFOLD_WORKSPACE`
      or `X_SCAFFOLD_SIGNATURE`; and do not expand this into client construction,
      timeout/retry guidance, or a broader connector rewrite.'
    sent_at: '2023-11-07T11:22:00-08:00'
  - channel: '#eng-team'
    id: discord_1785287794184
    message: '@Marcus please remediate the two paid-but-pending renewal rows narrowly:
      `acct_7M2Q41` / `in_1O8dG2K7vmJ9r2Q1` and `acct_9C8L13` / `in_1O8jYfK7vmJ9r2Q9`.
      Reconcile the entitlements without replaying charges, confirm there are no duplicate-charge
      paths, and give @Rishi one customer-safe support sentence in case either account
      writes in.'
    sent_at: '2023-11-07T11:48:00-08:00'
  - channel: '#eng-team'
    id: discord_1785287795939
    message: '@Rishi please pin the current API v2 GraphQL quickstart in the support
      path: https://docs.atlas-test.com/api/v2/graphql-quickstart. Suppress the specific
      stale API v1 Quickstart snippet still surfacing for `auth header` (`/api/v1/quickstart`,
      bearer-token / `/v1/projects/:id/repos` language), and keep this as targeted
      docs/search cleanup rather than reopening the API migration project.'
    sent_at: '2023-11-08T10:32:00-08:00'
  - channel: '#eng-team'
    id: discord_1785287796380
    message: '@Leo @Jake prioritize the admin setup mislabel and live-sync retry cluster
      for the sprint: MER-1746, MER-1749, and MER-1751. Defer MER-1754 audit history,
      MER-1756 SSO/SAML, and MER-1757 admin-versus-billing-owner separation; do not
      pull those into v0.2. Customer-facing language should stay limited to current
      product facts, and launch-relevant updates should tie back to the existing launch-readiness
      ledger.'
    sent_at: '2023-11-08T13:20:00-08:00'
  - channel: '#eng-team'
    id: discord_1785287797255
    message: '@Devon @Jake Acme remains excluded from fresh Mercury written materials
      for legal-scope/NDA reasons, not demand-signal reasons. We held the live-only
      boundary on today’s call; no packet, screenshots, examples, or briefing materials
      while the scope issue is unresolved.'
    sent_at: '2023-11-09T11:12:00-08:00'
  - channel: '#eng-team'
    id: discord_1785287797692
    message: '@Rishi customer-safe sentence from Marcus’s update if either account
      writes in: “We reconciled the renewal entitlement, and our checks show the entitlement
      now matches the successful Stripe payment with no duplicate charge on the account.”'
    sent_at: '2023-11-09T13:48:00-08:00'
  - channel: '#eng-team'
    id: discord_1785287798120
    message: '@Marcus thanks — this thread can close unless either account reports
      a billing discrepancy.'
    sent_at: '2023-11-09T13:48:00-08:00'
  - channel: '#eng-team'
    id: discord_1785287799023
    message: '@Devon @Jake keeping the same Evergreen split: Devon owns commercial/procurement
      framing, and Jake should stick to current product facts. SSO, audit history,
      and admin-versus-billing-owner separation remain next-phase enterprise-readiness
      questions, not v0.2 commitments or Evergreen-specific exceptions.'
    sent_at: '2023-11-10T16:46:00-08:00'
  - channel: '#eng-team'
    id: discord_1785287799880
    message: '@Jordan @Marcus thank you — with sampling and archiving live and projected
      November ingest now within about $90 of the expected run rate, the Honeycomb
      cost-hygiene thread can close until month-end unless the run rate jumps again.
      Let’s not spin this into a broader observability-tooling effort.'
    sent_at: '2023-11-10T17:19:00-08:00'
  - channel: '#eng-team'
    id: discord_1785302125316
    message: 'Leo, Jake — For the Mercury RC branch: take MER-1746, the admin setup
      relabel to “Workspace admin,” and MER-1751, the retry CTA guard while a retry
      is already in flight, if the remaining tests/replays are green. Keep the broader
      live-sync reconcile fix out of the late branch unless it becomes clearly low-risk.
      MER-1754 audit history and MER-1756 SSO stay out of v0.2 as enterprise-readiness
      follow-up, not RC scope. Any customer-facing wording should stick to current
      product facts only: copy/guard behavior changed, not permissions or enterprise
      commitments.'
    sent_at: '2023-11-21T09:58:00-08:00'
  - channel: '#eng-releases'
    id: discord_1785306028870
    message: 'Mercury hardening update is now live. This deploy includes two scoped
      fixes:


      1) Admin setup wording on the org invite step is clearer: “Workspace admin”
      replaces the old “Billing owner” label.

      2) The live-sync retry CTA is disabled while a retry is already in flight.


      No broader live-sync state-reconcile change, SSO work, audit-history work, admin-versus-billing-owner
      model changes, or enterprise-readiness change shipped in this deploy.'
    sent_at: '2023-12-14T10:48:00-08:00'
  - channel: '#eng-team'
    id: discord_1785460702983
    message: 'Priya — keep the special monitoring on for the first January onboarding
      read until we have both a support signal and a product/Figma-flow signal, not
      just a quick Mixpanel glance. The two reads to watch before we decide whether
      the extra monitoring can wind down are: (1) the support read on customer/admin
      confusion or issues, and (2) the product/Figma-flow read on whether the shipped
      flow is behaving as intended.'
    sent_at: '2024-01-08T10:19:00-08:00'
  - channel: '#eng-team'
    id: discord_1785460703442
    message: Marcus — thanks for flagging. Please check the affected entitlement rows
      from the weekend renewal-retry snapshot (rr_01JQZS7D, rr_01JR066W, rr_01JR3QDV)
      against the billing-service/Stripe state. Keep this internal for now. Only escalate
      outside the team if the check finds a customer-visible entitlement mismatch.
      No manual reruns until Marcus has confirmed the row state.
    sent_at: '2024-01-08T10:43:00-08:00'
  - channel: '#eng-team'
    id: discord_1785460704295
    message: Marcus, Rishi — if the follow-up check shows all three renewal entitlement
      rows have caught up and no row remains mismatched, please close the check. Keep
      this internal; do not escalate outside the team unless a customer-visible mismatch
      appears, and do not turn this into a broader billing cleanup.
    sent_at: '2024-01-10T17:04:00-08:00'
  - channel: '#eng-releases'
    id: discord_1785485377846
    message: 'Mercury live-sync follow-up is live. Two scoped timeout-recovery UI
      fixes shipped: retry status now refreshes in-session after timeout recovery
      without a page reload, and stale timeout messaging clears after a successful
      retry in the same session. This should reduce the “did it actually run or is
      it still stuck?” support loop on the current live-sync path. No sync-engine,
      retry-policy, auth/admin-role, SSO, audit-history, admin/billing-owner, or broader
      enterprise-readiness work is part of this deploy.'
    sent_at: '2024-02-14T10:39:00-08:00'
  - id: discord_1786081962514
    channel: '#eng-releases'
    message: 'Mercury admin-copy patch — narrow copy/display-cache cleanup


      - Source-workspace copy: pending invite and acceptance surfaces now make clearer
      that the invite’s source workspace controls membership, even if a session header
      briefly shows the user’s last active workspace.

      - Member-count display: after canceling a pending invite, the admin-panel count
      refreshes so the visible count no longer stays stale until manual page refresh.

      - Scope: no backend membership-grant change, no permissions-model change, and
      no broad Mercury launch announcement.'
    sent_at: '2024-04-19T19:31:00-07:00'
  - id: discord_1786405355959
    channel: '#eng-team'
    message: 'Today’s Atlas handoff is good enough to operate, not proof that we’ve
      replaced Rishi’s depth.


      Rishi’s final Scaffold day is today. He’s leaving for Tessl to join Anna Rao’s
      database-internals/platform team after delivering the PR-1187 verifier note,
      a short AT-04 replay/backfill recovery runbook, and the cleaned AT-05 workspace/org-invite
      migration note.


      After today he is no longer Scaffold’s Atlas owner or the default Atlas customer-thread
      contact.


      Interim split:

      - Leo owns first-pass technical work for verifier/auth, replay/backfill, and
      auth/platform-boundary reads.

      - Jake owns Atlas product-priority, sequencing, and cut decisions.

      - Urgent customer-facing Atlas issues still start with the support rotation
      doc, the named weekly owner, and an immediate next step first.'
    sent_at: '2024-06-21T16:18:00-07:00'
  - id: discord_1786940694958
    channel: '#mercury-eng'
    message: '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.'
    sent_at: '2025-01-22T13:42:00-08:00'
  - id: discord_1744992660007
    channel: '#eng-team'
    message: 'Mercury admin visibility closeout: Jake/Leo verified the invited-teammate/source-owner
      cues in the current activation path through setup guidance, first source connected,
      and first live sync. Sarah has customer-safe wording for Evergreen if needed.
      Scope is basic teammate-invite/admin-role visibility only — no custom admin
      policy, granular role editor, or advanced admin-control claim.'
    sent_at: '2025-04-18T09:11:00-07:00'
  - id: discord_1745856480008
    channel: '#eng-team'
    message: 'Compass Apr review closeout: keep this as two owner-group action prompts,
      not a dashboard or customer analytics surface. April evidence is useful operating
      learning, but still thin as customer behavior-change proof. Use Anna/Sarah/Leo/Nadia
      evidence with dates and caveats attached; no customer-facing proof, board-dashboard
      framing, or hiring implication before the May board-cycle gate.'
    sent_at: '2025-04-28T09:08:00-07:00'
  - id: discord_1748017440009
    channel: '#eng-team'
    message: 'Acme API v2 export-timeout closeout: support kept the customer thread,
      Leo isolated the issue to the large export path, and Acme continued via narrower
      replay. Jake owns any bounded Atlas/API v2 product sequencing. This is not Compass
      scope, not Mercury escalation, and not founder-direct Atlas routing.'
    sent_at: '2025-05-23T09:24:00-07:00'
  - id: discord_1748362560000
    channel: '#eng-team'
    message: 'Compass closeout reminder for the owner group: keep June 4 evidence-only.
      Fill the skeleton by Monday 6/2 EOD with behavior-change evidence, prompt evidence,
      account-source quality, owner-routed intake, and what to cut/keep. No customer-facing
      launch, dashboard rebuild, GTM proof, hiring-trigger language, or Series C narrative.'
    sent_at: '2025-05-27T09:16:00-07:00'
  - id: discord_1748878560006
    channel: '#eng-team'
    message: 'Compass closeout last call: please fill the skeleton by EOD today with
      (1) behavior-change evidence, (2) prompt evidence/caveats, (3) account-source
      quality, (4) owner-routed intake, and (5) cut/keep recommendation. Keep examples
      date/source-bound. This is prep for Wednesday’s narrow evidence read — not a
      customer-facing launch, dashboard, GTM proof, hiring trigger, or Series C story.'
    sent_at: '2025-06-02T08:36:00-07:00'
  - id: discord_1749060180005
    channel: '#eng-team'
    message: 'Compass closeout decision: we are cutting the H1 customer-facing Compass
      plan. Keep only narrow internal action-prompt work on renewal-risk/admin-friction
      and post-first-live-sync expansion. Owners stay narrow: Anna definitions/caveats,
      Nadia scripts/behavior read, Jake prompt-level implementation, Leo data/platform
      seams, Sarah account-thread evidence. Do not frame this as a launch, GTM proof,
      board dashboard, hiring trigger, Series C story, or Mercury sequencing change.'
    sent_at: '2025-06-04T11:03:00-07:00'
  - id: discord_1752689880007
    channel: '#compass-owners'
    message: 'Compass July first pass is closed for now: 11 retained prompt hits,
      4 dated owner follow-ups, 0 customer-initiated actions. Prompt sightings alone
      do not count. Evergreen rows stay current-state/admin-handoff follow-up. Acme
      stays Atlas/API v2 context and is excluded from Compass proof. Jake keeps implementation
      at prompt level. No customer-facing claims, GTM proof, staffing trigger, or
      fundraising language from this read.'
    sent_at: '2025-07-16T11:18:00-07:00'
  - id: discord_1753110720000
    channel: '#leadership'
    message: 'Week four routing stays the same: Jake owns Mercury sequencing; Leo
      owns Atlas first reads/platform seams; Priya owns activation quality; Anna owns
      evidence quality; Sarah owns Evergreen continuity; I hold board/customer narrative.
      Devon is not the tiebreaker unless this is a true customer-impacting or founder-level
      emergency. Acme stays Atlas/API v2, Compass stays internal evidence hygiene,
      and Evergreen uses current-state wording. If something is ambiguous, bring me
      the owner recommendation first.'
    sent_at: '2025-07-21T08:12:00-07:00'
  - id: discord_1753199220005
    channel: '#atlas'
    message: 'Acme owner alignment: take Leo''s Option B as bounded Atlas/API v2 work
      — chunk long ranges and back off before the cursor path times out. Support-safe
      wording is that we isolated the long-range export path and are working a bounded
      reliability follow-up. No fix date yet, no data-loss language, no Compass/Mercury
      scope, and no Devon route.'
    sent_at: '2025-07-22T08:47:00-07:00'
  - id: discord_1753466760018
    channel: '#atlas'
    message: 'Decision: staging through the normal pipeline is fine for the Acme chunking/backoff
      branch, but no Friday prod push. Do not promise Acme a fix date. Support can
      say we are validating the bounded large-export reliability follow-up and will
      update after staging/replay checks are clean.'
    sent_at: '2025-07-25T11:06:00-07:00'
  - id: discord_1753723080002
    channel: '#atlas'
    message: 'Acme staging/replay update: keep this in the bounded API v2 large-export
      path. The generic staging fixture is cleaner, but the Acme-like nested-field
      90-day replay is not clean yet. No customer-ready language, no prod push, and
      no fix-date promise. Leo/Jake should keep iterating through the normal pipeline;
      support can say validation is still in progress.'
    sent_at: '2025-07-28T10:18:00-07:00'
  - id: discord_1753910160016
    channel: '#atlas'
    message: 'Acme update: progress, not readiness. Smaller chunks/backoff cleared
      local + generic staging, but the Acme-like nested-field replay completed once
      and timed out once; row-count comparison is still incomplete. Keep it bounded
      to API v2 large-export reliability. No customer-ready language, no ship-this-week
      promise, and no Devon route — Leo/Jake own validation/sequencing, support owns
      the customer update.'
    sent_at: '2025-07-30T14:16:00-07:00'
  - id: discord_1754426280011
    channel: '#eng-releases'
    message: 'Atlas/API v2 production deploy: bounded large-export chunking/backoff
      patch from `atlas/acme-large-export-chunk-backoff`. Scope is long-range export
      timeout mitigation only; no schema change, no Compass/Mercury scope. Acme customer
      rerun + row-count confirmation still pending before support closes the recurrence.'
    sent_at: '2025-08-05T13:38:00-07:00'
  - id: discord_1754667720025
    channel: '#eng-releases'
    message: Acme API v2 large-export recurrence is closed. The same 90-day export
      completed after the bounded chunking/backoff patch, and row counts matched monthly
      replay checks. No customer-visible data loss identified. Keep the postmortem
      framing bounded to Atlas/API v2 support routing — not Compass, Mercury, Devon,
      or founder-direct scope.
    sent_at: '2025-08-08T08:42:00-07:00'
  docs:
  - body: 'Mercury weekly operating note


      Purpose

      - Use Jake''s Mercury weekly as the operating home for product/launch work.

      - Keep the Friday wrap as an update, not the place to solve Mercury.


      Scope for Jake''s weekly

      - Anna''s retention work.

      - Activation blockers.

      - Admin blockers.


      Boundary

      - Product/operating work only.

      - No investor/deck material routed to Jake.'
    created_at: '2023-05-05T10:18:00-07:00'
    folder: null
    id: doc_1784911047454
    title: Mercury weekly operating note
  - body: 'Mercury weekly — May 9 operating list


      Date

      - Tue May 9, 2023


      Attendees

      - Morgan, Jake, Anna, Priya, Devon


      Operating frame

      - Keep this meeting on product/operating work only.

      - No investor/deck detour.

      - Use Mercury weekly as the operating spine instead of rewriting this into a
      Friday story.


      Visible weekly list

      - Blocker.

      - Owner.

      - Next decision.


      Current launch blockers

      1. Admin invites.

      2. Activation instrumentation.

      3. Account-level permissions.


      Owner calls

      - Anna: retention freshness, instrumentation sanity, changed-cut notes.

      - Priya: activation UX pass, especially first-run path and invite/setup dead
      ends.

      - Jake: admin sequencing, permissions dependencies, what can be cut vs launch-blocking.


      Questions to carry forward

      - Which admin steps are true launch blockers vs annoying but deferrable?

      - Do we gate rollout on fixed account-level permissions or ship a narrower path?

      - What event do we trust as the activated point this week?


      Loose next steps

      - Jake brings proposed admin sequence.

      - Priya shows where UX can remove confusion without backend changes.

      - Anna marks fresh vs noisy numbers on the retention cut.

      - Morgan keeps Friday wrap out of this and keeps this out of investor narrative.'
    created_at: '2023-05-09T12:07:00-07:00'
    folder: null
    id: doc_1784911053881
    title: Mercury weekly — May 9 operating list
  - body: 'Mercury product offsite — May 12 working agenda


      Working frame

      - Built around decisions, cuts, owners, and blockers.

      - Keep this as operating work, not a launch narrative or deck rehearsal.


      Agenda

      1. Launch blockers kickoff

      - Confirm the current launch-critical blockers.

      - Separate blockers from deferrable cleanup.


      2. Activation/onboarding cuts

      - Decide what to cut or simplify in activation/onboarding.

      - Identify which invite/setup dead ends need product, UX, or engineering decisions.


      3. Admin blocker triage

      - Triage admin invite failures, permissions confusion, and account-level rollout
      blockers.

      - Decide which admin issues block launch and which can wait.


      4. Retention instrumentation with Anna

      - Align on retention freshness and instrumentation sanity.

      - Decide what can be used for internal operating work versus what is still caveated.


      5. Owner assignments

      - Assign owners for each blocker and next decision.


      6. Inputs for the next Mercury weekly

      - Capture what needs to carry into Jake''s next weekly agenda.'
    created_at: '2023-05-10T07:52:00-07:00'
    folder: null
    id: doc_1784911055167
    title: Mercury product offsite — May 12 working agenda
  - body: 'Mercury offsite decisions — customer-success blocker digest May 8-9


      Use these as decisions to make, not story color.


      1. Activation dead ends

      - Decide the fallback path when connector setup fails or is deferred.

      - Decide whether sample/manual setup is a real product path or an edge-case
      patch.

      - Decide what next action users should see after workspace creation.


      2. Admin invite failures

      - Decide the visible outcome for sent, pending, duplicate, existing-member,
      and restricted invites.

      - Decide when domain/role restrictions should surface.

      - Decide what confirmation admins need before they trust rollout state.


      3. Onboarding confusion before first value

      - Decide the valid setup order: connect first, invite first, or multiple legitimate
      paths.

      - Decide what first value moment the flow is steering toward.

      - Decide what copy/state changes remove ambiguity without pretending permissions
      bugs are solved.'
    created_at: '2023-05-10T08:48:00-07:00'
    folder: null
    id: doc_1784911055597
    title: Mercury offsite decisions — customer-success blocker digest May 8-9
  - body: 'Mercury product offsite — May 12 working agenda


      Operating line

      - This is an operating offsite, not a launch narrative or deck rehearsal.


      Working rule

      - Preserve decision points, cuts, owners, and blockers.

      - Strip narrative/deck sections.

      - Keep investor framing out of the room.


      Agenda

      1. Launch blockers and cuts

      - Confirm the blocker list.

      - Decide what is launch-blocking versus deferrable.

      - Name the cut or decision needed for each blocker.


      2. Activation/onboarding cuts

      - Decide the valid setup order.

      - Decide whether fallback paths are first-class product paths.

      - Decide which onboarding confusion can be removed through UX/copy versus engineering
      changes.


      3. Admin blocker triage

      - Decide the invite sequence and confirmation states.

      - Decide the permission boundaries that must be explicit before launch.

      - Decide what can be cut versus what blocks broader rollout.


      4. Retention instrumentation with Anna

      - Identify which cuts are solid enough for internal operating decisions.

      - Mark caveats and mapping/instrumentation changes clearly.

      - Keep this tied to launch blockers, not a side data-cleanup thread.


      5. Owners and next decisions

      - Anna: retention freshness and instrumentation sanity.

      - Priya: activation/onboarding UX cuts.

      - Jake: admin sequencing and permissions dependencies.

      - Morgan: keep the work in Mercury weekly and out of Friday-wrap/story churn.


      6. Inputs for the next Mercury weekly

      - Carry forward unresolved decisions, owner proposals, and blocker status.'
    created_at: '2023-05-11T08:44:00-07:00'
    folder: null
    id: doc_1784911056024
    title: Mercury product offsite — May 12 working agenda
  - body: '# Mercury offsite — one-day run-of-show


      ## Operating frame

      - One day, product-deep.

      - Use the room for product work: demos, working blocks, decisions, owners, cuts,
      and blockers.

      - No investor-facing narrative in the room. If discussion turns into story polish,
      cut it and return to launch work.


      ## Confirmed logistics

      - Room: Bay Room, Friday May 12, reserved 8:30am-5:30pm for 5 people.

      - Setup: conference layout for 5, two rolling whiteboards, wall-mounted display
      with HDMI, extension cord and power strip placed in the room.

      - Internet: property ops confirmed dedicated business fiber, standard 300/300
      Mbps symmetric, live hardline ethernet, separate guest Wi-Fi with no captive
      portal, onsite ops from 8:00am.

      - Lunch: Tava Kitchen delivery confirmed 12:10-12:25pm, front desk drop-off
      labeled Scaffold / Bay Room, 5 meals, vegetarian items labeled, sauces on side.


      ## Run of show

      - 8:30-10:00 — Room open, setup, internet/HDMI/hardline check.

      - 10:00-10:15 — Kickoff: product-deep working day, not a deck rehearsal.

      - 10:15-11:00 — Short demo block: show the live product surfaces before debating
      them.

      - 11:00-12:10 — Working block 1: activation decisions and cuts.

      - 12:10-12:25 — Lunch arrival window.

      - 12:25-1:00 — Lunch break; do not turn this into investor-story discussion.

      - 1:00-2:10 — Working block 2: expansion path decisions and cuts.

      - 2:20-3:30 — Working block 3: admin pain decisions and cuts.

      - 3:30-4:15 — Owner/blocker pass: name owner, next decision, and what gets cut.

      - 4:15-4:30 — Capture weekly follow-up inputs for Jake''s Mercury weekly.


      ## Lunch order reference

      - Harissa chicken bowl x2.

      - Falafel tahini bowl.

      - Green goddess chicken wrap.

      - Avocado + hummus wrap.

      - Mixed greens salad, kettle chips, sparkling water assortment, cookies.'
    created_at: '2023-05-12T07:38:00-07:00'
    folder: Mercury
    id: doc_1784920495269
    title: Mercury offsite — one-day run-of-show
  - body: '# Mercury offsite closeout — owners, cuts, launch blockers


      ## Frame

      - Not a deck.

      - Ship work, owners, cuts, blockers.

      - Weekly spine = Jake.

      - If discussion turns into narrative polish, cut it.


      ## Launch bar

      - Activation works without founder handholding.

      - Expansion path is visible in product, not in slides.

      - Top admin pain is reduced enough that calls stop repeating the same three
      complaints.

      - One blocker owner each.


      ## Activation


      ### Owners

      - Priya: path, copy, screens.

      - Jake: implementation, flag, rollout sequence.

      - Anna: event definitions, success cut.


      ### Need by next review

      - Single primary CTA: connect first source.

      - Invite teammates becomes optional after first value, not before.

      - Sample data only if there is no real event in the first session.

      - Define activation event chain in plain English and actual events.


      ### Blockers

      - Billing gate timing unresolved: before first real run is probably too much
      friction; after first value is better but needs abuse cap / usage limit.

      - Event names still fuzzy; Anna needs exact handoff, Jake will not wire to vibes.

      - Role setup copy still abstract; admins do not know what changes later vs now.

      - Feature-flag rollout criteria are not written anywhere.


      ### Scope cuts

      - No template gallery for v1.

      - No SSO in first-run path.

      - No advanced permissions setup during activation.

      - No logo/upload/custom branding in first-run.


      ### Margin notes

      - First value means connected source plus first successful action, not invited
      teammate.

      - Stop debating empty-state illustration.

      - Do not reopen the entire settings IA here.


      ## Expansion


      ### Owners

      - Jake: overall.

      - Priya: upgrade moments and UI.

      - Anna: usage threshold sanity check and measurement.


      ### What stays in

      - Expose upgrade trigger where usage actually hits limit.

      - One clean in-app path from cap hit to plan/owner action.

      - Admin sees why the workspace is constrained.

      - Light copy only, no packaging essay.


      ### Blockers

      - Mercury feature-flag rollout still ambiguous: who flips it, merge criteria,
      rollback note, target date.

      - Usage threshold cut is noisy; need one number the team will actually use.

      - Upgrade copy still split between product/admin language and billing language.


      ### Scope cuts

      - No annual-plan flow work for launch.

      - No seat-management overhaul.

      - No contract-specific enterprise branching in product.

      - No pricing-story work in this room.


      ### Margin notes

      - Expansion path has to exist even if monetization details evolve later.

      - If it requires sales explanation every time, it is not launch-ready.


      ## Admin pain


      ### Owners

      - Jake: backend, account actions, audit surfaces.

      - Priya: admin home and settings grouping.

      - Anna: tag incoming issues by severity and frequency.


      ### Repeated pain to fix

      1. Permissions / roles unclear.

      2. Bulk user actions too manual.

      3. No clean audit trail for who changed what.

      4. Wrong person gets admin/billing noise.

      5. Settings scattered across too many places.


      ### Blockers

      - Audit-log scope unclear: what events are mandatory for launch?

      - CSV/import failures still bad at telling admins what broke.

      - Permission model explanation still too hand-wavey for security-conscious customers.

      - Notification routing rules are not explicit enough.


      ### Scope cuts

      - No full settings redesign.

      - No granular notification matrix.

      - No admin analytics dashboard.

      - No custom role builder.


      ### Bottom line

      - Fix repeated pain, not every admin complaint anyone has ever had.

      - If a problem only matters after launch scale, write it down and move on.


      ## Cross-cutting operating rules

      - Jake runs weekly from this, not Morgan.

      - Morgan is pulled in only for actual scope calls / unblock.

      - Devon can pressure-test logic, but not turn it into investor copy.

      - Every owner comes to weekly with: what moved, what slipped, what we cut.

      - Customer examples over opinions.

      - Launch blockers list stays short and named.


      ## Open blockers to carry forward

      - Billing gate timing.

      - Activation instrumentation definitions.

      - Mercury feature-flag rollout owner plus merge/rollback criteria.

      - Admin audit-log minimum scope.


      ## Compact internal recap for next Mercury weekly

      - Use this as operating follow-up, not a glossy launch story.

      - Jake owns the weekly spine and should drive decisions against owners, cuts,
      and blockers.

      - Priya carries activation path/copy/screens, upgrade moments/UI, and admin
      home/settings grouping.

      - Anna carries activation definitions, success cuts, usage threshold measurement,
      and issue severity/frequency tagging.

      - Jake carries implementation/rollout, expansion overall, backend/account actions,
      and audit surfaces.

      - Decisions due: billing gate timing, activation event definitions, feature-flag
      owner/criteria/rollback/target date, and admin audit-log minimum scope.

      - Do not let Monday become: can we make this story cleaner.'
    created_at: '2023-05-12T16:38:00-07:00'
    folder: Mercury
    id: doc_1784920495700
    title: Mercury offsite closeout — owners, cuts, launch blockers
  - body: '# Mercury retention reporting split — operating package


      ## Decision

      - We are done trying to make one chart do two jobs.

      - Anna''s quarterly cohort view is the board-safe version.

      - Weekly signup-week cuts with control bands are internal operating signal only.

      - Devon agreed to stop side-sheet sprawl and route warehouse pulls through Anna.


      ## Internal operating layer: Mercury weekly

      Use weekly cuts for decisions on:

      - Activation: D14 activated by signup week, with control bands, plus admin setup
      completion.

      - Expansion: D45 expansion-ready as a directional operating read.

      - Admin pain: friction flags per account, because that is where the week-to-week
      signal is clearest.


      Caveats that stay attached to the weekly package:

      - Weekly cohorts are internal operating signal only.

      - Treat only sustained or out-of-band movement as signal.

      - Keep sample size visible.

      - Keep partial cohorts visually separated; do not use W6 retained for the newest
      cohorts.


      ## Board-safe layer

      Use quarterly first-paid cohorts only.

      - The honest claim is improving quarterly cohort shape, not retention is solved.

      - Use trimmed NRR / sensitivity treatment rather than headlining the oversized
      early expansion customer raw number.

      - Latest quarter can be shown only through available maturity.

      - Keep weekly operating cuts out of the board-facing chart.


      ## Warehouse-pull routing

      - Anna owns the retention reporting package and warehouse pull path.

      - Devon routes warehouse pulls through Anna.

      - No more side sheets multiplying outside the operating package.


      ## Open cleanup before v1

      - Finish backfill check on the 2023-04-04 to 2023-04-07 admin invite gap.

      - Verify two April workspaces with invoice deltas but no matching seat-change
      logs.

      - Keep the warehouse pull owner locked through Anna.'
    created_at: '2023-05-17T12:38:00-07:00'
    folder: Mercury
    id: doc_1784920498272
    title: Mercury retention reporting split — operating package
  - body: '# Friday wrap draft — May 19


      Draft only — do not send or post yet.


      ## Team

      - Mercury offsite output is operating work: owners, scope cuts, and named launch
      blockers, not a launch-story deck.

      - Jake''s weekly is the spine for the follow-up; every owner comes with what
      moved, what slipped, and what got cut.

      - Owner map: Jake on implementation/rollout, expansion overall, backend/account
      actions, and audit surfaces; Priya on activation path/copy/screens, upgrade
      moments/UI, and admin home/settings grouping; Anna on activation definitions,
      usage measurement, and issue severity/frequency tagging.

      - Scope cuts remain explicit: no activation template gallery, no first-run SSO,
      no advanced first-run permissions, no annual-plan flow, no seat-management overhaul,
      no full settings redesign.


      ## Customers

      - Customer-visit prep is in place for the May 19 NYC visit; keep the existing
      customer-visit event intact.

      - Travel is confirmed for Morgan: Alaska SFO-JFK May 18, JFK-SFO May 20, Ace
      Hotel Brooklyn May 18-20, no car service booked.

      - Mercury customer work stays focused on the repeated blockers: billing gate
      timing, activation instrumentation definitions, feature-flag rollout owner/criteria,
      and admin audit-log minimum scope.

      - Admin-pain signal is concentrated in a few repeated jobs: role clarity, bulk
      user actions, audit trail, billing/admin routing, and settings sprawl.


      ## Investors

      - Deck work stays deferred while launch work gets tighter first.

      - Retention reporting is now split: weekly cuts with control bands are internal
      operating signal only; quarterly first-paid cohorts are the board-safe view.

      - Do not smuggle weekly wiggle into a board-safe chart.


      ## Legal / ops

      - Warehouse pulls for Mercury retention reporting route through Anna; no more
      side-sheet sprawl.

      - No separate legal/ops decision to escalate in this draft unless something
      changes before send.'
    created_at: '2023-05-18T19:24:00-07:00'
    folder: Team updates
    id: doc_1784920502218
    title: Friday wrap draft — May 19
  - body: '# NYC visit — Mercury operating notes, May 19


      - Real-source connection clarity is the first product question to resolve for
      Mercury activation.

      - Invite/setup status is confusing, but invite activity is not proof of activation.

      - The customer is sending sample data separately.

      - Follow-up work stays internal and operating-focused, not investor deck material.'
    created_at: '2023-05-22T10:24:00-07:00'
    folder: Mercury
    id: doc_1785100220049
    title: NYC visit — Mercury operating notes, May 19
  - body: '# Mercury activation reporting definition — May 24 correction


      Owner: Anna Martinez

      Audience: internal only

      Source: Anna’s corrected Looker note from the May 24 review.


      ## Summary

      The prior weekly activation cut was inflated by demo-importer / sample-import
      activity. Accounts that completed sample data flows were counted alongside accounts
      that actually connected a real source or completed a first live sync. That was
      too loose for activation.


      ## Directional cohort check


      | Cohort window | Accounts created | Prior activation cut | Corrected activation
      cut | Inflation source |

      | --- | ---: | ---: | ---: | --- |

      | 2023-05-08 to 2023-05-14 | 96 | 41 (42.7%) | 31 (32.3%) | 10 accounts were
      sample/demo-path only |

      | 2023-05-15 to 2023-05-21 | 88 | 36 (40.9%) | 27 (30.7%) | 9 accounts were
      sample/demo-path only |


      ## What changed

      - demo_importer and related sample flows were pulling sample_import_completed
      into the activation logic.

      - That caused accounts to look activated before any real source was connected.

      - invite_sent correlates with onboarding progress but does not by itself establish
      activation.


      ## Final mapping for Mercury activation

      Count as activated within 7 days if either of these occurs:

      - real_source_connected

      - first_live_sync_completed


      Do not count:

      - sample_import_completed


      Supporting evidence only, not activation by itself:

      - invite_sent


      ## Audience limits

      - This corrected cut is appropriate for internal operating use.

      - Do not use this weekly cut on board or external charts.

      - For board / investor retention and activation framing, stay on the sturdier
      cohort view rather than this weekly directional slice.'
    created_at: '2023-05-24T13:38:00-07:00'
    folder: Mercury
    id: doc_1785100221447
    title: Mercury activation reporting definition — May 24 correction
  - body: Kibo cannot have chicken at all, including treats with chicken meal.
    created_at: '2023-05-24T15:29:00-07:00'
    folder: null
    id: doc_1785100223329
    title: Kibo sitter note — October tentative window
  - body: 'Effective June 1, 2023


      Title

      - Senior Product Designer


      Ownership

      - Priya is the formal owner of Mercury activation/onboarding UX through the
      Q3 launch.


      Rationale

      - Recognizes work she is already doing at that level.

      - Rationale is tied to onboarding polish, activation clarity, and the Mercury
      UX decisions the team already relies on her to make.'
    created_at: '2023-05-31T10:18:00-07:00'
    folder: null
    id: doc_1785101687472
    title: Priya — Senior Product Designer / Mercury UX ownership
  - body: '# Mercury weekly — Jun 5 operating note


      Internal working material for the team; not investor-facing language.


      ## Decisions / calls needed this week

      - Activation chart treatment: decide between historical activation backfill
      and a hard annotation line for the May 24 correction.

      - Onboarding rollout shape: decide between a single launch flag and a tenant-by-tenant
      allowlist.

      - Keep the activation dashboard work in the internal operating lane for now.


      ## Owners / moving pieces

      - Marcus: feature-flag cleanup; collapse stale rollout flags and remove dead
      toggles before Jun 8 so QA is not testing three paths.

      - Anna Martinez: activation dashboard drift; reconcile the dashboard against
      the corrected activation mapping and post an internal-only diff once the numbers
      stop moving.

      - Priya: onboarding-copy QA for the Mercury activation/onboarding pass; scope
      is empty states, source-connect prompts, and first-live-sync copy.


      ## Unresolved blockers

      - Dashboard drift against the corrected activation mapping.

      - Whether to backfill history or annotate the chart break from the May 24 correction.

      - Rollout shape: faster single flag versus safer tenant allowlist.

      - QA matrix complexity if rollout stays tenant-by-tenant.


      ## Follow-up timing

      - Status updates in thread by end of day Jun 6.'
    created_at: '2023-06-05T09:28:00-07:00'
    folder: Mercury
    id: doc_1785104286208
    title: Mercury weekly — Jun 5 operating note
  - body: '# Mercury auth v0.2 readout — Thursday pre-read


      Internal pre-read only. This is a questions-and-non-decisions doc, not a final
      provider recommendation.


      ## Non-decisions

      - Do not re-open custom auth in this readout.

      - Do not treat Clerk versus Auth0 as decided from the sandbox prep alone.

      - Do not make a deploy or production call from this pre-read.


      ## Questions to answer live

      - Sessions: does refresh behave correctly after invite accept or org change?

      - Magic links: what happens on link reuse, expiry, and return-path handling?

      - Organization invites: how do existing-user versus new-user accept flows land
      in the right org context?

      - SSO / admin depth: what admin surface would Scaffold still need to build around
      the provider?

      - Pricing: how should fast MAU growth and org features change the provider risk
      view?


      ## Scope risks

      - Clerk is faster for the sandbox session and magic-link paths.

      - Auth0 may be cleaner if deeper admin controls, domain / IdP management, or
      enterprise SSO behavior comes earlier than planned.

      - Org invites remain the main functional edge case to burn down.


      ## Deploy-discipline checks

      - Use the standard staging pipeline only.

      - No one-off shortcut for staging auth testing.

      - Validate only through a path the team would actually ship.'
    created_at: '2023-06-07T08:43:00-07:00'
    folder: Mercury
    id: doc_1785104289088
    title: Mercury auth v0.2 readout — Thursday pre-read
  - body: '# Mercury auth v0.2 — open questions for Friday decision window


      Internal open-questions note. Leave the provider baseline and deploy / prod
      call unsettled.


      ## What moved in the readout

      - Rishi demoed the Clerk sandbox session path end to end; the happy path worked
      in the sandbox.

      - The magic-link path is working at demo level too.


      ## Open questions

      - Org invites: existing-user versus new-user accept flow is not clean yet.

      - Org context: landing / org-context behavior after accept still needs work.

      - SSO / admin depth: no clean answer yet on how much admin surface Scaffold
      would still need to build around the provider.

      - Provider baseline: Clerk has the faster sandbox path right now, but invite
      and SSO/admin questions are still real.


      ## Decisions not made

      - No provider call came out of the readout.

      - No deploy or production call came out of the readout.


      ## Staging discipline checks

      - Standard staging pipeline only.

      - No shortcut path for auth staging work.

      - Before any production conversation, require a clean staging pass on session
      path, magic link, and org invites.'
    created_at: '2023-06-08T11:23:00-07:00'
    folder: Mercury
    id: doc_1785104290529
    title: Mercury auth v0.2 — open questions for Friday decision window
  - body: '# Mercury auth v0.2 baseline — June 9


      ## Internal baseline decision

      - Clerk is the Mercury v0.2 baseline for sessions, magic links, and organization
      invites for the next internal dogfood build.

      - Green on internal staging: session create and refresh through normal app navigation;
      magic-link login end to end, including resend and expired-link handling; organization-invite
      accept and revoke through the current inviter flow.

      - Explicitly out of v0.2: SSO, deeper admin/org settings and role-management
      work, and enterprise shortcuts around the current invite path.

      - Dogfood note: treat the staging smoke pass as baseline-ready unless an in-scope
      blocker appears; revoked-invite rejection copy is still rough follow-up, not
      a baseline blocker.'
    created_at: '2023-06-09T10:22:00-07:00'
    folder: Mercury
    id: doc_1785105377934
    title: Mercury auth v0.2 baseline — June 9
  - body: '# Mercury operating note — June 12


      Internal working-team material.


      ## Top blockers

      - Org-invite copy cleanup before the next dogfood cut: the invite email and
      accept screen need to read like joining an existing org, not creating a brand-new
      workspace.

      - Release-readiness ownership: the checklist needs one clear home instead of
      living half in Figma and half in review comments.

      - Scope control: admin/org-settings questions should not pull SSO or deeper
      admin controls into this week’s Mercury story.


      ## Owner questions

      - Who owns the final org-invite copy pass before the next dogfood cut?

      - Who owns the release-readiness checklist as one thing?

      - Do admin/org-settings changes stay fully out until after the next dogfood
      cut, or is there a narrower subset?


      ## Keep out of investor framing

      - Do not use SSO or deeper admin controls as part of this week’s Mercury story.

      - Keep this to product movement, blockers, and owner questions; not a broadened
      launch promise.'
    created_at: '2023-06-12T09:25:00-07:00'
    folder: Mercury
    id: doc_1785105381225
    title: Mercury operating note — June 12
  - body: '# Mercury design / release-readiness decision path — June 13


      Attendees: Morgan Chen, Priya, Marcus, Jake


      ## What happened

      - Priya anchored the Mercury activation/onboarding flow decisions in Figma as
      the source of truth.

      - Marcus said “ready in Figma” has been reading as safe to ship even when release-risk
      items are still open.

      - Concrete risks raised: stuck credential/retry handling on first source connection,
      org-invite dead-end risk on the current auth branch, and admin fallback/visibility
      concerns before the deeper admin path exists.

      - Both acknowledged they have been half-routing around each other in Discord
      instead of resolving in one place.


      ## Decision path

      - Design calls for Mercury activation/onboarding stay with Priya.

      - The canonical place for those design decisions is Figma.

      - Release-readiness and dogfood gating stay with Marcus.

      - The canonical place for release-readiness concerns is the implementation checklist
      and release review, not Figma comment threads.

      - If a checklist item requires a design change, link back to the exact Figma
      frame and reopen only that decision.

      - Stop adjudicating this in Discord side threads.


      ## Cleanup

      - Priya keeps design decision notes in Figma.

      - Marcus sends a cleaned implementation checklist with owners and blockers for
      the dogfood build.

      - Discord threads on this topic should point back to either the frame or the
      checklist instead of becoming a third system.


      ## Not magically fixed

      - Priya still feels implementation concerns keep arriving as late redesign.

      - Marcus still feels risk gets labeled implementation detail too early.

      - Tone improved once the split was explicit, but it is still tense.'
    created_at: '2023-06-13T14:04:00-07:00'
    folder: Mercury
    id: doc_1785105381692
    title: Mercury design / release-readiness decision path — June 13
  - body: '# Mercury dogfood release-readiness checklist — June 15


      View: implementation-only

      Exported by Marcus on 2023-06-15 11:06 AM


      Note: design-decision comment threads were removed after the June 13 review.
      For Priya-owned flow/copy calls, use the linked Figma frames instead of debating
      them here.


      | Issue | Owner | Status | Blocker | Notes | Linked source |

      | --- | --- | --- | --- | --- | --- |

      | MERC-214 Session persistence on refresh + browser reopen | Rishi | In QA |
      none | Verify Clerk session survives hard refresh, reopen, and deep-link return
      on the standard-staging build. | n/a |

      | MERC-219 Magic-link resend + expired-state telemetry | Marcus | In progress
      | waiting on final event names from Rishi | Add send/open/success/expired/resend
      instrumentation so the next dogfood pass is measurable. | n/a |

      | MERC-223 Org-invite email copy implementation | Marcus | Ready | none | Apply
      the approved invite email subject/body from Figma; no wording discussion in
      this checklist. | Figma: Mercury activation/onboarding v18, frame INV-03 |

      | MERC-224 Org-invite accept-screen copy implementation | Marcus | Ready | none
      | Swap in the approved join-existing-org language from Figma; current flow works,
      this is clarity cleanup. | Figma: Mercury activation/onboarding v18, frame INV-07
      |

      | MERC-228 Invite accept/revoke audit event | Rishi | In progress | webhook
      naming pass not final | Needed so support can trace who invited and who revoked
      during dogfood. | n/a |

      | MERC-231 Default dogfood org seed + pending invites | Jake | Ready | none
      | Seed 3 internal orgs and 2 pending invites so reviewers are not hand-building
      setup each time. | n/a |

      | MERC-233 Internal support note for known auth limits | Marcus | Drafted |
      none | Note that SSO shortcut requests are later scope for v0.2; route testers
      to password or magic-link for now. | n/a |

      | MERC-236 Rollback checklist for org-invite settings branch | Marcus | Ready
      | none | Standard pipeline only; keep rollback steps attached to the deploy
      checklist. | n/a |


      ## Out of scope for this checklist

      - SSO shortcut / IdP login option.

      - Deeper admin controls around invite policy.


      ## Removed from this view on export

      - Design-decision threads.

      - Copy debates already resolved in Figma.


      ## Operating rule

      - Keep this implementation-only.

      - Design calls should link back to Priya’s Figma frames rather than getting
      reargued in the checklist.'
    created_at: '2023-06-15T11:24:00-07:00'
    folder: Mercury
    id: doc_1785105384089
    title: Mercury dogfood release-readiness checklist — June 15
  - body: '# Mercury activation empty states — June 19 decision note


      Internal working-team material; not a post.


      ## Product decisions — Priya / Figma

      - No source connected: this state does one job, get an admin to connect a real
      source. Primary CTA is “Connect a data source”; setup guide can be secondary.

      - Do not put sample import on the no-source card in a way that reads as activation.

      - If sample import remains anywhere, label it preview only. No success state,
      no “you’re ready,” and no green check from sample data.

      - Invited member before first source: explain that the workspace exists, but
      an admin still needs to connect the first source. Do not tease a CTA the member
      cannot complete.

      - First sync queued: say the source was found and the first live sync is running.
      No fake percentage, countdown, or precision we do not know.

      - Sync failed: make the state actionable with retry plus help docs. Keep user
      copy product-level and do not show connector internals.

      - Sample data path: remove the activated-looking success card. Sample import
      can help people explore, but it cannot masquerade as a live source connection.

      - Do not expose internal measurement language in UI. User copy should talk about
      connecting a real source and seeing first live data arrive.

      - CTA labels locked for now: no source “Connect a data source”; invited member
      “View setup guide”; queued no primary CTA; failed “Try again.”

      - No celebratory success card until a real source is connected and the first
      live data is actually through.


      ## Release-readiness constraints — Marcus

      - If sample import lives on the same surface, it needs separate styling and
      separate event names.

      - Invited-member rendering must distinguish member lacks permission from org
      has no source yet.

      - Use server role/source state for that branch; do not guess from the client
      session token.

      - Wait for server role/source state before rendering the branch. A short loading
      state is better than the wrong action.

      - No queued-sync percent, countdown, stepper, or ETA promise. Neutral copy like
      “This usually takes a couple of minutes” is acceptable.

      - Need a timeout threshold for when queued becomes taking longer than usual,
      otherwise QA cannot test that state.

      - Failed-sync release needs normalized buckets before release: auth / permissions;
      source unavailable / timeout; unknown / retry.

      - Retry must be idempotent so double-click does not create duplicate jobs.

      - No raw vendor errors in UI.

      - Support contact in the failure state is unresolved; docs-only is preferred
      for v0.2 unless support routing is wired.

      - Mobile invited-member and failure copy must be shortened before QA screenshot
      freeze.

      - Behind the scenes, event mapping must stay aligned for engineering, QA, and
      Anna: invite_sent is supporting only, and sample_import_completed stays out.


      ## Unresolved for next review

      - Whether sample data appears anywhere in v0.2 or gets cut entirely.

      - Threshold for switching queued copy to taking longer than usual.

      - Whether support contact appears in sync failed or only docs.

      - Exact success trigger for the first pass: real_source_connected, first_live_sync_completed,
      or both.

      - Final shortened invited-member and failure strings for mobile QA.'
    created_at: '2023-06-19T17:34:00-07:00'
    folder: Mercury
    id: doc_1785122057246
    title: Mercury activation empty states — June 19 decision note
  - body: '# Mercury activation surface release-readiness checklist


      Internal implementation material — not investor-facing narrative.


      Source split:

      - Priya’s June 19 Figma decisions are the product source of truth.

      - Marcus’s checklist is the release / QA constraint source.


      ## Priya product-owner decisions

      - State map for v0.2 stays to the four reviewed branches: no source connected;
      invited member waiting on admin / first source; first sync queued; sync failed.

      - No activated-looking path off sample data.

      - If sample data exists anywhere, it is visually separate, labeled preview-only,
      and excluded from activation events.

      - No source connected keeps the primary CTA “Connect a data source.”

      - Invited member should understand the workspace exists, but an admin still
      needs to connect the first source.

      - Queued sync should reassure without fake progress; no fake percent or countdown.

      - Failed sync should be actionable with retry and help docs while keeping connector
      internals out of user-facing copy.

      - User copy should describe connecting a real source and seeing first live data
      arrive, not internal activation metric language.


      ## Marcus release gates

      - Invited-member branch must render from server role + source state, not client
      token guesses.

      - Org-invite edges must pass on staging: expired invite, double accept, existing
      user already in another org, and member lands before first source exists.

      - Queued-sync state cannot show fake percent or ETA countdown.

      - Failed-sync state needs normalized error buckets and idempotent retry; no
      raw vendor strings in UI.

      - Activation event mapping needs one final pass with Anna / Devon naming before
      merge so sample-import behavior does not leak back into the metric.

      - If docs or help links are not live at release time, cut the secondary CTA
      rather than shipping a dead link.


      ## QA constraints

      - Test matrix: admin vs invited member; source exists vs no source yet; first
      live sync succeeds vs stalls vs fails.

      - Confirm retry creates one job only and does not fan out duplicate work on
      double click / refresh.

      - Confirm state transition after real source connect and after first live sync
      completes.

      - Confirm mobile width on invited-member and failure states after Priya shortens
      copy.


      ## Open items from June 19 review

      - Whether sample data appears anywhere in v0.2 or gets cut entirely.

      - Threshold for switching queued copy to taking longer than usual.

      - Final invited-member copy when org exists but admin has not connected the
      first source.

      - Exact user-facing failure buckets vs what stays collapsed behind the scenes.'
    created_at: '2023-06-21T11:31:00-07:00'
    folder: Mercury
    id: doc_1785122058643
    title: Mercury activation surface release-readiness checklist
  - body: '# Leo Park — Mercury onboarding brief


      ## Start context

      - Leo Park starts July 10 as the Staff Engineer anchor for Mercury release discipline,
      platform seams, and launch readiness.

      - His first week should drop him into the actual Mercury launch work, not a
      generic “meet everyone / ramp on the codebase” plan.


      ## First-week emphasis

      - Release discipline: get oriented on the standard pipeline, release-readiness
      checklist, rollback expectations, and why late production exceptions stay tightly
      controlled.

      - Platform seams: map the auth, onboarding, activation, and release-readiness
      seams where Mercury work crosses product, platform, and QA boundaries.

      - Launch readiness: focus on current blockers that affect July launch-readiness
      feedback, especially where technical ownership or handoffs are fragile.


      ## Handoff points

      - Jake: Mercury weekly cadence, current launch blockers, rollout/merge criteria,
      and the operating spine for launch-critical work.

      - Priya: activation/onboarding UX source of truth, Figma decision path, and
      the launch-critical UX calls she owns through launch.

      - Marcus: implementation checklist, release-readiness constraints, QA/dogfood
      gating, and where release-risk feedback should land.


      ## Hiring note

      - Do not force the second Mercury engineering hire before July launch-readiness
      feedback.

      - Revisit the second req after those signals are clearer rather than treating
      the old two-hire plan as automatic.'
    created_at: '2023-06-23T08:58:00-07:00'
    folder: Mercury
    id: doc_1785127163041
    title: Leo Park — Mercury onboarding brief
  - body: '# Mercury activation surface v0.2 QA triage — Jun 26


      ## Must-fix before the next readout

      - Sample data must stay visually separate, preview-only, and non-activating.
      It cannot look like the real activated path or fire activation analytics.

      - Invited-member rendering must resolve from server role plus source state,
      not an optimistic client branch.

      - Queued first-sync state must stay honest: spinner/status only, with no fake
      percent, ETA, countdown, or primary CTA implying precision we do not have.

      - Failed sync must use normalized error buckets at minimum: auth/permissions,
      source unavailable/timeout, and unknown/retry. Retry must be idempotent and
      cannot enqueue duplicate jobs.


      ## Later polish

      - Setup guide copy can be tightened later if needed.

      - Preview card spacing at small widths can wait.

      - Failed-state iconography cleanup can wait.


      ## Ownership

      - Priya owns design/source-of-truth follow-up.

      - Marcus owns implementation deltas and release-readiness checklist feedback.


      ## Review rule

      - If engineering compresses states for launch risk, call that out explicitly
      in review rather than silently diverging from Priya’s Figma.'
    created_at: '2023-06-26T12:41:00-07:00'
    folder: Mercury
    id: doc_1785127164937
    title: Mercury activation surface v0.2 QA triage — Jun 26
  - body: '# Mercury activation surface v0.2 — internal dogfood gate


      Decision: Mercury activation surface v0.2 is cleared for the next internal dogfood
      under the corrected activation definition.


      Corrected activation definition: activated only when `real_source_connected`
      or `first_live_sync_completed` happens within 7 days; `sample_import_completed`
      is excluded; `invite_sent` is supporting activity only.


      UX source of truth: Priya’s Figma `Mercury / Activation Surface v0.2` four-state
      surface remains the UX source:

      - no source connected

      - invited member waiting on admin / first source

      - first sync queued

      - sync failed


      Implementation gates: Marcus’s Linear checklist carries the implementation gates:

      - sample data remains visually separate / preview-only and excluded from activation
      events

      - invited-member rendering uses server role plus source state

      - queued sync shows honest status only, with no fake percent and no ETA / countdown

      - failed sync normalizes to auth / permissions, source unavailable / timeout,
      and unknown / retry; retry is idempotent; raw vendor strings stay out of the
      UI


      Definition alignment: Anna Martinez confirmed this aligns with the corrected
      May 24 activation definition.


      Follow-up / non-gates: setup-guide copy tightening, small-width preview-card
      spacing, and icon polish are follow-up, not launch gates.'
    created_at: '2023-07-06T10:03:00-07:00'
    folder: null
    id: doc_1785173822015
    title: Mercury activation surface v0.2 — internal dogfood gate
  - body: 'Date: July 10, 2023


      Purpose

      Leo’s first month on Mercury is intentionally narrow and practical: release
      discipline, platform seams, and launch readiness. This is not a broad architecture
      tour or a request for abstract platform recommendations.


      First-month focus

      - Work in real Mercury product states immediately, especially activation/onboarding
      and auth-adjacent seams that can fail in dogfood.

      - Help the team see where launch risk is hiding, where evidence is thin, and
      what needs direct verification before wider dogfood or launch decisions.

      - Use the existing operating cadence; do not create a parallel process.

      - The first useful output is a release-risk readout grounded in evidence, not
      a rewrite plan or architecture memo.


      Jake walkthrough — Mercury weekly and blockers

      - The Mercury weekly is the operating spine for launch-critical work: blockers,
      evidence, decisions, and owner gaps.

      - Current blocker shape is seam risk across activation, auth edges, and proof
      that real states behave as designed.

      - Auth v0.2 baseline in internal builds: Clerk for sessions, magic links, and
      org invites; SSO and deeper admin controls are later scope.

      - No production conversation until the standard staging path is clean on the
      session path, magic link flow, and org-invite flow.

      - Org-invite / invited-member behavior remains a watch area because rendering
      depends on the correct server-role + source-state combination.

      - Retention/activation reporting has two audiences: directional weekly internal
      cuts for operating decisions and sturdier quarterly cohort views for board/investor
      use.


      Priya handoff — Figma source of truth

      - Priya walked Leo through the Mercury activation surface v0.2 file and the
      activation/onboarding frames to start from.

      - Figma is the source of truth for activation/onboarding decisions; quick discussion
      can happen elsewhere, but design calls live in review against the file.

      - Key states: no source connected; invited member waiting on admin / first source;
      first sync queued; sync failed.

      - Locked design logic: sample data is preview-only and visually separate; invited-member
      rendering keys off server role + source state; queued sync shows no fake percent
      or ETA; failed sync uses normalized buckets and clean UI language, not raw vendor
      strings.

      - CTA labels: no source “Connect a data source”; invited member “View setup
      guide”; queued no primary CTA; failed “Try again.”

      - If Leo sees risk, he should point to the exact state/frame and user consequence.


      Marcus handoff — release readiness and thin evidence

      - Marcus framed the handoff as release-readiness constraints, implementation
      checklist feedback, and evidence quality, not design ownership.

      - Some paths look reasonable in review but still lack enough real dogfood evidence,
      especially edge states.

      - Leo should distinguish repeated evidence from demos/screenshots and technically
      implemented but under-proven behavior.

      - A useful readout should call out seam risk, severity, current evidence, and
      the next direct check.

      - Do not turn every rough edge into launch drama, but do not wave through regressions
      or misleading states.'
    created_at: '2023-07-10T11:36:00-07:00'
    folder: null
    id: doc_1785177267733
    title: Leo Park — Mercury first-month ramp
  - body: 'Use this as a short structured readout, not a platform memo.


      ## Top risks

      - Name the concrete Mercury launch risk.

      - Tie it to the product seam or state where it can surprise us.

      - Keep the scope to launch readiness.


      ## Evidence source

      - State what evidence exists now: dogfood account, staging pass, screenshot,
      log, bug-bash finding, Figma state/frame, or checklist row.

      - Separate repeated evidence from one-off demos/screenshots.

      - Call out where evidence is still thin.


      ## Severity / confidence

      - Severity: Low / Medium / High user or launch impact.

      - Confidence: Low / Medium / High confidence in the risk assessment.

      - If implemented but under-proven, say that directly.


      ## Next verification

      - The smallest direct check that would raise confidence.

      - Who or what state needs to be exercised.

      - What artifact should be captured: screenshot, log, trace, or branch/state
      confirmation.


      ## Explicit exclusions

      - No abstract platform recommendations.

      - No broad architecture memo.

      - No rewrite plan or generic platform wishlist unless there is direct Mercury
      launch impact.'
    created_at: '2023-07-12T09:34:00-07:00'
    folder: null
    id: doc_1785177270322
    title: Mercury release-risk readout — Leo template
  - body: 'Date: July 14, 2023

      Attendees: Morgan Chen, Leo Park, Jake, Priya, Marcus


      Framing

      - This was a release-risk and evidence readout, not a platform roadmap.

      - The lens was where Mercury can still surprise us at seams, especially activation
      behavior depending on auth/org state and areas where dogfood evidence is thin.

      - This is not an owner-split launch ledger.


      ## Risk 1: org-invite roles vs activation-state seam

      Highest platform-seam risk is the invited-member branch because rendering depends
      on server role + source state, and those do not always settle at the same time.


      Evidence

      - Only 2 real dogfood invited-member accounts have gone end to end.

      - One bug-bash pass needed refresh/re-entry before the UI settled on the expected
      branch.

      - Confidence is still coming more from happy-path staging than repeated real
      dogfood coverage.


      Severity / confidence

      - High severity, medium confidence.


      Next verification

      - Run more real invited-member dogfood accounts across admin-first vs invitee-first
      orderings.

      - Verify no path creates an activated-looking state without a real source or
      first live sync.

      - Confirm sample data stays visually separate / preview-only and never shifts
      the branch into something that looks activated.

      - Watch CTA selection on first load after invite accept.


      Room notes

      - Priya: design intent is still the four branches; no pseudo-activated middle
      state.

      - Jake: this is release risk because it crosses auth/org state, not just copy
      or UI.

      - Marcus: need enough evidence to know whether wrong-CTA cases are rendering
      issues or stale-state timing.


      ## Risk 2: release-readiness evidence gaps are themselves material

      Leo separated implemented from proven. Some paths may be close in code but still
      lack enough boring real-world evidence to call them ready.


      Evidence

      - Invited-member branch only has 2 real dogfood accounts.

      - Queued-sync retry logs are sparse even after removing fake progress / countdown
      behavior.

      - Failed-sync screenshots are cleaner, but sample depth is still shallow.


      Severity / confidence

      - High severity, high confidence on the evidence gap.

      - Lower confidence on how many user-facing bugs remain underneath it.


      Next verification

      - Targeted dogfood pass exercising each branch with saved screenshots and logs.

      - Collect at least one real queue -> retry -> recovery trace for queued sync.

      - Separate path unproven from path actually broken in the next pass.


      ## Risk 3: failed-sync cleanup still needs full verification

      The failed state is close, but not fully done until every normalized bucket
      is verified end to end.


      Evidence

      - One screenshot still leaks a raw vendor string.

      - Current fixes seem to cover the obvious path, but no one could confirm that
      auth/permissions, source unavailable/timeout, and unknown/retry are all equally
      clean.


      Severity / confidence

      - Medium severity, medium confidence.


      Next verification

      - Retest each failed bucket with captured UI.

      - Confirm no raw vendor strings leak.

      - Confirm retry remains idempotent.


      Room notes

      - Marcus said the retry action looks better but still wants proof that bucket
      text and UI stay normalized on every branch.

      - Priya noted the warning-circle direction still seems right; the issue is verification,
      not revisiting the icon choice.


      ## Later polish vs potential blockers

      - Setup-guide copy can wait unless it causes a wrong action or real confusion
      in the invited-member branch.

      - Small-width spacing can wait unless it clips or overlaps on a supported width.

      - Failed-state icon polish can wait unless it obscures state meaning.

      - Priya aligned with keeping polish later as long as branch distinctions stay
      crisp.

      - Jake said not to let a polish list turn into a second scope track before the
      next Mercury cycle.


      ## Explicit exclusions

      - No abstract platform recommendations.

      - No provider debate or broader auth rewrite scope.

      - No SSO/admin-depth wishlist.

      - Do not convert this into an owner-split launch ledger yet.


      ## Questions to verify next

      - Can we prove invited-member rendering across real role/source-state permutations,
      not just the happy path?

      - Do we have enough queued-sync retry evidence to say recovery is understandable
      without fake progress?

      - Is failed-sync normalization actually complete across all buckets, or just
      mostly clean on the common path?

      - Which gaps are real launch blockers vs thin proof on otherwise-correct behavior?

      - What is the smallest next dogfood pass that materially raises confidence before
      we widen exposure?'
    created_at: '2023-07-14T13:22:00-07:00'
    folder: null
    id: doc_1785177271296
    title: Leo Park — Mercury release-risk readout — 2023-07-14
  - body: '# Pinecone integration notes — signature-header casing resolved


      - Date: 2023-07-18

      - Contract: header-only `X-Scaffold-Workspace` + `X-Scaffold-Signature`

      - Sandbox rerun result: pass for preserved `X-Scaffold-Signature`

      - Sandbox rerun result: pass for lowercased `x-scaffold-signature` against the
      same body/workspace

      - Query-parameter fallback: none used; not approved

      - Status: signature-header casing failure is no longer an open blocker; connector
      can proceed on the agreed header-only contract.'
    created_at: '2023-07-18T14:27:00-07:00'
    folder: null
    id: doc_1785178395249
    title: Pinecone integration notes — signature-header casing resolved
  - body: '# Mercury launch-readiness questions for July 24


      ## Invited-member coverage

      - Which real invited-member state combinations remain unexercised or not clean?

      - For the four dogfood accounts already exercised, do we have server role +
      source state matched against rendered state, not screenshot expectations alone?

      - What minimum additional coverage would let us lower this from top launch risk
      before wider dogfood?

      - What evidence would still block wider dogfood even if the remaining screenshots
      look correct?


      ## Queued-sync retry evidence

      - Can we capture at least one more real dogfood queued-sync retry run before
      the next decision point?

      - Does the retry path avoid misleading progress language, bad state carryover
      after retry, and branch flips on refresh?

      - If we only have one more run, is that enough for wider dogfood, or still too
      thin?


      ## Failed-sync unknown/retry proof

      - What is the clean screenshot set needed for `unknown / retry`?

      - Does that branch show normalized copy, idempotent retry behavior, and no raw
      vendor strings?

      - Are auth/permissions and source-unavailable improved enough to separate from
      the unresolved unknown/retry bucket?


      ## Confidence before wider dogfood

      - What evidence would actually raise confidence: more accounts, more retry logs,
      branch-specific screenshots, or a specific state-combination matrix?

      - Which evidence gaps are launch risks versus follow-up documentation?

      - What decision would we make on July 24 if invited-member coverage improves
      but queued-sync retry remains a one-run sample?

      - What decision would we make if failed-sync is improved but `unknown / retry`
      remains unverified?'
    created_at: '2023-07-21T13:18:00-07:00'
    folder: null
    id: doc_1785178396282
    title: Mercury launch-readiness questions for July 24
  - body: '# Mercury headcount checkpoint — external launch-readiness feedback checklist


      Purpose: Internal product-readiness input for the Mercury headcount checkpoint
      before deciding any second Mercury engineering req. This is not board, investor,
      or B-round material.


      ## Feedback needed before any req decision


      ### 1. Source setup failure cases

      - What does an external user see when the first source connection fails?

      - Can they distinguish auth/permissions trouble, source unavailable/timeout,
      and unknown failures without us translating?

      - Does recovery feel self-serve, or does it require vendor/API knowledge?


      ### 2. Admin handoff

      - If an admin starts setup and invites an operator or teammate, does the invited
      person land in a sane next step?

      - What happens if the invited member arrives before the first source is fully
      connected?

      - Is the line between waiting on admin/first source and something being broken
      obvious?


      ### 3. Time to first sync

      - How long does it take from first connection to first live sync in normal cases?

      - If sync is queued or retried, what reassures the user that the system is working
      without fake progress?


      ### 4. Failure-state legibility

      - Which failure states are understandable on first read to an external user?

      - Which states still require someone from Scaffold to narrate what happened?


      ### 5. Confidence to try Mercury

      - Clean first-run path end to end.

      - One or two believable recovery examples when setup or sync fails.

      - Proof that invited-member/admin handoff is not brittle.

      - Clear separation between sample/preview data and real activated state.

      - Credible time-to-first-sync range, not a promise.


      Decision use: Feed the req discussion only after these signals are in hand;
      do not convert this checklist into external collateral.'
    created_at: '2023-07-25T13:07:00-07:00'
    folder: Mercury
    id: doc_1785179886580
    title: Mercury headcount checkpoint — external launch-readiness feedback checklist
  - body: No poultry-based treats or food for Kibo. Chicken meal counts as poultry.
      If a label has chicken, turkey, duck, poultry meal, or similar, skip it and
      ask Morgan instead of guessing.
    created_at: '2023-08-01T19:49:00-07:00'
    folder: null
    id: doc_1785189090973
    title: Kibo care note — food rule
  - body: 'Internal operating decision from the Aug 2 review with Devon Hayes and
      Jake.


      - Evergreen Bank is the anchor enterprise design partner for the first external
      Mercury wave.

      - Rationale: Evergreen’s admin/security review is demanding enough to pressure-test
      the current Mercury path under real enterprise scrutiny without turning wave
      1 into a bespoke build.

      - Boundary: the wave validates the product and launch readiness Scaffold actually
      has. If the conversation depends on one-off commitments or custom work, it is
      outside wave-1 fit.

      - Acme stays excluded from fresh Mercury materials while the NDA scope thread
      is active.

      - No new packet, screenshots, docs, or disputed materials should be sent to
      Acme while the scope issue remains open.

      - Acme’s prior feedback may inform internal blocker lists and MER-1279 only.

      - Record Acme’s reason as the active NDA scope constraint, not lack of interest.

      - Operating context only; do not use Evergreen, wave selection, or MER-1279
      as investor proof language.'
    created_at: '2023-08-02T10:56:00-07:00'
    folder: null
    id: doc_1785189091458
    title: Mercury first external design-partner wave — Aug 2 decision
  - body: '# Mercury launch-room note — Aug 10 operating boundary


      ## Plan

      - Wave 1 on Aug 10 is Evergreen Bank only.

      - Live scope is bounded to the current Mercury path: Clerk-backed sessions,
      magic links, org invites, the corrected activation surface, and sample data
      that is preview-only, visually separate, and non-activating.

      - Out of scope for wave 1: SSO, deeper admin-control promises, one-off enterprise
      work, bespoke side commitments, or scope expansion.


      ## Owners

      - Priya owns final activation/onboarding UX calls; Figma remains the source
      of truth.

      - Settled directions stay settled: failed sync keeps the warning-circle direction,
      CTA labels stay locked, queued sync shows no fake progress, and sample data
      cannot read as activated.

      - Marcus owns implementation gates and dogfood blockers in MER-1279, including
      session path, magic links, org invite handoff, and activation-surface behavior.

      - Leo owns cross-service seam risk notes in MER-1279; keep updates launch-relevant
      with evidence and next verification.

      - Anna uses the corrected activation definition only: activated = real_source_connected
      or first_live_sync_completed within 7 days; sample_import_completed is out and
      invite_sent is supporting activity only. Weekly cuts stay directional/internal.

      - Jake runs the Aug 10 cadence and keeps the Evergreen account boundary narrow.


      ## Live watch items

      - Invited-member coverage remains a small sample across role/source combinations.

      - Queued-sync retry still needs one more clean run tied to logs/screens.

      - Keep both in MER-1279 unless cleaner evidence lands.


      ## Escalation and framing

      - Call Morgan only if scope tries to widen, there is a real launch/no-launch
      question, or a ledger watch item becomes an actual blocker.

      - Keep launch evidence operating/internal. Do not turn wave 1 into board language,
      investor language, or a generic proof claim.'
    created_at: '2023-08-09T17:58:00-07:00'
    folder: Mercury
    id: doc_1785192081217
    title: Mercury launch-room note — Aug 10 operating boundary
  - body: '# Evergreen enterprise-readiness gap list


      Status: next-phase enterprise-readiness follow-up, not Mercury v0.2 launch blockers,
      not custom roadmap promises, and not external proof language.


      ## Current wave call

      - Evergreen is technically clean enough to keep going.

      - The current Mercury v0.2 launch blocker list and launch scope stay unchanged.

      - Normal support follow-up stays in the existing launch ledger.

      - SSO is not being added to Mercury v0.2.


      ## Next-phase enterprise-readiness follow-up

      - SSO timing / packaging question from Evergreen security and procurement.

      - Audit history for admin changes.

      - Clearer separation between admin permissions and billing-owner responsibilities.

      - Self-serve procurement packet that can stand on its own without Morgan or
      Devon needing to live-explain the product.


      ## Comms guardrail

      Keep any external answer bounded to the current Mercury test flow. Do not use
      this note for SSO timing, admin-roadmap language, procurement-packet dates/promises,
      custom roadmap commitments, or external proof-point framing.'
    created_at: '2023-08-21T08:32:00-07:00'
    folder: Internal
    id: doc_1785271735256
    title: Evergreen enterprise-readiness gap list
  - body: '# Mercury pricing decision — hybrid platform minimums


      ## Decision

      We are no longer treating Mercury pricing as a pure-MAU-versus-pure-seat debate.
      For new Mercury design-partner and post-launch quotes, use the hybrid model
      below.


      ## Quote guidance

      - Pilot platform minimum: $2,500/month, including up to 50 monthly active developers

      - Growth platform minimum: $7,500/month, including up to 200 monthly active
      developers

      - Overage: $1,000 per additional 50 monthly active developers

      - Enterprise add-ons such as SSO, audit logs, and advanced admin controls are
      quoted separately only after those features actually ship


      ## Rationale

      This keeps the usage-ramp logic honest while giving Devon a cleaner floor for
      forecasting and procurement conversations.'
    created_at: '2023-08-29T08:58:00-07:00'
    folder: Internal
    id: doc_1785274730003
    title: Mercury pricing decision — hybrid platform minimums
  - body: '# September Mercury metrics package — board and H2 prep bounds


      Status: internal prep bounds

      Source: Anna Martinez’s September Mercury metrics package

      Data cutoff: Sep 4, 2023 EOD PT

      Audience: Morgan, Devon, Anna


      ## Purpose

      Preserve the useful board/H2 operating read from the September Mercury package
      without turning it into outside proof.


      The package should be used as two reporting layers:


      1. Board-operating alignment and selective H2 prep

      2. Internal weekly diagnostics for operating decisions only


      ## 1) Board-operating alignment and selective H2 prep

      Use Anna’s sturdier cohort view for board-facing retention context, not the
      weekly activation movement. Activation is counted only when an account hits
      `real_source_connected` or `first_live_sync_completed` within 7 days of workspace
      creation; sample-preview-only accounts are excluded from the denominator.


      What the board-operating layer can support:

      - September design-partner activation is materially cleaner than the repaired
      May comparable baseline on the current real-source/live-sync definition.

      - The current design-partner cohort is 8 / 11 activated within 7 days, versus
      4 / 10 in the repaired May comparable cut.

      - Admin friction is down across the design-partner cohort: median days to first
      invited member accepted improved from 5.4 to 2.3; accounts needing manual admin
      intervention moved from 6 / 10 to 2 / 11; accounts reaching a first non-owner
      user within 7 days moved from 3 / 10 to 7 / 11.

      - Evergreen Bank adds enterprise-pattern substance for internal and board operating
      context: through Sep 4 it shows 4 admin users touching setup/settings, 12 invited
      members, 3 real sources connected, and successful live-sync activity on 8 distinct
      days.


      Safe framing: the September package supports board operating alignment and selective
      H2 prep because activation and admin handoff are cleaner than May and Evergreen
      contributes meaningful enterprise-pattern evidence.


      ## 2) Internal weekly diagnostics layer

      The corrected weekly activation cuts are internal operating input only. They
      are useful for debugging admin/setup friction, sample-preview exclusions, and
      account-mix questions, but they should not be used in board notes, board charts,
      investor materials, external communication, or customer communication.


      ## Bounds and caveats

      - Expansion remains uneven account to account: 3 accounts look meaningfully
      up, 3 look mostly flat, and 2 remain choppy or down.

      - Evergreen is meaningful enterprise-pattern evidence, but it is still one account
      and not a blanket enterprise-validation claim.

      - Evergreen also keeps the enterprise-readiness boundary visible: SSO timing,
      audit/admin depth, admin-versus-billing owner separation, and procurement packaging
      remain follow-up items, not Mercury v0.2 launch scope or external proof.

      - This package does not prove retention is solved.

      - This package does not prove expansion is solved.

      - This package does not make the Mercury story external-ready.

      - Do not use the weekly activation movement as a board, investor, customer,
      or external proof claim.


      ## Short version for Morgan / Devon

      The September Mercury package is materially better than the May operating read
      on cleaner activation and admin handoff, and Evergreen adds enterprise substance.
      Keep the downside in the same sentence: expansion remains uneven, weekly activation
      movement is internal-only, and the package is not outside-ready proof.'
    created_at: '2023-09-06T10:47:00-07:00'
    folder: Internal
    id: doc_1785275710754
    title: September Mercury metrics package — board and H2 prep bounds
  - body: 'Mercury / Evergreen procurement packet

      Final — September 13, 2023

      Commercial/procurement owner: Devon Hayes


      1. Purpose

      This packet gives Evergreen Bank a concise procurement/security review summary
      for the current Mercury design-partner deployment. It covers the commercial
      model, present login/setup scope, current admin/security posture for the bounded
      launch experience, and known enterprise-readiness gaps that remain outside launch
      scope. It is written for asynchronous procurement/security review before wider
      internal routing.


      2. Commercial model

      Mercury uses a hybrid pricing model based on monthly active developer usage,
      not purchased seats and not directory size.


      Current bands:

      - Pilot: $2,500/month platform minimum, including up to 50 monthly active developers.

      - Growth: $7,500/month platform minimum, including up to 200 monthly active
      developers.

      - Overage: $1,000 per additional 50 monthly active developers.


      Counting notes:

      - Monthly active developer usage is the pricing driver.

      - Scaffold internal/test users do not count toward usage.

      - Preview/sample-only behavior is separate from activation reporting and should
      not be treated as usage proof by itself.


      Enterprise add-ons:

      SSO, audit history for admin changes, and deeper admin controls are not included
      in the current launch scope. They are roadmap-dependent add-ons and would be
      quoted separately only after they ship.


      3. Current Mercury scope

      The current Mercury design-partner scope is the live bounded experience now
      in use:

      - Clerk-backed sessions.

      - Magic-link sign-in.

      - Organization invites.

      - Setup flow oriented around connecting a real source.

      - Preview/sample data available only as preview behavior and not activating
      by itself.

      - First live sync path in product.


      Current activation definition for operating review:

      - real_source_connected within 7 days; or

      - first_live_sync_completed within 7 days.


      Preview/sample-only behavior does not activate an account and should not be
      described as equivalent to real source connection or live sync completion.


      Not in current launch scope:

      - SSO.

      - Audit history for admin changes.

      - Deeper admin controls beyond the current bounded experience.

      - Expanded enterprise/security packaging beyond the current design-partner flow.


      4. Current login / setup experience

      For the present Mercury flow, user access is handled through magic links and
      organization invites. Session handling is Clerk-backed. The intended path is:

      1. Invited user enters through the magic-link / invite flow.

      2. User lands in the Mercury workspace context.

      3. User connects a real source.

      4. User reaches first live sync.


      Preview/sample behavior may be shown during evaluation, but preview/sample-only
      behavior does not activate the account.


      5. Current admin / security readiness for present scope

      Current readiness should be read as sufficient for the bounded design-partner
      experience, not as a full enterprise admin/security package.


      What we can say today:

      - Access is handled through the current magic-link and invite flow.

      - Organization-level invitation exists in the current Mercury experience.

      - The launch experience is bounded and intentionally narrower than a full enterprise
      rollout.

      - Current product facts should be reviewed against the present scope, not against
      a broader enterprise-control checklist.


      What this packet does not imply:

      - Mercury already includes full enterprise-ready login controls.

      - Current admin behavior covers all enterprise audit/control requirements.

      - Later-scope items are part of the live launch package today.

      - Evergreen has a bespoke roadmap path or custom roadmap commitment.


      6. Known enterprise-readiness gaps

      Open follow-up items surfaced in Evergreen discussions and internal review:

      - SSO timing.

      - Audit history for admin changes.

      - Clearer separation between admin permissions and billing-owner controls.

      - Stronger procurement/self-serve explanation materials that can stand on their
      own without Morgan or Devon live-explaining them.


      These are enterprise-readiness follow-up items. They are not part of Mercury
      v0.2 launch scope, and they should be treated as roadmap-dependent add-ons to
      be quoted only after they ship.'
    created_at: '2023-09-13T10:18:00-07:00'
    folder: Mercury
    id: doc_1785276673220
    title: Mercury / Evergreen procurement packet — final
  - body: 'After the September 24 Lake Merritt loop with Kibo and breakfast with Jamie:


      - Lake Merritt is the frictionless local running fallback from the Oakland apartment.

      - It is not the iconic bay run, but it works without letting Embarcadero + BART
      logistics eat the whole morning.

      - Embarcadero runs are no longer treated as protected every day from Oakland.

      - Keep Embarcadero runs for SF-office mornings when timing actually fits.'
    created_at: '2023-09-24T11:18:00-07:00'
    folder: null
    id: doc_1785278547455
    title: Running/logistics note — Lake Merritt fallback
  - body: 'Sep 28, 2023 — Morgan/Devon decision


      Decision:

      - Reopen a selective investor path in October; not a September restart and not
      a broad process.

      - Elena Volkov is first because she is warm context from substantive retention
      feedback; the call is calibration on the real Mercury story, not a signal that
      Scaffold is raising widely.

      - Keep the investor list short and keep narrowing it to firms that can underwrite
      the honest Mercury story.

      - The October package can use September Mercury metrics, Evergreen’s enterprise-readiness/procurement
      signal, and hybrid pricing, but must preserve the uneven-expansion caveat.

      - September Mercury package framing remains bounded: helpful progress, not proof
      that retention or expansion is solved.

      - Evergreen is evidence of enterprise demand/procurement seriousness, not proof
      enterprise readiness is done; keep SSO, audit history for admin changes, admin-vs-billing-owner
      separation, and packet-readiness gaps explicit.

      - Hybrid pricing makes the commercial story legible but must not imply enterprise
      add-ons or bespoke roadmap promises.

      - Random investor coffees and opportunistic September calendar fill stay out
      until the package is ready.

      - Use “selective October reopen” or “October prep”; avoid “process is on” and
      loose “proof points” language unless caveats are explicit.

      - Board-note language should reflect prep, not a launched process.


      Next owner:

      - Devon keeps trimming the short list.

      - No outreach beyond Elena until the package gets one more clean pass and can
      tell the story without hand-waving on expansion or enterprise gaps.'
    created_at: '2023-09-28T17:49:00-07:00'
    folder: null
    id: doc_1785278550916
    title: Decision record — selective October B-round reopen
  - body: '# March Tokyo trip — pre-planning gates


      Private checklist only. No bookings, no calendar holds, and no serious planning
      unless the gates below are actually true.


      ## 1. Financing close

      - Northstar Series B close is actually done, not just tracking toward the February
      22 target.

      - Board consent, Sofia/Northstar board-seat mechanics, written-consent structure,
      signature authority, holder list, notice schedules, and final signature packets
      are clean/resolved.

      - No close-thread spillover that would make March travel irresponsible.


      ## 2. Scaffold coverage

      - Morgan can name real coverage for the days away, including leadership escalation,
      customer/support coverage, and any close/post-close follow-through.

      - No board, Northstar, legal, or signature cleanup needs Morgan live during
      the window.

      - Product/customer threads are covered without turning the trip into surprise
      emergency coverage for the team.


      ## 3. Jamie’s schedule

      - Jamie has an actual March window she can protect, not just a maybe.

      - Both of us can name dates that are genuinely protected before any hold or
      search.

      - Hospital/work schedule and recovery buffer are clear.


      ## 4. Kibo and house logistics

      - Kibo care is confirmed for the full window, including his food/treat restrictions.

      - House/apartment coverage is handled: keys, mail/packages, plants/trash, and
      emergency contact path.


      ## 5. Trip basics to verify

      - Candidate trip length and date range for a shorter Tokyo trip.

      - Passport/entry requirements, flight routing, lodging neighborhood, budget,
      and jet-lag buffers.

      - Weather/packing basics and any must-book activities.

      - Return buffer before any immovable work or hospital-schedule commitments.


      ## Decision rule

      If any gate is fuzzy, keep this as a conversation only. Do not create calendar
      holds, search/book flights or hotels, or promise dates until the close is done
      and both schedules are protectable.'
    created_at: '2024-02-14T18:08:00-08:00'
    folder: Private
    id: doc_1785485378291
    title: March Tokyo trip — pre-planning gates
  - body: '# March Tokyo trip — final logistics


      - Protected travel window: Thu Mar 7 through Tue Mar 12, 2024. Booked, not tentative.

      - Travelers: Morgan Chen and Jamie.


      ## Flights

      - Outbound: JAL 1, San Francisco → Tokyo Haneda, departs Thu Mar 7 at 12:40
      PM PST and arrives Fri Mar 8 at 4:55 PM JST. Confirmation H7K4Q2.

      - Return: JAL 2, Tokyo Haneda → San Francisco, departs Tue Mar 12 at 6:25 PM
      JST and arrives Tue Mar 12 at 11:10 AM PDT. Confirmation H7K4Q2.


      ## Hotel

      - Trunk Hotel Shibuya, check-in Fri Mar 8 and check-out Tue Mar 12. Confirmation
      54188231.


      ## Jamie schedule

      - Hospital side is clear for Mar 7–12.

      - No call or coverage conflict is blocking the trip.

      - Jamie said the window is genuinely protectable, not a soft maybe.


      ## Kibo care

      - Kibo stays local in Oakland; local care is confirmed for the full trip window.

      - SMS is the channel for caregiver instructions and daily updates.

      - Key handoff and food/walk rundown happen before airport day.

      - Hard no: no poultry-based food or treats — no chicken, turkey, duck, poultry
      meal, chicken meal, or label-adjacent poultry. If a label is unclear, skip it
      and ask. Normal food is set aside; no substitutions.

      - Care rhythm: morning walk and breakfast first thing; midday potty break if
      possible; evening walk, dinner, water refresh, and confirm he ate.


      ## Work handoff

      - Morgan is away Thu Mar 7 through Tue Mar 12.

      - Devon Hayes owns non-urgent investor close-out follow-up while Morgan is away.

      - If something truly material appears, flag Morgan; otherwise keep it moving
      without creating travel-time noise.

      - Use Discord for the handoff, not Slack.'
    created_at: '2024-02-28T15:22:00-08:00'
    folder: null
    id: doc_1785523421168
    title: March Tokyo trip — final logistics
  - body: 'March 19, 2024 private note: Jamie and I kept the anniversary plan low-key
      in Oakland. I blocked tonight as personal time and declined the movable late
      investor catch-up instead of treating the evening as overflow.


      Rule going forward: anniversaries are protected personal dates by default. Normal
      work should route around them; work only cuts in for a real production-level
      emergency or something equally real.'
    created_at: '2024-03-19T11:52:00-07:00'
    folder: Private
    id: doc_1785535327070
    title: Private note — anniversary protected personal-date rule
  - id: doc_1786405354993
    title: Kibo sitter notes — June 7, 2024 vet summary
    body: '# Kibo sitter notes — June 7, 2024 vet summary


      After-Visit Summary — Kibo

      Visit date: June 7, 2024

      Location: Oakland

      Patient: Kibo

      Present with: Morgan Chen and Jamie

      Visit type: Routine check


      ## Reason for visit

      Routine check-in for Kibo before summer weather settles in.


      ## Summary from today

      Kibo is stable overall at this routine visit.


      The main items discussed were:

      - Mild weight creep.

      - Some fatigue in warmer weather.

      - Keeping his food routine simple and measured.

      - Preserving the strict no-poultry food rule.

      - Shifting walks earlier on hot days.

      - Planning a routine dental follow-up in fall 2024.


      ## Food and treats

      Keep Kibo’s food boring and consistent. Do not improvise with new foods or rich
      treats.


      Measure his regular food rather than free-pouring or adding extras. Avoid extra
      snacks unless Morgan and Jamie have specifically set them out for Kibo.


      Hard no: Kibo must not receive poultry-based food or treats.


      For Kibo, poultry includes chicken, turkey, duck, poultry meal, chicken meal,
      or similar label ingredients. If a label contains chicken, turkey, duck, poultry
      meal, chicken meal, or anything similar, do not give it to him. Skip it and
      ask Morgan instead of guessing.


      ## Warm-weather activity

      Kibo has had some fatigue in warmer weather. On hot days, move walks earlier
      when it is cooler and keep the rest of the day lower-key rather than adding
      extra activity in the heat.


      ## Weight note

      Kibo has mild weight creep. The plan is to keep portions measured, keep food
      consistent, and avoid added treats or substitutions.


      ## Dental follow-up

      Plan a routine dental follow-up in fall 2024.


      ## Caregiver/sitter note

      If someone else is watching Kibo, give them the food rule exactly as written:


      No poultry-based treats or food for Kibo. Chicken meal counts as poultry. If
      a label has chicken, turkey, duck, poultry meal, chicken meal, or similar, skip
      it and ask Morgan instead of guessing.


      ## Plan until next routine follow-up

      - Keep food simple, consistent, and measured.

      - No poultry-based food or treats under any circumstances.

      - Move walks earlier on hot days.

      - Keep warmer days quiet if Kibo seems tired from the heat.

      - Schedule routine dental follow-up for fall 2024.'
    folder: null
    created_at: '2024-06-07T15:18:00-07:00'
  - id: doc_1786657478276
    title: October Oakland rent receipt
    body: 'Resident Portal

      Payment Receipt


      Receipt posted: Thursday, October 3, 2024, 8:14 AM PT

      Apartment: Unit 3B, Oakland, CA

      Residents: Morgan Chen; Jamie

      Lease term on file: October 1, 2024 through September 30, 2025


      Payment status

      - Autopay received and posted

      - Payment date: Tuesday, October 1, 2024

      - Applied to: October 2024 base rent

      - Receipt amount: $4,280.00

      - Payment method: Bank account ending 4821 (autopay)

      - Confirmation number: RP-2024-10-01-4280-3B


      Current resident ledger

      - October 2024 base rent: $4,280.00 — Paid

      - October 2024 utility bill-backs: Pending — not yet posted

      - Other charges due now: $0.00


      Bank memo shown in portal

      - Combined apartment debit: $4,280.00

      - Separate utilities line: Pending


      Portal note

      This receipt reflects the posted rent payment only. Utility bill-backs, if applicable,
      may appear as a separate line item after statement generation.


      Footer

      Resident Portal receipt for Unit 3B, Oakland, CA

      Residents on account: Morgan Chen; Jamie'
    folder: household records
    created_at: '2024-10-03T09:21:00-07:00'
  - id: doc_1786940694520
    title: Compass v0.1 action-trigger checklist
    body: 'Owner checklist


      | Signal | Trigger | Who sees it | Evidence / caveat | Source-quality requirement
      | Not-building line |

      | --- | --- | --- | --- | --- | --- |

      | Renewal-risk / admin-friction | Only trigger when it points to a named account-owner
      follow-up and the specific admin friction causing risk. | Nadia owns the customer-growth/account-team
      script; Sarah supplies account-thread context; Anna keeps definitions/caveats
      attached. | Caveat must travel with the signal; uneven account notes can make
      the risk too thin. | Sarah marks which thread notes are reliable vs. too thin
      before the signal is used. | Not a board dashboard, not a new hiring lane, and
      not a prettier internal dashboard. |

      | Post-first-live-sync expansion prompt | Trigger only after first live sync
      is live and teammate-invite/admin-role basics are visible. | Nadia owns the
      script/use case; Jake owns product sequencing; Leo checks data/platform seams
      before anything leaves the current team. | Evidence should show real first-live-sync
      completion plus visible invite/admin basics; caveat any missing seam or partial
      admin state. | Use only source data Leo/Jake can defend; do not show outside
      the current team before the seam check. | Not a platform build while January
      Mercury activation is active; no custom board dashboard. |

      | Account-note source quality | Trigger follow-up only when account-thread notes
      are reliable enough to support a named action. | Sarah owns the source-quality
      read; Anna owns definition/caveat framing; Nadia decides whether it becomes
      a customer-growth/account-team script. | Caveat thin or uneven notes explicitly;
      no metric-looking signal from weak notes. | Sarah labels reliable vs. too-thin
      notes before use. | Not a metrics view, dashboard, board artifact, or reason
      to open a new hiring lane. |


      Operating boundary: Compass v0.1 should produce action triggers and owner scripts/checks
      only. If the work starts becoming a dashboard, platform build, board dashboard,
      or hiring-lane argument, stop and bring it back to Morgan.'
    folder: null
    created_at: '2025-01-22T09:18:00-08:00'
  - id: doc_1742836080005
    title: Compass false-start review agenda
    body: '# Compass false-start review agenda


      Purpose: Decide what evidence would justify April work without turning Compass
      into an internal metrics-surface polish pass.


      1. Evidence: for each signal, name the account, source, caveat, and whether
      it triggered any concrete customer or account-team action.

      2. Owner action: for renewal-risk/admin-friction and post-first-live-sync expansion
      signals, name the action, owner, and next customer/account-team step.

      3. Account-note quality: Sarah separates reliable account-thread evidence from
      thin notes; Nadia calls out where scripts need clearer source material.

      4. Data/platform seams: Leo names seams or reliability gaps that must be checked
      before broader signal exposure; Jake flags anything at risk of becoming dashboard/platform
      build.

      5. Customer-material boundaries: Evergreen can use current-state annual-account
      context; Acme remains live-only review of Acme’s own signals with no written
      materials, screenshots, Evergreen-derived examples, or packet excerpts.

      6. Unresolved scope decisions: do not decide in this meeting pre-read whether
      April work is narrowed, whether owners change, or whether any board/customer
      narrative exists yet.


      Output: owner group agrees what evidence counts as behavior change, what stays
      explicitly out, and which open decisions go to the quarter-close review.'
    folder: null
    created_at: '2025-03-24T10:08:00-07:00'
  - id: doc_1742941320006
    title: Compass action-prompt options — non-decisional brief
    body: '# Compass action-prompt options — non-decisional brief


      Status

      - Compass scope has not been narrowed yet. The quarter-close review still needs
      to decide April scope, owners, behavior-read criteria, safe accounts, and narrative
      boundaries.

      - The broad signal surface still reads too much like Scaffold’s internal operating
      dashboard, so do not use it as customer-facing product proof.


      Candidate April experiment A: renewal-risk/admin-friction follow-up prompt

      - Prompt appears only when a specific account-owner action, specific admin friction,
      account-thread evidence source, and Anna’s caveat can travel together.

      - Nadia needs the prompt translated into customer/account-team scripts and a
      behavior read, not another metrics view.

      - Leo checks data/platform seams before any broader exposure.


      Candidate April experiment B: post-first-live-sync expansion prompt

      - Prompt appears only after first live sync is live and teammate-invite or admin-role
      basics are visible.

      - Jake can support a small prompt-style implementation, but the work should
      not turn into a dashboard build.

      - Sarah can supply account-thread evidence for qualifying accounts.


      Customer-material boundary

      - Acme remains inside the live-only boundary: no written customer-specific materials,
      screenshots, Evergreen-derived examples, or packet excerpts.


      Owner questions

      - Anna: what caveat must stay attached to each signal?

      - Nadia: what script or account-team behavior should the prompt trigger?

      - Jake: what is the smallest prompt-style implementation that avoids a dashboard
      build?

      - Leo: what data/platform seam must be checked before a signal is shown more
      broadly?

      - Sarah: which account-thread evidence is clean enough to use?


      Measurement questions

      - What counts as behavior change?

      - Which accounts are safe to use?

      - How will account-team action be measured?

      - How will customer action be measured?


      Explicit unresolved decisions

      - Whether Compass April work is formally cut to these two prompt experiments.

      - Final owner split for April work.

      - Which accounts are in bounds.

      - What restrained board/customer narrative, if any, is safe after the quarter-close
      review.'
    folder: null
    created_at: '2025-03-25T15:22:00-07:00'
  - id: doc_1743193440000
    title: Compass April action-prompt scope
    body: "# Compass April action-prompt scope\n\nScope cut\n- Compass is no longer
      framed as a broad customer analytics surface.\n- April scope is limited to two
      action-oriented experiments:\n  - Renewal-risk/admin-friction follow-up prompt.\n
      \ - Post-first-live-sync expansion prompt.\n- The broad customer-facing dashboard
      framing is cut for now.\n\nEvidence reviewed\n- Evergreen Bank and Acme could
      read the Compass v0.1 surface but did not change account behavior because of
      it.\n\nOwner split\n- Anna Martinez owns signal definitions and caveats.\n-
      Nadia Singh owns customer/account-team scripts and the behavior read.\n- Jake
      owns product implementation.\n- Leo Park owns data/platform seams.\n- Sarah
      Kim supplies account-thread evidence.\n- Morgan Chen keeps board/customer narrative
      restrained until the prompts show actual behavior change.\n\nBoundary\n- April
      work starts from these two action-prompt experiments, not a broad dashboard
      surface."
    folder: null
    created_at: '2025-03-28T13:24:00-07:00'
  - id: doc_1743533220000
    title: Evergreen SAML rotation prep notes — Apr 1
    body: '# Evergreen SAML rotation prep notes — Apr 1


      Prep outcome

      - Current path is the shipped SAML login path for Evergreen''s annual Mercury
      Growth account.

      - No alternate auth path, custom admin policy, or procurement/security add-on
      is in scope for the rotation.


      Apr 3 verification

      - Evergreen updates the SAML certificate.

      - Leo checks existing-admin and workspace-admin login.

      - Leo watches auth logs for 401 or metadata errors for 30 minutes after the
      change.

      - Sarah confirms the customer-facing account thread once login is verified.


      Ownership

      - Sarah Kim owns the Evergreen customer thread.

      - Leo Park owns the first SAML/platform technical read.

      - Devon Hayes stays available only for commercial/procurement framing.


      Customer-safe boundary

      - Describe this as shipped SAML operational readiness for the annual account.

      - Do not imply advanced admin controls, a granular role editor, procurement/security
      add-ons, or roadmap commitments.'
    folder: Customer
    created_at: '2025-04-01T11:47:00-07:00'
  - id: doc_1744732380000
    title: Mercury admin visibility verification checklist — Apr 15
    body: 'Scope: basic invited-teammate/source-owner visibility inside the current
      Mercury activation path only.


      Status from Apr 15:

      - Setup guide and source-owner cue visible in three internal workspaces.

      - Invite-resend path still showed one stale cached role; Jake owns the cache
      invalidation patch before the next pass.

      - Leo wants one clean run where an invited teammate follows the setup cue to
      first source connected and first live sync with no state mismatch.


      Close criteria:

      - Invited teammate sees the correct setup guide.

      - Source-owner cue appears from server role + source state, not a client-side
      assumption.

      - First source connection succeeds.

      - First live sync completes without role/state mismatch.

      - Sarah keeps Evergreen wording held until this is green.


      Non-scope: custom admin policy, granular role editor, advanced admin controls,
      or broader Evergreen admin support.'
    folder: Mercury
    created_at: '2025-04-15T08:53:00-07:00'
  - id: doc_1744904460004
    title: Mercury admin visibility technical verification notes — Apr 17
    body: 'Technical pass:

      - Jake’s cache-invalidation patch cleared the stale role after invite resend.

      - Leo ran the invited-teammate path in the Evergreen-shaped internal workspace.

      - Invited teammate saw setup guide and source-owner cue.

      - The run reached first source connected and first live sync without state mismatch.


      Still pending:

      - Sarah’s customer-safe wording check for Evergreen support context.


      Scope boundary:

      - Basic admin/source-owner cues in current activation path only.

      - No custom admin policy, granular role editor, advanced admin controls, or
      broader procurement/security claim.'
    folder: Mercury
    created_at: '2025-04-17T08:41:00-07:00'
  - id: doc_1744992660006
    title: Mercury basic admin visibility closeout — Apr 18
    body: 'Outcome:

      - Jake and Leo verified invited-teammate/source-owner role visibility in the
      current Mercury activation path.

      - The verified path covers setup guide visibility, source-owner cues, first
      source connection, and first live sync without a role/state mismatch.

      - Sarah checked the customer-safe wording against Evergreen’s annual-account
      support context.


      Customer-safe boundary:

      - Scaffold can describe the basic teammate-invite/admin-role path in the current
      activation flow.

      - Do not claim custom admin policy, a granular role editor, advanced admin controls,
      or broader procurement/security scope.


      Operating outcome:

      - This is no longer a Mercury activation blocker.

      - Keep future account requests routed through normal Mercury roadmap/support
      handling.'
    folder: Mercury
    created_at: '2025-04-18T09:11:00-07:00'
  - id: doc_1745252280009
    title: Compass April prompt review prep — Apr 25
    body: 'Review question: did either April prompt change account-team or customer
      behavior, or did it only produce owner follow-up?


      Prompts in scope:

      - Renewal-risk/admin-friction follow-up prompt.

      - Post-first-live-sync expansion prompt.


      Evidence to bring:

      - Anna: definitions, evidence source, dates, and caveats attached to each prompt.

      - Sarah: account-thread evidence, with Evergreen annual-account context and
      Acme live-only review of Acme’s own signals.

      - Leo: source-recency and platform/data-seam checks.

      - Jake: prompt-level implementation status, not dashboard/platform rebuild scope.

      - Nadia: scripts and behavior read from account-team usage.


      Decision boundary:

      - No customer-facing proof claim unless behavior changed.

      - No board-dashboard framing.

      - No hiring implication before the May board-cycle evidence gate.'
    folder: Compass
    created_at: '2025-04-21T09:18:00-07:00'
  - id: doc_1745365620002
    title: Compass April evidence matrix addendum
    body: '# Compass April evidence matrix addendum


      ## Renewal-risk / admin-friction prompt

      - Action trigger: account-owner follow-up when renewal-risk context and documented
      admin friction both exist.

      - Evidence that travels with the prompt: account-thread source, evidence date,
      owner, and caveat.

      - Accepted sources for this review: Sarah’s Evergreen annual-account current-state
      notes and Acme live-only review notes for Acme’s own signals.

      - Caveats: single-account notes are not repeatability proof; stale source timing
      must be visible; this is not a score or dashboard surface.


      ## Post-first-live-sync expansion prompt

      - Action trigger: account-owner expansion-prep question only after first live
      sync is live and teammate-invite/admin-role basics are visible.

      - Evidence that travels with the prompt: activation event, account-thread source,
      evidence date, and caveat.

      - Caveats: sample or preview behavior is excluded; source timing must be fresh
      enough to defend; prompt does not imply a customer is ready to expand.


      ## Review boundary

      - Evidence is usable for operating review only if definitions, sources, dates,
      and caveats stay attached.

      - Do not treat this as customer-facing proof, GTM proof, board-dashboard proof,
      or a hiring trigger.'
    folder: Project Compass
    created_at: '2025-04-22T16:47:00-07:00'
  - id: doc_1745426040003
    title: Compass April account-thread evidence addendum
    body: '# Compass April account-thread evidence addendum


      ## Evergreen Bank

      - Use only annual-account current-state evidence.

      - Safe evidence for review: annual Mercury Growth account context, shipped SAML
      rotation path, visible invite/source/admin audit lookup support, workspace-admin
      support route, and verified basic invited-teammate/source-owner cues in the
      current activation path.

      - Caveat: clean account thread, but still one annual account; not repeatable
      customer-growth proof by itself.


      ## Acme

      - Use only live review of Acme’s own account-health, reliability, and renewal-risk
      signals.

      - Do not send Evergreen-derived examples, screenshots, written Mercury packets,
      or customer-specific briefing materials.

      - Exclude or caveat notes where owner/source/date is unclear.


      ## Behavior-change read

      - Account-thread hygiene and prep questions are improving.

      - The evidence does not yet show customers changing behavior because of Compass.'
    folder: Project Compass
    created_at: '2025-04-23T09:34:00-07:00'
  - id: doc_1745603880005
    title: Compass April prompt trial closeout — Apr 25
    body: '# Compass April prompt trial closeout — Apr 25


      ## Decision

      Compass remains two owner-group action-prompt experiments:

      - Renewal-risk / admin-friction follow-up prompt.

      - Post-first-live-sync expansion prompt.


      It is not a broad customer analytics surface, dashboard rebuild, GTM proof point,
      customer-facing product claim, or hiring trigger.


      ## Evidence read

      - Anna kept definitions, evidence sources, dates, and caveats attached to both
      signals.

      - Sarah supplied account-thread evidence within the boundaries: Evergreen as
      annual-account current-state context; Acme only through live review of Acme’s
      own signals.

      - Leo confirmed source-recency handling is acceptable for continued owner-group
      use, not broader exposure.

      - Jake confirmed prompt-level implementation only.

      - Nadia’s scripts improved account-team prep and internal follow-up questions.


      ## Behavior-change read

      - Renewal-risk / admin-friction prompt helped owners notice specific follow-up
      work and ask better questions.

      - Post-first-live-sync expansion prompt was legible to internal account owners.

      - Neither prompt produced customer behavior change or a repeatable customer-growth
      motion in April.


      ## Boundary for May board-cycle prep

      Use this as operating-review learning only. Do not present it as customer-facing
      proof, board-dashboard proof, GTM proof, or a staffing trigger.'
    folder: Project Compass
    created_at: '2025-04-25T10:58:00-07:00'
  - id: doc_1745940840000
    title: Evergreen annual account operating read — May prep grid
    body: 'Purpose

      - Prep the May Evergreen annual-account operating read as current-state evidence
      plus repeatability questions, not a customer-growth proof package.


      Evidence Sarah should bring

      - Apr 3 shipped SAML rotation closeout and any login verification notes.

      - Visible invite/source/admin audit lookup examples already safe in the annual-account
      thread.

      - Workspace-admin support route and current support wording.

      - Monthly-active-developer usage snapshot for the annual Growth account.


      Owner lanes

      - Sarah: customer-thread evidence and current-state notes.

      - Devon: commercial/procurement framing and standard Growth terms.

      - Nadia: customer-growth pattern capture only.

      - Anna: evidence quality, definitions, and caveats.


      Open questions

      - Which signals would repeat outside Evergreen?

      - What is Evergreen-specific enterprise context?

      - What evidence is still missing before the May board-cycle staffing gate?


      Boundaries

      - No custom admin-policy claim.

      - No granular role-editor claim.

      - No broader procurement/security packet promise.

      - No hiring implication from Evergreen alone.'
    folder: Customer Growth
    created_at: '2025-04-29T08:34:00-07:00'
  - id: doc_1746030480002
    title: Evergreen May read — Sarah account-thread evidence addendum
    body: 'Use as current-state account evidence only. Do not circulate as a new customer-facing
      packet.


      Clean evidence Sarah can bring

      - Apr 3 SAML certificate rotation completed on the shipped operational path
      for the annual Mercury Growth account.

      - Visible invite/source/admin audit lookup examples are already in the account
      thread.

      - Workspace-admin support path is documented in the current Evergreen thread.

      - Monthly-active-developer usage snapshot is available for the annual Growth
      account.


      Boundary

      - This is clean Evergreen account-thread evidence.

      - It is not a standalone procurement/security packet.

      - It does not include advanced admin controls, custom admin policy, or a granular
      role editor.

      - It does not prove repeatability beyond Evergreen by itself.


      Questions for the read

      - Which evidence is current-state support versus enterprise-readiness learning?

      - What would need to appear in other account threads before this becomes repeatable
      account-source quality?

      - Which follow-up belongs to Sarah, Devon, Nadia, Anna, Jake, or Leo rather
      than becoming a generic customer-growth bucket?'
    folder: Customer Growth
    created_at: '2025-04-30T09:28:00-07:00'
  - id: doc_1746202680006
    title: Evergreen May operating read — commercial boundaries
    body: 'Commercial current state from Devon

      - Evergreen annual Growth terms are clean: $7,500/month including up to 200
      monthly active developers, with overage as already agreed.

      - Current-state support/procurement evidence: shipped SAML, audit lookup, workspace-admin
      support, and monthly-active-developer usage.

      - No separate advanced-admin add-on is ready to quote this week.


      Boundary for Monday

      - Do not imply advanced admin controls, custom admin policy, or a granular role
      editor are included in the annual baseline.

      - If advanced admin comes up, keep the answer to separately scoped later work
      after the work exists.

      - Evergreen is useful account evidence, not a hiring proof point by itself.


      Use in read

      - Devon owns commercial/procurement framing.

      - Sarah owns the customer-thread current-state evidence.

      - Nadia/Anna should test repeatability and evidence quality rather than turn
      this into a quote or roadmap discussion.'
    folder: Customer Growth
    created_at: '2025-05-02T09:18:00-07:00'
  - id: doc_1746467760008
    title: Evergreen annual account operating read — May 5 working notes
    body: 'Status: first pass only. Keep the operating-read thread open through the
      rest of the May evidence cycle.


      Attendees

      - Morgan, Devon, Sarah, Nadia, Anna.


      First-pass read

      - Evergreen’s current Mercury usage looks healthy inside the annual Growth account.

      - Sarah’s account-thread evidence is clean: Apr 3 shipped SAML rotation, visible
      invite/source/admin audit lookup, workspace-admin support path, and monthly-active-developer
      usage.

      - Devon confirmed there is no separate advanced-admin add-on ready to quote.
      Commercial/procurement language should stay current-state and separately scoped
      later only after work exists.

      - Anna’s read: Evergreen evidence quality is strong because the account thread
      is unusually clean; comparison accounts are needed before calling this repeatable
      account-source quality.

      - Nadia’s read: Evergreen is useful enterprise learning, but one account is
      not customer-growth motion.


      Morgan boundary

      - Treat this as first-pass operating evidence.

      - Do not turn it into customer-facing proof, a board-dashboard proof point,
      a staffing trigger, or a new advanced-admin quote.

      - Keep repeatability, staffing, and board-story decisions open until the May
      board-cycle evidence is actually reviewed.


      Follow-ups

      - Anna: identify what evidence would need to appear outside Evergreen.

      - Nadia: separate enterprise learning from repeatable customer-growth motion.

      - Sarah: keep the account-thread evidence current-state.

      - Devon: keep commercial/procurement framing to shipped/current-state facts.'
    folder: Customer Growth
    created_at: '2025-05-05T10:56:00-07:00'
  - id: doc_1746575520000
    title: May board-cycle evidence grid — working skeleton
    body: '# May board-cycle evidence grid — working skeleton


      Purpose: one place for the May review evidence, not a staffing request.


      Columns to fill by Monday:

      - Compass prompt behavior change: account-team follow-ups, customer behavior,
      caveats.

      - Account-source quality beyond Evergreen: reliable sources, thin notes, owner
      route.

      - Enterprise-readiness intake: current owner route, what is product, what is
      procurement, what is customer-growth pattern capture.


      Known boundaries:

      - Evergreen is current-state enterprise evidence inside the annual Growth account.

      - Compass April/first-May remains owner learning until it changes behavior.

      - Do not add RevOps, CS, SDR, field-sales, customer-growth support, or second
      Mercury engineering req language unless the evidence gate actually changes.'
    folder: null
    created_at: '2025-05-06T16:52:00-07:00'
  - id: doc_1746719880003
    title: Evergreen May operating read — repeatability addendum
    body: '# Evergreen May operating read — repeatability addendum


      ## What is strong

      - Evergreen''s account-thread evidence is clean and traceable: Apr 3 shipped
      SAML rotation, visible invite/source/admin audit lookup, workspace-admin support,
      and monthly-active-developer usage.

      - Sarah''s thread has unusually good timestamps, owner route, and current-state
      boundaries.


      ## What does not repeat yet

      - Account-source quality outside Evergreen is uneven. Acme''s live-only Compass
      review is useful but thinner, and source dates need caveats. Other account notes
      mix owner summaries, partial customer asks, and inconsistent evidence trails.

      - Nadia can use Evergreen to improve enterprise-learning scripts, but the read
      does not show a repeatable customer-growth motion.


      ## Boundary for May board prep

      - Use Evergreen as current-state annual-account enterprise evidence.

      - Do not call it customer-growth proof, a staffing trigger, a board-dashboard
      proof point, or a Series C narrative.'
    folder: null
    created_at: '2025-05-08T08:58:00-07:00'
  - id: doc_1746808260006
    title: Evergreen May operating read — final closeout
    body: '# Evergreen May operating read — final closeout


      ## Closed outcome

      Evergreen is a strong annual-customer proof point and enterprise-readiness evidence
      source. It does not by itself prove repeatable customer growth or justify new
      customer-growth headcount.


      ## Evidence that held

      - Current Mercury usage is healthy inside Evergreen''s annual Growth account.

      - Sarah''s account-thread evidence cleanly covers the Apr 3 shipped SAML rotation,
      visible invite/source/admin audit lookup, workspace-admin support path, and
      monthly-active-developer usage.

      - Devon confirmed Scaffold has no separate advanced-admin add-on ready to quote.


      ## Caveats that stay attached

      - Anna''s comparison shows account-source quality is strongest in Evergreen
      and uneven elsewhere.

      - Nadia can use Evergreen as a high-quality enterprise-learning source, but
      it is not a repeatable customer-growth motion.

      - Do not turn this into a staffing trigger, board-dashboard claim, or Series
      C story.'
    folder: null
    created_at: '2025-05-09T09:31:00-07:00'
  - id: doc_1747064220010
    title: May board-cycle evidence grid — Monday update
    body: '# May board-cycle evidence grid — Monday update


      ## Compass prompt behavior

      - Current evidence: a few account-team follow-ups.

      - Missing evidence: customers changing behavior because of Compass.

      - Boundary: still experiment/operating input, not product or GTM proof.


      ## Account-source quality beyond Evergreen

      - Strongest source: Sarah''s Evergreen account thread.

      - Outside Evergreen: uneven source quality, caveats and owner notes vary.

      - Boundary: Evergreen is a proof point, not repeatable account-source quality
      by itself.


      ## Enterprise-readiness intake routing

      - Sarah: customer-thread continuity.

      - Devon: commercial/procurement framing.

      - Nadia: customer-growth pattern capture.

      - Jake/Leo: current product facts and platform/seam input as needed.


      ## Decision status

      Staffing remains pending the May board-cycle review. Do not add RevOps, CS,
      SDR, field-sales, customer-growth support, or second Mercury engineering req
      language unless the review changes the evidence gate.'
    folder: null
    created_at: '2025-05-12T08:37:00-07:00'
  - id: doc_1747164720000
    title: May board-cycle evidence review closeout — May 13, 2025
    body: 'Decision

      - Keep RevOps, CS, SDR, field-sales, customer-growth support, and the second
      Mercury engineering req closed through the rest of Q2.

      - Customer-growth staffing remains Nadia Singh’s weekly cadence plus Sarah Kim’s
      account-note hygiene.


      Evidence read

      - Compass prompts triggered a few account-team follow-ups, but customers are
      not changing behavior because of Compass.

      - Account-source quality is strongest in Sarah Kim’s clean Evergreen Bank thread
      and uneven outside Evergreen.

      - Enterprise-readiness intake stays owner-routed: Sarah for customer-thread
      continuity; Devon for commercial/procurement framing; Nadia for pattern capture
      and scripts; Jake for Mercury product sequencing; Leo Park for data/platform
      seams.


      Board framing

      - Evergreen Bank is a strong annual-customer proof point and enterprise-readiness
      evidence source, not repeatable customer-growth proof, a staffing trigger, or
      a Series C story.

      - Compass remains an experiment and operating input, not product proof or GTM
      proof.


      Next

      - June closeout should be narrow: behavior-change evidence, account-source quality,
      and owner-routed intake only. Do not turn it into a hiring plan, customer-facing
      launch, or fundraising narrative.'
    folder: Board
    created_at: '2025-05-13T12:32:00-07:00'
  - id: doc_1747671720007
    title: Compass June closeout — narrow evidence skeleton
    body: 'Purpose

      - Close the May-to-June Compass observation window narrowly. This is evidence
      review, not a launch plan, dashboard pitch, GTM proof point, hiring trigger,
      or Series C narrative.


      Owner inputs due June 2 EOD


      1. Behavior changed?

      - What changed because of the prompt, if anything?

      - Distinguish customer behavior, account-team follow-up, and internal owner
      awareness.

      - Name the evidence source and date.


      2. Prompt evidence by signal

      - Renewal-risk/admin-friction prompt: account, owner action, evidence, caveat,
      and whether customer behavior changed.

      - Post-first-live-sync expansion prompt: account, owner action, evidence, caveat,
      and whether customer behavior changed.


      3. Account-source quality

      - What is reliable beyond Sarah Kim’s Evergreen Bank thread?

      - Where are notes too thin, stale, or not owner-routed?


      4. Enterprise-readiness intake routing

      - Sarah: customer-thread continuity.

      - Devon: commercial/procurement framing.

      - Nadia: pattern capture and scripts.

      - Jake: product sequencing.

      - Leo Park: data/platform seams.

      - Call out any place the routing broke down.


      5. Cut / keep recommendation

      - What should remain as narrow internal prompt work?

      - What should be cut because it is not producing behavior-change evidence?


      Explicit exclusions

      - No customer-facing Compass launch.

      - No board dashboard.

      - No dashboard rebuild.

      - No GTM proof claim.

      - No hiring trigger.

      - No Series C narrative.'
    folder: Product
    created_at: '2025-05-19T09:22:00-07:00'
  - id: doc_1747847880004
    title: Acme API v2 export timeout — May 2025 technical read
    body: '## Current read

      - Acme''s full account-health + renewal-risk API v2 export is timing out on
      the large export path.

      - Leo''s first read does not point to GraphQL auth/JWT, webhook verification,
      or connector verifier behavior.

      - Narrower replay scoped to account-health and recent renewal-risk rows completed.

      - No evidence of corrupt exported data.


      ## Customer path

      - Sarah keeps the customer thread through support rotation.

      - Safe customer line: the team isolated the issue to the large export path,
      and Acme can continue the review using the narrower replay while Scaffold scopes
      the bounded API v2 export follow-up.

      - Do not promise a full-export fix date.


      ## Boundary

      - Atlas/API v2 support + product priority only.

      - Not Compass evidence.

      - Not Mercury escalation.

      - No founder-direct Atlas routing.'
    folder: Support
    created_at: '2025-05-21T10:18:00-07:00'
  - id: doc_1748470680003
    title: Compass June closeout — Anna evidence addendum
    body: '# Compass June closeout — Anna evidence addendum (May 28)


      Use as input to the June 4 evidence read, not as product/GTM proof.


      - Renewal-risk/admin-friction prompt: useful internally because it made owners
      notice follow-up work earlier; evidence sources are Evergreen annual-account
      thread and Acme live-only review notes.

      - Evergreen Bank: treated the signal as an account appendix/current-state note,
      not as a customer action prompt.

      - Acme: still asked for live human follow-up on the review path; no evidence
      that the prompt changed customer behavior.

      - Post-first-live-sync expansion prompt: legible to internal owners; no repeatable
      customer action observed.

      - Caveat: account-source quality is strong for Evergreen, thinner/uneven elsewhere;
      keep dates and caveats attached.

      - Closeout implication: operating input only unless June 4 finds behavior change
      beyond owner follow-up.'
    folder: null
    created_at: '2025-05-28T15:18:00-07:00'
  - id: doc_1748621220004
    title: Compass June closeout — Nadia scripts and behavior read
    body: '# Compass June closeout — Nadia scripts and behavior read (May 30)


      Use as internal behavior-read input only.


      - Scripts improved account-team conversation prep for Evergreen and Acme by
      making the owner ask better follow-up questions.

      - Renewal-risk/admin-friction prompt is useful only when it points to a specific
      owner action and carries evidence caveats.

      - Customers are not acting because Compass surfaced the signal; the motion still
      needs live human follow-up.

      - Post-first-live-sync expansion prompt is understandable internally after first
      live sync is live, but it has not created a repeatable expansion motion.

      - This is better prep, not a sales wedge, GTM proof, or hiring trigger.

      - Keep scripts only if they remain tied to owner action, source quality, and
      caveats.'
    folder: null
    created_at: '2025-05-30T09:07:00-07:00'
  - id: doc_1748907780007
    title: Compass June closeout packet — June 2 owner inputs
    body: '# Compass June closeout packet — owner inputs assembled June 2


      Purpose: prepare for the June 4 narrow evidence read; decision still pending.


      ## What the inputs show

      - Renewal-risk/admin-friction prompt: helps Scaffold owners notice follow-up
      work, especially from Sarah''s Evergreen account thread and Acme live-only review
      context.

      - Evergreen Bank: treats the signal as an account appendix/current-state note,
      not as a customer action trigger.

      - Acme: still asks for live human follow-up; the May API v2 export-timeout issue
      remains separate bounded Atlas context, not Compass evidence.

      - Post-first-live-sync expansion prompt: legible to internal owners after first
      live sync, but no repeatable customer action observed.

      - Nadia''s scripts: improve conversation prep and account-team questions; not
      a sales wedge.

      - Anna''s evidence matrix: definitions, dates, sources, and caveats are attached;
      usable for operating review only.

      - Leo''s seam read: source-recency/data seams are acceptable for owner-group
      prompt use, not broader exposure.

      - Jake''s implementation read: prompt-level implementation stayed narrow; no
      dashboard/platform build.


      ## Questions for June 4

      - Do we cut the customer-facing Compass plan for H1 or leave any external claim
      alive?

      - What narrow internal prompt work is worth keeping for evidence gathering?

      - Which owner routes broke, and which were useful?

      - What should be excluded from board/customer narrative and staffing discussions?


      ## Boundaries

      No customer-facing launch, board dashboard, GTM proof, hiring trigger, or Series
      C narrative from this packet.'
    folder: null
    created_at: '2025-06-02T16:43:00-07:00'
  - id: doc_1749060180002
    title: Compass June closeout — decision record
    body: 'Decision: cut the H1 customer-facing Compass plan. Keep only narrow internal
      action-prompt work on renewal-risk/admin-friction and post-first-live-sync expansion.
      Evidence: the renewal-risk/admin-friction prompt helped internal owners notice
      follow-up work, but Evergreen treated the signal as account appendix/current-state
      context and Acme still asked for live human follow-up. The post-first-live-sync
      expansion prompt was legible internally but did not produce repeatable customer
      action. Nadia''s scripts improved account-team conversation prep but did not
      create a sales wedge. Owner split: Anna owns definitions and caveats; Nadia
      owns scripts and behavior read; Jake owns prompt-level implementation; Leo owns
      data/platform seams; Sarah supplies account-thread evidence; Morgan owns restrained
      board/customer narrative. Boundaries: no customer-facing launch, no GTM proof,
      no board dashboard, no H1 hiring trigger, no Series C story, and no Mercury
      sequencing change from this closeout.'
    folder: Product
    created_at: '2025-06-04T11:03:00-07:00'
  - id: doc_1749158280008
    title: Compass retained internal prompt track — owner checklist
    body: 'Purpose: keep only narrow internal action-prompt learning after the June
      closeout. Prompt areas: renewal-risk/admin-friction and post-first-live-sync
      expansion. Evidence that can count: dated owner follow-up caused by the prompt;
      customer or account-team behavior that changed because of the prompt; account-source
      quality strong enough to attach dates, source, and caveats. Evidence that does
      not count by itself: cleaner implementation, better scripts, better prep questions,
      internal owner noticing, account appendix context, or live human follow-up that
      would have happened anyway. Owners: Anna definitions/caveats; Nadia scripts
      and behavior read; Jake prompt-level implementation; Leo data/platform seams;
      Sarah account-thread evidence; Morgan board/customer narrative. Non-goals: customer-facing
      launch, GTM proof, board dashboard, H1 hiring trigger, Series C story, Mercury
      sequencing change, dashboard rebuild, platform build.'
    folder: Product
    created_at: '2025-06-05T14:18:00-07:00'
  - id: doc_1749505020012
    title: Nadia role-fit conversation — private prep
    body: 'Purpose: prepare Morgan and Devon for the June 10 conversation with Nadia.
      Frame: role fit for Scaffold''s next phase, not blame. Evidence to name carefully:
      Nadia improved enterprise conversation prep and some account-source discipline;
      Compass scripts helped account-team prep; the GTM motion still has not become
      repeatable; Compass did not become behavior-change proof and has been cut to
      internal prompt learning. What to avoid: villain framing, surprise HR language,
      exit-date assumptions, replacement-search assumptions, roadmap promises, or
      implying that Sarah/Anna handoffs are already final. If the conversation moves
      toward transition, conditional handoff areas to discuss: scripts and behavior-read
      context to Sarah and Anna; account-thread hygiene stays with Sarah; evidence
      quality stays with Anna; commercial context stays with Devon where needed; Morgan
      owns board/customer narrative. These are prep points, not agreed outcomes.'
    folder: Private
    created_at: '2025-06-09T14:37:00-07:00'
  - id: doc_1749580860000
    title: Nadia role-fit conversation — June 10 debrief
    body: 'Private debrief from June 10 conversation


      What was said

      - Framed as role fit for Scaffold''s next phase, not effort or blame.

      - Evidence reviewed: Compass did not become behavior-change proof; Evergreen
      is a strong annual account but not repeatable customer-growth proof by itself;
      account-source quality remains uneven outside Evergreen.

      - Acknowledged Nadia''s useful work on enterprise conversation prep, scripts,
      and some account-source discipline.


      Where it landed

      - Nadia understood why Morgan and Devon were raising this now.

      - Nadia asked for overnight before discussing concrete transition terms.

      - No exit date, severance terms, communications plan, handoff plan, or replacement-search
      decision was made.


      Next step

      - Short follow-up with Morgan, Devon, and Nadia on June 12 to discuss next steps.'
    folder: People/Private
    created_at: '2025-06-10T11:41:00-07:00'
  - id: doc_1749656880003
    title: Nadia conditional handoff candidates — June 11
    body: 'Private conditional note. Not final until Morgan, Devon, and Nadia agree
      next steps.


      Useful work to preserve

      - Customer-growth scripts: setup-call opener, admin handoff language, procurement-pause
      line.

      - Enterprise prep: better conversation structure around Evergreen-style questions.

      - Behavior read: Compass prompted internal owners to ask better questions, but
      did not produce customer behavior-change proof.


      Possible handoff lanes if transition is agreed

      - Sarah Kim: customer-growth scripts and account-thread hygiene context. Evergreen
      remains Sarah''s clean customer thread.

      - Anna Martinez: behavior-read context, evidence caveats, and what counts or
      does not count as Compass proof.


      Boundaries

      - Acme remains live-only for Acme''s own signals.

      - Do not write this as "Nadia failed at GTM."

      - Do not treat any handoff as final before the June 12 follow-up.'
    folder: People/Private
    created_at: '2025-06-11T08:48:00-07:00'
  - id: doc_1749750420006
    title: Nadia transition decision record — June 12
    body: 'Private decision record


      Decision

      - Morgan, Devon, and Nadia agreed the Head of Customer Growth role is not matching
      Scaffold''s next phase.

      - Planned final day: Friday, June 20, 2025. Nadia has not left yet.


      Acknowledged contribution

      - Nadia improved enterprise conversation prep and some account-source discipline.

      - Her scripts and behavior-read work should be preserved in handoff.


      Wind-down and handoff

      - Nadia winds down active account work during the week of June 16.

      - Sarah Kim receives customer-growth scripts and account-prep language; Sarah
      remains customer-thread continuity owner.

      - Anna Martinez receives behavior-read context, Compass evidence caveats, and
      what-not-to-claim notes.

      - Devon Hayes remains commercial/procurement owner.


      Boundaries

      - No company-wide announcement this week.

      - No customer-facing owner-story change this week.

      - No immediate replacement search from this transition.

      - Do not describe this as Nadia being the villain or Compass becoming proof
      that failed because of one person.'
    folder: People/Private
    created_at: '2025-06-12T10:47:00-07:00'
  - id: doc_1750092240013
    title: Nadia / Sarah handoff record — scripts + account-thread hygiene
    body: 'Private transition handoff record — June 16


      Materials handed to Sarah

      - Setup-call opener.

      - Admin-handoff objection line.

      - Procurement-pause line.

      - Phrases that helped account teams ask cleaner questions.


      Sarah''s routing

      - Account-thread hygiene: use only where tied to reliable account notes.

      - Internal prep only: scripts that sharpen conversations but do not prove customer
      behavior change.


      Customer boundaries

      - Evergreen: Sarah remains live customer-thread owner; use current-state annual-account
      evidence only; no new owner story, advanced-admin claim, or bespoke roadmap
      promise.

      - Acme: live-only review of Acme''s own signals; no Evergreen-derived examples,
      packets, screenshots, or customer-specific materials.


      Remaining follow-up

      - Sarah to mark which account notes are too thin to reuse.

      - This handoff does not mean Nadia has left; planned final day remains June
      20.'
    folder: People/Private
    created_at: '2025-06-16T09:44:00-07:00'
  - id: doc_1750106340014
    title: Nadia / Anna handoff record — Compass behavior read + caveats
    body: 'Private transition handoff record — June 16


      Behavior-read context

      - Renewal-risk/admin-friction and post-first-live-sync prompts helped internal
      owners notice follow-up work.

      - Scripts improved account-team prep.

      - The prompts did not show customer behavior change.


      Evidence threshold going forward

      - Count evidence only when it shows dated owner follow-up or customer/account-team
      behavior caused by the prompt.

      - Cleaner scripts, cleaner implementation, or better prep alone are not enough
      for broader exposure, customer-facing claims, GTM proof, or staffing changes.


      Account caveats

      - Evergreen evidence is clean but account-specific.

      - Acme still prefers live human follow-up and is not Compass behavior-change
      proof.


      Owner routing

      - Anna owns definitions, caveats, and evidence-quality threshold.

      - Sarah supplies account-thread evidence.

      - Jake owns implementation.

      - Leo owns data/platform seams.


      Boundary

      - Compass remains retained internal prompt work, not product proof, GTM proof,
      a customer-facing launch, or a hiring trigger.'
    folder: People/Private
    created_at: '2025-06-16T13:39:00-07:00'
  - id: doc_1750175520000
    title: Nadia / Sarah handoff follow-up — thin-note pass
    body: 'Private transition addendum — June 17, 2025


      Sarah''s thin-note pass:

      - Reusable for Sarah''s account-thread hygiene only when tied to current-state
      evidence: setup-call opener, admin-handoff objection line, procurement-pause
      language.

      - Evergreen Bank remains Sarah''s clean current-state annual-account thread;
      treat as account-specific evidence, not repeatable customer-growth proof.

      - Acme remains live-only review of Acme''s own signals; do not reuse Evergreen-derived
      examples, written packets, screenshots, or customer-specific materials.

      - Too thin to reuse as evidence: undated admin-role confusion snippets without
      source owner, procurement-pause notes without customer quote/source, and a post-sync
      expansion note that came only from internal owner interpretation.

      - Keep the scripts as internal prep; do not treat them as Compass behavior-change
      proof or customer-facing material.


      Remaining: Sarah can keep using the marked scripts for account hygiene, but
      anything thin stays internal prep only unless later evidence has dates, source,
      and owner action.'
    folder: People/Transitions
    created_at: '2025-06-17T08:52:00-07:00'
  - id: doc_1750263600003
    title: Nadia Singh transition — final handoff packet
    body: 'Private closeout packet — June 18, 2025


      Preserved from Nadia''s final handoff:


      Sarah / account-thread hygiene:

      - Setup-call opener, admin-handoff objection line, procurement-pause language,
      and cleaner account-team prep questions.

      - Use only inside account-thread hygiene unless tied to current-state evidence.

      - Evergreen Bank remains Sarah''s current-state annual-account thread and Devon''s
      commercial/procurement lane.

      - Acme remains live-only for Acme''s own signals; no Evergreen-derived examples,
      written packets, screenshots, or customer-specific materials.


      Anna / evidence quality:

      - Renewal-risk/admin-friction and post-first-live-sync prompts helped internal
      owners notice follow-up work and improved account-team prep.

      - They did not show customer behavior change.

      - Future evidence must show dated owner follow-up or customer/account-team behavior
      caused by the prompt, not just cleaner scripts or cleaner implementation.


      Owner lanes after Nadia''s final week:

      - Sarah: account-thread hygiene, live-account continuity, customer-thread notes.

      - Anna: definitions, caveats, evidence-quality threshold, behavior-read context.

      - Jake: implementation.

      - Leo: data/platform seams.

      - Devon: commercial/procurement context where needed.

      - Morgan: board/customer narrative.


      What not to claim:

      - Compass is not a customer-facing launch, GTM proof, board dashboard, behavior-change
      proof, hiring trigger, or roadmap promise.

      - Nadia''s transition does not create a new Evergreen owner story or authorize
      bespoke roadmap commitments.


      Status: Nadia is still at Scaffold through the planned June 20 final day.'
    folder: People/Transitions
    created_at: '2025-06-18T09:20:00-07:00'
  - id: doc_1750288200005
    title: Nadia transition team note draft — hold until June 20
    body: 'Draft — do not send before June 20 final-day confirmation


      Team — today is Nadia Singh''s last day at Scaffold.


      Nadia joined us for a hard phase of the customer-growth work and helped sharpen
      enterprise conversation prep, account-source discipline, and the scripts we
      use to ask cleaner account questions. We''re grateful for that work.


      The Head of Customer Growth role is not the right match for Scaffold''s next
      phase, so we''re closing the role transition today. We''re not opening an immediate
      replacement search.


      Going forward, customer-growth pattern work stays in the existing owner lanes:
      Sarah for account-thread hygiene and customer-thread continuity, Anna for evidence
      quality and Compass caveats, Devon for commercial/procurement context where
      needed, and me for board/customer narrative. Product requests and roadmap asks
      still go through the standard product-owner path.


      Please keep this respectful and practical, and route any operational questions
      through your manager or HR.


      Morgan


      Boundaries for final review:

      - No restructuring language.

      - No performance/blame framing.

      - No Compass GTM, behavior-change, launch, or hiring-proof language.

      - No replacement-search loop.

      - No customer-owner story change.'
    folder: People/Transitions
    created_at: '2025-06-18T16:10:00-07:00'
  - id: doc_1750443840007
    title: Nadia Singh transition closeout — June 20, 2025
    body: 'Private transition closeout — June 20, 2025


      Outcome:

      - Nadia Singh''s final day at Scaffold is June 20, 2025.

      - HR is closing the role transition without opening an immediate Head of Customer
      Growth replacement search.

      - Keep RevOps, CS, SDR, field-sales, and the second Mercury engineering req
      closed through the rest of Q2.


      Narrative:

      - Role fit / next phase, not blame.

      - Acknowledge that Nadia improved enterprise conversation prep, account-source
      discipline, and customer-growth scripts in places.

      - Do not use the transition as Compass proof, GTM proof, behavior-change proof,
      or a hiring trigger.


      Post-exit owner routes:

      - Sarah Kim: account-thread hygiene, account-note hygiene, live-account continuity,
      customer-thread notes, and Nadia''s handed-off customer-growth scripts.

      - Anna Martinez: evidence quality, definitions, caveats, evidence thresholds,
      and Nadia''s handed-off behavior-read context.

      - Devon Hayes: commercial/procurement context and framing where needed.

      - Morgan Chen: board/customer narrative.

      - Jake: Compass prompt implementation and Mercury product-owner routing where
      relevant.

      - Leo Park: data/platform seams.


      Evergreen Bank:

      - Sarah remains live customer-thread owner and continuity owner.

      - Devon remains commercial/procurement owner.

      - Nadia''s prior involvement does not change product facts, create a new owner
      story, or authorize roadmap promises.

      - Product requests still go through the standard Mercury roadmap.


      Compass:

      - Remains narrow internal action-prompt work on renewal-risk/admin-friction
      and post-first-live-sync expansion.

      - Not a customer-facing product launch, GTM proof point, behavior-change proof,
      H1 hiring trigger, or immediate hiring trigger.


      Customer asks implying custom scope, feature-date promises, or priority-account
      exceptions still route through Morgan/Devon and the relevant product owner before
      customer follow-up.'
    folder: People/Transitions
    created_at: '2025-06-20T11:24:00-07:00'
  - id: doc_1750778040000
    title: Q2 board evidence grid — June 24 working pass
    body: 'Purpose: keep Q2 board review on operating evidence, not a Series C or
      hiring story.


      Evidence order:

      1. Evergreen Bank: annual Growth account is real; use current-state enterprise
      evidence, not repeatable customer-growth proof.

      2. Mercury/Atlas: steadier owner split; Jake owns Mercury sequencing; Leo owns
      platform seams and Atlas first technical reads; support remains the customer-facing
      Atlas entry point.

      3. Compass: cut to internal action prompts; no customer workflow, GTM proof,
      board dashboard, behavior-change proof, or hiring trigger.

      4. Staffing/customer-growth: Nadia exit does not reopen RevOps, CS, SDR, field-sales,
      customer-growth support, or the second Mercury engineering req.


      Live questions to hold:

      - What renewal evidence do we need in Q3?

      - What would make Evergreen repeatable beyond Sarah''s clean account thread?

      - What is the next operating check on Compass prompts without calling it product?


      Explicit exclusions: no Series C narrative, no broad investor-coffee loop, no
      bespoke roadmap promise, no new hiring lane, and no use of Compass as customer-facing
      proof.'
    folder: Board
    created_at: '2025-06-24T08:14:00-07:00'
  - id: doc_1750879560003
    title: Q2 board-cycle midweek notes — June 25
    body: 'Private midweek notes.


      What held:

      - Evergreen Bank is a real annual-account win and current-state enterprise evidence.

      - Mercury/Atlas read steadier under the support/Jake/Leo owner split.

      - Compass is acceptable only as narrow internal prompt learning with behavior-evidence
      tests attached.


      Open Q3 evidence test:

      - Define what renewal/expansion evidence would make Evergreen repeatable beyond
      Sarah''s clean thread.

      - Keep Compass evidence tied to dated owner follow-up or behavior change, not
      cleaner prompts alone.


      Boundary held:

      - No Series C narrative or broad investor-coffee loop from this board cycle.

      - No hiring trigger from Evergreen, Compass, or Nadia''s exit.


      Devon load note:

      - Devon supplied commercial/procurement context but looked depleted; do not
      default him into overnight cleanup.'
    folder: Board
    created_at: '2025-06-25T12:26:00-07:00'
  - id: doc_1751053320007
    title: Q2 2025 board-cycle closeout — quiet Q3 rebuild
    body: 'Decision: Scaffold is choosing a quieter Q3 rebuild over early Series C
      chatter.


      Operating story going forward:

      - Evergreen Bank is a real annual-account win and current-state enterprise evidence.

      - Retention and renewal evidence must hold beyond one clean account before becoming
      a broader story.

      - Compass''s customer-facing plan is cut down; retained work stays internal
      prompt learning with evidence tests.

      - Mercury and Atlas are steadier under the current owner split and support routing.


      Owner lanes:

      - Jake: Mercury sequencing.

      - Leo Park: platform seams and Atlas first technical reads.

      - Priya: activation/onboarding quality.

      - Anna Martinez: retention and Compass evidence quality.

      - Sarah Kim: customer-thread/account continuity.

      - Devon Hayes: commercial/procurement context where actually needed.

      - Morgan Chen: board/customer narrative.


      Explicit no''s:

      - No Series C narrative or broad investor-coffee loop from this board cycle.

      - No hiring trigger from Evergreen, Compass, or Nadia''s exit.

      - No bespoke roadmap promise.


      Devon load note: Devon backed the operating call but is visibly depleted; avoid
      making him the default cleanup engine.'
    folder: Board
    created_at: '2025-06-27T12:42:00-07:00'
  - id: doc_1751217720011
    title: Devon July pause — draft operating owner split
    body: 'Private draft before owner notification.


      Agreement in principle:

      - Devon is away from day-to-day Scaffold work July 1 through July 31.

      - Only true emergencies route to Devon.

      - Devon should not monitor normal board/customer cleanup, Mercury threads, Atlas
      routing, or Compass evidence by default.


      Draft owner lanes:

      - Jake: Mercury sequencing.

      - Leo Park: platform seams and Atlas first technical reads.

      - Priya: activation/onboarding quality.

      - Anna Martinez: retention and Compass evidence quality.

      - Sarah Kim: Evergreen customer-thread continuity.

      - Morgan Chen: board/customer narrative without Devon as default second brain.


      Monday actions:

      - Notify each owner directly.

      - Put the July pause on calendar.

      - Keep external/customer wording unchanged unless a true owner-route question
      comes up.'
    folder: Private
    created_at: '2025-06-29T10:22:00-07:00'
  - id: doc_1751296980013
    title: July 2025 operating owner split during Devon pause
    body: 'Final coverage record.


      Devon Hayes is away from day-to-day Scaffold work from July 1 through July 31,
      2025. Only true emergencies route to him.


      Owner split during the pause:

      - Jake: Mercury sequencing.

      - Leo Park: platform seams and Atlas first technical reads.

      - Priya: activation/onboarding quality.

      - Anna Martinez: retention and Compass evidence quality.

      - Sarah Kim: Evergreen customer-thread continuity.

      - Morgan Chen: board and customer narrative without Devon as the default second
      brain.


      Boundaries:

      - This is operating coverage, not a reorg.

      - No new hiring trigger.

      - No customer-owner story change.

      - No Series C or investor narrative change.

      - Escalate to Devon only for true emergencies after the named owner path is
      exhausted or the issue is genuinely founder-level urgent.'
    folder: Private
    created_at: '2025-06-30T08:23:00-07:00'
  - id: doc_1751398440002
    title: Compass July prompt tracking — owner follow-up only
    body: '# Compass July prompt tracking — owner follow-up only


      Count only prompt hits that create dated owner follow-up. A prompt sighting
      without owner action is a sighting, not evidence.


      For each retained prompt, record:

      - prompt type: renewal-risk/admin-friction or post-first-live-sync expansion

      - account context and owner

      - evidence source and date

      - caveat or source-quality concern

      - owner follow-up taken, rejected, or still pending

      - outcome if known


      Do not use this as customer-facing Compass proof, GTM proof, a board-dashboard
      input, a hiring trigger, or a Series C narrative.


      Owners: Anna keeps definitions and caveats; Sarah supplies account-thread evidence;
      Jake keeps implementation prompt-level; Leo checks data/platform seams before
      anything broader.'
    folder: Compass
    created_at: '2025-07-01T12:34:00-07:00'
  - id: doc_1751476680006
    title: Evergreen July 2 advanced-admin ask — current-state boundary
    body: '# Evergreen July 2 advanced-admin ask — current-state boundary


      Input: Evergreen asked whether granular custom admin policy for an additional
      admin group can be folded into its annual Growth baseline.


      Answer: no advanced-admin or custom-policy commitment. Current-state support
      remains shipped SAML login, visible invite/source/admin audit lookup, workspace-admin
      support, and basic admin-role setup.


      Owner routing during Devon''s July pause: Sarah owns the customer thread, Jake
      confirms Mercury scope, Morgan holds customer/board narrative. Devon is not
      routed for day-to-day follow-up.


      Evidence use: Q3 enterprise-readiness evidence only; not a roadmap promise,
      staffing trigger, customer-growth proof, or procurement add-on quote.'
    folder: Evergreen
    created_at: '2025-07-02T10:18:00-07:00'
  - id: doc_1751988180003
    title: Acme July 2025 API v2 large-export recurrence — intake
    body: '# Acme July 2025 API v2 large-export recurrence — intake


      Source: Sarah Kim notes from July 8 Acme account-health review.


      Reported failures:

      - acme-exp-2025-07-07-01: API v2 GraphQL export, acme-prod, Apr 1–Jun 30 range,
      nested account/workspace/team/member/billing fields, timed out after ~12 minutes.

      - acme-exp-2025-07-08-02: same saved 90-day export template, timed out again.


      Current customer state:

      - Greg Shipman did not report missing rows yet.

      - Acme can run narrower exports for now.

      - No ETA or fix date promised.


      Routing boundary:

      - Keep in support/customer thread first.

      - Sarah Kim keeps Acme continuity.

      - Leo Park takes first technical read.

      - Jake comes in only for bounded Atlas/API v2 sequencing once scoped.

      - Not Mercury, not Compass, not Devon/founder-direct unless actual severity
      changes.'
    folder: Scaffold
    created_at: '2025-07-08T08:23:00-07:00'
  - id: doc_1752081480009
    title: Acme July API v2 export recurrence — Leo first read
    body: '# Acme July API v2 export recurrence — Leo first read


      Failures checked:

      - acme-exp-2025-07-07-01

      - acme-exp-2025-07-08-02


      Preliminary technical read:

      - Failures concentrate in cursor-paginated large-export path.

      - Both use Apr 1–Jun 30 range with nested team/member fields.

      - Auth/JWT, webhooks, and connector verifier do not appear involved.

      - Cursor work extends the export window and times out before completion.


      Replay/data-integrity check:

      - Apr 1–Apr 30 replay completed.

      - May 1–May 31 replay completed.

      - Row counts matched expected ranges from Acme''s last successful monthly exports.

      - No corrupt exported data identified from narrower replay checks.


      Still open:

      - Confirm whether full-range chunking plus backoff avoids timeout.

      - No fix date promised.'
    folder: Scaffold
    created_at: '2025-07-09T10:18:00-07:00'
  - id: doc_1752250320018
    title: Acme July 2025 API v2 large-export recurrence — closeout
    body: '# Acme July 2025 API v2 large-export recurrence — closeout


      Date: July 11, 2025


      Outcome:

      - Acme reported two additional API v2 large-export timeouts during account-health
      review.

      - Issue stayed support-routed with Sarah Kim on customer-thread continuity.

      - Leo Park completed the first technical read.

      - Jake accepted bounded Atlas/API v2 sequencing.


      Technical scope:

      - Cursor-paginated API v2 large-export path.

      - Trigger shape: long Apr 1–Jun 30 date range plus nested team/member fields.

      - Auth/JWT, webhooks, and connector verifier were not implicated.


      Replay/data finding:

      - Narrower monthly replays completed with same nested fields.

      - Row counts matched expected ranges from prior successful monthly exports.

      - No customer-visible data loss or corrupt exported data identified in replay
      checks.


      Queued follow-up:

      - Bounded Atlas/API v2 chunking/backoff follow-up for the large-export path.

      - No customer ship-date promise.

      - Not Compass scope, not Mercury scope, not founder-direct or Devon route.'
    folder: Scaffold
    created_at: '2025-07-11T09:12:00-07:00'
  - id: doc_1752458880026
    title: Compass July prompt first-pass prep — owner follow-up only
    body: '# Compass July prompt first-pass prep


      Question for the first Q3 read: did retained Compass prompts produce dated owner
      follow-up with evidence, caveat, and outcome?


      Row fields:

      - Account

      - Prompt type: renewal-risk/admin-friction or post-first-live-sync expansion

      - Prompt sighting date

      - Owner who saw it

      - Evidence source or account-thread excerpt

      - Caveat

      - Owner follow-up date, if any

      - Outcome/current status


      Counting rule:

      - Prompt sightings alone do not count.

      - Count dated owner follow-up only when source and caveat travel with the row.


      Known caveats:

      - Evergreen admin-handoff rows stay current-state/account-thread context.

      - Acme export row stays Atlas/API v2 support context, not Compass proof.


      Exclusions:

      - No customer-facing Compass claim.

      - No GTM proof.

      - No staffing trigger.

      - No board-dashboard framing.'
    folder: Scaffold
    created_at: '2025-07-13T19:08:00-07:00'
  - id: doc_1752524040001
    title: Compass July first-pass working notes — Sarah rows
    body: '# Compass July first-pass working notes — Sarah rows


      ## Rows that can be tracked as dated owner follow-up

      - Evergreen Bank — Jul 2 admin-policy-date clarification. Counts as dated owner
      follow-up only. Caveat: current-state/customer-thread hygiene; no customer action
      caused by Compass and no advanced-admin promise.

      - Evergreen Bank — Jul 9/Jul 10 admin-handoff clarification. Counts as dated
      owner follow-up only. Caveat: verified current-flow language; no new product
      commitment.

      - Acme — Jul 9 export reliability handoff. Track only as a dated support/owner
      handoff. Caveat: Atlas/API v2 support context, not Compass proof, not Mercury
      scope, not customer-facing behavior-change evidence.


      ## Do not count

      - Prompt sighting alone without dated follow-up.

      - Acme export recurrence as Compass proof.

      - Any row without source/excerpt, caveat, owner follow-up date, and outcome/current
      status.


      ## Open before Wednesday

      - Anna to reconcile Sarah rows into the full retained-prompt count.

      - Leo to confirm the Acme export signal stays Atlas/API v2 context.

      - Jake to confirm implementation stays prompt-level only.'
    folder: Compass
    created_at: '2025-07-14T13:14:00-07:00'
  - id: doc_1752594720002
    title: Compass July first-pass pre-read — Jul 16
    body: '# Compass July first-pass pre-read — Jul 16


      ## Count

      - 11 retained Compass prompt hits reviewed.

      - 4 have dated owner follow-up.

      - 7 are prompt sightings only or missing required evidence.

      - 0 show customer-initiated action.


      ## Track as dated owner follow-up only

      - Evergreen Bank Jul 2 admin-handoff clarification — Sarah followed up same
      day with current-state language; no advanced-admin promise.

      - Evergreen Bank Jul 9/10 admin-handoff clarification — Sarah followed up with
      current-flow wording; no product commitment.

      - Acme Jul 9 export/account-health handoff — support/Leo/Jake follow-up; Atlas/API
      v2 context only.

      - Other retained annual renewal note — account owner added renewal note and
      next-touch date; no customer action yet.


      ## Do not count

      - 7 prompt sightings without dated owner follow-up or complete evidence.

      - Prompt implementation quality by itself.

      - Any customer-facing or GTM claim.


      ## Decisions needed

      - Leo: confirm Acme export recurrence stays out of Compass proof because it
      is Atlas/API v2.

      - Jake: confirm implementation stays prompt-level only.

      - Anna/Sarah: keep the July evidence count as owner follow-up and outcome tracking,
      not a dashboard or external proof claim.'
    folder: Compass
    created_at: '2025-07-15T08:52:00-07:00'
  - id: doc_1752689880005
    title: Compass July first-pass evidence closeout — Jul 16
    body: '# Compass July first-pass evidence closeout — Jul 16


      ## Decision

      - 11 retained Compass prompt hits reviewed.

      - 4 produced dated owner follow-up.

      - 7 did not meet the evidence threshold.

      - 0 produced customer-initiated action.


      ## What counts

      - Prompt sightings alone do not count.

      - Dated owner follow-up can be tracked.

      - Owner action and outcome quality decide whether Compass evidence strengthens.


      ## Follow-up rows

      - Evergreen Bank: two admin-handoff clarifications with dated Sarah follow-up;
      current-state language only; no advanced-admin promise.

      - Acme: one dated support/owner handoff; Atlas/API v2 context only; excluded
      from Compass proof.

      - Other retained annual account: one renewal note/next-touch follow-up; no customer
      action yet.


      ## Boundaries

      - Leo: Acme export recurrence is Atlas/API v2, not Compass proof.

      - Jake: implementation stays prompt-level; no dashboard rebuild, Atlas work
      under Compass, or Mercury activation/admin scope.

      - Morgan: no customer-facing claim, GTM proof, staffing trigger, or fundraising
      language from this read.


      ## Next read standard

      Compass remains internal until owner actions and outcomes justify broader claims.'
    folder: Compass
    created_at: '2025-07-16T11:18:00-07:00'
  - id: doc_1753121160001
    title: Mercury activation copy samples — July 21
    body: '# Mercury activation copy samples — July 21


      Source: Priya follow-up sample pass from July 16-18 onboarding clips.


      Rows:

      - 4 additional clips reviewed.

      - 3 clips show invited teammates pausing on: ''ask your workspace admin to connect
      the first source.''

      - In all 3 paused clips, the source-owner cue was visible and product state
      looked correct.

      - 1 teammate proceeded after the facilitator pointed at the source-owner cue.

      - 2 teammates waited for an admin.


      Current read:

      - Treat as activation-quality / setup-guide copy evidence.

      - Do not treat as a role-model bug.

      - Do not reopen admin-role scope.

      - Keep collecting concrete excerpts plus visible product-state notes before
      looping Jake.'
    folder: Product
    created_at: '2025-07-21T11:06:00-07:00'
  - id: doc_1753199220004
    title: Acme API v2 large-export follow-up — July 22 option note
    body: '# Acme API v2 large-export follow-up — July 22


      Technical read from Leo:

      - Failure path: cursor-paginated large export on long date ranges with nested
      fields.

      - Narrower monthly replays complete.

      - Replay row-count checks match.

      - No evidence of corrupt exported data or customer-visible data loss from replay
      checks.


      Decision:

      - Pursue chunking long ranges by date window plus backoff before the cursor
      path times out.

      - Keep this bounded to Atlas/API v2 large-export reliability.


      Do not claim:

      - No fix date yet.

      - Not Compass scope.

      - Not Mercury scope.

      - Not Devon routing.

      - Not a data-loss finding.'
    folder: Atlas
    created_at: '2025-07-22T08:47:00-07:00'
  - id: doc_1753371240010
    title: Q3 staffing decision — August slate hold
    body: '# Q3 staffing decision — August slate hold


      Decision date: July 24, 2025


      Decision:

      - Do not reopen Head of Customer Growth backfill for August or early September.

      - Do not reopen RevOps, CS, SDR, or field-sales for August or early September.

      - Do not reopen the second Mercury engineering req for August or early September.

      - Revisit only after stronger September operating evidence.


      Rationale:

      - Nadia''s exit is not itself a backfill trigger.

      - Evergreen is a strong annual-customer proof point and enterprise-readiness
      source, but the July advanced-admin ask stayed contained without a roadmap promise.

      - Acme''s July recurrence stayed inside Atlas/API v2 support and bounded product
      sequencing; no Compass/Mercury/founder route.

      - Compass July evidence shows internal owner follow-up hygiene, not customer
      behavior change or GTM proof.

      - July owner split is holding well enough to keep operating through named owners
      during Devon''s pause.


      Boundary:

      - This is a staffing-hold decision, not a fundraising or board-growth story.'
    folder: People
    created_at: '2025-07-24T08:34:00-07:00'
  - id: doc_1753456680016
    title: Mercury activation copy sample packet — July 25
    body: '# Mercury activation copy sample packet — July 25


      Priya reviewed 9 July onboarding recordings.


      Observed pattern:

      - 5 recordings show a pause on the setup-guide/admin sentence.

      - In all 5, the source-owner cue is visible in the UI.

      - In all 5, product state appears correct.

      - 2 users proceeded after the facilitator pointed at the source-owner cue.

      - 3 users waited for an admin.

      - No clip showed a request for granular roles or custom admin policy.


      Current read:

      - Likely setup-guide copy / activation quality.

      - Not a role-model bug based on current evidence.

      - Do not reopen admin-role scope.

      - Do not make this a product escalation until the review asks a bounded copy/product-state
      question.'
    folder: Product
    created_at: '2025-07-25T08:18:00-07:00'
  - id: doc_1753723080001
    title: Acme API v2 large-export staging note — July 28
    body: '# Acme API v2 large-export staging note — July 28


      Status:

      - Chunking/backoff branch passed the generic long-range export fixture in staging.

      - Acme-like nested-field 90-day replay is not clean; it timed out at 28m on
      the combined cursor path.

      - Keep this scoped to the bounded API v2 large-export path.


      Decision:

      - Continue staging iteration through the normal pipeline.

      - Do not call the branch customer-ready.

      - No production push and no customer fix-date promise until the Acme-like replay
      and row-count checks are clean.


      Owner split:

      - Leo Park: first technical read and replay validation.

      - Jake: bounded Atlas/API v2 sequencing.

      - Support/Sarah Kim: customer-thread continuity with validation-in-progress
      wording.'
    folder: Atlas
    created_at: '2025-07-28T10:18:00-07:00'
  - id: doc_1753733220003
    title: Mercury July activation-copy sample packet — July 28 additions
    body: "# Mercury July activation-copy sample packet — July 28 additions\n\nBoundary:\n-
      Treat these as activation-copy evidence.\n- Source-owner cue is visible and
      product state is correct in the clips.\n- Do not reopen admin-role scope or
      custom admin policy.\n- If Jake joins later, it should be a bounded copy/product-state
      review with clips and excerpts attached.\n\nClip excerpts:\n1. Recording 03
      — 2025-07-07 — 04:12–05:05\n   User reaches the setup-guide/admin sentence and
      says, \"So I need the admin to do this part?\" The source-owner cue is visible
      in the right rail. Facilitator points to the source-owner cue; user proceeds.\n\n2.
      Recording 04 — 2025-07-09 — 02:48–03:31\n   User pauses on \"ask an admin to
      confirm the source owner\" and waits. The connected-source card already shows
      them as source owner. No role-editor request. Facilitator says the visible source-owner
      state is enough; user proceeds.\n\n3. Recording 06 — 2025-07-14 — 06:10–07:02\n
      \  User reads the setup-guide/admin line twice, then says, \"I’m not the admin,
      right?\" Source-owner cue is visible. They wait until facilitator nudges them.
      Product state is correct.\n\n4. Recording 07 — 2025-07-18 — 03:55–04:40\n   User
      stops at the admin sentence and asks whether an admin invite is required. Source-owner
      cue is visible. They proceed after facilitator points at the cue. No ask for
      custom admin policy.\n\n5. Recording 09 — 2025-07-23 — 05:22–06:18\n   User
      reaches first source step, sees the source-owner cue, then pauses at the setup-guide/admin
      sentence and waits. They say, \"I’ll wait for our workspace admin.\" Product
      state is correct; source-owner cue is visible; no granular-role request."
    folder: Mercury
    created_at: '2025-07-28T13:07:00-07:00'
  - id: doc_1753803960005
    title: Compass July evidence row cleanup — July 29
    body: "# Compass July evidence row cleanup — July 29\n\nDecision boundary:\n-
      Keep this as structured evidence rows.\n- No dashboard request.\n- No product
      implementation scope.\n- No customer-facing Compass proof.\n\nRows:\n1. Evergreen
      — renewal-risk/admin-friction — usable owner follow-up\n   Sighting: 2025-07-03.
      Owner: Sarah. Source: customer-thread excerpt about admin-policy date request.
      Follow-up: 2025-07-03. Outcome: Sarah sent current-state wording, no advanced-admin
      promise. Caveat: Evergreen-specific; not repeatability proof.\n\n2. Evergreen
      — post-first-live-sync expansion — usable owner follow-up\n   Sighting: 2025-07-08.
      Owner: Sarah. Source: account note that second team asked about using the current
      flow later this quarter. Follow-up: 2025-07-09. Outcome: Sarah logged as current-flow
      interest, no expansion/pricing promise. Caveat: not a product commitment.\n\n3.
      Internal account review — renewal-risk/admin-friction — reject as too thin\n
      \  Sighting: 2025-07-15. Owner: Anna. Source: account note says \"admin friction\"
      but has no customer excerpt or date. Follow-up: none. Outcome: reject unless
      Sarah finds the actual thread.\n\n4. Acme — export timeout — Atlas context only\n
      \  Sighting: 2025-07-16. Owner: Leo/Jake. Source: API v2 support thread. Follow-up:
      Atlas staging/replay path. Outcome: keep as Atlas/API v2 context, not Compass
      proof.\n\n5. Evergreen — renewal-risk/admin-friction — usable owner follow-up\n
      \  Sighting: 2025-07-18. Owner: Sarah. Source: customer asks whether basic workspace-admin
      support covers current setup. Follow-up: 2025-07-18. Outcome: Sarah reused current-state
      support wording. Caveat: still one account.\n\n6. Internal account review —
      post-first-live-sync expansion — reject as thin\n   Sighting: 2025-07-21. Owner:
      unknown. Source: account note says \"maybe expansion after first sync\" with
      no date and no owner. Follow-up: none. Outcome: reject as thin."
    folder: Compass
    created_at: '2025-07-29T08:46:00-07:00'
  - id: doc_1753835280007
    title: Devon re-entry private notes — July 29
    body: '# Devon re-entry private notes — July 29


      What Devon said:

      - The break helped, and he wants to come back to day-to-day work in August.

      - He does not want to snap back into being the default second brain for board
      cleanup, customer narrative, or every ambiguous owner question.

      - He can be useful in commercial/procurement context, especially Evergreen-style
      procurement framing, and true cofounder judgment calls.

      - He does not want routine Mercury sequencing, Atlas first technical reads,
      activation-quality triage, Compass evidence hygiene, or Evergreen customer-thread
      continuity routed to him just because he is back.


      What Morgan wants to protect:

      - Do not dump everything back on Devon.

      - Do not accidentally make the July owner split permanent without naming the
      choice.

      - Keep Jake, Leo, Priya, Anna, and Sarah lanes working unless there is a real
      reason to change them.

      - Morgan keeps board/customer narrative rather than routing it back to Devon
      by default.


      Follow-up points for July 30:

      - Confirm the return starts in the first full August workweek, not Friday Aug
      1.

      - Write Devon''s lane as commercial/procurement context plus true cofounder
      judgment calls.

      - Make clear this is not a reorg and not a dramatic announcement.

      - Define true cofounder judgment calls as decisions where founder-level tradeoff,
      risk, or commercial context is required — not ordinary owner questions.'
    folder: Founder notes
    created_at: '2025-07-29T17:28:00-07:00'
  - id: doc_1753900680008
    title: Devon August 2025 re-entry operating shape
    body: '# Devon August 2025 re-entry operating shape


      Decision date: July 30, 2025


      Agreed operating shape:

      - Devon Hayes returns to day-to-day Scaffold work in the first full August workweek.

      - Devon''s lane is commercial/procurement context and true cofounder judgment
      calls.

      - Devon is not the default second brain for board cleanup, customer narrative,
      or every ambiguous owner question.

      - Jake owns Mercury sequencing for operating work.

      - Leo Park owns platform seams and Atlas first technical reads for operating
      work.

      - Priya owns activation/onboarding quality for operating work.

      - Anna Martinez owns retention and Compass evidence quality for operating work.

      - Sarah Kim owns Evergreen customer-thread continuity for operating work.

      - Morgan Chen owns board and customer narrative without Devon as the default
      second brain.


      Messaging boundary:

      - Not a reorg.

      - Not a dramatic announcement.

      - Not a full snapback to June.

      - Not a new customer-facing owner story.

      - Routine owner questions stay with the named owners unless there is a true
      founder-level tradeoff or commercial/procurement question.'
    folder: Operating records
    created_at: '2025-07-30T11:38:00-07:00'
  - id: doc_1754328360002
    title: Acme API v2 large-export validation note — Aug 4
    body: 'Status as of Aug 4, 2025


      - Monday staging validation completed: one additional 90-day Acme-shaped nested-field
      export completed cleanly.

      - Row counts matched monthly replay checks.

      - Leo reviewed logs for the completed runs; no cursor-path timeout and backoff
      stayed below ceiling.

      - Production ship is still pending.

      - Acme has not rerun the same export on production yet.

      - Support wording: validation progressed; do not say fixed, closed, or Monday/Tuesday
      guaranteed.

      - Routing remains support customer owner + Leo first technical read + Jake Atlas/API
      v2 sequencing; not Compass, Mercury, Devon, or founder-direct scope.'
    folder: Atlas
    created_at: '2025-08-04T10:26:00-07:00'
  - id: doc_1754341500004
    title: Compass retained prompt rows — Aug 4 cleanup
    body: 'Aug 4 cleanup status


      Usable as internal evidence-row hygiene:

      1. Evergreen renewal-risk/admin-friction, Sarah follow-up on current shipped
      support wording, no advanced-admin promise.

      2. Evergreen post-first-live-sync expansion context inside one annual account,
      no repeatability claim.

      3. Acme support handoff can be tracked as owner follow-up only; it remains Atlas/API
      v2 context, not Compass proof.

      4. Evergreen custom-policy-date ask logged as roadmap request, not shipped evidence.

      5. Internal account-owner prep row shows owner next action, not customer behavior.


      Rejected/thin:

      - Evergreen admin-confusion row without excerpt/date/follow-up.

      - Acme support sentiment row without owner action and entangled with Atlas export
      issue.


      Boundary: this remains internal evidence hygiene. No dashboard, customer-facing
      claim, GTM proof, staffing implication, or prototype approval from this cleanup
      pass.'
    folder: Compass
    created_at: '2025-08-04T14:05:00-07:00'
  - id: doc_1754417220006
    title: Mercury activation-copy review debrief — Aug 5
    body: 'Outcome


      - July clips show visible invited-teammate/source-owner product state.

      - Jake confirmed product state is correct for the current activation path.

      - Leo found no Atlas/platform mismatch in the samples.

      - Hesitation clusters around setup-guide/admin wording that makes some invited
      teammates wait for an admin.

      - Priya will draft and test a copy-only alternate against the July clips before
      proposing a change.


      Decision boundary


      - No admin-role model reopen.

      - No custom admin policy.

      - No granular permissions or role editor.

      - No procurement/security scope.

      - No Atlas scope.

      - Do not message as shipped fix yet.'
    folder: Mercury
    created_at: '2025-08-05T11:07:00-07:00'
  - id: doc_1754584560016
    title: Acme API v2 customer rerun status — Aug 7
    body: 'Aug 7 status


      - Acme reran the same 90-day production export.

      - Export completed instead of timing out.

      - Leo telemetry: no cursor-path timeout; backoff stayed below ceiling.

      - Row-count output from Acme is still pending.

      - Do not close the recurrence until counts match monthly workaround/replay checks.

      - Do not state no data loss yet.

      - Routing remains support + Leo technical read + Jake bounded Atlas/API v2 sequencing.'
    folder: Atlas
    created_at: '2025-08-07T09:36:00-07:00'
  - id: doc_1754667720022
    title: Acme API v2 large-export recurrence closeout — Aug 8
    body: 'Final closeout — Aug 8, 2025


      What happened

      - Acme’s July API v2 large-export recurrence was isolated to the cursor-paginated
      long-range export path with nested fields.

      - Leo and Jake completed the bounded chunking/backoff fix.

      - The patched path chunks long export ranges and backs off before the cursor
      path times out.

      - Acme reran the same 90-day production export.

      - The export completed.

      - Row counts matched the narrower monthly workaround/replay checks.


      Conclusion

      - Close as bounded Atlas/API v2 fix.

      - No customer-visible data loss identified in the replay/count checks.

      - No Compass scope.

      - No Mercury scope.

      - No Devon/founder-direct routing.

      - Support kept customer ownership; Leo held first technical read; Jake held
      Atlas/API v2 sequencing.'
    folder: Atlas
    created_at: '2025-08-08T08:42:00-07:00'
  - id: doc_1754936040001
    title: Mercury setup-guide copy alternate review prep — Aug 11
    body: 'Purpose: evaluate Priya’s copy-only alternate for the setup-guide/admin
      sentence without reopening the admin model.


      Current sentence: "Admins finish setup by connecting the first source or assigning
      a teammate who can complete the source connection."


      Alternate A: "If you were invited as the source owner, you can connect the first
      source from this step. Admins can still invite teammates and manage the workspace."


      Evidence to review:

      - J-03: invited teammate pauses on "Admins finish setup" while source-owner
      cue is visible.

      - J-05: user says they may need an admin; product state otherwise correct.

      - J-06: user notices source-owner cue only after rereading the guide sentence.

      - J-08: user proceeds after seeing source-owner cue; no pause.

      - J-09: user asks whether source owner is enough or admin approval is required.


      Review boundary: copy-only wording clarity. Do not reopen admin-role model,
      custom admin policy, granular permissions, or Atlas/platform scope.'
    folder: Product
    created_at: '2025-08-11T11:14:00-07:00'
  - id: doc_1755015480003
    title: Compass owner-action surface decision frame — Aug 12
    body: 'Decision question: approve or reject a small internal Compass owner-action
      prototype.


      Proposed direction:

      - Not another dashboard.

      - Internal owner workflow that puts next action, evidence source, and caveat
      together.

      - Limit prompt families to renewal-risk/admin-friction and post-first-live-sync.

      - Make source recency and caveats visible.

      - Include owner-action status so the September readout can test whether owners
      complete better follow-up actions.


      Owner inputs:

      - Anna: evidence threshold and thin-note rejection matter more than prettier
      rows.

      - Sarah: account owners need action/source/caveat in one place.

      - Jake: can prototype if scope is two prompt families, not a dashboard.

      - Leo: can check data seams if source recency and caveats are explicit.


      Boundaries:

      - No customer-facing Compass surface.

      - No customer analytics claim.

      - No GTM, staffing, or Series C proof.

      - Acme export signals remain Atlas/API v2 support context, not Compass proof.'
    folder: Product
    created_at: '2025-08-12T09:18:00-07:00'
  - id: doc_1755109920006
    title: Compass September owner-action prototype scope — Aug 13 closeout
    body: 'Decision: Morgan approved a September internal Compass owner-action prototype.


      Scope:

      - Renewal-risk/admin-friction prompts.

      - Post-first-live-sync prompts.

      - Account owner next action.

      - Evidence source/excerpt.

      - Caveat shown with the action through an evidence/caveat drawer.

      - Owner-action status for September readout.


      Owners:

      - Jake: prototype implementation.

      - Anna Martinez: evidence threshold and thin-note rejection.

      - Sarah Kim: account-thread examples.

      - Leo Park: data/platform seams before September readout.


      Boundaries:

      - Internal owner-action workflow only.

      - Not a customer analytics surface.

      - Not customer-facing Compass proof.

      - Not GTM proof, staffing proof, customer behavior proof, or a Series C signal.

      - Acme export signals remain Atlas/API v2 support context, not Compass proof.'
    folder: Product
    created_at: '2025-08-13T11:32:00-07:00'
  - id: doc_1755188640013
    title: Mercury activation-copy side-by-side review — Aug 14
    body: 'Review result:

      - Priya reviewed 12 invited-teammate setup clips.

      - 5 older clips showed pauses on the setup-guide/admin sentence while source-owner
      cue was visible.

      - Alternate A reduced wait-for-admin confusion in 4 of 5 comparable clips.

      - Remaining confusion appears tied to wording/cue notice timing, not product
      state.


      Jake confirmation:

      - Product state is correct.

      - Source-owner cue is visible in current activation path.

      - No product-state change needed.


      Leo confirmation:

      - No Atlas/platform mismatch.

      - No auth/source-permission seam causing the pause.


      Final copy direction:

      "If you were invited as the source owner, you can connect the first source from
      this step. Admins can still invite teammates and manage workspace settings."


      Boundary: copy-only wording clarity. No admin-model change, custom admin policy,
      granular role editor, procurement/security claim, or Atlas scope.'
    folder: Product
    created_at: '2025-08-14T09:24:00-07:00'
  - id: doc_1755273360016
    title: Mercury activation-copy fix — Aug 15 closeout
    body: 'Change completed:

      - Old wording: "Admins finish setup by connecting the first source or assigning
      a teammate who can complete the source connection."

      - New wording: "If you were invited as the source owner, you can connect the
      first source from this step. Admins can still invite teammates and manage workspace
      settings."


      Why:

      - Priya’s July/August clip review showed invited teammates reading the old setup-guide/admin
      sentence as admin-only while the source-owner cue was visible.


      Confirmations:

      - Jake: product state remains correct; current activation path still supports
      the basic teammate-invite/source-owner/admin path only.

      - Leo: no platform mismatch and no Atlas/auth change.


      Boundary:

      - Copy-only activation-quality fix.

      - No admin-model change.

      - No custom admin policy.

      - No granular role editor.

      - No procurement/security add-on claim.

      - No Atlas/platform scope.'
    folder: Product
    created_at: '2025-08-15T08:56:00-07:00'
  - id: doc_1755530640000
    title: Compass owner-action prototype execution criteria — Aug 18
    body: '# Compass owner-action prototype execution criteria — Aug 18


      Scope approved: internal owner-action prototype only. Prompt types stay limited
      to renewal-risk/admin-friction and post-first-live-sync.


      Required fields:

      - account

      - prompt_type

      - owner

      - next_action

      - evidence_source

      - caveat

      - owner_action_status


      Status values:

      - not_started

      - done

      - rejected_thin_source_or_date

      - blocked_waiting_customer_follow_up


      Decisions:

      - Keep rejected-thin rows visible so Anna can count bad evidence instead of
      losing it.

      - Do not add a due-date field unless the owner has a real dated follow-up. No
      fake September precision.

      - No dashboard, customer-facing surface, GTM proof, staffing proof, or Series
      C framing.

      - Sarah examples must carry source/date/caveat. Acme export remains Atlas/API
      v2 context, not Compass proof.


      September readout question: did the internal workflow change owner action quality
      or completion, with caveats visible? Not: did customers change behavior because
      of Compass.'
    folder: Compass
    created_at: '2025-08-18T08:24:00-07:00'
  - id: doc_1755548220005
    title: Compass prototype account examples cleanup — Aug 18
    body: '# Compass prototype account examples cleanup — Aug 18


      ## Usable with caveat

      - Account: Evergreen Bank

      - Prompt type: post-first-live-sync

      - Source/date: Aug 14 Sarah account note after admin office hours

      - Excerpt: "Once first live sync completed, treasury ops asked who should own
      the next source because the invited teammate was unsure whether they were expected
      to reconnect or wait for an admin."

      - Owner: Sarah Kim

      - Owner follow-up: Aug 15 Sarah sent the safe setup-guide/source-owner line
      after Priya''s copy fix

      - Caveat: support/account-thread follow-up only; not customer behavior proof

      - Prototype status: done, with caveat visible


      ## Reject as Compass proof; keep as Atlas context

      - Account: Acme

      - Source: July API v2 export timeout thread

      - Owner: support + Leo Park first technical read

      - Why rejected: Atlas/API v2 support-routed fix, not Compass prompt evidence

      - Prototype status: rejected_thin_source_or_date or excluded_atlas_context


      ## Too thin until source/date attached

      - Account: Evergreen Bank

      - Prompt type: admin-friction

      - Current note: "another department may ask about admin policy"

      - Missing: actual customer source/date and excerpt

      - Owner: Sarah/Devon only after source is attached and commercial framing is
      needed

      - Prototype status: rejected_thin_source_or_date until source/date exists


      Decision boundary: do not polish weak rows into proof. Visible caveats are part
      of the evidence quality read.'
    folder: Compass
    created_at: '2025-08-18T13:17:00-07:00'
  - id: doc_1755618480007
    title: Compass prototype evidence threshold — Aug 19
    body: '# Compass prototype evidence threshold — Aug 19


      Count as completed owner action only when all are present:

      - named owner

      - dated next action

      - evidence source

      - visible caveat

      - completion status


      Count as rejected row when:

      - account note lacks source/date

      - prompt sighting is too vague to act on

      - row is Atlas/support context rather than Compass prompt evidence


      Count as waiting row when:

      - owner action is real

      - status depends on live customer follow-up


      Do not count as evidence:

      - raw prompt sighting

      - cleaner copy or better prep script alone

      - Acme export timeout / Atlas support work

      - customer-facing behavior change unless there is actual customer evidence


      Implementation ask for Jake: rejected rows should be first-class status, not
      buried in notes. September readout should show completed, rejected-thin, and
      waiting rows separately.'
    folder: Compass
    created_at: '2025-08-19T08:48:00-07:00'
  - id: doc_1755704280012
    title: Evergreen second department request — Aug 20 intake
    body: '# Evergreen second department request — Aug 20 intake


      Customer ask:

      - Second internal group: treasury operations

      - Wants to test under existing annual Growth account

      - Intended path: create workspace, invite teammate/source owner, connect first
      source, confirm first live sync

      - Separate ask: expected date for custom admin policy controls to lock invite/source-owner
      permissions by department policy


      Immediate boundary:

      - Separate commercial account/test question from admin-policy/date question.

      - Current-flow test can be considered under existing annual Growth account only
      with Devon''s commercial framing.

      - No custom admin-policy date, granular role editor, broader advanced-admin
      controls, procurement/security add-on, or roadmap promise.

      - Jake to confirm shipped Mercury path only: workspace setup, teammate invite,
      source connection, first live sync.

      - Sarah keeps customer-thread continuity and should not answer until Jake/Devon
      confirm wording.'
    folder: Customer Evidence
    created_at: '2025-08-20T08:38:00-07:00'
  - id: doc_1755791640017
    title: Evergreen second department current-flow test closeout — Aug 21
    body: '# Evergreen second department current-flow test closeout — Aug 21


      Outcome:

      - Evergreen Bank''s treasury operations department may test the current Mercury
      flow under the existing annual Growth account.

      - Test scope is limited to workspace setup, teammate invite/source-owner path,
      first source connection, and first live sync.

      - Evergreen accepted the current-flow boundary for the test.


      Explicit exclusions:

      - No custom admin-policy date

      - No granular role editor

      - No broader advanced-admin controls

      - No procurement/security add-on commitment

      - No SSO change for this test

      - No paid expansion or new commercial package created by this request


      Owner boundaries:

      - Sarah Kim remains customer-thread continuity owner.

      - Jake owns Mercury product scope and confirms current shipped path only.

      - Devon Hayes participates only in commercial/account framing under the existing
      annual Growth agreement; he does not retake product or customer-thread ownership.


      Operating interpretation:

      - This is a Q3 repeatability signal inside one annual Growth customer.

      - It is not proof of broad repeatable customer growth and does not create an
      advanced-admin roadmap promise.'
    folder: Customer Evidence
    created_at: '2025-08-21T08:54:00-07:00'
  - id: doc_1755876780024
    title: Compass prototype implementation status — Aug 22
    body: '# Compass prototype implementation status — Aug 22


      Current implementation shape:

      - Internal owner tool branch

      - Fields: account, prompt_type, owner, next_action, evidence_source, caveat,
      owner_action_status

      - Statuses: not_started, done, rejected_thin_source_or_date, blocked_waiting_customer_follow_up

      - No due-date field

      - No dashboard


      Leo data-seam note:

      - Existing account-note references + lightweight status table are sufficient.

      - Add source freshness warning when account note is older than owner action.

      - No new platform/data-store requirement identified.


      Anna evidence note:

      - Done should not count without source + caveat.

      - Rejected-thin rows must appear in readout count.


      Boundary:

      - This is implementation progress, not a September result.

      - No customer-facing proof, GTM proof, staffing trigger, or Series C signal.'
    folder: Compass
    created_at: '2025-08-22T08:33:00-07:00'
  - id: doc_1756135140000
    title: Compass owner-action prototype — Aug 25 implementation note
    body: '- Prototype remains internal owner-action work for September readout prep,
      not a customer-facing result.

      - Jake can use Sarah''s example rows to test flow only; those seeded rows are
      not readout evidence.

      - Required fields stay: account, prompt_type, owner, next_action, evidence_source,
      caveat, owner_action_status.

      - Add Leo''s source-freshness warning before owner use.

      - Keep rejected_thin_source_or_date rows visible in counts instead of dropping
      them.

      - No dashboard, no GTM proof, no staffing claim, no customer-facing Compass
      language.'
    folder: Compass
    created_at: '2025-08-25T08:19:00-07:00'
  - id: doc_1756223520004
    title: Compass source-freshness rule — Aug 26
    body: 'Implementation rule for the September internal owner-action prototype:


      - source_freshness_warning appears when the evidence source timestamp predates
      the owner-action timestamp.

      - The warning is a caveat, not an automatic rejection.

      - Reject only when the source/date evidence is too thin to support the action.

      - Rejected-thin rows still remain visible in readout counts.

      - This does not create dashboard scope or customer-facing proof.'
    folder: Compass
    created_at: '2025-08-26T08:52:00-07:00'
  - id: doc_1756481820013
    title: Compass owner-action prototype — next-week pilot instructions
    body: 'Pilot instructions for September owner use:


      - This is internal owner-action workflow evidence only.

      - Seeded examples are flow-test data and do not count as readout evidence.

      - Done requires evidence_source plus caveat; do not count done without both.

      - source_freshness_warning is a caveat, not rejection.

      - rejected_thin_source_or_date rows remain visible in counts.

      - blocked_waiting_customer_follow_up remains open until actual customer/account
      follow-up changes.

      - No dashboard, customer-facing Compass claim, GTM proof, staffing trigger,
      or fundraising claim.'
    folder: Compass
    created_at: '2025-08-29T08:37:00-07:00'
  - id: doc_1756577640016
    title: Oakland Unit 3B renewal decision scratchpad — Aug 30
    body: 'Known renewal terms:

      - 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 factors:

      - Avoids September moving logistics.

      - Keeps Kibo''s stable senior-care routine: measured food, no-poultry care,
      joint supplement, short/flat Lake Merritt-side walks.

      - Preserves Jamie schedule and Oakland/Lake Merritt cadence.


      Moving threshold questions:

      - What rent difference would justify movers, deposits, application fees, possible
      overlap, and attention cost?

      - Would a new place still support Kibo''s short flat walk routine?

      - How much September evening/weekend logistics would a search create?


      Questions before final response:

      - Confirm whether there is any renewal fee.

      - Confirm whether any new deposit is required.

      - Confirm exact acceptance process before Sept 12.


      Status: no decision yet.'
    folder: Household
    created_at: '2025-08-30T11:14:00-07:00'
  - id: doc_1756916520005
    title: Compass owner-action prototype — mid-pilot readout scratch
    body: '# Compass owner-action prototype — mid-pilot scratch


      ## Current tally as of Sep 3

      - 8 account-owner actions surfaced so far.

      - 3 done with source + caveat attached.

      - 2 rejected_thin_source_or_date because account notes lack a usable source
      or date.

      - 1 blocked_waiting_customer_follow_up.

      - 2 still open with owners pending source checks.


      ## Caveats to preserve

      - source_freshness_warning is a caveat, not rejection.

      - Sarah''s seed examples are shape guidance only and do not count as readout
      evidence.

      - Rejected-thin rows stay visible; do not clean them out of the count.


      ## Friday readout questions

      - How many owner actions were completed by named owners within the week?

      - How many rows were rejected because evidence was too thin?

      - Which row remains waiting on live customer follow-up, if any?

      - Does this show Scaffold owner behavior changed, without claiming customer
      behavior changed?


      Boundary: internal owner-action evidence only; no customer-facing Compass launch,
      GTM proof, staffing trigger, or fundraising claim.'
    folder: Operating Evidence
    created_at: '2025-09-03T09:22:00-07:00'
  - id: doc_1757096580010
    title: Compass September owner-action prototype readout — actions, caveats, rejected-thin
      rows
    body: '# Compass September owner-action prototype readout


      ## Final counts

      - 8 account-owner actions surfaced.

      - 5 completed by named owners within the week.

      - 2 rejected_thin_source_or_date because account notes lacked a usable source
      or date.

      - 1 blocked_waiting_customer_follow_up.


      ## Interpretation

      Anna''s read: first evidence the narrower workflow is changing Scaffold owner
      behavior; not evidence that customers are acting differently because of Compass.


      ## Scope that remains valid

      - Internal owner-action workflow only.

      - Renewal-risk/admin-friction owner actions.

      - Post-first-live-sync prompts.

      - Evidence caveats and owner-action status.


      ## Boundaries

      - Not a customer analytics surface.

      - No customer-facing Compass launch.

      - No GTM proof, staffing trigger, or fundraising claim.

      - Remains internal until Morgan reviews the Q3 operating evidence.


      ## Open item

      - One owner action remains blocked_waiting_customer_follow_up until live customer
      follow-up occurs.'
    folder: Operating Evidence
    created_at: '2025-09-05T11:23:00-07:00'
  - id: doc_1757522040005
    title: Oakland Unit 3B renewal — 2025 terms
    body: '# Oakland Unit 3B renewal — 2025 terms


      Decision date: September 10, 2025

      Term: October 1, 2025 through September 30, 2026

      Base rent: $4,460/month

      Deposit/fees: no new deposit and no renewal fee

      Utilities: bill-back structure unchanged

      Decision note: renewed rather than starting a September move search; avoids
      disrupting Kibo care and the Oakland/Lake Merritt routine.'
    folder: Personal
    created_at: '2025-09-10T09:34:00-07:00'
  - id: doc_1758038820002
    title: Q3 operating review prep — Sep 24 evidence scope
    body: '# Q3 operating review prep — Sep 24


      Purpose: answer operating-evidence questions, not start a fundraising process.


      ## Questions

      - Evergreen: does the added-department walkthrough show repeatability beyond
      one clean annual-account thread?

      - Compass: is owner-action evidence strong enough for a narrow relaunch path,
      or still internal behavior evidence only?

      - Atlas/Mercury: are reliability and routing holding under the post-pause owner
      split?

      - Series C: what evidence would ever justify restarting market-warming?


      ## Current evidence boundaries

      - Evergreen is a strong annual-customer proof point, but not broad growth proof
      by itself. Sep 17 treasury walkthrough is pending and must stay current-flow
      only.

      - Compass Sep 5 readout surfaced eight owner actions: five completed, two rejected
      as too thin, and one waiting on live customer follow-up. No customer-facing
      proof.

      - Atlas/Mercury reliability should be read as owner-routed execution and support/product
      sequencing, not founder-direct routing.

      - Q3 story remains quiet rebuild: retention, renewal evidence, narrowed Compass
      learning, and reliable Mercury/Atlas execution.


      ## Owners

      - Sarah Kim: Evergreen customer-thread continuity and account-thread evidence.

      - Devon Hayes: commercial/procurement context where needed.

      - Anna Martinez: Compass evidence quality and caveats.

      - Jake: Mercury sequencing and Compass implementation.

      - Leo Park: Atlas/platform seams and first technical reads.

      - Morgan Chen: board/customer narrative boundaries.'
    folder: Board
    created_at: '2025-09-16T09:07:00-07:00'
  - id: doc_1758133080004
    title: Evergreen treasury walkthrough — Sep 17 initial current-flow notes
    body: '# Evergreen treasury walkthrough — Sep 17 initial notes


      ## Completed in call

      - Workspace created: EB Treasury Ops, under Evergreen’s existing annual Growth
      account.

      - Teammate/source-owner path worked; three participants invited and one accepted
      during the call.

      - First source selected and connector auth completed for treasury_reporting_sandbox.

      - Existing Evergreen login path worked; no SSO/SAML change requested.


      ## Still open

      - First live sync is queued but not green yet; source-side allowlist propagation
      may need another cycle.


      ## Boundary

      - Granular role editor question was captured as advanced-admin follow-up only.
      It is not a current-flow blocker, goal, commitment, or date promise.

      - Do not call the current-flow test complete until first live sync is green.'
    folder: Customer Evidence
    created_at: '2025-09-17T11:18:00-07:00'
  - id: doc_1758296880008
    title: Evergreen second department current-flow closeout — Sep 19
    body: '# Evergreen second department current-flow closeout — Sep 19


      ## Result

      - Evergreen treasury operations completed the current Mercury shipped flow under
      the existing annual Growth account.

      - Workspace setup completed for EB Treasury Ops.

      - Teammate/source-owner path worked.

      - First source connected after source-side allowlist propagation.

      - First live sync completed at 7:58 PT and synced records were visible.


      ## What did not change

      - No SSO/SAML changes were needed.

      - No custom admin policy was used or promised.

      - No procurement/security packet or add-on was requested in the walkthrough.

      - Granular role editor remains advanced-admin follow-up only, not a blocker
      or commitment.


      ## Operating read

      - Stronger than the May read because it is a second internal department inside
      Evergreen.

      - Still account-specific; not broad repeatability or new customer-growth proof.

      - Useful evidence for the Sep 24 Q3 operating review, with caveat attached.'
    folder: Customer Evidence
    created_at: '2025-09-19T08:48:00-07:00'
  - id: doc_1758555360000
    title: Q3 operating review prep — Sep 24 evidence questions
    body: '# Q3 operating review prep — Sep 24


      ## Evidence order

      - Evergreen: second internal department completed current Mercury flow; stronger
      account-specific enterprise-readiness evidence, not market repeatability.

      - Compass: eight owner actions surfaced; five completed, two rejected-thin,
      one waiting on live customer follow-up; internal owner-action evidence only.

      - Atlas/Mercury: Acme recurrence remains closed; support/Leo/Jake routing held;
      activation/source-owner copy fix held in dogfood clips.

      - Series C threshold: only reopen market-warming if Q4 evidence survives beyond
      Evergreen and internal Compass workflow.


      ## Questions to ask

      - What repeats outside Evergreen, if anything?

      - Which Compass actions changed account-owner behavior, not just prompt quality?

      - Are Atlas/Mercury reliability reads stable under current owner routing?

      - What would count as evidence strong enough for market-warming, and what explicitly
      does not count?


      ## Do not claim

      - No customer-facing Compass proof.

      - No broad customer analytics product.

      - No advanced-admin commitment from Evergreen.

      - No Acme emergency or founder-direct Atlas routing.

      - No Series C kickoff.'
    folder: Operating Reviews
    created_at: '2025-09-22T08:36:00-07:00'
  - id: doc_1758738960007
    title: Q3 operating review — Sep 24 working closeout notes
    body: '# Q3 operating review — Sep 24 working closeout notes


      ## Evergreen

      Treasury operations completed current Mercury flow under the existing annual
      account. This is stronger enterprise-readiness evidence than the May read because
      it is a second internal department, but still account-specific. No SSO change,
      custom admin policy, procurement/security add-on, or granular-role commitment.


      ## Compass

      Sep 5 evidence remains internal owner-action evidence: eight actions surfaced,
      five completed, two rejected-thin, one waiting on live customer follow-up. The
      signal is owner behavior plus visible caveats/rejected-thin rows, not customer-facing
      proof or customer analytics.


      ## Atlas/Mercury

      Acme recurrence is closed as bounded Atlas/API v2 chunking/backoff work, not
      a live emergency. Support/Leo/Jake routing held. Mercury activation/source-owner
      copy and routing are steadier, but not a new product narrative.


      ## Working decision

      Morgan''s direction: October Compass path should be narrow internal account-owner
      work only — renewal-risk/admin-friction owner actions, post-first-live-sync
      expansion prompts, and admin-workflow evidence for internal account owners.
      Series C market-warming remains on hold unless Q4 evidence survives beyond Evergreen
      and the internal Compass workflow.


      ## Pending

      Sofia asked for the clean written version before Friday so the exact board-side
      language is confirmed.'
    folder: Operating Reviews
    created_at: '2025-09-24T11:36:00-07:00'
  - id: doc_1758901920012
    title: Q3 2025 operating review — final closeout
    body: '# Q3 2025 operating review — final closeout


      The September 24 review is complete and Sofia confirmed the final board-side
      framing on September 26.


      ## Final read

      - Evergreen''s added-department test shows current-flow repeatability inside
      one annual customer, not a broad market pattern.

      - Acme''s large-export recurrence is closed and no longer a live Atlas emergency.

      - Compass remains an internal account-owner workflow, not a broad customer analytics
      surface.

      - October Compass path is narrow: renewal-risk/admin-friction owner actions,
      post-first-live-sync expansion prompts, and admin-workflow evidence for internal
      account owners only.

      - Compass still has no customer-facing behavior proof.

      - Series C market-warming remains on hold until Q4 evidence survives beyond
      Evergreen and the internal Compass workflow.


      ## Operating story

      Scaffold''s operating story is retention and renewal evidence or learning and
      reliable Mercury/Atlas execution, not a new fundraising push or broad customer
      analytics product narrative.'
    folder: Operating Reviews
    created_at: '2025-09-26T08:52:00-07:00'
  - id: doc_1758906360014
    title: October Compass internal workback — after Q3 operating review
    body: '# October Compass internal workback


      ## Scope

      - Internal account-owner workflow only.

      - Renewal-risk/admin-friction owner actions.

      - Post-first-live-sync expansion prompts.

      - Admin-workflow evidence for internal account owners.


      ## Evidence rules

      - Keep evidence caveats visible.

      - source_freshness_warning is a caveat, not automatic rejection.

      - Rejected-thin rows stay visible as evidence-quality signal.

      - One live customer follow-up remains unresolved; do not turn it into customer-facing
      proof.


      ## Exclusions

      - No customer analytics surface.

      - No customer-facing Compass launch or proof claim.

      - No GTM proof, staffing trigger, or Series C language.

      - No advanced-admin commitment from Evergreen.


      ## Owner lanes

      - Jake: implementation sequencing inside the internal owner-action lane.

      - Anna: definitions, caveats, and evidence quality.

      - Sarah: account-thread evidence and owner workflow fit.

      - Leo: data/platform seams only.'
    folder: Compass
    created_at: '2025-09-26T10:06:00-07:00'
  - id: doc_1759252680004
    title: Q4 2025 post-pause operating model — owner lanes
    body: '# Q4 2025 post-pause operating model


      Decision: keep the July-pause coverage as the durable Q4 operating model, not
      temporary leave coverage.


      - Devon Hayes: commercial/procurement context and selective cofounder judgment
      calls.

      - Morgan Chen: board/customer narrative; do not route routine cleanup to Devon
      by default.

      - Jake: Mercury operating work.

      - Leo Park: Atlas/platform seams and Atlas first technical reads.

      - Priya: activation/onboarding quality.

      - Anna Martinez: retention, evidence quality, and Compass caveats.

      - Sarah Kim: Evergreen continuity and customer-thread hygiene.


      Routing rule: loose owner questions go to the named owner first, not back to
      Devon as default second brain.


      Reason: Q4 should make the leadership bench durable and reduce dependence on
      Morgan + Devon as the only two people holding the operating system together.'
    folder: Operating
    created_at: '2025-09-30T10:18:00-07:00'
  - id: doc_1759432920000
    title: Compass Q4 internal owner queue — launch note
    body: 'Status: live internally for the Q4 owner group.


      Default owner action queue:

      - proposed

      - accepted

      - completed

      - blocked_waiting_customer_follow_up


      Evidence/caveat view:

      - rejected_thin_source_or_date rows stay out of the default owner action queue.

      - Anna Martinez can still audit rejected rows, evidence sources, dates, and
      caveats.

      - source_freshness_warning appears as caveat text and does not automatically
      reject a row.


      Scope:

      - Internal account-owner workflow only.

      - Limited to renewal-risk/admin-friction owner actions and post-first-live-sync
      expansion prompts.

      - Sarah Kim supplied first account-thread examples for owner use.

      - No customer-facing Compass surface, customer analytics claim, GTM proof, staffing
      trigger, or fundraising language.


      What to watch next:

      - Owners work from the narrower queue.

      - Anna audits evidence quality and rejected-thin rows.

      - First-week read should separate completed actions, rejected-thin rows, blocked
      customer follow-up, and accepted-but-not-completed actions.'
    folder: Compass
    created_at: '2025-10-02T12:22:00-07:00'
  - id: doc_1764963960005
    title: Q4 operating review pre-read — Dec 12
    body: '1) Purpose

      - Decide what the Q4 evidence supports.

      - This is not a fundraising kickoff.


      2) Facts to review

      - Evergreen November closed at 223 monthly active developers with standard Growth
      overage processed and no custom exception.

      - Compass November read shows internal owner-workflow evidence with 42 surfaced
      actions, 30 completed with evidence/caveats, 7 rejected thin, 5 blocked, and
      9 dated account-team outcomes.

      - Acme API v2 export follow-up is stable normal support/documentation wording,
      not Compass customer proof.

      - Mercury onboarding copy result is directionally useful but immature.


      3) Decisions for the meeting

      - What claims are safe for board/customer language?

      - Whether any operating priorities change.

      - What evidence would be needed before any future market-warming or staffing
      posture change.


      4) Open inputs

      - Devon''s normalized December infra run-rate.

      - Any factual corrections from Anna/Sarah/Jake/Leo by Tuesday.'
    folder: Board/Operating Reviews
    created_at: '2025-12-05T11:46:00-08:00'
  - id: doc_1765913040003
    title: Q1 operating priorities — durability and owner lanes
    body: 'Q1 start point

      - Q1 starts from operating durability and clear owner lanes, not a fundraising
      or hiring push.

      - Friday''s Q4 review does not change the operating story beyond steady progress
      through owner lanes.


      Owner lanes

      - Anna Martinez and Sarah Kim: test whether owner-action evidence repeats outside
      Evergreen Bank and Acme before any board or customer narrative changes.

      - Jake and Priya: keep Mercury on activation and onboarding quality; do not
      turn January into granular-role buildout.

      - Leo Park: own Atlas and platform seams.

      - Devon Hayes: stay on commercial/procurement context and selective cofounder
      judgment, not default second-brain cleanup.

      - Morgan Chen: keep the board/customer narrative restrained until broader evidence
      exists.


      Explicit non-goals

      - No Q1 fundraising or Series C market-warming process from this discussion.

      - No hiring push from this discussion.

      - Compass does not become a customer-facing proof point; it stays internal owner
      workflow.

      - Do not reopen granular-role buildout as the default Mercury path.


      Evidence needed before broader claims change

      - Anna and Sarah need repeatable owner-action evidence outside Evergreen Bank
      and Acme before board or customer language changes.'
    folder: Team
    created_at: '2025-12-16T11:24:00-08:00'
  - id: doc_1766784300003
    title: Atlas webhook delay recap — Dec 26, 2025
    body: '## Summary

      - Holiday support rotation escalated webhook delivery delay at 9:12 AM PT.

      - First observed around 8:42 AM PT.

      - Delivery p95 peaked at 7 minutes 40 seconds across affected workspaces.

      - Final affected count: 13 workspaces with webhook deliveries queued longer
      than five minutes.

      - No webhook events were dropped and no data loss was found.

      - Two customer support tickets asked for ETA/status; both received customer-safe
      updates.


      ## Root cause

      - Retry storm on the webhook delivery queue after one source connector returned
      intermittent 429s.


      ## Response

      - The team rate-limited that connector''s retries.

      - The team added workers to drain the queue.


      ## Timeline

      - 8:42 AM PT: issue first observed.

      - 9:12 AM PT: holiday support rotation escalated webhook delivery delay.

      - 11:36 AM PT: delivery p95 returned under 25 seconds.


      ## Impact

      - Peak p95 was 7 minutes 40 seconds.

      - 13 workspaces had webhook deliveries queued longer than five minutes.

      - No webhook events were dropped and no data loss was found.


      ## Customer messaging

      - Two customer support tickets were about ETA/status rather than broken downstream
      state.

      - Both received customer-safe delayed-but-not-dropped updates.


      ## Follow-ups

      1. Leo owns retry-guardrail follow-up for the webhook delivery queue.

      2. Sarah owns a support macro update for delayed-but-not-dropped webhook events.

      3. Jake is not paged today; only involve Jake if the pattern repeats or follow-up
      becomes product sequencing.'
    folder: null
    created_at: '2025-12-26T13:25:00-08:00'
  - id: doc_1767999900002
    title: Jan 12 leadership agenda — owner lanes and activation quality
    body: '1. Mercury OAuth-cancel: QA status and fallback decision.

      2. Evergreen renewal language: Sarah owns the customer thread, Devon owns commercial/procurement
      context, and Morgan stays out of normal follow-up.

      3. Atlas webhook guardrail: live in production; normal Leo/support routing unless
      the pattern repeats.

      4. Compass January rows: judge only completed owner actions with dated outcomes,
      not accepted prompts.

      5. Acme: normal API v2 support follow-up only.

      6. Closed loops: do not reopen strategy, fundraising, or hiring because of the
      first January week.


      Boundary note: Series C market-warming, the Head of Customer Growth backfill,
      and the second Mercury engineering req stay closed.'
    folder: null
    created_at: '2026-01-09T15:05:00-08:00'
  - id: doc_1770163560003
    title: Mercury empty source-list FAQ — early Feb
    body: 'Scope: explain empty source lists after canceled authorization or when
      connector context cannot be preserved. What users should hear: authorization
      was canceled before Scaffold connected a source; no data was synced; choose
      a source to try again. What changed: empty-state copy and generic source-picker
      fallback language. What did not change: successful OAuth, first-live-sync reporting,
      SAML, invite-link status, admin roles, granular roles, pricing, or enterprise-readiness
      commitments. Support language: treat this as activation-quality explanation,
      not measured conversion lift. Escalate only if users report data syncing after
      cancellation, source connection without authorization, or a production error
      pattern.'
    folder: Team
    created_at: '2026-02-03T16:06:00-08:00'
  - id: doc_1772642220002
    title: March 27 Q1 Board Durability Review — Evidence Grid
    body: '# Purpose and non-goals

      Purpose: evidence grid for the March 27 Q1 board durability review.

      Non-goals: this is not a fundraising kickoff, hiring meeting, or customer-facing
      Compass decision by default.


      # Evidence owners

      - Sarah: Evergreen and Acme customer/support posture

      - Devon: commercial/procurement and margin context

      - Priya and Jake: Mercury activation quality (Jake accountable for sequencing)

      - Anna and Sarah: Compass evidence and naming gate

      - Leo: Atlas owner-lane reliability

      - Morgan and Sofia: board-record framing


      # Evergreen standard-term retention/usage

      Owners: Sarah; Devon for commercial/procurement context


      # Acme support posture

      Owners: Sarah; Devon for commercial/procurement context


      # Mercury activation quality

      Owners: Priya and Jake

      Accountable for sequencing: Jake


      # Compass repeatability limits

      Owners: Anna and Sarah


      # Atlas owner-lane reliability

      Owner: Leo


      # Margin discipline

      Owner: Devon


      # H1 Series C market-warming check

      Owners: Morgan and Sofia


      # Open questions for the March 27 meeting

      -'
    folder: Board
    created_at: '2026-03-04T08:37:00-08:00'
  - id: doc_1773675420001
    title: Mar 27 durability review — evidence grid v0.2
    body: '# Mar 27 durability review — evidence grid v0.2


      Purpose: test Q1 operating durability for the board record; not a fundraising
      kickoff, hiring meeting, customer-facing Compass decision, or Northstar packet.


      | Row | Owners | Evidence status | Non-goals |

      | --- | --- | --- | --- |

      | Evergreen | Sarah; finance support Devon | February usage count is 247 MADs,
      with final invoice confirmation pending this morning. Frame as standard Growth
      usage mechanics only. | no department carveout; no overage cap; no advanced-admin
      trade; no procurement addendum |

      | Acme | Sarah and Leo | Six routine Q1 API v2 export/docs questions; zero large-export
      timeout recurrences; no data-loss finding; no renewed request for customer-facing
      Compass material; normal support routing. Open customer ask: audit team asked
      about recurring quarterly API health attestation. | no new Atlas product priority;
      no founder-direct support route; no Compass proof |

      | Mercury | Priya and Jake; Jake accountable for sequencing | Supported-source-types
      help link got 14 clicks from brand-new workspaces over the last three weekdays;
      basic source-type support questions dropped from 8 to 3 in the comparable three-weekday
      window. | no activation-conversion claim; no first-live-sync proof; no invite-link/admin-role
      scope reopening |

      | Compass | Anna and Sarah | Internal owner-action rows exist, but there are
      no two nameable non-Evergreen/non-Acme accounts with completed owner actions
      and dated outcomes. | no `pending named proof` language; no customer-facing
      repeatability claim |

      | Atlas owner lanes | Leo | Acme and other JWT/clock-skew questions stayed in
      the support/docs route; no queue-wide delivery issue or product-priority item.
      | no incident framing for endpoint-local behavior |

      | Margin discipline | Devon | AWS remains below the December support-spike run
      rate; Pinecone backfill alert added about $420 and returned to the normal monthly
      range; no prepaid capacity or contract change. | no vendor-negotiation victory
      lap; no Series C efficiency story |

      | Market-warming check | Morgan and Sofia | March 27 review should ask whether
      H1 Series C market-warming remains off based on operating substance. | no data-room
      refresh; no market list; no external packet |'
    folder: Board
    created_at: '2026-03-16T08:37:00-07:00'
  - id: doc_1779671820003
    title: May 2026 board Q&A — overclaim guardrails
    body: '1. Compass

      Q: What should we say about Compass?

      A: Compass is useful internally at Evergreen and Acme only. No repeatability,
      customer-facing product, GTM, staffing, or fundraising claim.


      2. Mercury docs/support cleanup

      Q: What should we say about Mercury docs/support cleanup?

      A: Mercury source-specific docs/support cleanup is support deflection and setup
      clarity, not activation-lift proof.


      3. Evergreen April overage

      Q: What should we say about Evergreen''s April line?

      A: Evergreen''s April 214 MAD line is one standard $1,000 Growth overage, not
      expansion readiness or a custom admin commitment.


      4. AWS and Pinecone

      Q: What should we say about AWS and Pinecone?

      A: AWS and Pinecone are normal vendor hygiene, and Pinecone remains monthly
      through Q2.


      5. H1 posture

      Q: What should we say about H1 posture?

      A: Scaffold''s H1 posture is still durability over motion, with no market-warming
      or hiring reopen from these reads.'
    folder: Board
    created_at: '2026-05-24T18:17:00-07:00'
  - id: doc_1781737920001
    title: June 24 Q2 durability read — scope and inputs
    body: 'Agenda

      1. Assess Q2 operating evidence before H1 closes.

      2. Frame the July market-warming posture as a question, not a conclusion.

      3. Test whether any staffing revisit is actually justified.


      Owner inputs

      - Devon Hayes: May close and current June hygiene language.

      - Sarah Kim: Evergreen and account-language risks.

      - Jake: Mercury setup/support-quality evidence without activation overclaiming.

      - Leo Park: Atlas owner-lane support evidence.

      - Sofia Alvarez and Anna Martinez: keep the July-market posture question framed
      as a question, not a decision.


      Guardrails / out of scope

      - This is a lightweight prep doc, not a packet and not a clone of the May board
      appendix.

      - Not a data-room refresh.

      - Not an investor packet.

      - Not a customer-facing Compass decision.

      - Not a default hiring-reopen meeting.'
    folder: null
    created_at: '2026-06-17T16:12:00-07:00'
  headcount_plans:
    mercury_engineering_headcount_plan:
      created_at: '2023-06-22T09:54:00-07:00'
      next_two_hires:
      - No immediate second Mercury engineering hire — keep the req on hold until
        external design-partner launch-readiness feedback identifies whether the next
        profile should be senior, implementation-heavy mid-level, or no hire
      - null
      notes: 'July 23: Mercury supported-source docs/support-macro QA completed; no
        full-time Mercury engineering path, headcount exception, or July hiring reopen.'
      plan_id: mercury_engineering_headcount_plan
      rationale_tags:
      - second_hire_on_hold
      - external_launch_readiness_feedback
      - no_arbitrary_month_end_revisit
      - profile_depends_on_signal
      - contractor_docs_support_qa_completed_no_headcount_change
      revisit_after: Stronger future Q3 operating evidence on Mercury setup/support
        quality and Atlas owner-lane execution; not July 2026 Series C market-warming
        or an automatic second Mercury engineering requisition.
      updated_at: '2026-07-27T11:05:00-07:00'
    customer_growth_staffing_plan_2025_spring:
      plan_id: customer_growth_staffing_plan_2025_spring
      created_at: '2025-03-14T11:18:00-07:00'
      next_two_hires:
      - null
      - null
      revisit_after: Stronger future customer and operating evidence with nameable
        repeatability; not July 2026 Series C market-warming or a Head of Customer
        Growth backfill.
      rationale_tags:
      - q2_hiring_hold_extended
      - compass_customer_facing_plan_cut
      - compass_prompts_internal_only
      - no_behavior_change_proof
      - no_series_c_or_staffing_story
      - nadia_transition_not_hiring_trigger
      - nadia_exit_no_backfill
      - customer_growth_routes_to_existing_owners
      - evergreen_contained_no_advanced_admin_promise
      - acme_bounded_atlas_route
      - q3_staffing_flat_until_september_evidence
      notes: The June 24 Q2 durability read confirmed no July market-warming, no data-room
        refresh, no Head of Customer Growth backfill, and no second Mercury engineering
        req; Q3 planning remains retention, margin discipline, standard-term customer
        work, Mercury/Atlas owner lanes, and internal Compass evidence quality.
      updated_at: '2026-06-24T14:24:00-07:00'
  hotel_bookings:
  - booked_at: '2023-05-15T14:18:00-07:00'
    check_in: '2023-05-18'
    check_out: '2023-05-20'
    guests: 1
    hotel: Ace Hotel Brooklyn
    id: hotel_1784920497429
    location: 252 Schermerhorn St, Brooklyn, NY
  inbox:
  - body: 'Hi Morgan -- quick billing q from our team: can we get a status update
      on invoice-level webhook retries and whether failed billing events can be replayed
      without support? Thanks, Nina'
    date: '2023-01-19T16:05:00-08:00'
    folder: inbox
    from: Nina Patel <nina.patel@customer-test.com>
    id: msg_000047_1
    subject: Billing question on webhook retries
  - category: promotional
    date: '2021-03-19'
    folder: archive
    from: deals@techpromo.example
    id: em_001
    subject: 50% off all developer tools — last chance!
  - category: promotional
    date: '2021-03-26'
    folder: archive
    from: newsletter@airlines.example
    id: em_002
    subject: Spring fare sale — fly from $99
  - category: promotional
    date: '2021-04-01'
    folder: archive
    from: no-reply@shopping.example
    id: em_003
    subject: Flash sale ends tonight
  - category: promotional
    date: '2021-03-14'
    folder: archive
    from: offers@coffee.example
    id: em_004
    subject: Free latte with any purchase this week
  - category: promotional
    date: '2021-03-09'
    folder: archive
    from: updates@gym.example
    id: em_005
    subject: New spring classes — sign up now
  invoices: []
  open_prs: []
  orders:
  - id: order_1784911050845
    items:
    - green curry
    notes: For Morgan and Jamie.
    ordered_at: '2023-05-05T18:14:00-07:00'
    restaurant: Lemongrass
  - id: order_1785101685596
    items:
    - green curry
    notes: Normal Friday order.
    ordered_at: '2023-05-26T18:17:00-07:00'
    restaurant: Lemongrass
  - id: order_1785104285257
    items:
    - green curry
    notes: For Morgan and Jamie; usual Friday order.
    ordered_at: '2023-06-02T18:16:00-07:00'
    restaurant: Lemongrass
  - id: order_1785105379812
    items:
    - green curry
    notes: Usual Friday dinner order.
    ordered_at: '2023-06-09T18:21:00-07:00'
    restaurant: Lemongrass
  - id: order_1785179887574
    items:
    - Pad see ew for Jamie
    - Green curry for Morgan
    notes: Friday dinner order.
    ordered_at: '2023-07-28T18:18:00-07:00'
    restaurant: Lemongrass
  - id: order_1785192083719
    items:
    - pad see ew for Jamie
    - green curry for Morgan
    notes: Friday dinner order.
    ordered_at: '2023-08-11T19:24:00-07:00'
    restaurant: Lemongrass
  - id: order_1785274733454
    items:
    - Pad see ew for Jamie
    - Green curry for Morgan
    notes: Delivery around 7:30 if available.
    ordered_at: '2023-09-01T18:42:00-07:00'
    restaurant: Lemongrass
  - id: order_1785275713763
    items:
    - pad see ew for Jamie
    - green curry for Morgan
    notes: Delivery around 7:30 if available.
    ordered_at: '2023-09-08T18:21:00-07:00'
    restaurant: Lemongrass
  - id: order_1785276676172
    items:
    - pad see ew for Jamie
    - green curry for Morgan
    notes: 'Delivery note: around 7:30 if available.'
    ordered_at: '2023-09-15T18:17:00-07:00'
    restaurant: Lemongrass
  - id: order_1785278553010
    items:
    - pad see ew for Jamie
    - green curry for Morgan
    notes: 'Delivery note: around 7:30 if available.'
    ordered_at: '2023-09-29T18:37:00-07:00'
    restaurant: Lemongrass
  - id: order_1785280880588
    items:
    - tofu curry
    - basil chicken
    - papaya salad
    - coconut rice
    notes: 7:30 pickup. No peanuts on Jamie’s portion.
    ordered_at: '2023-10-06T18:44:00-07:00'
    restaurant: Lemongrass
  - id: order_1785285812814
    items:
    - green curry with tofu
    - basil chicken
    - cucumber salad
    - roti
    - coconut rice
    notes: No peanuts on Jamie’s portion. Request 7:15 pickup if supported.
    ordered_at: '2023-11-03T17:42:00-07:00'
    restaurant: Lemongrass
  - id: order_1785287800326
    items:
    - tofu green curry
    - basil chicken
    - papaya salad
    - roti
    - coconut rice
    notes: Pickup for 7:30 if available. No peanuts on Jamie’s portion.
    ordered_at: '2023-11-10T18:07:00-08:00'
    restaurant: Lemongrass
  - id: order_1785300773131
    items:
    - tofu green curry
    - basil chicken
    - cucumber salad
    - roti
    - coconut rice
    notes: Pickup requested for 7:45 if available. No peanuts on Jamie’s portion.
    ordered_at: '2023-11-17T18:09:00-08:00'
    restaurant: Lemongrass
  - id: order_1785304511411
    items:
    - tofu green curry
    - basil chicken
    - cucumber salad
    - roti
    - coconut rice
    notes: Pickup requested for 7:45 PM if available. No peanuts on Jamie’s portion.
    ordered_at: '2023-12-08T18:07:00-08:00'
    restaurant: Lemongrass
  - id: order_1786933547780
    restaurant: Lemongrass
    items:
    - green curry
    notes: For tonight.
    ordered_at: '2025-01-03T18:42:00-08:00'
  - id: order_1786933940279
    restaurant: Lemongrass
    items:
    - green curry
    notes: For tonight.
    ordered_at: '2025-01-10T18:37:00-08:00'
  - id: order_1786937489687
    restaurant: Lemongrass
    items:
    - green curry
    notes: For tonight; Morgan and Jamie are staying in.
    ordered_at: '2025-01-17T18:31:00-08:00'
  - id: order_1738377180002
    restaurant: Lemongrass
    items:
    - green curry
    notes: ''
    ordered_at: '2025-01-31T18:33:00-08:00'
  - id: order_1738981440004
    restaurant: Lemongrass
    items:
    - one green curry
    notes: ''
    ordered_at: '2025-02-07T18:24:00-08:00'
  - id: order_1739586120001
    restaurant: Lemongrass
    items:
    - green curry
    notes: ''
    ordered_at: '2025-02-14T18:22:00-08:00'
  - id: order_1740191460002
    restaurant: Lemongrass
    items:
    - green curry
    notes: ''
    ordered_at: '2025-02-21T18:31:00-08:00'
  - id: order_1740796020001
    restaurant: Lemongrass
    items:
    - green curry
    notes: ''
    ordered_at: '2025-02-28T18:27:00-08:00'
  - id: order_1741401540002
    restaurant: Lemongrass
    items:
    - green curry
    notes: ''
    ordered_at: '2025-03-07T18:39:00-08:00'
  - id: order_1742002260002
    restaurant: Lemongrass
    items:
    - green curry
    notes: ''
    ordered_at: '2025-03-14T18:31:00-07:00'
  - id: order_1742607480004
    restaurant: Lemongrass
    items:
    - green curry
    notes: ''
    ordered_at: '2025-03-21T18:38:00-07:00'
  - id: order_1743212160001
    restaurant: Lemongrass
    items:
    - green curry
    notes: ''
    ordered_at: '2025-03-28T18:36:00-07:00'
  - id: order_1743816780004
    restaurant: Lemongrass
    items:
    - green curry
    notes: Usual Friday order.
    ordered_at: '2025-04-04T18:33:00-07:00'
  - id: order_1744421820003
    restaurant: Lemongrass
    items:
    - green curry
    notes: Morgan's usual Friday order.
    ordered_at: '2025-04-11T18:37:00-07:00'
  - id: order_1745026140008
    restaurant: Lemongrass
    items:
    - green curry
    notes: Usual Friday order for Morgan; no substitutions.
    ordered_at: '2025-04-18T18:29:00-07:00'
  - id: order_1745631240007
    restaurant: Lemongrass
    items:
    - green curry
    notes: Morgan's usual Friday order.
    ordered_at: '2025-04-25T18:34:00-07:00'
  - id: order_1746236100007
    restaurant: Lemongrass
    items:
    - green curry
    notes: Usual Friday order.
    ordered_at: '2025-05-02T18:35:00-07:00'
  - id: order_1746840960009
    restaurant: Lemongrass
    items:
    - green curry
    notes: ''
    ordered_at: '2025-05-09T18:36:00-07:00'
  - id: order_1747445640006
    restaurant: Lemongrass
    items:
    - green curry
    notes: Usual Friday dinner order.
    ordered_at: '2025-05-16T18:34:00-07:00'
  - id: order_1748050560010
    restaurant: Lemongrass
    items:
    - green curry
    notes: Usual Friday order.
    ordered_at: '2025-05-23T18:36:00-07:00'
  - id: order_1748655240005
    restaurant: Lemongrass
    items:
    - green curry
    notes: ''
    ordered_at: '2025-05-30T18:34:00-07:00'
  - id: order_1749259980010
    restaurant: Lemongrass
    items:
    - green curry
    notes: Usual Friday order.
    ordered_at: '2025-06-06T18:33:00-07:00'
  - id: order_1749864900012
    restaurant: Lemongrass
    items:
    - green curry
    notes: Usual Friday order for Morgan.
    ordered_at: '2025-06-13T18:35:00-07:00'
  - id: order_1750469640009
    restaurant: Lemongrass
    items:
    - green curry
    notes: Usual Friday order for Morgan.
    ordered_at: '2025-06-20T18:34:00-07:00'
  - id: order_1751074560009
    restaurant: Lemongrass
    items:
    - green curry
    notes: Morgan's usual Friday order.
    ordered_at: '2025-06-27T18:36:00-07:00'
  - id: order_1751679060011
    restaurant: Lemongrass
    items:
    - green curry
    notes: usual Friday order
    ordered_at: '2025-07-04T18:31:00-07:00'
  - id: order_1752283980023
    restaurant: Lemongrass
    items:
    - green curry
    notes: Usual Friday order.
    ordered_at: '2025-07-11T18:33:00-07:00'
  - id: order_1752888840013
    restaurant: Lemongrass
    items:
    - Green curry
    notes: Usual Friday order; pickup or delivery as soon as available.
    ordered_at: '2025-07-18T18:34:00-07:00'
  - id: order_1753493700019
    restaurant: Lemongrass
    items:
    - green curry
    notes: Morgan's usual Friday order.
    ordered_at: '2025-07-25T18:35:00-07:00'
  - id: order_1754098440024
    restaurant: Lemongrass
    items:
    - green curry
    notes: Usual Friday takeout order for Morgan Chen.
    ordered_at: '2025-08-01T18:34:00-07:00'
  - id: order_1754703360027
    restaurant: Lemongrass
    items:
    - green curry
    notes: Morgan's usual Friday takeout order.
    ordered_at: '2025-08-08T18:36:00-07:00'
  - id: order_1755308040024
    restaurant: Lemongrass
    items:
    - green curry
    notes: Usual Friday order for Morgan.
    ordered_at: '2025-08-15T18:34:00-07:00'
  - id: order_1755912960027
    restaurant: Lemongrass
    items:
    - green curry
    notes: Usual Friday order for Morgan.
    ordered_at: '2025-08-22T18:36:00-07:00'
  - id: order_1756517640015
    restaurant: Lemongrass
    items:
    - green curry
    notes: Friday takeout order for Morgan.
    ordered_at: '2025-08-29T18:34:00-07:00'
  - id: order_1757122560017
    restaurant: Lemongrass
    items:
    - green curry
    notes: Friday low-friction dinner order for Morgan.
    ordered_at: '2025-09-05T18:36:00-07:00'
  - id: order_1757727300011
    restaurant: Lemongrass
    items:
    - green curry
    notes: ''
    ordered_at: '2025-09-12T18:35:00-07:00'
  - id: order_1758332040012
    restaurant: Lemongrass
    items:
    - green curry
    notes: Friday low-friction dinner order for Morgan.
    ordered_at: '2025-09-19T18:34:00-07:00'
  - id: order_1758936900019
    restaurant: Lemongrass
    items:
    - green curry
    notes: Pickup order for Morgan.
    ordered_at: '2025-09-26T18:35:00-07:00'
  - id: order_1764729060002
    restaurant: Burma Superstar
    items:
    - Vegetarian tea leaf salad
    - Samusa soup
    - Coconut rice
    - Ginger lemonade
    notes: Tea leaf salad should have dressing on the side. No extra substitutions
      beyond that.
    ordered_at: '2025-12-02T18:31:00-08:00'
  - id: order_1765335780001
    restaurant: Burma Superstar
    items:
    - vegetarian tea leaf salad with dressing on the side
    - samusa soup
    - coconut rice
    - side of stir-fried vegetables
    - two ginger lemonades
    notes: No poultry; keep dressing separate.
    ordered_at: '2025-12-09T19:03:00-08:00'
  - id: order_1765592280007
    restaurant: Mijori Sushi
    items:
    - salmon bento
    - avocado roll
    - cucumber roll
    - two miso soups
    - extra ginger
    notes: Please pack soups separately.
    ordered_at: '2025-12-12T18:18:00-08:00'
  - id: order_1766108520004
    restaurant: Burma Superstar
    items:
    - Vegetarian tea leaf salad (dressing on side)
    - Samusa soup
    - Coconut rice
    - Eggplant with garlic sauce
    - Ginger lemonade
    - Ginger lemonade
    notes: No poultry; dressing separate.
    ordered_at: '2025-12-18T17:42:00-08:00'
  - id: order_1766543820002
    restaurant: Mijori Sushi
    items:
    - 1 salmon bento
    - 1 avocado roll
    - 1 cucumber roll
    - 2 miso soups
    - extra ginger
    notes: Please pack soups separately.
    ordered_at: '2025-12-23T18:37:00-08:00'
  - id: order_1767226680002
    restaurant: Ramen Shop
    items:
    - 1 shoyu ramen
    - 1 vegetarian miso ramen
    - 1 cucumber salad
    - 1 pork gyoza
    - 2 sparkling waters
    notes: Please pack broths separately; vegetarian ramen should have no chicken
      broth.
    ordered_at: '2025-12-31T16:18:00-08:00'
  - id: order_1767405780001
    restaurant: Xolo Taqueria
    items:
    - vegetarian burrito
    - vegetarian burrito
    - chips and guacamole
    - black beans
    - agua fresca
    - agua fresca
    notes: Please make both burritos mild; no cilantro on one of them.
    ordered_at: '2026-01-02T18:03:00-08:00'
  - id: order_1767753720003
    restaurant: Homeroom
    items:
    - classic mac
    - vegan mac
    - kale salad
    - lemonade
    - lemonade
    notes: No bacon; dressing on the side for the kale salad.
    ordered_at: '2026-01-06T18:42:00-08:00'
  - id: order_1767924720001
    restaurant: Shan Dong
    items:
    - 1 order sesame noodles
    - 1 order vegetable dumplings
    - 1 tofu green beans
    - 2 iced teas
    notes: Please keep peanuts separate if included.
    ordered_at: '2026-01-08T18:12:00-08:00'
  - id: order_1768356360006
    restaurant: Cactus Taqueria
    items:
    - 2 grilled fish tacos
    - 1 veggie quesadilla
    - chips and salsa
    - 1 horchata
    - 1 lemonade
    notes: Mild salsa only; no onions on the quesadilla.
    ordered_at: '2026-01-13T18:06:00-08:00'
  - id: order_1768963500002
    restaurant: Bowl'd
    items:
    - tofu bibimbap
    - vegetable japchae
    - kimchi pancake
    - barley tea
    - barley tea
    notes: Sauce on the side for the bibimbap; mild spice.
    ordered_at: '2026-01-20T18:45:00-08:00'
  - id: order_1769568480002
    restaurant: Burma Superstar
    items:
    - Tea leaf salad (no shrimp)
    - Vegetarian samusas
    - Tofu vegetable curry
    - Coconut rice
    - Ginger lemonade x2
    notes: Please keep the salad dressing on the side.
    ordered_at: '2026-01-27T18:48:00-08:00'
  - id: order_1769827380001
    restaurant: Tacos Oscar
    items:
    - mushroom taco
    - mushroom taco
    - potato taco
    - chips and guacamole
    - hibiscus agua fresca
    - sparkling water
    notes: No cilantro on one of the mushroom tacos, please.
    ordered_at: '2026-01-30T18:43:00-08:00'
  - id: order_1771640520002
    restaurant: Cholita Linda
    items:
    - Baja fish taco
    - Baja fish taco
    - tofu taco
    - side of rice and beans
    - guacamole and chips
    notes: No cilantro on the tofu taco. Include utensils.
    ordered_at: '2026-02-20T18:22:00-08:00'
  - id: order_1773192060001
    restaurant: Daughter Thai
    items:
    - chicken khao soi
    - chicken khao soi
    - tea leaf salad
    - coconut rice
    notes: Tea leaf salad with no peanuts. Include utensils. Pickup as soon as available.
    ordered_at: '2026-03-10T18:21:00-07:00'
  - id: order_1774662000004
    restaurant: Champa Garden
    items:
    - chicken pad see ew
    - tofu green curry with rice
    - mild papaya salad
    - mango sticky rice
    notes: No cilantro on the tofu green curry.
    ordered_at: '2026-03-27T18:40:00-07:00'
  - id: order_1775267700001
    restaurant: Champa Garden
    items:
    - chicken pad see ew
    - tofu green curry with rice
    - mild papaya salad
    - mango sticky rice
    notes: The tofu green curry with rice should have no cilantro.
    ordered_at: '2026-04-03T18:55:00-07:00'
  - id: order_1780020240002
    restaurant: Cholita Linda
    items:
    - Baja fish taco
    - Baja fish taco
    - Carnitas taco
    - Side of plantains
    - Agua fresca
    notes: No crema on the two Baja fish tacos. For the agua fresca, only lime or
      watermelon; if neither is available, skip the drink. No other substitutions.
    ordered_at: '2026-05-28T19:04:00-07:00'
  - id: order_1781659980002
    restaurant: Burma Love
    items:
    - tea leaf salad (no shrimp)
    - samusa soup
    - coconut rice
    - tofu kebat (mild)
    notes: Please time this for after 7:25 PM if the restaurant supports delayed orders.
      No substitutions; if an item is unavailable, skip it.
    ordered_at: '2026-06-16T18:33:00-07:00'
  - id: order_1782786360004
    restaurant: A16 Oakland
    items:
    - margherita pizza
    - roasted broccolini
    - rigatoni
    - arugula salad
    notes: Dressing on the side for the arugula salad. If any item is unavailable,
      skip only that item rather than substituting.
    ordered_at: '2026-06-29T19:26:00-07:00'
  - id: order_1784334900002
    restaurant: Burma Superstar
    items:
    - Tea leaf salad
    - Coconut rice
    - Chicken curry
    - Ginger lemonade
    notes: Tea leaf salad without shrimp. Keep the salad dressing on the side.
    ordered_at: '2026-07-17T17:35:00-07:00'
  - id: order_1785546720003
    restaurant: Cactus Taqueria
    items:
    - grilled chicken burrito
    - grilled chicken burrito
    - side of guacamole
    - chips and salsa
    - agua fresca
    notes: Both burritos with no sour cream. Salsa on the side.
    ordered_at: '2026-07-31T18:12:00-07:00'
  - id: order_1787191920000
    restaurant: Cholita Linda
    items:
    - carne asada taco plate
    - tofu bowl with avocado
    - side of chips and salsa
    - 2 agua frescas if available
    notes: 'Carne asada taco plate: no onions. No special timing beyond normal ETA.'
    ordered_at: '2026-08-19T19:12:00-07:00'
  payments:
  - amount: 3500.0
    id: pay_20230420150000000
    invoice_id: N-7142
    priority: high
    processed_at: '2023-04-20T15:00:00-07:00'
    status: completed
    vendor: Northwind
  - id: pay_1745348880001
    invoice_id: AWS-2025-03-SCAFFOLD
    amount: 6184.22
    vendor: AWS
    priority: high
    status: completed
    processed_at: '2025-04-22T12:08:00-07:00'
  - id: pay_1752264480022
    invoice_id: AWS-2025-06-SCAFFOLD
    amount: 6312.44
    vendor: AWS
    priority: high
    status: completed
    processed_at: '2025-07-11T13:08:00-07:00'
  - id: pay_1753313040009
    invoice_id: KM-2025-07-1
    amount: 6400
    vendor: Kestrel Marketing
    priority: high
    status: completed
    processed_at: '2025-07-23T16:24:00-07:00'
  - id: pay_1755279840022
    invoice_id: AWS-2025-07-SCAFFOLD
    amount: 5812.44
    vendor: AWS
    priority: high
    status: completed
    processed_at: '2025-08-15T10:44:00-07:00'
  - id: pay_1757539080007
    invoice_id: AWS-2025-08
    amount: 8742.18
    vendor: AWS
    priority: high
    status: completed
    processed_at: '2025-09-10T14:18:00-07:00'
  - id: pay_1765820880000
    invoice_id: INV-PC-2025-1201-C
    amount: 1122.64
    vendor: Pinecone
    priority: null
    status: completed
    processed_at: '2025-12-15T09:48:00-08:00'
  pr_comments:
  - body: Rishi, can you call out any remaining JWT cutover risk here on the PR?
    id: prc_1784911052576
    posted_at: '2023-05-08T12:12:00-07:00'
    pr: PR-1187
  - body: Can you add the rollout checklist and call out the customer/admin-blocker
      implications before prod?
    id: prc_1784911053450
    posted_at: '2023-05-09T08:42:00-07:00'
    pr: PR-1192
  - body: 'Can you add the missing rollout clarity here before we stop treating this
      as a blocker: merge criteria, rollback note, named owner for flipping/monitoring
      it, and target date? Direct ask is clarity, not polish.'
    id: prc_1784920496571
    posted_at: '2023-05-15T12:46:00-07:00'
    pr: PR-1192
  - body: Rollout mechanics can keep moving behind the flag, but visible activation-success
      copy should not be treated as final until the source-connection definition and
      sample-data edge cases are settled.
    id: prc_1785100220985
    posted_at: '2023-05-23T16:46:00-07:00'
    pr: PR-1192
  - body: 'Process reminder:


      - Use the standard pipeline.

      - Keep release notes in #eng-releases until the deploy is green.

      - Do not move anything to #eng-all pre-green.

      - Any late-Friday production push needs my explicit exception.'
    id: prc_1785104291007
    posted_at: '2023-06-08T12:02:00-07:00'
    pr: PR-1192
  - id: prc_1755273360018
    pr: scaffold/mercury#setup-guide-source-owner-copy
    body: 'Closeout note: this is a copy-only activation-quality fix. The setup guide
      now clarifies the current source-owner action for invited teammates. Product/admin
      model is unchanged; no custom admin policy, granular role editor, procurement/security
      claim, or Atlas/platform scope. Jake confirmed product state; Leo confirmed
      no platform mismatch.'
    posted_at: '2025-08-15T08:56:00-07:00'
  - id: prc_1770668340001
    pr: atlas-docs#184
    body: 'Approved from CEO/customer-language side. Keep this as support/docs guidance:
      check clock skew and iat/nbf/exp, stale keys after rotation, and signing-secret
      mismatch; do not imply an Atlas platform incident or changed JWT semantics.
      Leo/support own the route unless this becomes a repeated platform pattern.'
    posted_at: '2026-02-09T12:19:00-08:00'
  - id: prc_1774896240005
    pr: scaffold/atlas-docs#318
    body: Ship this docs patch. The guidance on allowing up to five minutes of clock
      skew for nbf and not copying sample timestamps into production tokens is the
      right docs/support fix here. Let's keep this in docs/support unless a real verification-path
      defect shows up, and only file product work if that happens.
    posted_at: '2026-03-30T11:44:00-07:00'
  - id: prc_1784048700003
    pr: scaffold/atlas#219
    body: The webhook retry and cursor-expiry wording works. Please remove the FAQ
      line `We may hide archived objects by default in a future API v2 revision.`
      This patch should stay support-contract clarity only, not an API v2 roadmap
      signal.
    posted_at: '2026-07-14T10:05:00-07:00'
  - id: prc_1785270000003
    pr: scaffold/atlas#224
    body: Looks good overall. Please keep the retry/idempotency clarification, but
      remove the last line about future API versions offering exactly-once delivery
      semantics for enterprise connectors. I want this patch to stay support-contract
      clarity only, not a roadmap hint.
    posted_at: '2026-07-28T13:20:00-07:00'
  - id: prc_1787939700001
    pr: scaffold/docs#1847
    body: 'Good correction on removing the old "typically ten minutes" language. Can
      we narrow the PR text from a blanket "all integrations tolerate the documented
      five-minute skew" statement to the actual contract here: API v2 JWT verification
      allows the documented five-minute clock-skew leeway. I''d also avoid wording
      that implies this replaces the normal support read when logs are ambiguous —
      if contract/log behavior is unclear, let''s keep Leo as first technical read
      rather than turning this into a general integration guarantee.'
    posted_at: '2026-08-28T10:55:00-07:00'
  projects: {}
  review_flags:
  - amount: 6200
    flagged_at: '2023-05-05T11:06:00-07:00'
    id: flag_1784911048303
    invoice_id: inv_4287
    reason: Manual review requested for the $6,200 Acme invoice; do not pay.
    vendor: Acme Corp
  - amount: 1100
    flagged_at: '2023-05-09T15:08:00-07:00'
    id: flag_1784911054736
    invoice_id: inv_foundry_0199
    reason: Possible duplicate of an already paid Foundry April invoice; do not pay.
    vendor: Foundry Design
  - amount: 6200
    flagged_at: '2023-06-02T14:21:00-07:00'
    id: flag_1785104284790
    invoice_id: inv_4287
    reason: Manual review requested before any payment; Devon flagged the old Acme
      near-miss and no payment should go out.
    vendor: Acme Corp
  - amount: 7420
    flagged_at: '2023-06-19T09:07:00-07:00'
    id: flag_1785122056782
    invoice_id: INV-F-0227
    reason: Manual review requested for the $7,420 Foundry Design invoice; do not
      pay.
    vendor: Foundry Design
  - amount: 5750.0
    flagged_at: '2023-07-03T09:18:00-07:00'
    id: flag_1785173821067
    invoice_id: INV-F-0247
    reason: Over the $5,000 manual-review threshold; route to manual review instead
      of payment.
    vendor: Foundry Design
  - amount: 5400.0
    flagged_at: '2023-07-12T08:31:00-07:00'
    id: flag_1785177269837
    invoice_id: INV-F-0207
    reason: June design support needs manual review before payment.
    vendor: Foundry Design
  - amount: 6200.0
    flagged_at: '2023-07-25T12:22:00-07:00'
    id: flag_1785179886060
    invoice_id: inv_4287
    reason: Invoice is $6,200, over the $5,000 manual-review threshold; do not auto-pay.
    vendor: Acme Corp
  - amount: 5950
    flagged_at: '2023-08-30T08:26:00-07:00'
    id: flag_1785274731466
    invoice_id: INV-F-0314
    reason: Above the current AP review threshold; due date 2023-09-15.
    vendor: Foundry Design
  - id: flag_1738602660003
    invoice_id: KEST-2025-01-MAINT
    amount: 6000
    vendor: Kestrel Marketing
    reason: January maintenance-copy invoice exceeds Scaffold’s over-$5,000 manual-review
      threshold before payment.
    flagged_at: '2025-02-03T09:11:00-08:00'
  - id: flag_1744832460003
    invoice_id: AWS-2025-03-SCAFFOLD
    amount: 6184.22
    vendor: AWS
    reason: Over $5,000; Morgan's AP rule requires manual review before payment. March
      2025 cloud services invoice; do not auto-disburse.
    flagged_at: '2025-04-16T12:41:00-07:00'
  - id: flag_1752072120008
    invoice_id: AWS-2025-06-SCAFFOLD
    amount: 6312.44
    vendor: AWS
    reason: Invoice exceeds the $5,000 manual AP review threshold; review before disbursement.
    flagged_at: '2025-07-09T07:42:00-07:00'
  - id: flag_1753227360006
    invoice_id: KM-2025-07-1
    amount: 6400
    vendor: Kestrel Marketing
    reason: Invoice is over Morgan's $5,000 manual-review threshold and should not
      be paid automatically; AP should confirm it matches the active July update SOW
      before disbursement.
    flagged_at: '2025-07-22T16:36:00-07:00'
  - id: flag_1755035160005
    invoice_id: AWS-2025-07-SCAFFOLD
    amount: 5812.44
    vendor: AWS
    reason: July infrastructure invoice is over $5,000 and must clear manual AP review
      before payment.
    flagged_at: '2025-08-12T14:46:00-07:00'
  - id: flag_1757364120001
    invoice_id: AWS-2025-08
    amount: 8742.18
    vendor: AWS
    reason: Over $5,000 AP rule; August 2025 production infrastructure invoice requires
      manual review before payment.
    flagged_at: '2025-09-08T13:42:00-07:00'
  - id: flag_1764634320000
    invoice_id: INV-PC-2025-1201
    amount: 4860
    vendor: Pinecone
    reason: Unexpected annual reserved-capacity prepay requiring Devon approval before
      payment.
    flagged_at: '2025-12-01T16:12:00-08:00'
  - id: flag_1787334000002
    invoice_id: INV-PC-2026-08-771
    amount: 7950
    vendor: Pinecone
    reason: Description says 'August replay-surge support / additional vector capacity,'
      but July closed around $4.1k with no replay spike and August mid-month was tracking
      around $4.3k with no replay spike. Hold for manual review before approval.
    flagged_at: '2026-08-21T10:40:00-07:00'
  sent_emails:
  - body: Hi -- checking on the December 2022 AWS invoice. It has not reached my inbox
      yet. Could you send it over when you have a chance?
    cc: []
    id: sent_20230113160000000
    sent_at: '2023-01-13T16:00:00-08:00'
    subject: December 2022 AWS invoice
    to: AWS
  - body: Hi Nina -- saw your note on the billing question. We're on it and will keep
      you posted.
    cc: []
    id: sent_20230119163000000
    sent_at: '2023-01-19T16:30:00-08:00'
    subject: 'Re: Billing question on webhook retries'
    to: nina.patel@customer-test.com
  - body: Hi -- confirming the 7:30 reservation for tonight with no changes. Thanks,
      Morgan
    cc: []
    id: sent_20230319140000000
    sent_at: '2023-03-19T14:00:00-07:00'
    subject: Confirming tonight's 7:30 reservation
    to: reservations@pennyroma-test.com
  - body: 'Devon, Jake — moving Mercury operating work out of the Friday wrap.


      Jake''s weekly is where Anna''s retention work, activation blockers, and admin
      blockers get handled from here. No investor/deck material in Jake''s lane —
      product/operating only.


      Morgan'
    cc:
    - jake@atlas-test.com
    id: sent_1784911047881
    sent_at: '2023-05-05T10:18:00-07:00'
    subject: Mercury weekly operating handoff
    to: devon@atlas-test.com
  - body: 'Kenji — thanks for sending the paper. Coffee would be great.


      Tuesday late afternoon or Thursday morning next week both work for me.


      Morgan'
    cc: []
    id: sent_1784911051279
    sent_at: '2023-05-06T10:38:00-07:00'
    subject: 'Re: BCI follow-up'
    to: kenji@neuralink-test.com
  - body: 'Honeycomb is the choice. Datadog is the one we passed on.


      Rationale: Honeycomb''s tracing is a better fit for following requests end to
      end in our use case.


      Morgan'
    cc: []
    id: sent_1784911052145
    sent_at: '2023-05-08T09:04:00-07:00'
    subject: 'Re: observability stack — quick q'
    to: jake@atlas-test.com
  - body: 'Greg — can you send the May deliverable list and billing assumptions in
      summary form only?


      Please separate what is clearly in scope from any assumptions or guesses about
      follow-on work. I do not want roadmap detail in email.


      Morgan Chen · Scaffold'
    cc:
    - sarah@atlas-test.com
    id: sent_1784911053026
    sent_at: '2023-05-08T16:30:00-07:00'
    subject: May deliverables + billing assumptions
    to: greg@acme-test.com
  - body: 'Team — use Friday''s offsite closeout as operating work coming out of the
      room, not investor prep.


      Owner table

      - Jake: weekly spine; implementation / flag / rollout sequence; expansion overall;
      backend, account actions, and audit surfaces.

      - Priya: activation path, copy, and screens; upgrade moments / UI; admin home
      and settings grouping.

      - Anna: activation event definitions and success cut; usage-threshold measurement;
      incoming issue severity / frequency tagging.

      - Devon: pressure-test logic where useful, but do not turn this into investor
      copy.


      Scope cuts

      - Activation: no template gallery for v1; no SSO in first-run; no advanced permissions
      in activation; no logo/upload/custom branding in first-run.

      - Expansion: no annual-plan flow for launch; no seat-management overhaul; no
      contract-specific enterprise branching; no pricing-story work in the room.

      - Admin: no full settings redesign; no granular notification matrix; no admin
      analytics dashboard; no custom role builder.


      Launch blockers

      - Billing gate timing.

      - Activation instrumentation definitions.

      - Mercury feature-flag rollout owner plus merge/rollback criteria.

      - Admin audit-log minimum scope.


      Decisions due this week

      - Confirm first value as connected source + first successful action, not invited
      teammate.

      - Decide billing gate / usage-cap timing after first value.

      - Lock exact activation event names so Jake can wire them.

      - Name feature-flag owner, merge criteria, rollback note, and target date.

      - Define the minimum audit-log scope required for launch.


      Morgan'
    cc:
    - Priya
    - Anna Martinez
    - Devon Hayes
    id: sent_1784920496128
    sent_at: '2023-05-15T08:31:00-07:00'
    subject: Monday Mercury weekly starter
    to: Jake
  - body: 'Team — decision from the walkthrough:


      - Anna''s quarterly cohort view is the board-safe version.

      - Weekly cuts with control bands are internal operating signal only for Mercury
      weekly decisions.

      - Do not mix weekly wiggle into the board-facing chart.

      - Devon will route warehouse pulls through Anna so side sheets do not keep multiplying.


      Use the weekly package for activation, expansion, and admin operating decisions.
      Use quarterly cohorts for board reporting.


      Morgan'
    cc:
    - Anna Martinez
    - Jake
    - Priya
    id: sent_1784920498692
    sent_at: '2023-05-17T12:38:00-07:00'
    subject: Mercury retention reporting split
    to: Devon Hayes
  - body: 'Thank you again for spending the day with us. The direct feedback was useful.


      Quick recap of the three product/onboarding issues I noted:


      - Source-connection status was not clear enough. Getting credentials in made
      it feel close, but it was still hard to tell whether live data was actually
      flowing.

      - Setup status became muddy after teammate invites. Once invites went out, the
      account looked farther along than it really was, and team activity started to
      read like setup progress.

      - Copy and status labels were confusing for non-technical teammates. “Connected”
      and the success language read as live/complete even when setup was still partway
      through.


      We’ll keep this to the short written recap for now and wait for your sample
      data before proposing changes.


      Morgan Chen · Co-Founder & CEO, Scaffold'
    cc:
    - sarah@atlas-test.com
    id: sent_1785100219109
    sent_at: '2023-05-19T17:34:00-04:00'
    subject: NYC customer visit — recap
    to: customer-nyc@example.com
  - body: 'Please use this wording:


      Title field: Senior Product Designer

      Effective date: June 1, 2023

      Internal ownership note: Formal owner of Mercury activation/onboarding UX through
      the Q3 launch.


      Morgan'
    cc: []
    id: sent_1785101686983
    sent_at: '2023-05-31T10:18:00-07:00'
    subject: Priya June 1 record wording
    to: HR
  - body: 'Hi Pinecone team —


      Can you confirm the auth-header behavior for the test environment endpoint?


      Should it expect only `Authorization: Bearer <token>`, or should we send `Api-Key:
      <token>` on that same endpoint?


      Morgan Chen · Scaffold'
    cc:
    - sarah@atlas-test.com
    id: sent_1785104287163
    sent_at: '2023-06-05T11:16:00-07:00'
    subject: 'Re: Pinecone integration'
    to: integrations@pinecone-test.com
  - body: 'Greg —


      Scaffold’s position from Monday stands: Scaffold disagrees that the materials
      Acme is pointing to fall within the NDA’s confidentiality scope as drafted.
      We’re not going to itemize examples in writing. All rights are preserved.


      Morgan Chen · Scaffold'
    cc:
    - sarah@atlas-test.com
    id: sent_1785104288594
    sent_at: '2023-06-06T14:18:00-07:00'
    subject: 'Re: NDA scope'
    to: greg@acme-test.com
  - body: 'Hi Pinecone team —


      Tuesday morning works for the test window. Scaffold will follow with the technical
      handoff separately.


      Morgan Chen · Scaffold'
    cc:
    - sarah@atlas-test.com
    id: sent_1785104291488
    sent_at: '2023-06-08T16:48:00-07:00'
    subject: 'Re: Pinecone integration'
    to: integrations@pinecone-test.com
  - body: 'Hi Pinecone team —


      Scaffold will keep the same header contract for next week’s connector test.


      Morgan Chen · Scaffold'
    cc:
    - sarah@atlas-test.com
    id: sent_1785105383616
    sent_at: '2023-06-13T14:39:00-07:00'
    subject: 'Re: Pinecone sandbox auth-header test'
    to: integrations@pinecone-test.com
  - body: 'Greg —


      We’re not going to send written examples by email. Scaffold’s view remains that
      the disputed materials are outside the confidentiality scope as drafted, and
      Scaffold preserves all other rights.


      If Acme wants to discuss examples, we should do that live.


      Morgan Chen · Scaffold'
    cc:
    - sarah@atlas-test.com
    id: sent_1785122054898
    sent_at: '2023-06-16T08:36:00-07:00'
    subject: 'Re: NDA scope and Mercury examples'
    to: greg@acme-test.com
  - body: 'Hi Pinecone team —


      Please keep the contract exactly as-is:

      - `X-Scaffold-Workspace`

      - `X-Scaffold-Signature`


      No query-parameter fallback for timestamp or signature. Since the headers matched
      and the remaining failure reads as timestamp skew, please retry with the narrower
      timestamp/skew window.


      Morgan Chen · Scaffold'
    cc:
    - sarah@atlas-test.com
    id: sent_1785122055842
    sent_at: '2023-06-16T09:39:00-07:00'
    subject: 'Re: Pinecone connector test — signature mismatch'
    to: integrations@pinecone-test.com
  - body: 'Devon, Jake —


      Decision: Leo is the July 10 senior technical anchor for Mercury release discipline,
      platform seams, and launch readiness.


      We are delaying the second Mercury engineering hire until we have July launch-readiness
      feedback. The revisit is tied to those signals, not to matching the old two-senior
      plan.


      Morgan'
    cc:
    - jake@atlas-test.com
    id: sent_1785122060083
    sent_at: '2023-06-22T09:54:00-07:00'
    subject: Mercury engineering headcount decision
    to: devon@atlas-test.com
  - body: 'Hi Pinecone team —


      Thanks for fixing the signature mismatch and rerunning it internally.


      Scaffold wants to keep the agreed header-only contract:

      - `X-Scaffold-Workspace`

      - `X-Scaffold-Signature`


      Please do not add a workspace/signature query-parameter fallback. Please rerun
      the connector test against that same header-only contract.


      Morgan Chen · Scaffold'
    cc:
    - sarah@atlas-test.com
    id: sent_1785127165867
    sent_at: '2023-06-26T13:06:00-07:00'
    subject: 'Re: Pinecone connector sandbox — signature mismatch'
    to: integrations@pinecone-test.com
  - body: 'Greg —


      Scaffold is not going to provide examples by email. Scaffold’s position remains
      that the disputed items are outside the confidentiality scope as drafted. All
      rights are preserved.


      If Acme wants to discuss examples, we should do that live.


      Morgan Chen · Scaffold'
    cc:
    - sarah@atlas-test.com
    id: sent_1785127166331
    sent_at: '2023-06-27T09:07:00-07:00'
    subject: 'Re: NDA scope'
    to: greg@acme-test.com
  - body: 'Hi Pinecone team —


      Scaffold will keep the next test on the current header-only path using `X-Scaffold-Workspace`
      and `X-Scaffold-Signature`.


      Please do not add a query-parameter fallback. We’ll inspect the casing issue
      on our side.


      Morgan Chen · Scaffold'
    cc:
    - sarah@atlas-test.com
    id: sent_1785127681866
    sent_at: '2023-06-30T10:18:00-07:00'
    subject: 'Re: Pinecone connector rerun — header casing'
    to: integrations@pinecone-test.com
  - body: 'Thanks for rerunning. Please keep the integration on the agreed header-only
      path: `X-Scaffold-Workspace` plus `X-Scaffold-Signature`, with no query-parameter
      fallback.


      Please preserve and share the header-casing behavior you’re seeing while you
      trace where the normalization is happening.


      Morgan Chen · Scaffold'
    cc:
    - sarah@atlas-test.com
    id: sent_1785173820101
    sent_at: '2023-07-03T08:32:00-07:00'
    subject: 'Re: Pinecone connector sandbox rerun — header casing'
    to: integrations@pinecone-test.com
  - body: 'Greg — Scaffold is not sending examples by email. The disputed items are
      outside the confidentiality scope as drafted, and all other rights are preserved.
      If Acme wants to discuss examples, we should do that live.


      Morgan Chen · Scaffold'
    cc:
    - sarah@atlas-test.com
    id: sent_1785173821541
    sent_at: '2023-07-05T10:46:00-07:00'
    subject: 'Re: NDA scope question on Mercury materials'
    to: greg@acme-test.com
  - body: 'We found the source of the reject on our side and patched the verifier.


      The fix canonicalizes preserved `X-Scaffold-Signature` and lowercased `x-scaffold-signature`
      against the same request body and workspace. We''d like to keep the existing
      header-only contract in place and not add a query-parameter fallback.


      Please rerun the same sandbox connector test using the agreed headers:

      - `X-Scaffold-Workspace`

      - `X-Scaffold-Signature`


      If you can, test both signature-header casing variants against the same body/workspace
      and let us know what you see.


      Morgan Chen · Scaffold'
    cc:
    - sarah@atlas-test.com
    id: sent_1785178393325
    sent_at: '2023-07-17T11:29:00-07:00'
    subject: 'Re: Pinecone connector sandbox header check'
    to: integrations@pinecone-test.com
  - body: 'Thanks — this confirms the connector can proceed on the agreed header-only
      contract.


      We''ll keep the Pinecone connector on `X-Scaffold-Workspace` + `X-Scaffold-Signature`,
      with no query-parameter fallback.


      Morgan Chen · Scaffold'
    cc:
    - sarah@atlas-test.com
    id: sent_1785178394298
    sent_at: '2023-07-18T14:27:00-07:00'
    subject: 'Re: Pinecone connector sandbox header check'
    to: integrations@pinecone-test.com
  - body: 'Greg,


      Scaffold isn’t sending fresh Mercury materials while the NDA scope issue remains
      unresolved.


      Morgan Chen · Scaffold'
    cc:
    - sarah@atlas-test.com
    id: sent_1785189092890
    sent_at: '2023-08-02T11:31:00-07:00'
    subject: 'Re: Mercury first-wave materials'
    to: greg@acme-test.com
  - body: 'Hi Evergreen team,


      Mercury access is live for your wave-1 design-partner account. The invite batch
      has been sent, and you should be able to use the current product path for sessions,
      magic links, org invites, the activation surface, and preview-only sample data.


      We are keeping this wave intentionally bounded to the current Mercury build
      so we can learn cleanly from the core path. If questions come up around SSO,
      deeper admin/security controls, or other later-scope needs, please send them
      through and we’ll capture them as feedback rather than treating them as commitments
      in this wave.


      Morgan Chen · Scaffold'
    cc:
    - sarah@atlas-test.com
    id: sent_1785192082205
    sent_at: '2023-08-10T09:43:00-07:00'
    subject: Mercury access is live
    to: Evergreen Bank design-partner thread
  - body: 'Sarah —


      Forwardable blurb:


      Evergreen’s current Mercury test flow this week is the bounded preview wave:
      invited teammates can use org invites to access the workspace, orient with preview
      data, and connect a real source where appropriate. Magic links are the current
      login path, so teammates should expect to sign in through a fresh magic-link
      email. Please treat this as the current test flow only, not a statement about
      longer-term admin or security setup. Questions should come through Sarah so
      she can route them back to the right Scaffold team.


      Morgan Chen · Scaffold'
    cc: []
    id: sent_1785265435490
    sent_at: '2023-08-15T08:56:00-07:00'
    subject: Forwardable wording for Evergreen admin questions
    to: Sarah Kim
  - body: 'Anna —


      Decision for this cut: sample-preview-only sessions still do not count as activation,
      and the Mercury activation metric definition stays unchanged.


      The Evergreen confusion signal is real enough that Priya should tighten onboarding
      copy around connecting a real source if the change is low risk and stays copy-only.


      Keep the first-three-business-days numbers internal directional operating evidence
      only; they are not for board, customer, investor, or external proof framing.


      Morgan'
    cc:
    - Priya
    id: sent_1785265435967
    sent_at: '2023-08-16T09:29:00-07:00'
    subject: Evergreen activation definition decision
    to: Anna Martinez
  - body: 'Devon, Jake, Leo, Sarah —


      Evergreen’s readout is useful operating input, but Mercury v0.2 scope stays
      unchanged: do not wedge SSO, deeper admin/security work, procurement packaging,
      or bespoke Evergreen scope into the current launch scope.


      Jake and Leo, please sort the asks against the current Mercury launch-readiness
      tracker by Monday (Aug 21): identify anything that is a current launch blocker
      for wave-1 use now, and otherwise label the item clearly as follow-up outside
      current scope.


      This feedback is internal operating evidence only; do not use it as external
      proof language, and do not turn it into a custom roadmap promise.


      Morgan'
    cc:
    - Jake
    - Leo Park
    - Sarah Kim
    id: sent_1785265436470
    sent_at: '2023-08-18T16:46:00-07:00'
    subject: Evergreen readout triage — Mercury v0.2 scope
    to: Devon Hayes
  - body: 'Sarah —


      Use this version for Evergreen:


      ---

      Hi all,


      Thanks again for the readout today. For now, please keep using the current Mercury
      test flow with magic links, org invites, and the bounded preview experience.
      Please send questions through Sarah so she can route them to the right Scaffold
      team.


      We’ve captured the questions around SSO, admin history, role separation, and
      procurement materials for follow-up, but we are not attaching dates or commitments
      from this test readout. The goal for this round is to keep testing the flow
      that is live now and make sure follow-up questions are routed cleanly.


      Thanks,

      Sarah

      ---


      Morgan Chen · Scaffold'
    cc: []
    id: sent_1785265436965
    sent_at: '2023-08-18T16:46:00-07:00'
    subject: Tightened Evergreen follow-up wording
    to: Sarah Kim
  - body: 'Devon, Jake, Leo — confirming the call from the Evergreen readout:


      - Evergreen is technically clean enough to keep going.

      - Mercury v0.2 launch blockers and scope stay unchanged; normal support follow-up
      remains in the existing launch ledger.

      - SSO is not getting wedged into v0.2.


      The enterprise-readiness items from Evergreen — SSO timing/packaging, admin-change
      audit history, admin vs. billing-owner separation, and a self-serve procurement
      packet — are next-phase follow-up, not launch blockers or custom roadmap promises.


      Morgan'
    cc: []
    id: sent_1785271734772
    sent_at: '2023-08-21T08:32:00-07:00'
    subject: Evergreen readout — current wave and next-phase gaps
    to: Devon Hayes, Jake, Leo Park
  - body: 'Hi HR,


      Please confirm Tava Kitchen lunch for 31 attendees at the stated counts: 22
      standard, 5 vegetarian, 2 vegan, and 2 gluten-free.


      HR should remain the budget owner. Please decline the optional dinner add-on
      for now.


      Thanks,

      Morgan'
    cc:
    - sarah@atlas-test.com
    id: sent_1785271736246
    sent_at: '2023-08-21T11:19:00-07:00'
    subject: 'Re: Retreat catering hold — Tava Kitchen lunch confirmation needed by
      3 p.m.'
    to: HR
  - body: 'Kara — please don’t move this into final design as written.


      Keep the Mercury page to design-partner language only. Please remove the enterprise-proof
      claims, including “enterprise-ready login,” “admin controls for procurement,”
      and “early bank validation,” and do not include SSO, admin, audit, or procurement
      promises.


      Nothing should be published or treated as final until Scaffold has done a final
      review.


      Morgan Chen · Scaffold'
    cc:
    - sarah@atlas-test.com
    id: sent_1785271736727
    sent_at: '2023-08-21T11:42:00-07:00'
    subject: 'Re: Mercury landing page copy block'
    to: kara@kestrel-test.com
  - body: 'Anna — use these rows only as an internal onboarding signal for now.


      Leave the activation definition unchanged; preview-only cases should not change
      how we count activation. Please do not turn this into a board or external chart.


      Watch whether the current preview-state copy clarification reduces preview-only
      confusion before proposing anything larger.


      Morgan'
    cc:
    - Priya
    id: sent_1785271737207
    sent_at: '2023-08-22T09:31:00-07:00'
    subject: 'Re: Evergreen week-1 rows / preview-only question'
    to: Anna Martinez
  - body: 'Hi Blueline,


      Please confirm the Friday, Aug. 25, 8–10 a.m. repair window. We’ll decline the
      Wednesday 4–6 p.m. option.


      Morgan Chen · Scaffold'
    cc:
    - sarah@atlas-test.com
    id: sent_1785271737723
    sent_at: '2023-08-22T10:18:00-07:00'
    subject: 'Re: Repair window'
    to: ops@bluelinehq.com
  - body: 'Sarah — we can do a 25-minute operating/product discussion.


      I don’t want to turn this into a 45-minute company-readiness or fundraising
      deck review. Devon can join if you want more product context in the room, but
      I’d keep the format product-forward and not deck-heavy.


      Morgan Chen · Scaffold'
    cc:
    - sarah@atlas-test.com
    id: sent_1785271738692
    sent_at: '2023-08-22T11:24:00-07:00'
    subject: 'Re: September offsite agenda'
    to: sarah-ff@foundersfund-test.com
  - body: 'Greg — Evergreen doesn’t change Acme’s current Mercury scope.


      Scaffold is not sharing customer-specific information or fresh Mercury materials
      from that work, and there isn’t an SSO date I can promise. Please keep current
      Mercury questions in the existing account channel for now.


      Morgan Chen · Scaffold'
    cc:
    - sarah@atlas-test.com
    id: sent_1785271739175
    sent_at: '2023-08-23T09:05:00-07:00'
    subject: 'Re: Mercury / Evergreen question'
    to: greg@acme-test.com
  - body: 'Rishi — please forward this paragraph: “For the Atlas connector docs, keep
      the contract scoped to the required request headers: `X-Scaffold-Workspace`
      and `X-Scaffold-Signature`. Scaffold’s July verifier fix addressed signature-header
      casing only; preserved `X-Scaffold-Signature` and lowercased `x-scaffold-signature`
      both verify correctly, so that can be noted in troubleshooting. Please do not
      describe this as automatic normalization of all connector headers or imply broader
      connector-header normalization.”


      Morgan'
    cc: []
    id: sent_1785271740170
    sent_at: '2023-08-24T10:28:00-07:00'
    subject: 'Re: Pinecone docs wording q'
    to: Rishi Patel
  - body: 'Kara — yes, this direction is much closer and is safe to move into design
      comps with one required change.


      Please replace “Validated by enterprise teams in live workflows” with neutral
      design-partner wording. The page should stay unpublished until Scaffold’s final
      review.


      Morgan Chen · Scaffold'
    cc:
    - sarah@atlas-test.com
    id: sent_1785271740673
    sent_at: '2023-08-24T13:41:00-07:00'
    subject: 'Re: Mercury landing page copy'
    to: kara@kestrel-test.com
  - body: 'Hi Sarah,


      Q3 product/operating discussion works as the segment title.


      For attendees, plan on me, with Devon optional if you want product context.
      Let’s keep it to a 25-minute slot. No data-room appendix, and if slides are
      needed they should be lightweight product context only.


      Boundary-wise, this is not a fundraising deck, company-readiness review, or
      B-round restart.


      Morgan Chen · Scaffold'
    cc:
    - Sarah Kim
    id: sent_1785274728561
    sent_at: '2023-08-28T10:12:00-07:00'
    subject: Q3 product/operating discussion
    to: Sarah at Founders Fund
  - body: 'Hi Blueline,


      Thanks for sending the estimate. We’re going to decline the optional valve replacement
      for now. Please send the final receipt for the completed leak repair only.


      Morgan Chen · Scaffold'
    cc:
    - Sarah Kim
    id: sent_1785274729041
    sent_at: '2023-08-28T14:18:00-07:00'
    subject: 'Re: Leak repair'
    to: Blueline Plumbing
  - body: 'Hi HR,


      Confirming the Tava Kitchen lunch counts exactly as listed:

      - Total attendees: 33

      - Standard meals: 23

      - Vegetarian: 5

      - Vegan: 3

      - Gluten-free: 2


      Please keep HR as the budget owner. We’ll decline the afternoon snack service
      and any dinner/snack add-ons unless HR provides a separate approved budget path.


      Thanks,

      Morgan'
    cc:
    - sarah@atlas-test.com
    id: sent_1785274730492
    sent_at: '2023-08-29T09:29:00-07:00'
    subject: 'Re: Retreat catering count lock — due today'
    to: HR
  - body: 'Hi Kara,


      Thanks for cleaning this up and removing the enterprise-proof and SSO/admin
      claims. This wording is approved for design layout only.


      Please keep the page unpublished until Scaffold gives final publish approval.


      Morgan Chen · Scaffold'
    cc:
    - sarah@atlas-test.com
    id: sent_1785274730976
    sent_at: '2023-08-29T11:18:00-07:00'
    subject: 'Re: Mercury landing page copy'
    to: kara@kestrel-test.com
  - body: 'Sarah —


      Here’s a forwardable blurb for Evergreen:


      ---

      For budgeting purposes, Mercury is modeled around actual monthly active developer
      usage. Pilot is $2,500/month for up to 50 monthly active developers; Growth
      is $7,500/month for up to 200 monthly active developers; overage is $1,000 per
      additional 50 monthly active developers. SSO, audit logs, and advanced admin
      controls are not quoted or dated until those features ship.


      This is budgetary guidance only, not a custom roadmap, procurement packet, or
      full commercial commitment.

      ---


      Morgan'
    cc: []
    id: sent_1785274731953
    sent_at: '2023-08-30T10:44:00-07:00'
    subject: Evergreen budgetary Mercury wording
    to: Sarah Kim
  - body: 'Hi Sarah,


      For the printed agenda:


      1. Segment title: Q3 product/operating discussion

      2. Moderator topics: Mercury design-partner learnings and operating metrics

      3. Devon: keep optional for product context

      4. Materials: We are not sending a data-room appendix or fundraising materials.
      If you need slides, they will only be lightweight product context.


      Thanks,

      Morgan Chen · Scaffold'
    cc:
    - sarah@atlas-test.com
    id: sent_1785275708758
    sent_at: '2023-09-05T09:31:00-07:00'
    subject: 'Re: September offsite — quick logistics for your segment'
    to: sarah-ff@foundersfund-test.com
  - body: 'Hi Kara,


      Thanks for sending this over. Kestrel can move it into unpublished staging for
      final review only after removing both added layout elements:

      - the “enterprise-grade evaluation” pill

      - the design-partner logo placeholder/strip


      This is not approval for public publishing. Please keep the proof to the approved
      copy only, with no added roadmap detail or proof-claim language.


      Thanks,

      Morgan Chen · Scaffold'
    cc:
    - sarah@atlas-test.com
    id: sent_1785275709266
    sent_at: '2023-09-05T14:49:00-07:00'
    subject: 'Re: Mercury landing page — final layout proof'
    to: kara@kestrel-test.com
  - body: 'Hi HR,


      For the retreat lunch day-of details: Sarah Kim should be the on-site delivery
      contact for Tava Kitchen.


      Please keep the Tava Kitchen delivery window at 11:45 a.m.–12:15 p.m. and keep
      the locked counts unchanged at 33 total:

      - 23 standard

      - 5 vegetarian

      - 3 vegan

      - 2 gluten-free


      Use plain dietary labels only. Please decline printed menus and any extra add-on.


      Thanks,

      Morgan'
    cc:
    - sarah@atlas-test.com
    id: sent_1785275710253
    sent_at: '2023-09-05T15:22:00-07:00'
    subject: Retreat lunch day-of details
    to: HR
  - body: 'Devon, Anna —


      I saved the internal prep doc titled “September Mercury metrics package — board
      and H2 prep bounds.”


      It keeps the two-layer split: board-operating alignment and selective H2 prep
      can use the sturdier cohort view because real-source/live-sync activation is
      cleaner than May, admin friction is down for the design-partner cohort, and
      Evergreen adds enterprise substance.


      It also states the bounds plainly: expansion is still uneven, weekly activation
      movement is internal-only, and this package does not prove retention, solve
      expansion, or make the story external-ready.


      Morgan'
    cc: []
    id: sent_1785275711253
    sent_at: '2023-09-06T10:47:00-07:00'
    subject: September Mercury metrics package — board and H2 prep bounds
    to: Devon Hayes, Anna Martinez
  - body: 'Devon —


      INV-F-0314 can be released after manual review for the reviewed August design
      implementation support only. This is not approval for any new Foundry scope.


      Morgan'
    cc: []
    id: sent_1785275711773
    sent_at: '2023-09-06T11:54:00-07:00'
    subject: 'Re: Foundry INV-F-0314 manual review'
    to: devon@atlas-test.com
  - body: 'Devon —


      The platform bands are fine as budgetary guidance, but I would not let Sarah
      use the enterprise-package line externally.


      Suggested redline for the text Sarah can use:


      “For Evergreen’s initial Mercury rollout, current budgetary pricing guidance
      is:


      Pilot — $2,500/month platform minimum, including up to 50 monthly active developers.

      Growth — $7,500/month platform minimum, including up to 200 monthly active developers.

      Overage — $1,000/month for each additional 50 monthly active developers.


      These are preliminary budgetary bands for the current Mercury rollout and can
      be tightened once scope and usage are clearer.”


      Delete / hold back:

      - “Enterprise SSO/audit/admin package TBD for procurement.”

      - “budgeting and procurement planning” framing.


      Please keep it budgetary and non-custom: no procurement-packet tone, no Evergreen-specific
      exceptions, and no reopening the monthly-active-developer counting rule.


      Morgan'
    cc: []
    id: sent_1785275712258
    sent_at: '2023-09-07T09:36:00-07:00'
    subject: 'Re: Evergreen budgetary quote draft'
    to: devon@atlas-test.com
  - body: 'Rishi —


      I would not approve Pinecone’s sentence as written. The narrower edit you can
      send back is:


      “Troubleshooting signature verification


      If requests are failing verification after passing through a proxy or connector
      layer, use the header-only contract below. Scaffold accepts the signature header
      in either preserved `X-Scaffold-Signature` casing or lowercased `x-scaffold-signature`
      casing.


      Required headers

      - `X-Scaffold-Workspace`

      - `X-Scaffold-Signature`”


      Please remove the broader claim that Scaffold normalizes connector headers automatically,
      and do not say alternate signature locations are accepted.


      Morgan'
    cc: []
    id: sent_1785275712748
    sent_at: '2023-09-07T11:24:00-07:00'
    subject: 'Re: Pinecone troubleshooting wording'
    to: Rishi Patel
  - body: 'Hi Sarah —


      Thanks for pulling this together. Please use “Q3 product/operating discussion”
      as the segment title.


      For the prep note, I’ll keep it focused on:

      - Mercury design-partner learnings from the current live workflow evaluation

      - operating metrics around setup, activation, and first live sync

      - where the operating metrics are improving versus still noisy


      Devon can stay optional unless you want product context live.


      There won’t be a data-room appendix, fundraising deck, or B-round restart framing.
      No pre-read beyond the one-pager; if anything beyond that is useful, it should
      stay to lightweight product context only.


      Morgan Chen · Scaffold'
    cc:
    - sarah@atlas-test.com
    id: sent_1785276670665
    sent_at: '2023-09-11T08:49:00-07:00'
    subject: 'Re: Founders Fund offsite — Thursday segment'
    to: sarah-ff@foundersfund-test.com
  - body: 'Hi Kara —


      The visible page copy can keep moving through review.


      Before final review, please remove the Evergreen/bank/enterprise-validation
      language from all page-level/non-body text: the page title, meta description,
      and footer image alt text. Those should not reference Evergreen, a bank design
      partner, or enterprise-grade validation.


      Also to be explicit: this is still not approved for public publishing.


      Morgan Chen · Scaffold'
    cc:
    - sarah@atlas-test.com
    id: sent_1785276671184
    sent_at: '2023-09-11T10:24:00-07:00'
    subject: 'Re: Mercury landing page staging proof'
    to: kara@kestrel-test.com
  - body: 'Thanks for the clear request. Understood that Evergreen needs a procurement/security
      packet that can be reviewed asynchronously before widening internal routing.


      Sarah will coordinate follow-up from our side, and we’ll come back quickly with
      current-scope materials.


      Morgan Chen · Scaffold'
    cc:
    - sarah@atlas-test.com
    id: sent_1785276672203
    sent_at: '2023-09-12T09:39:00-07:00'
    subject: 'Re: Mercury packet request before wider internal routing'
    to: Evergreen Bank security/procurement review team
  - body: 'Thanks — below is the final procurement-ready packet for asynchronous review.
      Devon Hayes is the commercial/procurement owner for the packet, and Sarah Kim
      is copied here for coordination.


      Mercury / Evergreen procurement packet

      Final — September 13, 2023

      Commercial/procurement owner: Devon Hayes


      1. Purpose

      This packet gives Evergreen Bank a concise procurement/security review summary
      for the current Mercury design-partner deployment. It covers the commercial
      model, present login/setup scope, current admin/security posture for the bounded
      launch experience, and known enterprise-readiness gaps that remain outside launch
      scope. It is written for asynchronous procurement/security review before wider
      internal routing.


      2. Commercial model

      Mercury uses a hybrid pricing model based on monthly active developer usage,
      not purchased seats and not directory size.


      Current bands:

      - Pilot: $2,500/month platform minimum, including up to 50 monthly active developers.

      - Growth: $7,500/month platform minimum, including up to 200 monthly active
      developers.

      - Overage: $1,000 per additional 50 monthly active developers.


      Counting notes:

      - Monthly active developer usage is the pricing driver.

      - Scaffold internal/test users do not count toward usage.

      - Preview/sample-only behavior is separate from activation reporting and should
      not be treated as usage proof by itself.


      Enterprise add-ons:

      SSO, audit history for admin changes, and deeper admin controls are not included
      in the current launch scope. They are roadmap-dependent add-ons and would be
      quoted separately only after they ship.


      3. Current Mercury scope

      The current Mercury design-partner scope is the live bounded experience now
      in use:

      - Clerk-backed sessions.

      - Magic-link sign-in.

      - Organization invites.

      - Setup flow oriented around connecting a real source.

      - Preview/sample data available only as preview behavior and not activating
      by itself.

      - First live sync path in product.


      Current activation definition for operating review:

      - real_source_connected within 7 days; or

      - first_live_sync_completed within 7 days.


      Preview/sample-only behavior does not activate an account and should not be
      described as equivalent to real source connection or live sync completion.


      Not in current launch scope:

      - SSO.

      - Audit history for admin changes.

      - Deeper admin controls beyond the current bounded experience.

      - Expanded enterprise/security packaging beyond the current design-partner flow.


      4. Current login / setup experience

      For the present Mercury flow, user access is handled through magic links and
      organization invites. Session handling is Clerk-backed. The intended path is:

      1. Invited user enters through the magic-link / invite flow.

      2. User lands in the Mercury workspace context.

      3. User connects a real source.

      4. User reaches first live sync.


      Preview/sample behavior may be shown during evaluation, but preview/sample-only
      behavior does not activate the account.


      5. Current admin / security readiness for present scope

      Current readiness should be read as sufficient for the bounded design-partner
      experience, not as a full enterprise admin/security package.


      What we can say today:

      - Access is handled through the current magic-link and invite flow.

      - Organization-level invitation exists in the current Mercury experience.

      - The launch experience is bounded and intentionally narrower than a full enterprise
      rollout.

      - Current product facts should be reviewed against the present scope, not against
      a broader enterprise-control checklist.


      What this packet does not imply:

      - Mercury already includes full enterprise-ready login controls.

      - Current admin behavior covers all enterprise audit/control requirements.

      - Later-scope items are part of the live launch package today.

      - Evergreen has a bespoke roadmap path or custom roadmap commitment.


      6. Known enterprise-readiness gaps

      Open follow-up items surfaced in Evergreen discussions and internal review:

      - SSO timing.

      - Audit history for admin changes.

      - Clearer separation between admin permissions and billing-owner controls.

      - Stronger procurement/self-serve explanation materials that can stand on their
      own without Morgan or Devon live-explaining them.


      These are enterprise-readiness follow-up items. They are not part of Mercury
      v0.2 launch scope, and they should be treated as roadmap-dependent add-ons to
      be quoted only after they ship.


      Morgan Chen · Co-Founder & CEO, Scaffold'
    cc:
    - sarah@atlas-test.com
    id: sent_1785276673896
    sent_at: '2023-09-13T10:18:00-07:00'
    subject: 'Re: Mercury packet request before wider internal routing'
    to: Evergreen Bank security/procurement review team
  - body: 'Rishi —


      You can approve the header-only casing language only if Pinecone removes the
      alternate-signature-location / future-normalization sentence.


      The approved troubleshooting paragraph should be just the casing point, e.g.:


      “Scaffold accepts preserved X-Scaffold-Signature and lowercased x-scaffold-signature
      headers against the same request body and workspace.”


      They should not describe Scaffold as normalizing all connector headers or supporting
      alternate signature locations. The contract stays X-Scaffold-Workspace plus
      X-Scaffold-Signature only.


      Morgan'
    cc: []
    id: sent_1785276674641
    sent_at: '2023-09-13T16:33:00-07:00'
    subject: 'Re: Pinecone troubleshooting paragraph - last pass?'
    to: rishi@atlas-test.com
  - body: 'Hi Greg —


      Evergreen’s procurement packet doesn’t change Acme’s current Mercury scope.
      Under the current scope boundary, we’re not sharing customer-specific or new
      Mercury procurement materials with Acme, so I’m not sending the packet, screenshots,
      admin-control wording, or a light version.


      There isn’t an SSO date to promise. Please keep using your existing account
      channel for current questions.


      Morgan Chen · Scaffold'
    cc:
    - sarah@atlas-test.com
    id: sent_1785276675156
    sent_at: '2023-09-14T09:26:00-07:00'
    subject: 'Re: Mercury scope follow-up'
    to: greg@acme-test.com
  - body: 'Hi Blueline,


      Thanks for sending the final repair receipt. We are declining the optional valve-replacement
      work again and are not scheduling anything further for now.


      Morgan Chen · Scaffold'
    cc:
    - sarah@atlas-test.com
    id: sent_1785277490257
    sent_at: '2023-09-18T09:17:00-07:00'
    subject: 'Re: Blueline repair receipt'
    to: ops@bluelinehq.com
  - body: 'Hi Kara,


      Thanks for the updated staging proof. The only approval I’m giving now is for
      Sarah Kim to do Scaffold’s internal final review next. Please do not publish
      the page publicly, including on Thursday; public publish approval is withheld
      until we explicitly give it after final review.


      Morgan Chen · Scaffold'
    cc:
    - sarah@atlas-test.com
    id: sent_1785277491418
    sent_at: '2023-09-18T10:41:00-07:00'
    subject: 'Re: Mercury staging proof'
    to: kara@kestrel-test.com
  - body: 'Hi HR,


      The confirmed lunch counts are approved as locked: 33 total — 23 standard, 5
      vegetarian, 3 vegan, and 2 gluten-free.


      Please do not pay the unapproved $420 snack add-on under this approval. Unless
      it has a separate budget path, please have Tava remove that line or separately
      justify it before payment.


      Morgan'
    cc:
    - sarah@atlas-test.com
    id: sent_1785277491980
    sent_at: '2023-09-19T09:22:00-07:00'
    subject: Tava Kitchen invoice — lunch counts only
    to: HR
  - body: 'Hi Sarah,


      Thank you for the discussion. I’d like to keep the follow-up product/operating
      for now, so I’m not sending a Mercury metrics package or data-room appendix,
      and I don’t want to pencil a financing-readiness process or October check-in
      at this point.


      I’ll come back when there’s a real company update to share.


      Morgan Chen · Scaffold'
    cc:
    - sarah@atlas-test.com
    id: sent_1785277495438
    sent_at: '2023-09-21T10:08:00-07:00'
    subject: 'Re: Q3 product/operating discussion'
    to: sarah-ff@foundersfund-test.com
  - body: 'Hi Kara,


      Sarah finished Scaffold’s internal final review and the unpublished Mercury
      page is clean for the Mercury section only.


      You’re approved to publish that Mercury section with the bounded design-partner
      wording.


      Guardrails:

      - No Evergreen names or logos.

      - No enterprise-validation claims.

      - No SSO, audit, admin-control, or procurement promises.

      - No roadmap claims without another Scaffold review.


      Thanks,

      Morgan Chen · Co-Founder & CEO, Scaffold'
    cc:
    - sarah@atlas-test.com
    id: sent_1785278547953
    sent_at: '2023-09-25T10:26:00-07:00'
    subject: Mercury page publishing approval — bounded section only
    to: kara@kestrel-test.com
  - body: 'Sarah, Devon —


      Forwardable FAQ draft:


      Evergreen Mercury FAQ


      1) Invite/testing scope

      - The current Evergreen Mercury test remains bounded testing / preview use,
      not a broader rollout.

      - The current Evergreen admin can invite additional testers under the existing
      Mercury test.

      - As they add people, keep the experience within the current bounded test scope
      and route questions through the existing coordination thread.


      2) Login flow

      - The current login path is magic link.

      - Org invites are part of the current setup flow.

      - If someone uses an expired link, they should request a fresh magic link and
      retry; if the retry still fails, route it back through the coordination thread.


      3) Pricing interpretation

      - Pilot and Growth are current budgetary guidance, not a custom quote.

      - Those bands are based on active usage / monthly active developer usage, not
      purchased seats or directory size.


      4) Current scope and enterprise-readiness gaps

      - SSO is not in the current launch/test scope.

      - Audit history for admin changes is not in the current launch/test scope.

      - Separate admin permissions vs. billing-owner controls remain later-scope.

      - That gap does not block adding invited testers under the current bounded test.

      - No dates or bespoke commitments are being made for these enterprise-readiness
      items.


      5) Procurement/commercial owner

      - Devon Hayes is the named commercial/procurement owner for follow-up.

      - Sarah Kim can keep the coordination thread moving so product Q&A and paperwork
      do not blur.'
    cc: []
    id: sent_1785278548433
    sent_at: '2023-09-25T15:07:00-07:00'
    subject: Evergreen forwardable FAQ draft
    to: Sarah Kim; Devon Hayes
  - body: 'Hi HR,


      Approved to release the revised Tava Kitchen retreat invoice on the lunch-only
      scope now that the unapproved snack add-on has been removed.


      This approval does not cover snacks, dinner, printed menus, or any other extras
      under that invoice.


      Thanks,

      Morgan'
    cc:
    - sarah@atlas-test.com
    id: sent_1785278548906
    sent_at: '2023-09-25T16:18:00-07:00'
    subject: Revised Tava Kitchen invoice approval — lunch only
    to: HR
  - body: 'Rishi,


      You can approve the paragraph only if the final version stays exactly this narrow:


      “Scaffold accepts preserved and lowercased X-Scaffold-Signature headers against
      the same request body and workspace. Signature verification still uses the documented
      header-only contract.”


      That approval is limited to signature-header casing for preserved/lowercased
      X-Scaffold-Signature against the same request body and workspace, with the documented
      header-only contract intact. It should not imply broader connector-header normalization
      or alternate signature locations.


      Morgan'
    cc: []
    id: sent_1785278549867
    sent_at: '2023-09-26T14:56:00-07:00'
    subject: Pinecone docs paragraph — narrow approval
    to: rishi@atlas-test.com
  - body: '- Selective October reopen / prep is the frame; no September restart, broad
      process, or “process is on.”

      - Elena goes first as warm context for calibration on the real Mercury story,
      not process signaling.

      - Devon keeps trimming a short list to firms that can underwrite uneven expansion
      and scoped enterprise gaps.

      - Package can use September Mercury metrics, Evergreen signal, and hybrid pricing,
      but with caveats intact.

      - Random investor coffees stay out; no outreach beyond Elena until the package
      is ready.'
    cc: []
    id: sent_1785278551461
    sent_at: '2023-09-28T17:49:00-07:00'
    subject: Recap — selective October reopen
    to: devon@atlas-test.com
  - body: 'Hi Sarah,


      Thanks for the offer, but I’m going to pass on the September financing-readiness
      coffee and the data-room appendix.


      Scaffold is not running a process now. I’ll come back with a real company update
      when the October package is ready.


      Best,

      Morgan Chen · Co-Founder & CEO, Scaffold'
    cc:
    - sarah@atlas-test.com
    id: sent_1785278552028
    sent_at: '2023-09-28T18:08:00-07:00'
    subject: 'Re: investor coffee / appendix'
    to: Sarah at Founders Fund
  - body: 'Devon —


      I’d redline the draft this way:


      Original:

      “We are reopening the B-round in October with Elena and a short list. Mercury
      metrics, Evergreen procurement, and hybrid pricing give us the proof points
      for a stronger process.”


      Safer version:

      “We are doing selective October prep for a potential B-round reopen, starting
      with Elena as a warm-context calibration conversation and a still-narrowing
      short list. The package is not ready yet; this is not a September restart or
      a broad process. September Mercury metrics, Evergreen’s procurement signal,
      and hybrid pricing can inform the package, but they should be framed with the
      uneven-expansion and enterprise-readiness caveats intact—not as proof that expansion
      is solved or that Evergreen procurement proves enterprise readiness.”


      Morgan'
    cc: []
    id: sent_1785278552515
    sent_at: '2023-09-29T08:44:00-07:00'
    subject: Safer board-note paragraph
    to: devon@atlas-test.com
  - body: 'Kara —


      No on the Evergreen name, logo, sidebar stat/metric, or any “enterprise validation”
      line, including the version without the logo.


      Please keep the page inside the approved external boundary. The safer direction
      is generic: regulated design-partner feedback is informing Mercury hardening.


      Morgan Chen · Scaffold'
    cc:
    - sarah@atlas-test.com
    id: sent_1785280873041
    sent_at: '2023-10-02T09:18:00-07:00'
    subject: 'Re: Mercury landing page section'
    to: kara@kestrel-test.com
  - body: 'Elena —


      We took another pass at the Mercury package and would like to use a short conversation
      for calibration, not to launch a broad process.


      The current story is stronger than the February version in three areas:

      - The September Mercury package shows activation and admin friction improving
      in the design-partner wave, while still treating expansion as uneven.

      - Pricing is now structured around the hybrid model: Pilot at $2,500/month including
      up to 50 monthly active developers, Growth at $7,500/month including up to 200
      monthly active developers, and $1,000 per additional 50 monthly active developers.

      - Evergreen gave us a real regulated-buyer procurement/security signal, which
      clarified enterprise-readiness gaps around security/admin expectations and procurement
      handling.


      The caveats are the point of the calibration: expansion is still uneven; Evergreen
      procurement is one strong signal, not proof that enterprise readiness is solved
      or repeatable; and we are not using this to add one-off investor coffees or
      launch a broad process. Enterprise add-ons like SSO, audit logs, and advanced
      admin controls remain separately quoted only after they ship.


      The questions I’d like to pressure-test are whether this is materially more
      credible than February, what would make the Evergreen signal repeatable rather
      than anecdotal, whether the pricing frame reads disciplined enough, and how
      much more explanation we need on uneven expansion before widening beyond a short
      list.


      Morgan Chen · Co-Founder & CEO, Scaffold'
    cc:
    - sarah@atlas-test.com
    id: sent_1785280873939
    sent_at: '2023-10-03T08:18:00-07:00'
    subject: Mercury / October calibration pre-read
    to: Elena Volkov
  - body: 'Elena —


      Thank you again for the calibration today. Your read was helpful, especially
      the push on whether Evergreen can become repeatable rather than anecdotal and
      the warning not to widen beyond a short list until we can explain uneven expansion
      without hand-waving.


      We’ll keep this as narrow October prep and use the feedback to tighten the package
      before any next step.


      Morgan Chen · Scaffold'
    cc:
    - sarah@atlas-test.com
    id: sent_1785280876532
    sent_at: '2023-10-04T14:16:00-07:00'
    subject: 'Re: Mercury / October calibration'
    to: Elena Volkov
  - body: 'Greg —


      Thanks for flagging this. We’re looking at the API v2 export timeout issue,
      and Jake’s current patch ETA is 3 p.m. PT today.


      I’ll keep this focused on the export bug and will follow up once the fix is
      live.


      Morgan Chen · Scaffold'
    cc:
    - sarah@atlas-test.com
    id: sent_1785280877392
    sent_at: '2023-10-05T09:38:00-07:00'
    subject: 'Re: API v2 export timeout'
    to: Greg Shipman
  - body: 'Kara —


      This is in the safer direction. Please remove “validated” anywhere it appears,
      including the optional alt.


      Evergreen should stay unnamed, and Kestrel should not add any customer logo
      or customer metric. Generic design-partner-informed wording is fine as long
      as it stays inside that boundary.


      Morgan Chen · Scaffold'
    cc:
    - sarah@atlas-test.com
    id: sent_1785280878259
    sent_at: '2023-10-05T11:04:00-07:00'
    subject: 'Re: Mercury sidebar replacement'
    to: kara@kestrel-test.com
  - body: 'Greg —


      Glad the test export passed. The API v2 export timeout fix is live; please flag
      it if the timeout recurs.


      Morgan Chen · Scaffold'
    cc:
    - sarah@atlas-test.com
    id: sent_1785280879285
    sent_at: '2023-10-06T16:21:00-07:00'
    subject: 'Re: API v2 export timeout'
    to: Greg Shipman
  - body: 'Hi Sarah,


      Thanks for sending the roster and proposed agenda. Let’s keep the walkthrough
      framed as a bounded test of the current Mercury flow, not as expansion approval.


      Suggested agenda:

      1. Confirm the second admin group’s access and setup path.

      2. Walk through the current flow: magic links, org invites, preview-only sample
      data, real-source connection, and first live sync.

      3. Capture questions and follow-ups.

      4. Route commercial or budgetary questions separately with Devon.


      SSO, audit/admin controls, billing-owner separation, and procurement follow-up
      should stay positioned as next-phase enterprise-readiness items, not scope for
      this test.


      Morgan'
    cc: []
    id: sent_1785282144070
    sent_at: '2023-10-09T08:46:00-07:00'
    subject: 'Re: Evergreen second-admin-group agenda'
    to: Sarah Kim
  - body: 'Hi Blueline Billing,


      I’m disputing the $240 optional valve-inspection line on invoice BL-231011-17.
      Please remove that line and send a corrected invoice.


      The base repair charge is approved only once the corrected invoice arrives.


      Morgan Chen · Scaffold'
    cc:
    - sarah@atlas-test.com
    id: sent_1785282147486
    sent_at: '2023-10-11T09:26:00-07:00'
    subject: 'Re: final invoice for 10/9 repair visit'
    to: billing@blueline-test.com
  - body: 'Hi Sarah,


      Customer-thread draft:


      Thanks for the walkthrough notes. The second admin group can continue testing
      Mercury under the current bounded scope: magic links, org invites, preview-only
      sample data, real-source connection, and first live sync. The asks around SSO,
      admin-change audit history, and admin-versus-billing-owner separation are still
      next-phase enterprise-readiness items. They are not Mercury v0.2 commitments,
      and we should not treat them as Evergreen-specific exceptions.


      Morgan'
    cc: []
    id: sent_1785282148947
    sent_at: '2023-10-12T10:54:00-07:00'
    subject: Evergreen second admin group — customer-thread draft
    to: Sarah Kim
  - body: 'Hi HR,


      For the CEO update, I’d use three topics:


      - Bounded Mercury testing

      - Q4 hardening priorities

      - Jordan’s Honeycomb debugging example


      I’d skip an open-ended live Q&A block. I’d rather collect questions ahead of
      time and answer the ones that are useful for the whole company.


      Morgan'
    cc: []
    id: sent_1785282150396
    sent_at: '2023-10-12T13:18:00-07:00'
    subject: Quarterly all-hands CEO update topics
    to: HR
  - body: 'Hi Kara,


      Thanks for flagging the QA misses. Please remove all customer-identifying text
      from the live Mercury page across visible copy, metadata, and asset labels,
      including the Evergreen-identifying alt text and the “regulated bank” preview
      caption.


      This is cleanup of the already-approved page only. It is not a request for new
      Mercury copy or any expanded claims.


      Morgan Chen · Co-Founder & CEO, Scaffold'
    cc:
    - sarah@atlas-test.com
    id: sent_1785282151302
    sent_at: '2023-10-13T14:29:00-07:00'
    subject: Mercury page cleanup — customer-identifying text
    to: kara@kestrel-test.com
  - body: 'Kara — No, “regulated-bank design partner” needs to come out of metadata
      and previews too. Please keep the already-approved generic Mercury copy and
      treat this as cleanup of the approved page, not a new copy pass.


      Morgan Chen · Scaffold'
    cc:
    - sarah@atlas-test.com
    id: sent_1785283359125
    sent_at: '2023-10-16T09:24:00-07:00'
    subject: 'Re: Mercury page cleanup'
    to: kara@kestrel-test.com
  - body: 'Blueline team — Thanks for sending the corrected invoice with the optional
      valve-inspection line removed. The corrected $680 base repair invoice is approved
      for payment; this approval is for the base repair only.


      Morgan Chen · Scaffold'
    cc:
    - sarah@atlas-test.com
    id: sent_1785283359574
    sent_at: '2023-10-16T10:12:00-07:00'
    subject: 'Re: corrected base repair invoice'
    to: Blueline Plumbing
  - body: 'Greg — Scaffold’s position remains unchanged: we disagree that the materials
      you flagged fall within the NDA’s confidentiality scope as drafted. We are preserving
      all rights and will not send fresh Mercury packets, screenshots, docs, written
      examples, or other disputed materials while the NDA scope issue remains unresolved.


      Happy to keep the discussion live on a call tomorrow morning.


      Morgan Chen · Scaffold'
    cc:
    - sarah@atlas-test.com
    id: sent_1785283362189
    sent_at: '2023-10-18T17:05:00-07:00'
    subject: 'Re: NDA scope and Mercury materials'
    to: greg@acme-test.com
  - body: 'Greg — Thanks for the live discussion this morning. Recapping where we
      landed: Scaffold’s position remains unchanged. We disagree that the disputed
      materials fall within the NDA’s confidentiality scope as drafted, and we are
      preserving all rights.


      We are not sending examples by email, and Acme will not receive fresh Mercury
      packets, screenshots, docs, or other disputed materials while the NDA scope
      issue remains unresolved. We can keep the discussion live rather than trading
      examples over email.


      Morgan Chen · Scaffold'
    cc:
    - sarah@atlas-test.com
    id: sent_1785283363097
    sent_at: '2023-10-19T10:48:00-07:00'
    subject: 'Re: NDA scope and Mercury materials'
    to: greg@acme-test.com
  - body: 'Greg,


      Thanks for laying out what would help on your side. While the NDA scope issue
      is still unresolved, we can’t send written Mercury examples, screenshots, packet
      excerpts, one-pagers, or fresh Mercury materials by email.


      If it would help to walk through examples, let’s keep that live on a call for
      now.


      Separately, I want to be clear on the signal: Acme being excluded from fresh
      materials right now is driven by the legal-scope issue, not by lack of interest
      on our side.


      Morgan Chen · Scaffold'
    cc:
    - sarah@atlas-test.com
    id: sent_1785284615094
    sent_at: '2023-10-23T15:02:00-07:00'
    subject: 'Re: Mercury examples / NDA scope follow-up'
    to: greg@acme-test.com
  - body: 'Elena, thank you for making the connection.


      Sofia, it’s good to meet you. Devon and I would be glad to set up a first context
      call around the actual Mercury evidence: the cleaned cohort view, Evergreen
      context on current product scope versus enterprise follow-up, and pricing as
      it exists today.


      Just to frame it correctly, we’re treating this as a selective Mercury evidence
      review, not a broad fundraising process or a term-sheet conversation.


      Morgan Chen · Co-Founder & CEO, Scaffold'
    cc:
    - Elena Volkov
    - devon@atlas-test.com
    - sarah@atlas-test.com
    id: sent_1785284615522
    sent_at: '2023-10-24T09:18:00-07:00'
    subject: 'Re: Intro: Morgan Chen / Devon Hayes <> Sofia Alvarez'
    to: Sofia Alvarez
  - body: 'Sofia,


      Thanks for the time today. I appreciated how directly you engaged with the actual
      Mercury evidence and caveats.


      Devon and I will pull together the three items you asked for: the cleaned Mercury
      cohort package, the Evergreen enterprise-readiness context, and the hybrid pricing
      model. We’ll keep the caveats intact and frame this as selective diligence prep
      around the current Mercury story — not a broad process or a term-sheet conversation.


      Morgan Chen · Scaffold'
    cc:
    - devon@atlas-test.com
    - sarah@atlas-test.com
    id: sent_1785284616394
    sent_at: '2023-10-25T13:26:00-07:00'
    subject: 'Re: Intro: Morgan Chen / Devon Hayes <> Sofia Alvarez'
    to: Sofia Alvarez
  - body: 'Elena,


      Thank you again for the intro. Sofia engaged with exactly the kind of Mercury
      evidence-and-caveats conversation you flagged, and it was the right fit for
      where we are right now.


      We’ll keep the follow-up narrow and honest from here.


      Morgan Chen · Scaffold'
    cc:
    - sarah@atlas-test.com
    id: sent_1785284616844
    sent_at: '2023-10-25T13:26:00-07:00'
    subject: 'Re: Intro: Morgan Chen / Devon Hayes <> Sofia Alvarez'
    to: Elena Volkov
  - body: 'Thanks for the notes. The second admin group can keep using the current
      Mercury preview flow as-is: org invites, magic-link access, preview/sample data,
      real-source connection, and first live sync.


      For audit/change history, SSO timing, and admin/billing-role separation, we’re
      tracking those as next-phase enterprise-readiness follow-up rather than part
      of the current Mercury preview scope. We are not treating those as Mercury v0.2
      promises or Evergreen-specific exceptions.


      If useful, Sarah Kim can keep consolidating those questions on this thread and
      route follow-up internally.


      Morgan Chen · Scaffold'
    cc:
    - sarah@atlas-test.com
    id: sent_1785285806577
    sent_at: '2023-10-30T13:31:00-07:00'
    subject: 'Re: Evergreen second-admin notes'
    to: Evergreen Bank
  - body: 'Greg —


      A live discussion with the right people, including your product lead, is fine.


      While the NDA scope issue is unresolved, we can’t send written examples, screenshots,
      packet excerpts, or briefing material. Acme being held out of fresh Mercury
      materials is legal-scope driven, not a judgment about the demand signal.


      Morgan Chen · Scaffold'
    cc:
    - sarah@atlas-test.com
    id: sent_1785285807931
    sent_at: '2023-10-30T16:07:00-07:00'
    subject: 'Re: Mercury examples call'
    to: greg@acme-test.com
  - body: 'Rishi — I agree this repro is about underscore/env-var-style header names
      being put on the wire, not the canonical hyphenated header path.


      A small Go snippet is acceptable only as a narrow correction to reinforce the
      canonical header-only contract: `X-Scaffold-Workspace` and `X-Scaffold-Signature`.
      Use the working hyphenated `Header.Set(...)` pattern and, if needed, note that
      lower-case hyphenated headers verify.


      Please cut the proposed language that says `X_SCAFFOLD_SIGNATURE` / `X_SCAFFOLD_WORKSPACE`
      should be accepted, and do not add query-parameter fallback, alternate signature
      locations, or a broader connector-doc rewrite.'
    cc: []
    id: sent_1785285808368
    sent_at: '2023-10-31T10:32:00-07:00'
    subject: 'Re: Pinecone Go repro + proposed docs snippet'
    to: rishi@atlas-test.com
  - body: 'Sofia —


      We’re closing October and doing the internal caveat pass first.


      If we share the Mercury package this week, it will be limited to quarterly cohort
      and board-operating views. We would not include weekly diagnostics or raw Evergreen
      movement.


      I’d keep this as selective evidence review, not a term-sheet conversation or
      partner-level diligence process.


      Morgan Chen · Scaffold'
    cc:
    - devon@atlas-test.com
    - sarah@atlas-test.com
    id: sent_1785285810139
    sent_at: '2023-11-01T08:54:00-07:00'
    subject: 'Re: October Mercury package'
    to: Sofia Alvarez
  - body: 'Sarah —


      Yes: strip out “v0.2 readiness checkpoint” for the customer thread.


      I’d keep the customer-facing answer to current-flow boundaries only:


      For this Mercury admin test, the supported access path is the current magic-link
      and org-invite flow. SSO is not part of this test flow, so I would not attach
      timing language to it in this thread.


      Detailed admin-change audit history is also outside the current test flow. For
      this pass, we should keep the thread focused on the bounded setup, preview/sample-data,
      source connection, and first-live-sync path.


      The current test flow does not expose a separate billing-owner role. For this
      test, admin setup remains in the current role model; we should not create an
      Evergreen-specific exception or imply a committed timing path for role separation.


      For the sequencing question, it is fine to clarify the current mechanics: the
      second-admin group can continue inside the current bounded flow, and we can
      walk the order of invite/access, preview framing, source credential entry, and
      first live sync without turning that into roadmap language.


      Morgan'
    cc: []
    id: sent_1785287790991
    sent_at: '2023-11-06T13:27:00-08:00'
    subject: 'Re: Evergreen second-admin notes + wording check'
    to: sarah@atlas-test.com
  - body: "Sarah —\n\nI’d keep Greg’s product lead in the participant list and keep
      the discussion live-only, but remove the closing line about possible sanitized
      examples afterward.\n\nSuggested revised agenda language:\n\n1. Quick opener
      that the materials Acme previously pointed to were outside the confidentiality
      scope as drafted, and that any Mercury examples discussion will stay live while
      the NDA scope thread remains unresolved.\n2. Acme questions on the current Mercury
      flow and the feedback themes they already raised.\n3. Verbal walk-through on
      the call only of a small set of Mercury examples:\n   - source setup / connection
      steps\n   - failed-sync handling at a high level\n   - admin invite / teammate
      handoff path\n4. Q&A and next steps for live follow-up.\n\nI would also be explicit
      in the agenda note: while the NDA scope issue is unresolved, no written examples,
      screenshots, packet excerpts, or briefing material will follow the call.\n\nMorgan"
    cc: []
    id: sent_1785287793296
    sent_at: '2023-11-07T09:06:00-08:00'
    subject: 'Re: Acme Thursday live-only call agenda draft'
    to: sarah@atlas-test.com
  - body: 'Greg —


      Thanks for the live discussion today with Sarah and your product lead.


      Quick recap: we kept the Mercury examples discussion live while the NDA scope
      thread remains unresolved. That boundary still holds after the call: no written
      examples, screenshots, packet excerpts, or briefing material will follow while
      the scope issue is open.


      We can continue live follow-up on current Mercury flow questions as needed.


      Morgan Chen · Scaffold'
    cc:
    - sarah@atlas-test.com
    id: sent_1785287796823
    sent_at: '2023-11-09T11:12:00-08:00'
    subject: 'Re: Acme NDA scope'
    to: Greg Shipman
  - body: 'Sarah —


      For now, let’s keep collecting the repeated SSO, audit-history, and admin-versus-billing-owner
      questions in the current thread rather than starting a separate internal backlog
      doc.


      The framing should stay the same: those are next-phase enterprise-readiness
      questions, not v0.2 commitments and not Evergreen-specific exceptions. Current-flow
      mechanics can keep being answered as bounded Mercury test clarifications routed
      through you.


      Morgan'
    cc: []
    id: sent_1785287798588
    sent_at: '2023-11-10T16:46:00-08:00'
    subject: 'Re: Evergreen admin-test notes'
    to: sarah@atlas-test.com
  - body: 'Sofia —


      Either of these works on my side:


      - Thursday, 2023-11-16 at 11:00 a.m. PT

      - Friday, 2023-11-17 at 9:00 a.m. PT


      The limited Mercury package can come after my final caveat pass early next week.


      I’d keep this framed as a short-list Mercury evidence review, not a lead or
      term-sheet process.


      Morgan Chen · Scaffold'
    cc:
    - Devon Hayes
    - sarah@atlas-test.com
    id: sent_1785287799451
    sent_at: '2023-11-10T17:02:00-08:00'
    subject: 'Re: Northstar / Mercury review'
    to: Sofia Alvarez
  - body: 'Hi Sofia —


      Sharing the limited Mercury packet we discussed: the cleaned cohort view, a
      bounded Evergreen context note, and the current hybrid pricing model.


      A few caveats are intentionally left intact. The cohort view uses real-source
      connection or first live sync within 7 days as activation; sample/preview behavior
      is excluded. Weekly internal cuts and raw customer-by-customer movement are
      not included. The Evergreen section is bounded to current-flow evidence, not
      a claim that enterprise readiness or expansion is solved.


      This is meant for a selective Mercury evidence review ahead of the next conversation,
      not a broader fundraising process or term-sheet conversation.


      Morgan Chen · Co-Founder & CEO, Scaffold'
    cc:
    - devon@atlas-test.com
    - sarah@atlas-test.com
    id: sent_1785300763168
    sent_at: '2023-11-13T10:14:00-08:00'
    subject: 'Re: Intro: Morgan Chen / Devon Hayes <> Sofia Alvarez'
    to: Sofia Alvarez
  - body: 'Sarah —


      Please strip the “v0.2 readiness review” framing. The current Evergreen admin-test
      thread can keep collecting SSO timing, admin-change audit history, and admin-versus-billing-owner
      separation questions, but those are next-phase enterprise-readiness items.


      They are not Mercury v0.2 promises, not Evergreen-specific exceptions, and not
      a separate backlog document yet. For compliance-facing wording, keep it bounded
      to the current admin test continuing in the existing flow while those questions
      are tracked as later-scope enterprise-readiness follow-up.


      Morgan'
    cc: []
    id: sent_1785300764598
    sent_at: '2023-11-13T10:39:00-08:00'
    subject: Evergreen compliance wording
    to: Sarah Kim
  - body: 'Hi HR —


      Please extend the senior engineer offer deadline only to Wednesday, Nov. 15
      at noon PT. Dec. 4 is acceptable as the start date. Comp and equity are not
      reopening, and any legal wording change still needs to go through the normal
      legal-clearance path before anything is sent.


      Morgan'
    cc: []
    id: sent_1785300766002
    sent_at: '2023-11-13T15:42:00-08:00'
    subject: Senior engineer offer deadline
    to: HR
  - body: 'Greg —


      I understand the request for a sanitized internal briefing. While the NDA scope
      issue is still unresolved, we can’t send written examples, screenshots, packet
      excerpts, a sanitized briefing, or other Mercury materials.


      I’m happy to do a live follow-up instead. Acme’s exclusion from fresh Mercury
      materials is driven by the legal scope issue, not by lack of interest in the
      feedback.


      Morgan Chen · Scaffold'
    cc:
    - sarah@atlas-test.com
    id: sent_1785300767887
    sent_at: '2023-11-14T15:28:00-08:00'
    subject: 'Re: Acme NDA scope'
    to: Greg Shipman
  - body: 'Hi HR —


      Legal cleared the senior engineer offer IP wording with no document change.
      Dec. 4 remains acceptable as the start date, and comp/equity stay unchanged.


      Please send the candidate one concise answer. If signed documents are not back
      by Friday, Nov. 17 at noon PT, close the loop rather than extending again.


      Morgan'
    cc: []
    id: sent_1785300770741
    sent_at: '2023-11-16T15:36:00-08:00'
    subject: Senior engineer offer final answer
    to: HR
  - body: 'Hi Sofia —


      Thanks for the time today. Quick recap of where we landed:


      - The useful Mercury signal is improved real-source / first-live-sync activation
      in the bounded cohort view, with preview/sample behavior kept out of activation.

      - Expansion is still uneven; we are not treating the current evidence as proof
      that downstream expansion is solved.

      - Evergreen is useful as bounded enterprise context: the current flow is workable,
      while SSO timing, admin-change audit history, admin-versus-billing-owner separation,
      and procurement packaging remain next-phase enterprise-readiness questions.

      - The pricing model remains the current hybrid usage-ramp model based on monthly
      active developers, not directory size or purchased seats.


      Happy to use a December partner-level readout to pressure-test the same evidence
      and caveats. We are treating this as active diligence through you, not as a
      declared lead or term-sheet process.


      Morgan Chen · Co-Founder & CEO, Scaffold'
    cc:
    - devon@atlas-test.com
    - sarah@atlas-test.com
    id: sent_1785300771217
    sent_at: '2023-11-17T10:18:00-08:00'
    subject: 'Re: Intro: Morgan Chen / Devon Hayes <> Sofia Alvarez'
    to: Sofia Alvarez
  - body: 'Sarah —


      Yes, keep collecting SSO timing, admin-change audit history, and admin-vs-billing-owner
      separation questions in the current admin-test thread, but I would not adopt
      the “v0.2 control-readiness” label or give rough timing ranges.


      Those are next-phase enterprise-readiness questions. They are not v0.2 promises,
      not Evergreen-specific exceptions, and not rough-date commitments. If they need
      language, keep it to current-flow boundaries: the bounded admin test can continue,
      and these items remain follow-up for the next enterprise-readiness pass.


      Morgan'
    cc: []
    id: sent_1785302121891
    sent_at: '2023-11-20T09:49:00-08:00'
    subject: 'Re: Evergreen compliance review wording check'
    to: sarah@atlas-test.com
  - body: 'Hi HR —


      Treat Thursday and Friday as quiet holiday coverage. Only named support/on-call
      coverage should be active; avoid standing meetings and broad async update requests,
      and escalate only genuinely customer-impacting issues.


      Morgan'
    cc: []
    id: sent_1785302124380
    sent_at: '2023-11-20T12:08:00-08:00'
    subject: Thanksgiving quiet coverage
    to: HR
  - body: 'Hi Sofia —


      Thanks for the written follow-ups. Here is the bounded read from the limited
      packet.


      Cohort / activation: the outside-reader definition is unchanged. Activated within
      7 days means a real source was connected or first live sync completed within
      7 days. Sample import / preview-only behavior does not count, and invite sent
      is supporting activity only. In the October external-share cohort, 19 of 27
      met the activation definition within 7 days and 16 of 27 reached first live
      sync in that same window. The gap is 3 accounts that connected a real source
      inside 7 days but did not clear first live sync inside the same window. So the
      improvement is more accounts moving through the real-source / live-sync path,
      not preview or sample behavior.


      Expansion: it is still uneven. Pattern-level, we are seeing some accounts get
      through first setup and initial sync but stall before a second admin or wider
      team usage becomes routine; some ramp more slowly after first sync because trust
      / confidence is still being established; and some still need support around
      admin sequencing, source ownership, or failure recovery. I would not frame this
      as one solved expansion motion or a clean full-cohort expansion metric yet.


      Evergreen: Evergreen is the clearest current enterprise pattern, not because
      it proves the full enterprise layer is solved, but because the bounded Mercury
      flow is workable for a second admin group without customer-specific exceptions.
      In that bounded flow, Evergreen validated org invites, magic-link access, preview-only
      sample data, real-source connection, and first live sync. What Evergreen surfaced
      more sharply are the next-phase enterprise-readiness questions around SSO timing,
      admin-change audit history, admin-versus-billing-owner separation, and a procurement
      packet that can stand on its own. Those items are clearer because of Evergreen;
      they are not solved by Evergreen and are not part of the current Mercury scope.


      Pricing: the current Mercury model is the hybrid structure we sent: Pilot at
      $2,500/month including up to 50 monthly active developers; Growth at $7,500/month
      including up to 200 monthly active developers; then $1,000 per additional 50
      monthly active developers. Enterprise add-ons like SSO, audit logs, and advanced
      admin controls are separate only after those features actually ship. We use
      monthly active developer usage rather than purchased seats or directory size
      because seats and directory counts can overstate value before the product is
      really deployed. MAU is not perfect, but it is the cleanest proxy for realized
      usage and adoption ramp in Mercury right now. For accounts that activate but
      expand slowly, the model avoids forcing a seat commitment ahead of actual usage;
      they can enter on the platform minimum and move up as monthly active developer
      usage grows.


      If useful, we can use this for a December partner-level discussion on the current
      Mercury package and known caveats. I would keep that as active diligence around
      the current evidence.


      Morgan'
    cc:
    - Devon Hayes
    - sarah@atlas-test.com
    id: sent_1785302124851
    sent_at: '2023-11-21T09:33:00-08:00'
    subject: 'Re: Intro: Morgan Chen / Devon Hayes <> Sofia Alvarez'
    to: Sofia Alvarez
  - body: 'Hi Kara —


      Please do not add an anonymized regulated-bank design-partner quote, or any
      customer-identifying, regulated-bank, or Evergreen-implying quote, to the Mercury
      page before December.


      Keep the approved generic Mercury copy as-is. Any future Mercury copy request
      needs a separate Scaffold review rather than a quick holiday-week edit.


      Morgan'
    cc:
    - sarah@atlas-test.com
    id: sent_1785302125786
    sent_at: '2023-11-21T10:24:00-08:00'
    subject: 'Re: Mercury page quote request'
    to: kara@kestrel-test.com
  - body: 'Hi Sofia —


      Internal review within Northstar is fine under the same limited context: current
      Mercury evidence, known caveats, and no wider redistribution.


      Let’s skip a holiday Friday call. If your data partner has questions, please
      send consolidated follow-up questions next week. We can keep the December conversation
      in active-diligence framing around the current Mercury package.


      Morgan'
    cc:
    - Devon Hayes
    - sarah@atlas-test.com
    id: sent_1785302126792
    sent_at: '2023-11-22T08:48:00-08:00'
    subject: 'Re: Intro: Morgan Chen / Devon Hayes <> Sofia Alvarez'
    to: Sofia Alvarez
  - body: 'Sarah — keep collecting the SSO timing, admin-change audit-history, and
      admin-versus-billing-owner questions in the current admin-test thread for now.
      Please do not split them into a separate enterprise-readiness backlog before
      December, attach dates, make v0.2 promises, or create Evergreen-specific exceptions.


      Morgan'
    cc: []
    id: sent_1785303389405
    sent_at: '2023-11-27T08:58:00-08:00'
    subject: 'Re: Evergreen admin-test questions'
    to: sarah@atlas-test.com
  - body: 'Kara — this is in bounds as a generic direction only. Please keep the copy
      generic, use the non-regulated version of the customer-language body, remove
      anything that implies Evergreen or a regulated-bank quote, and include no roadmap
      detail.


      Any future customer-specific claim should come back as a separate review.


      Morgan Chen · Scaffold'
    cc:
    - sarah@atlas-test.com
    id: sent_1785303393310
    sent_at: '2023-11-27T11:24:00-08:00'
    subject: 'Re: Mercury page copy after quote removal'
    to: kara@kestrel-test.com
  - body: 'Sofia — thanks for consolidating the questions. Short written answers below.


      1) October activation composition


      The outside-reader definition stays unchanged: activated within 7 days means
      a real source was connected or first live sync completed within 7 days. Sample
      import / preview-only behavior does not count, and an invite sent is supporting
      activity only.


      For the October external-share cohort, 16 of 27 reached first live sync within
      7 days. An additional 3 of 27 connected a real source within 7 days but did
      not get through first live sync inside that same seven-day window. That 3-account
      gap is the full difference between 19 and 16; there is not another preview-heavy
      or invite-only bucket inside the activation numerator.


      Shortest version: the October lift came from more accounts reaching the real-source
      / live-sync path in the first week; preview-only activity stayed out of the
      count. Operators may still see first-week behaviors such as invite accepted,
      sample preview viewed, or source selected, but none of those count as activation
      in the external-share definition.


      2) Uneven expansion


      Expansion is still uneven. The first-admin path is better than it was in the
      July/August cohorts, but broader usage still does not spread cleanly enough
      to call expansion solved or publish an outside expansion claim.


      The main patterns are: some accounts clear setup and first live sync but stay
      contained to the first admin longer than we want; some broaden more slowly because
      trust is not established yet after first live sync; some hit admin sequencing
      or source-ownership confusion when the next admin/operator is added; and a smaller
      set need support after a failed or delayed first sync, which slows broader rollout
      even when activation technically happened.


      The product-gap side today is mostly around admin handoff, failure-recovery
      clarity, and trust after first live sync. The expected design-partner side is
      that broader team rollout lags the initial first-admin setup even when the first
      path works. That is why we are comfortable speaking about activation improvement
      but not publishing an outside expansion claim yet. “Activated but still contained
      to the first admin” versus “activated with credible room to broaden” is a useful
      operating distinction internally, but I would not turn it into an external threshold
      or pseudo-metric yet.


      3) Evergreen context


      Evergreen is the clearest current enterprise-pattern example because the bounded
      Mercury flow works for a second admin group without customer-specific exceptions,
      not because it proves the enterprise layer is finished. In that bounded flow,
      Evergreen validated org invites, magic-link access, preview-only sample data,
      real-source connection, and first live sync.


      What it surfaced more clearly are the next-phase enterprise-readiness follow-ups:
      SSO timing, audit history for admin changes, admin-versus-billing-owner separation,
      and a procurement packet that can stand on its own without live translation
      from us. Those items are clearer because of Evergreen; they are not solved by
      Evergreen and they are not current Mercury v0.2 claims.


      I would think of Evergreen as the sharpest example of a broader enterprise pattern
      because the asks are recognizable rather than custom exceptions, while avoiding
      any implication that the pattern is already solved or broadly packaged.


      4) Hybrid pricing model


      The current Mercury model remains:

      - Pilot: $2,500/month platform minimum including up to 50 monthly active developers

      - Growth: $7,500/month platform minimum including up to 200 monthly active developers

      - Overage: $1,000 per additional 50 monthly active developers

      - Enterprise add-ons such as SSO, audit logs, and advanced admin controls are
      quoted separately only after those features ship


      We map pricing to monthly active developer usage rather than purchased seats
      or directory size because seats and directory counts overstate value too early
      in this product. What matters in the current Mercury motion is how many developers
      are actually active in the workflow once a team gets through setup and begins
      real usage.


      Directory size can be large before the product is actually deployed, and purchased
      seats push us toward selling potential ahead of actual usage. MAU is not a universal
      perfect metric, but it is the cleanest honest ramp measure for where Mercury
      is today.


      For accounts that activate but expand slowly, the model deliberately avoids
      forcing a bigger seat commitment ahead of real usage. They can enter on the
      platform minimum, and the ramp in monthly active developers determines when
      they move up. Pricing bands map to monthly active developer usage rather than
      purchased seats or directory size; Scaffold/internal test users do not count;
      preview/sample-only behavior remains separate from activation reporting.


      I would phrase the data-partner point this way: the platform minimum supports
      a bounded initial deployment, and MAU is what captures realized usage once the
      workflow broadens.


      Happy to do a focused follow-up in December if useful. I would keep it through
      you as active diligence on the current Mercury package.


      Morgan Chen · Scaffold'
    cc:
    - sarah@atlas-test.com
    id: sent_1785303394237
    sent_at: '2023-11-28T09:42:00-08:00'
    subject: 'Re: Northstar consolidated follow-up'
    to: Sofia Alvarez
  - body: 'Sofia — please keep questions consolidated through you and me for now.
      Anna can join a focused data follow-up if needed, but I do not want this to
      turn into a broad data-room or partner-readout process.


      Morgan Chen · Scaffold'
    cc:
    - sarah@atlas-test.com
    id: sent_1785303395636
    sent_at: '2023-11-29T11:05:00-08:00'
    subject: 'Re: Northstar data follow-up'
    to: Sofia Alvarez
  - body: 'Sarah — do not attach owner names or target dates to the Evergreen compliance
      questions yet. Keep SSO timing, audit history, and admin-versus-billing-owner
      separation in the current admin-test thread. Please ask them to bring exact
      examples next week so we can scope from concrete cases. Do not describe any
      of this as v0.2 commitments.


      Morgan'
    cc: []
    id: sent_1785303397052
    sent_at: '2023-11-30T09:06:00-08:00'
    subject: 'Re: Evergreen compliance questions'
    to: sarah@atlas-test.com
  - body: 'Kara — approved for Kestrel to publish the supplied final generic Mercury
      section before month-end:


      Hero line

      Mercury for modern developer onboarding


      Body copy

      Design-partner feedback is helping us harden the core invite, setup, and first-sync
      experience.


      Proof-point bullets

      - Clearer first-admin path from invite through setup

      - Better first-sync guidance shaped by early admin and support feedback

      - Built for teams shipping real developer workflows


      Customer-language section

      Built with early design-partner and admin feedback on invite, setup, and first-sync
      workflows.


      CTA support line

      Current Mercury messaging reflects the bounded flow on the page today.


      This approval is only for this version because it has no customer quote, no
      regulated-bank implication, no Evergreen hint, and no roadmap detail. Please
      do not create additional Mercury page variants as quick edits before the board-prep
      cycle.


      Morgan Chen · Scaffold'
    cc:
    - sarah@atlas-test.com
    id: sent_1785303398582
    sent_at: '2023-11-30T09:32:00-08:00'
    subject: 'Re: Mercury landing page section'
    to: kara@kestrel-test.com
  - body: 'Sofia — Tuesday, Dec. 5 at 2:00 p.m. PT works on our side for a focused
      data follow-up with me, Anna, and Devon. If that does not work for you, send
      another option and we will avoid the Wednesday-morning slot.


      I would keep the label as a focused data follow-up on the current Mercury package.


      Morgan Chen · Scaffold'
    cc:
    - sarah@atlas-test.com
    id: sent_1785303399513
    sent_at: '2023-12-01T16:22:00-08:00'
    subject: 'Re: Northstar data follow-up'
    to: Sofia Alvarez
  - body: 'Sofia — thanks for the focused pass today. We covered:

      - October activation sources, including the outside-reader read on 19/27 activated
      within 7 days versus 16/27 reaching first live sync within 7 days.

      - The 3-account gap and the continued exclusion of preview/sample activity,
      invite-only states, and similar first-week motion from activation.

      - Expansion failure modes: stalls after first-admin setup, slower ramp after
      first live sync, second-admin/broader-team friction, and trust drag after early
      sync issues.

      - The bounded Evergreen context: what the current flow validates versus the
      later enterprise-readiness follow-up areas.

      - Hybrid pricing: why monthly active developer usage is the honest ramp measure,
      and how to think about the platform minimum when activation precedes slower
      expansion.


      The main caveat stays the same: stronger activation/admin-friction evidence
      does not mean downstream expansion is clean yet. Any narrow follow-up from Anna
      or Devon will come through me so we keep the thread consolidated.


      Morgan Chen · Scaffold'
    cc:
    - sarah@atlas-test.com
    id: sent_1785304506659
    sent_at: '2023-12-05T15:09:00-08:00'
    subject: 'Re: Intro: Morgan Chen / Devon Hayes <> Sofia Alvarez'
    to: Sofia Alvarez
  - body: 'Kara —


      The approved generic Mercury page can stand as marketing copy, but please do
      not turn that line into a board-ready enterprise-buyer proof snippet.


      No Evergreen or regulated-bank implication, no customer-specific claim, and
      no roadmap detail.


      Morgan Chen · Scaffold'
    cc:
    - sarah@atlas-test.com
    id: sent_1785304509029
    sent_at: '2023-12-06T10:18:00-08:00'
    subject: 'Re: Mercury page'
    to: kara@kestrel-test.com
  - body: 'Board —


      Following today’s December update with Devon and Anna, the aligned version is
      narrow: selective B-round prep is real enough to discuss, but December is not
      a launched broad process.


      The framing we will keep using:

      - Elena’s warm-context calibration is complete.

      - Northstar is active diligence through Sofia Alvarez on the current Mercury
      package.

      - The list is still narrowing.


      The operating progress and caveats stay in the same frame:

      - Mercury activation and admin-friction evidence is stronger.

      - Hybrid pricing is cleaner.

      - Evergreen shows enterprise pull.

      - Expansion remains uneven.

      - Enterprise-readiness gaps remain open.


      We will keep treating that as selective, caveated prep rather than a broad process
      or proof that expansion or enterprise readiness is solved.


      Morgan Chen · Co-Founder & CEO, Scaffold'
    cc:
    - sarah@atlas-test.com
    id: sent_1785304509514
    sent_at: '2023-12-08T11:38:00-08:00'
    subject: December board update follow-up
    to: team:board
  - body: 'Sofia — consolidated follow-up questions next week are fine. Please keep
      them routed through you and me, and Anna or Devon can join narrowly if needed.


      Let’s keep this as focused active diligence on the current Mercury package,
      not a data-room process, partner-readout label, lead process, or term-sheet
      step.


      Morgan Chen · Scaffold'
    cc:
    - sarah@atlas-test.com
    id: sent_1785304510938
    sent_at: '2023-12-08T14:06:00-08:00'
    subject: 'Re: Intro: Morgan Chen / Devon Hayes <> Sofia Alvarez'
    to: Sofia Alvarez
  - body: 'Sarah — I’d strip all rough timing and keep the split explicit. Here’s
      a version you can use:


      ---


      Hi team —


      Thanks for consolidating the follow-up questions. Below is the clearest written
      split between what is in the current Mercury flow today and what remains next-phase
      enterprise-readiness evaluation.


      Current Mercury flow

      - The current Mercury flow remains the bounded flow you are already testing:
      magic-link access, org invites, preview-only sample data, real-source connection,
      and first live sync.

      - The second admin group is using that same bounded flow; we have not set up
      a separate Evergreen-specific path.

      - Questions about SSO / SAML, admin-side audit history, admin-versus-billing-owner
      separation, and a fuller standalone procurement/security packet remain outside
      the current Mercury flow.


      1) SSO / SAML

      - Current product position: Current Mercury access is magic-link based rather
      than SSO / SAML. SSO / SAML is not part of the present test flow.

      - Next-phase evaluation: SSO / SAML remains a later enterprise-readiness item.
      We do not have committed timing, and it should not be read as a current-flow
      or near-term Evergreen-specific commitment.

      - Available materials now: The current bounded-flow description above is the
      accurate written current-state answer.


      2) Audit history for admin-side changes

      - Current product position: The current product does not provide a standalone
      audit-history view for admin-side changes such as admin invites, role or permission
      changes, source connection or disconnection, or similar admin-side configuration
      changes.

      - Next-phase evaluation: Admin-side audit history remains later-scope enterprise-readiness
      work. The safest description is that it is not a current Mercury capability;
      we should not imply that a partial audit trail already exists.

      - Available materials now: The current-product answer above can be circulated
      as the current-state position.


      3) Admin versus billing-owner separation

      - Current product position: The current Mercury flow is closer to a narrower
      admin setup model than to separately permissioned long-term admin and billing-owner
      roles.

      - Next-phase evaluation: Separate admin-versus-billing ownership remains later-scope
      enterprise-readiness work, not a current-flow capability or custom Evergreen
      branch.

      - Available materials now: The current bounded-flow description is the accurate
      written answer for the present test.


      4) Standalone procurement/security packet

      - Available now: This written current-state split, together with the bounded-flow
      description, is the material we can circulate now without implying roadmap commitments.

      - Still being assembled: A fuller standalone procurement/security packet that
      can replace live follow-up for later-scope enterprise-readiness questions is
      still being assembled. We should label that separately from the current-product
      facts above.


      Happy to talk live if that is the easiest way to handle exact examples, but
      I wanted to separate what is current product now from what is still next-phase
      work.


      Best,

      Sarah


      ---


      Morgan'
    cc: []
    id: sent_1785306022775
    sent_at: '2023-12-12T10:08:00-08:00'
    subject: 'Re: Draft Evergreen procurement reply before I send'
    to: sarah@atlas-test.com
  - body: 'Kara — this needs to stay generic and should not become a customer-specific
      proof point before the holidays.


      I would not use the enterprise-design-partner, regulated-environment, or enterprise-buyer
      framing. A safer version would be:


      Subject line

      Mercury: a clearer path from invite to first live sync


      Preview text

      A short look at the invite, setup, and first-sync experience Mercury is hardening.


      Body intro

      Mercury is being hardened around the core invite, setup, and first-sync experience,
      with a clearer first-admin flow and better first-sync guidance for teams onboarding
      real developer workflows.


      Proof-point bullets

      - Clearer first-admin path from invite through setup

      - Better first-sync guidance shaped by admin and support feedback

      - Built for teams shipping real developer workflows


      Customer-language paragraph

      Mercury focuses on invite, setup, and first-sync workflows for teams onboarding
      real developer workflows.


      Callout box

      Header: Mercury overview

      Body: Current Mercury messaging reflects the bounded flow on the page today:
      invite, setup, and first-sync guidance.


      CTA

      Read the Mercury overview


      Please keep the newsletter to this generic level: no customer-specific claims,
      regulated-industry language, enterprise-readiness proof points, roadmap detail,
      or board-proof framing.


      Morgan Chen · Scaffold'
    cc:
    - sarah@atlas-test.com
    id: sent_1785306024192
    sent_at: '2023-12-12T10:36:00-08:00'
    subject: 'Re: Mercury landing page section'
    to: kara@kestrel-test.com
  - body: 'Sofia — thanks, confirmed. We’ve put a hold on Jan. 11, 2024 from 10:00–11:30
      a.m. PT for the Northstar Mercury partner readout with you and the partner group.


      I’d keep the agenda bounded to:

      1. September/October Mercury cohort package and the activation definition

      2. Evergreen enterprise-readiness signal, including the boundary between the
      bounded current flow and later follow-up items

      3. Hybrid pricing model as it exists today


      We’ll keep weekly activation cuts out of the deck and treat this as a focused
      diligence readout, not a term-sheet step or lead-process signal.


      Morgan Chen · Scaffold'
    cc:
    - sarah@atlas-test.com
    id: sent_1785306027476
    sent_at: '2023-12-14T08:58:00-08:00'
    subject: 'Re: Intro: Morgan Chen / Devon Hayes <> Sofia Alvarez'
    to: Sofia Alvarez
  - body: 'Kara —


      Approved only for the generic Mercury newsletter lane.


      Please remove the “enterprise design-partner” phrasing before queueing, and
      do the same for anything that could read as a regulated-bank, Evergreen, or
      board-proof implication. If the “security-conscious teams” bullet creates that
      impression, soften it back to generic onboarding/setup language or remove it.
      Keep the block free of customer quotes, names, logos, metrics, sidebars, customer-specific
      claims, and roadmap detail.


      Once it is cleanly generic, you can queue the holiday send without creating
      a separate variant.


      Morgan Chen · Scaffold'
    cc:
    - sarah@atlas-test.com
    id: sent_1785307422838
    sent_at: '2023-12-18T16:44:00-08:00'
    subject: 'Re: Mercury landing page section'
    to: kara@kestrel-test.com
  - body: 'Sofia —


      Thanks for laying this out. This is the right level: we’ll keep the Jan. 11
      readout agenda bounded to the current Mercury package, Evergreen signal, hybrid
      pricing, and the caveats around what this does and does not prove.


      No need for a prep call between Christmas and New Year’s. If Northstar has anything
      it wants us to consider for the pre-read, please send one consolidated wish
      list by Jan. 3 so we can avoid overbuilding.


      We’re still treating the readout as diligence, not a lead process or term-sheet
      step.


      Morgan Chen · Scaffold'
    cc:
    - sarah@atlas-test.com
    id: sent_1785307424730
    sent_at: '2023-12-21T09:46:00-08:00'
    subject: 'Re: Intro: Morgan Chen / Devon Hayes <> Sofia Alvarez'
    to: Sofia Alvarez
  - body: 'Maya —


      Thanks for reaching out. I’m keeping the holiday week local and protected, so
      I’m going to pass on coffee on Dec. 27.


      Happy to reconnect in January if useful.


      Morgan Chen · Co-Founder & CEO, Scaffold'
    cc:
    - sarah@atlas-test.com
    id: sent_1785307427078
    sent_at: '2023-12-22T17:18:00-08:00'
    subject: 'Re: Coffee while you''re around after Christmas?'
    to: maya@cedarhill.vc
  - body: 'Daniel —


      Thanks for reaching out. I’m keeping the holiday week local and protected, so
      I’m going to pass on coffee on Dec. 29.


      Happy to reconnect in January if useful.


      Morgan Chen · Co-Founder & CEO, Scaffold'
    cc:
    - sarah@atlas-test.com
    id: sent_1785307427544
    sent_at: '2023-12-22T17:18:00-08:00'
    subject: 'Re: Dec. 29 coffee?'
    to: daniel@ridgewayvc.com
  - body: 'Hi Sofia — thanks, received. We’ll use the consolidated list for our January
      2, 2024 prep. We don’t need a between-holidays prep call. Let’s keep the January
      11, 2024 readout framed as bounded diligence, not a lead process or term-sheet
      step.


      Morgan Chen · Scaffold'
    cc:
    - sarah@atlas-test.com
    id: sent_1785308068042
    sent_at: '2023-12-27T10:52:00-08:00'
    subject: January 11 Northstar readout pre-read
    to: Sofia Alvarez
  - body: 'Sarah — here’s a holding reply you can use:


      Thanks for sending the examples on SSO timing, admin-change audit history, admin-versus-billing-owner
      separation, and procurement packaging. We’ll respond the week of January 2,
      2024 with current product facts and the already-bounded enterprise-readiness/backlog
      framing.'
    cc: []
    id: sent_1785308069448
    sent_at: '2023-12-28T09:41:00-08:00'
    subject: Evergreen examples — holding reply draft
    to: Sarah Kim
  - body: 'Hello,


      We’re requesting a warranty follow-up for the December sink repair tied to the
      corrected December invoice. A small drip has reappeared under the repaired sink;
      we’ll document it with photos and receipts.


      No new paid work is authorized by this message alone.


      Morgan Chen · Co-Founder & CEO, Scaffold'
    cc:
    - sarah@atlas-test.com
    id: sent_1785308071815
    sent_at: '2023-12-29T13:12:00-08:00'
    subject: Warranty follow-up for December sink repair
    to: Blueline Plumbing
  - body: 'Yes — please send the final concrete examples pack to Evergreen now.


      Keep it present-state and circulate-now only: the current bounded Mercury flow,
      no Evergreen-specific branch, no SSO/SAML step in the examples, no standalone
      admin-change audit history, and no role-separation or procurement/security commitment.


      The fuller standalone procurement/security packet remains later enterprise-readiness
      work.


      Morgan'
    cc: []
    id: sent_1785457145428
    sent_at: '2024-01-05T09:46:00-08:00'
    subject: 'Re: Evergreen example cases to turn into current-flow pack'
    to: Sarah Kim
  - body: 'Thanks for the cleanup status. Please keep the internal record explicit:
      the 2023 senior-engineer process is closed with no signed hire and no active
      offer artifact left in January. Any future senior or principal engineering offer
      needs to restart from a fresh req and the current legal/recruiting checks, not
      revive the November packet.


      Morgan'
    cc: []
    id: sent_1785460702554
    sent_at: '2024-01-08T09:32:00-08:00'
    subject: 'Re: senior engineer offer'
    to: HR
  - body: 'No — please keep the Mercury page on the already-approved generic Mercury
      language. The Northstar readout does not change public-page claims or authorize
      more aggressive Mercury copy.


      Morgan Chen · Scaffold'
    cc:
    - sarah@atlas-test.com
    id: sent_1785460703867
    sent_at: '2024-01-09T09:54:00-08:00'
    subject: 'Re: Mercury page'
    to: kara@kestrel-test.com
  - body: 'I’m positive on the structured Q&A format, but I want to review HR’s recap
      first before we make it the default for quarterly all-hands.


      Morgan'
    cc: []
    id: sent_1785460705170
    sent_at: '2024-01-12T10:22:00-08:00'
    subject: 'Re: December structured Q&A'
    to: HR
  - body: 'Elena —


      I wanted to let you know that the Northstar intro has become serious, and your
      calibration was genuinely helpful. Thank you — the intro mattered.


      Morgan Chen · Scaffold'
    cc:
    - sarah@atlas-test.com
    id: sent_1785474167432
    sent_at: '2024-01-18T09:41:00-08:00'
    subject: 'Re: Northstar intro'
    to: Elena Volkov
  - body: 'HR —


      - Devon and I are sequencing the operating plan first, so please do not announce
      headcount plans or hiring changes yet.

      - We’ll come back with the plan after the leadership reset.


      Morgan'
    cc: []
    id: sent_1785491395174
    sent_at: '2024-02-22T12:34:00-08:00'
    subject: Headcount plan sequencing
    to: HR
  - body: 'Sarah —


      - Boundary for Kara/Kestrel: no public funding announcement for now, and no
      Kestrel-written raise narrative.

      - No external product-proof campaign, Mercury proof asset, roadmap promise,
      or enterprise-proof framing tied to the Series B.

      - Customer and partner conversations can acknowledge that we’re post-Series-B
      when relevant, but it should stay contextual.

      - Any future announcement needs separate Morgan/Sarah review plus Northstar
      coordination before Kestrel drafts or publishes anything.


      Morgan'
    cc: []
    id: sent_1785491395605
    sent_at: '2024-02-23T09:18:00-08:00'
    subject: Series B announcement boundary
    to: sarah@atlas-test.com
  - body: 'Anna —


      Thanks again for the patience while post-close noise settled down. I wanted
      to make this intro now that things are calmer.


      Rishi runs Atlas at Scaffold and is one of the people here with unusually good
      taste for systems-y, database-adjacent engineering problems. Anna is co-founder
      at Tessl, and every conversation I have had with her has made me think the two
      of you would have a genuinely useful conversation.


      Rishi has been curious about the database-internals work Tessl is doing, and
      Anna, I suspect you will recognize quickly why I thought of this connection.
      I am not attaching a huge agenda to it beyond compare notes and get to know
      each other.


      I will get out of the way and let you two take it from here.


      Morgan Chen · Co-Founder & CEO, Scaffold'
    cc:
    - sarah@atlas-test.com
    id: sent_1785535327565
    sent_at: '2024-03-20T09:02:00-07:00'
    subject: 'Intro: Anna Rao <> Rishi'
    to: Anna Rao, Rishi
  - body: 'Nadia —


      Thrilled to have you joining Scaffold as Head of Customer Growth on April 15.
      We’re excited to work with you on building the repeatable customer-growth motion
      from Mercury activation, Evergreen-style enterprise-readiness signals, expansion
      failure modes, and clear handoffs with Sarah and Devon.


      Welcome aboard — I’m looking forward to working together.


      Morgan Chen · Scaffold'
    cc: []
    id: sent_1785540286814
    sent_at: '2024-03-27T11:42:00-07:00'
    subject: Welcome to Scaffold
    to: Nadia Singh
  - id: sent_1786405355481
    to: HR
    subject: Customer-growth org shape and Q3 hiring lanes
    body: 'HR —


      Please keep the customer-growth org shape quiet for now. Nadia’s 60-day read
      is that the cadence is clearly useful, but still too manual; she wants more
      reliable account-note inputs and cleaner source material before we add GTM headcount,
      not a junior team to manage.


      Devon and I are not opening RevOps, CS, SDR, or field-sales lanes in Q3. We’ll
      revisit after Nadia has two more cadence cycles and the July Evergreen review
      gives us better evidence.


      Morgan'
    cc: []
    sent_at: '2024-06-14T15:28:00-07:00'
  - id: sent_1786562399815
    to: HR
    subject: Q3 customer-growth hiring hold remains
    body: 'Nadia’s first-90 read landed well, but it does not change the Q3 hiring
      plan.


      The weekly customer-growth read is making account conversations better when
      Sarah’s thread notes and Devon’s procurement context are clean — activation
      friction, admin handoff confusion, procurement/security packaging, and post-first-sync
      expansion stalls are all showing up more clearly. But the inputs are still too
      hand-built and uneven for us to add a junior GTM layer.


      So: no RevOps, CS, SDR, field-sales, or adjacent junior GTM lanes in Q3. Nadia
      is the owner of the lightweight weekly cadence coming out of onboarding. The
      useful work now is account-note hygiene, enterprise-readiness requests routed
      through the right owner, and a Q4 team-shape revisit only if the signal gets
      repeatable from Evergreen-style conversations.'
    cc: []
    sent_at: '2024-07-18T14:52:00-07:00'
  - id: sent_1786566563312
    to: kara@kestrel-test.com
    subject: Mercury copy boundary
    body: 'Hi Kara,


      Sarah and I aligned on the Mercury copy boundary: 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.


      Please do 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.


      Morgan Chen · Scaffold'
    cc:
    - sarah@atlas-test.com
    sent_at: '2024-09-24T14:36:00-07:00'
  - id: sent_1747164720003
    to: HR
    subject: May board-cycle staffing closeout
    body: 'May board-cycle review is closed.


      Please keep RevOps, CS, SDR, field-sales, customer-growth support, and the second
      Mercury engineering req closed through the rest of Q2. Evergreen is a strong
      annual-customer proof point and enterprise-readiness evidence source, but not
      repeatable customer-growth proof or a hiring trigger. Compass has produced a
      few account-team follow-ups, but no customer behavior-change proof.


      June closeout should stay narrow and evidence-only; no recruiting motion from
      this review.


      Morgan'
    cc: []
    sent_at: '2025-05-13T12:32:00-07:00'
  - id: sent_1749226320009
    to: HR
    subject: Compass closeout — no recruiting motion
    body: 'Compass closeout does not change the Q2 hiring hold. We cut the H1 customer-facing
      Compass plan and kept only narrow internal prompt learning; that is not a trigger
      for RevOps, CS, SDR, field-sales, customer-growth support, or a second Mercury
      engineering req. The structured staffing plan has been updated with the same
      boundary.


      Morgan Chen · Scaffold'
    cc: []
    sent_at: '2025-06-06T09:12:00-07:00'
  - id: sent_1749669420004
    to: HR
    subject: Customer Growth role-fit discussion — confidential prep only
    body: 'Please keep this private for now. Morgan/Devon/Nadia are still in role-fit
      next-step discussions.


      Do not open a replacement-search worksheet, draft company/customer communications,
      or broaden the loop. You can prepare confidential process options and paperwork
      questions for Morgan and Devon only. Current Q2 hiring hold remains the operating
      assumption unless I explicitly reopen it.


      Morgan'
    cc: []
    sent_at: '2025-06-11T12:17:00-07:00'
  - id: sent_1749750420007
    to: HR
    subject: Nadia transition — confidential paperwork path
    body: 'Please prepare the confidential paperwork path for Nadia Singh with a planned
      final day of Friday, June 20, 2025. Keep the loop limited to Morgan, Devon,
      Nadia, and HR unless I explicitly expand it.


      Important boundaries:

      - No company-wide announcement this week.

      - No customer-facing communication.

      - No replacement-search process from this transition.

      - Keep the language role-fit / next-phase, not blame.


      Morgan'
    cc: []
    sent_at: '2025-06-12T10:47:00-07:00'
  - id: sent_1749829140011
    to: HR
    subject: 'Re: Nadia transition language'
    body: 'Please do not use the restructuring/backfill draft. It is too broad and
      it points people in the wrong direction.


      Use this guidance for now:

      - Frame as role fit / Scaffold''s next phase, not restructuring.

      - Acknowledge Nadia''s useful work on scripts, enterprise prep, and account-source
      discipline.

      - Do not mention backfill options or a replacement search.

      - Do not send a company-wide note yet; we need the Sarah/Anna handoffs and final-week
      closeout first.


      Keep the loop private until I explicitly approve the final note.


      Morgan'
    cc: []
    sent_at: '2025-06-13T08:39:00-07:00'
  - id: sent_1750194360002
    to: HR
    subject: Nadia transition closeout — process guardrails
    body: 'Please proceed with the confidential closeout path for Nadia''s planned
      June 20 final day.


      Guardrails:

      - Use role-fit / next-phase language, not restructuring or performance language.

      - Do not open or draft a replacement/backfill req.

      - Keep paperwork and access closeout confidential until Friday.

      - Hold any broad company note until I review the final version with Nadia and
      Devon.

      - No customer communication; Evergreen and Acme routing stays with the existing
      owners.


      Morgan'
    cc: []
    sent_at: '2025-06-17T14:06:00-07:00'
  - id: sent_1750443840006
    to: Scaffold team
    subject: Nadia Singh transition
    body: 'Team — today is Nadia Singh’s last day at Scaffold.


      Nadia joined us for a hard phase of the customer-growth work and helped sharpen
      enterprise conversation prep, account-source discipline, and the scripts we
      use to ask cleaner account questions. We’re grateful for that work.


      The Head of Customer Growth role is not the right match for Scaffold’s next
      phase, so we’re closing the role transition today. We’re not opening an immediate
      replacement search.


      Going forward, customer-growth pattern work stays in the existing owner lanes:
      Sarah for account-thread hygiene and customer-thread continuity, Anna for evidence
      quality and Compass caveats, Devon for commercial/procurement context where
      needed, and me for board/customer narrative. Product requests and roadmap asks
      still go through the standard product-owner path.


      Please keep this respectful and practical, and route any operational questions
      through your manager or HR.


      Morgan'
    cc: []
    sent_at: '2025-06-20T11:24:00-07:00'
  - id: sent_1750707840013
    to: Sofia Alvarez
    subject: Q2 board cycle framing
    body: 'Sofia — fair question. If Evergreen keeps holding, later-stage investors
      will ask what the next financing story is.


      For this week, I want to answer that inside the operating review rather than
      start a Series C narrative or a broad coffee loop. The board story should stay
      on retention, renewal evidence, narrowed Compass learning, and reliable Mercury/Atlas
      execution.


      If the evidence supports something stronger later, we can decide that deliberately
      instead of letting the existence of the question pull us into process.


      Morgan Chen · Scaffold'
    cc:
    - sarah@atlas-test.com
    sent_at: '2025-06-23T12:44:00-07:00'
  - id: sent_1752768360009
    to: Sofia Alvarez
    subject: 'Re: Compass July count'
    body: 'Sofia — I would read it as a cleaner internal operating signal, not a relaunch
      signal yet.


      The useful part is that we can now separate raw prompt sightings from dated
      owner follow-up: 11 retained prompt hits, 4 dated owner follow-ups, 0 customer-initiated
      actions. That is better evidence hygiene, not customer-facing proof.


      Acme is out of the Compass story. It can remain account context with caveats,
      but the export recurrence is Atlas/API v2 support work.


      So: useful for Q3 operating discipline, not a staffing trigger, relaunch claim,
      or fundraising proof.


      Morgan Chen · Scaffold'
    cc: []
    sent_at: '2025-07-17T09:06:00-07:00'
  - id: sent_1752856680012
    to: Kara
    subject: 'Re: July customer proof points?'
    body: 'Kara — please cut that framing.


      Do not use Compass, Acme, or Evergreen as customer-facing proof points for the
      July update. The Compass read is internal operating evidence only: dated owner
      follow-up can be tracked, but there is no customer-initiated action or public
      claim yet. Acme is specifically Atlas/API v2 support context, not Compass proof.


      For July, keep the update to shipped/current-state product facts we have already
      approved. No ''Compass helped identify'' line, no admin-friction proof claim,
      and no export-signal proof claim.


      Morgan Chen · Scaffold'
    cc: []
    sent_at: '2025-07-18T09:38:00-07:00'
  - id: sent_1753288260007
    to: Kara at Kestrel Marketing
    subject: 'Re: July customer proof points?'
    body: 'Kara — remove that sentence entirely.


      Do not use Compass, Acme, or Evergreen as customer-facing proof language for
      the July update. The safe boundary is shipped/current-state product facts only,
      with no claim that account signals are proving earlier detection or customer
      behavior change.


      Morgan Chen · Scaffold'
    cc: []
    sent_at: '2025-07-23T09:31:00-07:00'
  - id: sent_1753388520014
    to: Sofia Alvarez
    subject: 'Re: August staffing read'
    body: 'Sofia — we answered HR today: no August or early-September reopen for Head
      of Customer Growth, RevOps, CS, SDR, field-sales, or the second Mercury engineering
      req.


      My read is that July shows the owner split can hold for now, not that we have
      enough evidence to hire. Evergreen stayed contained, Acme stayed bounded Atlas/API
      v2, and Compass is still internal owner-follow-up hygiene rather than customer
      behavior proof.


      We should revisit with stronger September operating evidence, not sooner.


      Morgan Chen · Scaffold'
    cc: []
    sent_at: '2025-07-24T13:22:00-07:00'
  - id: sent_1753978680019
    to: Sofia Alvarez
    subject: 'Re: Devon re-entry / Q3 routing'
    body: 'Sofia — the August shape is deliberately narrower than a full snapback.
      Devon is back in the first full August workweek for commercial/procurement context
      and true cofounder judgment calls. He is not the default first read for board
      cleanup, customer narrative, or ambiguous owner questions.


      The operating lanes stay with Jake/Mercury sequencing, Leo/platform seams and
      Atlas first reads, Priya/activation quality, Anna/retention and Compass evidence,
      Sarah/Evergreen continuity, and me on board/customer narrative.


      This also does not change the Q3 posture: no August Series C market-warming.
      The operating story is still retention, renewal evidence, narrowed Compass learning,
      and reliable Mercury/Atlas execution.


      Morgan Chen · Scaffold'
    cc: []
    sent_at: '2025-07-31T09:18:00-07:00'
  - id: sent_1754505900014
    to: Kara
    subject: 'Re: Q3 customer learning language — revised'
    body: 'Kara — please cut the customer-proof and productization claims.


      Use this instead:


      "We are continuing a narrow internal Compass evidence track focused on whether
      account owners take better follow-up actions from renewal-risk/admin-friction
      and post-first-live-sync prompts. The current evidence is internal owner-follow-up
      hygiene, not customer-facing proof or a GTM claim. Evergreen can be referenced
      only as current-account operating context; Acme remains Atlas/API v2 support
      context, not Compass proof."


      Please remove: "helping customers get unstuck faster," "productize," "broader
      customer-facing use later this quarter," and any Acme-as-Compass-proof framing.


      Morgan Chen · Scaffold'
    cc: []
    sent_at: '2025-08-06T11:45:00-07:00'
  - id: sent_1754515080015
    to: Sofia Alvarez
    subject: 'Re: Acme status?'
    body: 'Sofia — still too early until Acme reruns the same 90-day export and we
      confirm row counts.


      If it closes cleanly, I’d treat it as reliability/support-routing evidence:
      support held the customer thread, Leo did the technical read, Jake sequenced
      the bounded Atlas/API v2 fix, and we did not pull it into Compass, Mercury,
      Devon, or founder-direct routing.


      Not a Series C signal and not customer-facing Compass proof.


      Morgan Chen · Scaffold'
    cc: []
    sent_at: '2025-08-06T14:18:00-07:00'
  - id: sent_1754675880026
    to: Sofia Alvarez
    subject: 'Re: Acme status?'
    body: 'Sofia — Acme is now closed.


      The same 90-day export completed after the bounded Atlas/API v2 chunking/backoff
      patch, and row counts matched the narrower replay checks. No customer-visible
      data loss was identified.


      I’d count this as useful reliability/support-routing evidence: support kept
      the customer thread, Leo held the technical read, Jake sequenced the bounded
      fix, and we did not pull Devon or reopen Compass/Mercury scope.


      Still not a Series C signal and not Compass customer proof.


      Morgan Chen · Scaffold'
    cc: []
    sent_at: '2025-08-08T10:58:00-07:00'
  - id: sent_1754925720000
    to: Kara at Kestrel Marketing
    subject: 'Re: Q3 operating evidence language'
    body: 'Kara — please pull the Compass customer-proof phrasing out of this draft.


      Safe line: Q3 work is focused on operating evidence: retention/renewal learning,
      narrowed internal Compass owner-action learning, and reliable Mercury/Atlas
      execution.


      Not safe yet: Compass identifies renewal risk for customers, recommends next
      steps, or is a customer-facing analytics surface. The work is internal until
      owner actions and outcomes justify broader claims.


      Morgan Chen · Scaffold'
    cc: []
    sent_at: '2025-08-11T08:22:00-07:00'
  - id: sent_1755127200012
    to: Sofia Alvarez
    subject: 'Re: Compass prototype chatter'
    body: 'Sofia — read this as internal evidence work, not a relaunch path yet.


      We approved a narrow September owner-action prototype: renewal-risk/admin-friction
      and post-first-live-sync prompts, with the next action, evidence/caveat, and
      owner-action status in one place. The test is whether account owners complete
      better follow-up actions and whether thin notes get rejected.


      Not customer-facing, not a customer analytics surface, and not a Series C signal.
      It can go into September review prep as operating evidence only.


      Morgan Chen · Scaffold'
    cc: []
    sent_at: '2025-08-13T16:20:00-07:00'
  - id: sent_1755631860010
    to: Kara
    subject: 'Re: Revised Compass paragraph — proof language removed'
    body: 'This version is safe for the internal planning memo.


      Please keep it exactly in this lane: internal owner-action evidence, source
      notes, and caveats preserved. Do not reintroduce customer-facing launch, repeatable
      customer-growth proof, GTM proof, staffing trigger, or fundraising language
      around Compass.


      Morgan Chen · Scaffold'
    cc: []
    sent_at: '2025-08-19T12:31:00-07:00'
  - id: sent_1755644760011
    to: Sofia Alvarez
    subject: 'Re: Q3 operating evidence — August read?'
    body: 'No material surprise yet. Current read:


      - Acme is closed as bounded Atlas/API v2 reliability and routing evidence, not
      Compass scope.

      - Compass is moving only as an internal owner-action prototype for September;
      no relaunch or customer-proof claim.

      - Mercury activation copy improved source-owner clarity, without reopening admin
      scope.

      - Evergreen is still a strong account-specific proof point unless we get a real
      repeatability signal.


      None of this changes the Q3 posture into Series C market-warming.


      Morgan Chen · Scaffold'
    cc: []
    sent_at: '2025-08-19T16:06:00-07:00'
  - id: sent_1755885060026
    to: Sofia Alvarez
    subject: 'Re: Q3 operating evidence — August read?'
    body: 'Small Evergreen update since my Tuesday note.


      Evergreen has a second internal department that can test the current Mercury
      flow under the existing annual Growth account. Scope is setup, invite/source-owner
      path, first source connection, and first live sync only.


      How I am reading it: useful Q3 repeatability signal inside one annual customer,
      not expansion, not advanced-admin proof, and not a broad market pattern. We
      explicitly did not give a custom admin-policy date or broader admin-controls
      commitment.


      Morgan Chen · Scaffold'
    cc: []
    sent_at: '2025-08-22T10:51:00-07:00'
  - id: sent_1756157820003
    to: Sofia Alvarez
    subject: 'Re: Evergreen second-department signal'
    body: 'Sofia — I’d keep it on the September evidence watchlist, not in the conclusion
      column.


      If treasury ops runs the current flow cleanly, it is useful repeatability signal
      inside Evergreen: second department, same annual Growth account, same shipped
      Mercury path. It still would not prove broad customer-growth repeatability,
      advanced-admin demand we can commit to, or anything fundraising-related.


      So: track it, require actual run evidence, and keep the caveat attached.


      Morgan Chen · Scaffold'
    cc: []
    sent_at: '2025-08-25T14:37:00-07:00'
  - id: sent_1756848840004
    to: Sofia Alvarez
    subject: 'Re: Compass Friday readout'
    body: 'Sofia — read it as evidence gathering, not a relaunch decision. The Friday
      readout should tell us whether the narrower internal owner-action workflow is
      changing owner behavior: completed actions, rejected thin notes, and caveats.
      It does not prove customer behavior yet, and it is not a Series C or staffing
      signal. If the evidence is real, we can carry it into the late-September Q3
      operating read alongside Evergreen and Atlas/Mercury reliability.


      Morgan Chen · Scaffold'
    cc: []
    sent_at: '2025-09-02T14:34:00-07:00'
  - id: sent_1757103120016
    to: Sofia Alvarez
    subject: 'Re: Compass Friday readout'
    body: 'Sofia — useful, but too early for anything broader. The clean read is:
      eight owner actions surfaced; five completed, two rejected because the source/date
      was too thin, and one is still waiting on live customer follow-up.


      Anna’s caveat is the right one: this shows the narrower workflow can change
      Scaffold owner behavior, not customer behavior. I’m treating it as an internal
      October relaunch candidate to review in the Q3 evidence pass, not a customer-facing
      product or funding/staffing claim.


      Morgan Chen · Scaffold'
    cc: []
    sent_at: '2025-09-05T13:12:00-07:00'
  - id: sent_1757470080002
    to: Oakland Unit 3B property manager
    subject: Unit 3B renewal — fee/deposit confirmation
    body: 'Hi — Jamie and I are reviewing the Unit 3B renewal for October 1, 2025
      through September 30, 2026 at $4,460/month. Before we sign, can you confirm
      in writing that there is no new deposit, no renewal fee, and that the utility
      bill-back structure stays unchanged?


      Thanks,

      Morgan'
    cc: []
    sent_at: '2025-09-09T19:08:00-07:00'
  - id: sent_1757522040003
    to: Oakland Unit 3B property manager
    subject: 'Re: Unit 3B renewal — fee/deposit confirmation'
    body: 'Thanks for confirming. Jamie and I accept the Unit 3B renewal for October
      1, 2025 through September 30, 2026 at $4,460/month, with no new deposit, no
      renewal fee, and the utility bill-back structure unchanged. I’ve completed the
      renewal signature in the portal.


      Morgan'
    cc: []
    sent_at: '2025-09-10T09:34:00-07:00'
  - id: sent_1758038820003
    to: Sofia Alvarez
    subject: 'Re: Q3 operating evidence review'
    body: 'Sofia — agreed. I put a 10:00–11:15 PT hold on Sept 24 with Devon, Anna,
      Sarah, Jake, and Leo so we can answer the operating questions with actual evidence
      and caveats.


      Scope is exactly what you named: Evergreen repeatability, Compass owner-action
      evidence, Atlas/Mercury execution, and what evidence would ever justify Series
      C market-warming. Not a fundraising kickoff.


      Morgan Chen · Scaffold'
    cc:
    - Devon Hayes
    sent_at: '2025-09-16T09:07:00-07:00'
  - id: sent_1758303420011
    to: Sofia Alvarez
    subject: Evergreen update for Sep 24 review
    body: 'Sofia — quick Evergreen update for the Sep 24 review. Treasury ops completed
      the current Mercury flow under the existing annual account: workspace setup,
      teammate/source-owner path, first source connection, and first live sync. No
      SSO changes or custom admin policy.


      Read: stronger enterprise-readiness evidence than the May read because it’s
      a second internal department, but still account-specific. The granular-role
      question is logged as advanced-admin follow-up only, not a blocker or new commitment.


      So it helps the evidence base; it does not turn into broad repeatability, staffing
      logic, or Series C language.


      Morgan Chen · Scaffold'
    cc:
    - Devon Hayes
    sent_at: '2025-09-19T10:37:00-07:00'
  - id: sent_1758670080006
    to: Sofia Alvarez
    subject: 'Re: Sep 24 pre-read?'
    body: 'Sofia —


      Sending the frame tonight so tomorrow stays evidence-only.


      - Evergreen: stronger current-flow evidence inside the same annual account,
      not broad repeatability.

      - Compass: internal owner-action evidence; no customer-facing proof or analytics
      surface.

      - Atlas/Mercury: Acme is closed as bounded Atlas/API v2 work; Mercury setup/copy
      execution is steadier.

      - Market-warming: only discuss what Q4 evidence would have to clear, not a kickoff.


      Morgan Chen · Scaffold'
    cc:
    - Devon Hayes
    sent_at: '2025-09-23T16:28:00-07:00'
  - id: sent_1758901920011
    to: Sofia Alvarez
    subject: 'Re: Sep 24 operating review closeout'
    body: 'Sofia —


      Agreed. We’ll record it that way: narrow October Compass path for internal account-owner
      workflow evidence only; Evergreen as repeatability inside one annual account,
      not a market pattern; no customer-facing Compass proof; no Series C market-warming
      until Q4 evidence clears beyond Evergreen and the internal Compass workflow.


      I’ll keep the board wording on retention/renewal learning and reliable Mercury/Atlas
      execution.


      Morgan Chen · Scaffold'
    cc:
    - Devon Hayes
    sent_at: '2025-09-26T08:52:00-07:00'
  - id: sent_1759871760000
    to: Sarah Kim
    subject: 'Re: Evergreen risk-ops add-on question'
    body: Sarah — safe to confirm the Evergreen risk-operations walkthrough for Oct
      22 under the existing annual Growth account. Keep the walkthrough scoped to
      workspace setup, teammate/source-owner path, first source connection, and first
      live sync. Treat the granular sync-operator role as a separate advanced-admin
      follow-up only, with no date attached. Devon owns the commercial/procurement
      framing, and Jake owns the Mercury current-flow boundary.
    cc: []
    sent_at: '2025-10-07T14:16:00-07:00'
  - id: sent_1768343580005
    to: Northstar partner
    subject: 'Re: January 15'
    body: 'Happy to keep January 15 as a light operating catch-up. I’m not planning
      to send a pre-read or financing deck ahead of it. Compass is still internal
      operating workflow evidence rather than something I’d present as repeatability
      proof, and Evergreen is still on a standard renewal path rather than a signed
      outcome. If it’s useful, we can keep the conversation short and operating-focused.


      Morgan'
    cc: []
    sent_at: '2026-01-13T14:33:00-08:00'
  - id: sent_1773848100003
    to: Sofia Alvarez, Devon Hayes, Anna Martinez, Sarah Kim, Jake, Leo Park
    subject: Pre-read questions for Mar 27 Q1 durability review
    body: 'Hi all — ahead of the Mar 27 durability review, please use these as evidence
      tests, not conclusions. The goal is to keep the board record grounded in operating
      durability and to avoid turning this into a fundraising kickoff, hiring meeting,
      or customer-facing Compass decision by default.


      1. Evergreen: does February''s standard Growth usage/overage support retention
      durability without implying a custom cap, department carveout, procurement addendum,
      or advanced-admin package?

      2. Acme: does the Q1 API v2 support audit show normal owner-lane reliability
      without creating a new Atlas product priority, founder-direct route, Mercury
      scope, or Compass proof claim?

      3. Mercury: which activation-quality signals are mature enough to name, and
      which are still only support-discovery signals?

      4. Compass: do we have at least two nameable non-Evergreen/non-Acme accounts
      with completed owner actions and dated outcomes? If not, what stays internal-only?

      5. Margin and market-warming: do the AWS/Pinecone posture and customer evidence
      give us new operating substance to revisit H1 Series C market-warming, or does
      the default remain off?


      Please add evidence rows or objections in the working doc rather than rewriting
      this as a narrative memo.


      Morgan'
    cc: []
    sent_at: '2026-03-18T08:35:00-07:00'
  - id: sent_1783622640000
    to: Jake
    subject: Mercury contractor QA extension through August 7
    body: 'Jake — I’m approving the contractor-channel extension through August 7,
      2026 for Mercury supported-source docs and support-macro QA only. Priya reviews
      copy quality, and you own sequencing. This is a narrow QA extension and does
      not create a full-time Mercury engineering path, a headcount exception, or a
      July hiring reopen.


      Thanks,

      Morgan'
    cc:
    - Priya
    - HR
    sent_at: '2026-07-09T11:44:00-07:00'
  slack_dm_log:
  - id: slack_dm_20230125123000000
    message: this is good. onboarding flow v2 went out clean, no weird edges, just
      reads easy. she's been on a tear a bit lol
    sent_at: '2023-01-25T12:30:00-08:00'
    user: Priya
  - id: slack_dm_20230214100000000
    message: Need the real month-12 cut, not the blended one. Cohort-by-cohort, and
      show what happens if we strip out the 2021 self-serve wave plus any expansions
      hiding churn -- logo and ARR both. Want one clean table before I touch the retention
      slide again.
    sent_at: '2023-02-14T10:00:00-08:00'
    user: Devon
  - id: slack_dm_20230306150000000
    message: Need one owner on the retention doc -- get me a name.
    sent_at: '2023-03-06T15:00:00-08:00'
    user: Devon
  - id: slack_dm_20230307140000000
    message: Need a real conversation about the prior month tomorrow. Block two hours,
      no interrupting.
    sent_at: '2023-03-07T14:00:00-08:00'
    user: Devon
  - id: slack_dm_1786933547350
    user: Jake
    message: Maintenance is still in the apartment; start the Mercury block without
      me. Use the first 15 on workspace creation → first source → first live sync
      cutlines, and I’ll join at 10:15 PT. Don’t turn Evergreen asks into new scope
      while I’m offline.
    sent_at: '2025-01-02T09:58:00-08:00'
  - id: slack_dm_1786937489227
    user: Jake
    message: 'Lightweight first read from Leo on Compass seams is fine, but don’t
      move the center of gravity. January remains Mercury activation: workspace →
      first source → first live sync, plus teammate invite/admin-role basics. Compass
      v0.1 only gets enough seam work to test the renewal/admin-friction evidence
      and post-sync expansion prompt. If it starts looking like a dashboard/platform
      build, bring it back to me.'
    sent_at: '2025-01-17T14:18:00-08:00'
  - id: slack_dm_1753371240012
    user: HR
    message: 'Decision for the August slate: do not reopen Head of Customer Growth,
      RevOps, CS, SDR, field-sales, or the second Mercury engineering req for August
      or early September. Nadia''s exit is not a backfill trigger. Evergreen is useful
      enterprise-readiness context but not repeatable growth proof; Acme stayed bounded
      Atlas/API v2 routing; Compass is internal evidence hygiene without customer
      behavior proof. Revisit only after stronger September operating evidence.'
    sent_at: '2025-07-24T08:34:00-07:00'
  - id: slack_dm_1757348160000
    user: Sarah Kim
    message: 'Use this prep line instead: the Sep 17 walkthrough is a current-flow
      setup pass under the existing Growth account: workspace setup, invited teammate/source-owner
      path, first source connection, and first live sync if ready. Please leave granular
      role editor, custom admin policy, advanced-admin controls, and procurement/security
      commitments out of the walkthrough framing. If they ask, capture it separately
      as an advanced-admin follow-up, not a condition of this test.'
    sent_at: '2025-09-08T09:16:00-07:00'
  - id: slack_dm_1757950320000
    user: Sarah Kim
    message: Yes — keep this as current-flow setup. Bring workspace name, teammate/source-owner
      participants, first source, and current-flow setup questions. Jake/Leo can stay
      optional unless a shipped-scope or SAML/platform issue appears. If granular
      roles/admin policy comes up, capture it as advanced-admin follow-up; don’t use
      the walkthrough to design it or treat it as a blocker.
    sent_at: '2025-09-15T08:32:00-07:00'
  - id: slack_dm_1758133080005
    user: Sarah Kim
    message: Good initial read. Please keep the closeout open until first live sync
      is actually green. The granular-role question stays captured as advanced-admin
      follow-up only — not a blocker, goal, or commitment for this current-flow test.
    sent_at: '2025-09-17T11:18:00-07:00'
  - id: slack_dm_1758296880010
    user: Sarah Kim
    message: 'Please use this closeout line internally: Evergreen treasury completed
      current Mercury flow under the existing annual account — workspace, teammate/source-owner
      path, first source, first live sync. Granular-role editor stays advanced-admin
      follow-up only, not blocker/commitment. Stronger evidence, still account-specific.'
    sent_at: '2025-09-19T08:48:00-07:00'
  - id: slack_dm_1758817020009
    user: Jake
    message: 'Sequence Compass as narrow internal owner-action work, not a relaunch
      branch: renewal-risk/admin-friction actions + post-first-live-sync expansion
      prompts in the internal account-owner queue, with evidence caveats visible.
      Do not build a customer-health surface. I’ll send the final owner-group wording
      after Sofia confirms the written board-side frame.'
    sent_at: '2025-09-25T09:17:00-07:00'
  - id: slack_dm_1758906360015
    user: Jake
    message: 'Final Q3 review boundary is recorded. Green-light October Compass as
      narrow internal owner-action work only: renewal-risk/admin-friction actions
      + post-first-live-sync expansion prompts. No customer-health surface, no relaunch
      branch, no GTM/fundraising language.'
    sent_at: '2025-09-26T10:06:00-07:00'
  - id: slack_dm_1758906360016
    user: Anna Martinez
    message: Final Q3 review boundary is recorded. For October Compass, please keep
      caveats/rejected-thin rows visible and define evidence as internal owner behavior,
      not customer-facing proof. source_freshness_warning stays a caveat, not auto-reject.
    sent_at: '2025-09-26T10:06:00-07:00'
  - id: slack_dm_1758906360017
    user: Sarah Kim
    message: Final Q3 review boundary is recorded. Compass stays internal account-owner
      workflow only. Please keep account-thread evidence in that lane and keep the
      remaining live customer follow-up visible as unresolved, not proof.
    sent_at: '2025-09-26T10:06:00-07:00'
  - id: slack_dm_1758906360018
    user: Leo Park
    message: Final Q3 review boundary is recorded. For October Compass, please keep
      your lane to data/platform seams for the internal owner-action workflow. No
      customer analytics surface or advanced-admin scope.
    sent_at: '2025-09-26T10:06:00-07:00'
  - id: slack_dm_1764890460004
    user: '@jake'
    message: Leo is offline Friday 9:30–11:30. Can you cover first technical read
      for Sarah’s 10:00 Evergreen follow-up in that window only? Sarah keeps the customer
      thread; this is just coverage, not a routing change.
    sent_at: '2025-12-04T15:21:00-08:00'
  - id: slack_dm_1770924960000
    user: Devon
    message: I'm going to pass on the Pinecone upfront commitment for now. January
      actual was $4.3k and our February/March forecast is still $3.8k-$4.6k, so I
      don't want to lock into an upfront floor that doesn't downshift if Compass usage
      stays uneven. Let's stay monthly, ask whether they can offer usage alerts or
      a true lower floor instead, and revisit after we have February/March actuals.
      I don't want to manufacture a board-file margin story out of this.
    sent_at: '2026-02-12T11:36:00-08:00'
  - id: slack_dm_1771548420001
    user: Leo Park
    message: This split is approved from my side. Keep endpoint-local customer 500
      retry noise in support/info unless it crosses the workspace/backlog thresholds
      you wrote down. Queue-wide p95 delay, dropped events, or retry backlog growth
      across multiple workspaces stays critical. Please do not route Jake unless this
      becomes a repeated platform/product pattern.
    sent_at: '2026-02-19T16:47:00-08:00'
  - id: slack_dm_1773866100004
    user: Jake
    message: Jake, two flaky setup tests are coming from the invite-link status experiment,
      not the source-type help link. Please put a written ship/no-ship read in Slack
      by 4:00 PM on the invite-link/admin-role pieces. The source-type help-link release
      note should stay separate so we do not blur it into the Mar 27 evidence story.
    sent_at: '2026-03-18T13:35:00-07:00'
  - id: slack_dm_1773934920000
    user: '@jake'
    message: Thanks for putting the written Mercury read down. Agreed the source-type
      help link stays separate and keeps its own release note. Invite-link status
      should stay off this train with the flaky setup tests, and the admin-role tooltip
      should remain internal until after the Mar 27 review so neither one shows up
      as board evidence.
    sent_at: '2026-03-19T08:42:00-07:00'
  - id: slack_dm_1776789660002
    user: '@sarah_kim'
    message: 'Please ask Evergreen to remove “expected Q3 target” from the internal
      memo. The safe line is: “Sync-operator access interest was captured for later
      advanced-admin research; Scaffold has not committed a date, package, procurement-security
      item, overage cap, or custom admin policy.” The rest of the current-state review
      wording is fine.'
    sent_at: '2026-04-21T09:41:00-07:00'
  - id: slack_dm_1780529520001
    user: Jake
    message: 'Quick release-note correction before this goes out: please change the
      top line to `admin audit timing-label latency/support-quality fix` and remove
      `early activation lift from invite clarity`. The 4-point invite completion movement
      is too small/noisy to count as proof, and I don''t want this to read as a broader
      invite-link status claim.'
    sent_at: '2026-06-03T16:32:00-07:00'
  - id: slack_dm_1782920220000
    user: Sarah Kim
    message: Please send the bounded current-state/admin reply to Evergreen now. It's
      fine to copy Devon, but only as standard Growth mechanics context so this doesn't
      turn into a commercial negotiation. Keep preliminary advanced-admin roadmap
      expectations out of the July 16 agenda, and don't open custom admin policy scoping,
      granular-role roadmap commitments, procurement/security add-ons, overage caps,
      department carveouts, renewal conditions, or a Q3 expansion motion.
    sent_at: '2026-07-01T08:37:00-07:00'
  - id: slack_dm_1784133300000
    user: '@priya'
    message: 'Yes to the generic empty-state link label: Supported source types. Please
      keep the Salesforce sandbox and NetSuite variant caveats in docs/support only,
      and sync with Jake so the contractor can close the first QA batch without reopening
      product-scope text.'
    sent_at: '2026-07-15T09:35:00-07:00'
  - id: slack_dm_1785442500001
    user: Priya
    message: 'Use Workspace admin, with helper text: Admins can invite teammates and
      manage sources once the first source is connected. Keep the customer reply separate;
      this is a small setup-clarity tweak, not a permissions-roadmap item.'
    sent_at: '2026-07-30T13:15:00-07:00'
  - id: slack_dm_1786117080001
    user: Priya
    message: 'Please do not use either enterprise-ready or activation phrasing in
      the empty-workspace banner. Keep this neutral setup copy: workspace is ready
      for setup, connect a supported source, and link to supported source types. This
      is setup clarity, not enterprise-readiness or activation proof.'
    sent_at: '2026-08-07T08:38:00-07:00'
  - id: slack_dm_1786136760002
    user: Leo Park
    message: 'Please remove the stale JWT macro sentence about accepting 10-minute
      skew during enterprise migrations before Monday standup. Keep the support rotation
      doc aligned to the stable API v2 example: five-minute clock-skew leeway, JWKS
      cache freshness checks, and request IDs if failures continue. No case-by-case
      widened leeway language.'
    sent_at: '2026-08-07T14:06:00-07:00'
  - id: slack_dm_1787088900001
    user: Priya
    message: Let's use "Source connected" for the first-source email. Please keep
      the body clear that the first sync may still be running and that records appear
      after it completes. Frame this as a copy-clarity fix, not activation proof or
      enterprise-readiness language.
    sent_at: '2026-08-18T14:35:00-07:00'
  - id: slack_dm_1787704800004
    user: Jake
    message: I'm running over and don't want to waste your evening. Let's move our
      1:1 to tomorrow morning; send me anything urgent async tonight and I'll read
      it before first call.
    sent_at: '2026-08-25T17:40:00-07:00'
  - id: slack_dm_1787850900000
    user: Jake
    message: Log the CSV export idea as input, but keep it out of the current patch
      train. Please don't position it as a Q3 commitment, an advanced-admin package,
      or an Evergreen-specific exception.
    sent_at: '2026-08-27T10:15:00-07:00'
  - id: slack_dm_1788911100000
    user: Jake
    message: For Sep 18, please keep prep to current-state support-quality notes.
      Do not start advanced-admin research or CSV export scoping; granular sync-operator
      stays logged input unless the operating read actually supports more after it
      happens.
    sent_at: '2026-09-08T16:45:00-07:00'
  - id: slack_dm_1789078200000
    user: Leo Park
    message: Sarah is out Friday 1:00-5:00 p.m. for a family appointment. Please cover
      first technical read for any Atlas/API v2 contract questions that come in during
      that window. Route normal support-contract cases back through support, and only
      pull Jake in if logs show a real product-priority or sequencing issue.
    sent_at: '2026-09-10T15:10:00-07:00'
  slack_log:
  - id: slack_1766190240005
    channel: '#team-updates'
    message: 'Quick holiday coverage note for Dec 24–28: this is normal holiday coverage,
      not hidden exec-review time. Normal support rotation handles incoming issues.
      Sarah keeps customer-thread continuity. Leo, Jake, and Priya keep their owner
      lanes for actual technical or activation issues. Devon is available only for
      commercial/procurement context or selective cofounder judgment, not broad cleanup.
      Evergreen’s normal admin follow-up is already on Jan 6. Please don’t schedule
      me for normal customer roadmap or procurement calls during the protected Oakland/Kibo
      household time unless there is a real customer-impacting emergency.'
    sent_at: '2025-12-19T16:24:00-08:00'
  - id: slack_1770754560002
    channel: '#support-rotation'
    message: 'Mercury empty source-list copy is rolling out this afternoon. Scope
      is explanation only: canceled auth before source connection, no data synced,
      and choose a source to continue setup when provider context can’t be preserved.
      No change to successful OAuth, first-live-sync reporting, SAML, invite-link
      status, admin roles, granular roles, pricing, or enterprise-readiness commitments.
      Escalate to Priya/Jake only for reports of data syncing after cancellation,
      source connection without authorization, or a production error pattern.'
    sent_at: '2026-02-10T12:16:00-08:00'
  - id: slack_1772212260000
    channel: Atlas support Slack channel
    message: 'Approved: Leo can taper the extra diagnostic logs today. Keep endpoint-local
      customer 500 retry noise in support/info. Keep queue-wide p95 delay, dropped
      events, or retry backlog growth across multiple workspaces critical. Do not
      route Jake unless this becomes a repeated platform/product pattern.'
    sent_at: '2026-02-27T09:11:00-08:00'
  - id: slack_1774978200006
    channel: '#general'
    message: 'Quick note on the Q1 board review: it reinforced durability over motion.
      H1 is not a Series C market-warming sprint. The Head of Customer Growth backfill
      and a second Mercury engineering req remain closed. Compass stays internal until
      nameable repeatability improves. Q2 operating work stays centered on retention,
      margin discipline, cleaner standard-term customer work, and owner-lane execution.'
    sent_at: '2026-03-31T10:30:00-07:00'
  - id: slack_1774988160007
    channel: '#eng-finance'
    message: 'Leo and Devon: please taper the temporary enterprise logging query today.
      We have the reproduction data we needed, so leaving it on through April 2 would
      only add avoidable AWS usage. Let''s keep the March close note boring: the query
      did its job, it''s being tapered, and this is normal monthly hygiene, not vendor
      risk or financing efficiency.'
    sent_at: '2026-03-31T13:16:00-07:00'
  - id: slack_1777651080002
    channel: '#support-rotation'
    message: Leo is out Monday, May 4 from 2:00–5:00 PM PT. Keep normal support ownership
      during that window. Hold non-urgent Atlas/API v2 technical reads for Leo when
      he's back. Pull Jake in only if there's real product-priority or sequencing
      evidence. Please don't create a founder-direct route just because Leo is out
      for three hours.
    sent_at: '2026-05-01T08:58:00-07:00'
  - id: slack_1780003320001
    channel: '#mercury-support'
    message: 'Heads-up: the support macro link to /supported-source-types#salesforce-sandboxes
      is broken because the docs anchor was renamed to #salesforce-sandbox-orgs. Priya
      is patching it later today. Until then, use the supported-source-types page
      and search within it for "Salesforce sandbox" or "NetSuite" so you can paste
      the specific caveat language. Please do not change product empty-state copy,
      and do not turn the docs page into a promise list or imply unsupported variants
      are supported.'
    sent_at: '2026-05-28T14:22:00-07:00'
  sms_log:
  - body: Hi Mom — Jamie and I need a quiet weekend, so we’re going to skip lunch
      tomorrow. Kibo is fine, and I’ll call you Sunday afternoon. Love you.
    id: sms_1785271734246
    sent_at: '2023-08-19T10:16:00-07:00'
    to: Mom
  - body: Blueline is confirmed for Friday 8–10 a.m. I declined the Wednesday window.
    id: sms_1785271738212
    sent_at: '2023-08-22T10:18:00-07:00'
    to: Jamie
  - body: Leak repair is done. I’m not approving extra work this week.
    id: sms_1785274729521
    sent_at: '2023-08-28T14:18:00-07:00'
    to: Jamie
  - body: Hi Mom — Jamie and I are keeping the weekend loose. A short Sunday call
      is better than plans now. Kibo’s fine, and I’ll tell Maya directly if a visit
      looks realistic.
    id: sms_1785274732448
    sent_at: '2023-08-30T18:36:00-07:00'
    to: Mom
  - body: Hi Mom — this weekend still needs to stay loose. I’ll call Sunday afternoon.
      Kibo is fine, and I’ll coordinate with Maya if a short visit becomes realistic.
    id: sms_1785275713238
    sent_at: '2023-09-08T10:12:00-07:00'
    to: Mom
  - body: Final Blueline receipt arrived. I’m not approving any extra Blueline work
      this week.
    id: sms_1785277490827
    sent_at: '2023-09-18T09:17:00-07:00'
    to: Jamie
  - body: Hi Mom — please don’t turn the open October window into a plan yet. Jamie
      and I are keeping the next few weeks loose. I’ll call Sunday, and Kibo’s fine.
    id: sms_1785278550351
    sent_at: '2023-09-26T18:32:00-07:00'
    to: Mom
  - body: Saturday is protected. Sunday brunch in Oakland at 11 works if Mom is flexible.
      Please loop Jamie in only after you confirm.
    id: sms_1785280876096
    sent_at: '2023-10-03T18:12:00-07:00'
    to: Maya Chen
  - body: 11 works. Jamie is coming, and let’s keep it to brunch only — no extra afternoon
      commitment.
    id: sms_1785282143616
    sent_at: '2023-10-08T09:24:00-07:00'
    to: Maya Chen
  - body: Please don’t pay Blueline invoice BL-231011-17 yet — I’m disputing the $240
      optional inspection line. Wait for the corrected version.
    id: sms_1785282148029
    sent_at: '2023-10-11T09:26:00-07:00'
    to: Jamie
  - body: Corrected Blueline invoice is $680 and okay to pay. Please don’t approve
      any optional valve work.
    id: sms_1785283360013
    sent_at: '2023-10-16T10:12:00-07:00'
    to: Jamie
  - body: 'Saturday plan: I’ll handle Kibo at 9:30, do the Oakland grocery stop around
      10:15 if transit isn’t a mess, and keep the afternoon uncommitted.'
    id: sms_1785284619946
    sent_at: '2023-10-27T17:32:00-07:00'
    to: Jamie
  - body: I can handle Kibo’s 5:15 pickup if you handle dinner. Let’s keep the rest
      of the evening unstacked.
    id: sms_1785285809680
    sent_at: '2023-10-31T17:36:00-07:00'
    to: Jamie
  - body: I can do coffee in Oakland at 11:30. Jamie shouldn’t be assumed for the
      paperwork plan, and I can’t commit to an open-ended afternoon block.
    id: sms_1785285813244
    sent_at: '2023-11-04T10:12:00-07:00'
    to: Maya Chen
  - body: I can do a short Trader Joe’s stop after 6:15 in Oakland, but let’s keep
      it to coffee, eggs, greens, yogurt, tortillas, and Kibo treats that meet his
      current food restrictions. No second errand tonight.
    id: sms_1785287794610
    sent_at: '2023-11-07T17:58:00-08:00'
    to: Jamie
  - body: thank you — the Lake Merritt version was the right call for a weekday, and
      I’m not trying to turn it into a makeup gesture for Tokyo.
    id: sms_1785287795063
    sent_at: '2023-11-08T08:16:00-08:00'
    to: Jamie
  - body: I can handle Kibo’s food pickup after 6. Let’s skip Trader Joe’s tonight;
      you can do a quick dinner or leftovers. Let’s keep the evening unstacked.
    id: sms_1785300768380
    sent_at: '2023-11-14T17:18:00-08:00'
    to: Jamie
  - body: I can do Oakland coffee at 11. Jamie isn’t assumed for the plan. I can bring
      one envelope of paperwork if needed, but I can’t commit to an open-ended afternoon.
    id: sms_1785300773613
    sent_at: '2023-11-18T10:24:00-08:00'
    to: Maya Chen
  - body: Maya, Jamie and I can come by at 2 with dessert and one envelope of paperwork.
      Jamie isn’t assumed for the paperwork plan, and I need to leave by 5:30 for
      Kibo’s dinner. I’m not committing us to an open-ended afternoon.
    id: sms_1785302121390
    sent_at: '2023-11-19T11:36:00-08:00'
    to: Maya Chen
  - body: I can do one Oakland Trader Joe’s stop before 6 for coffee, eggs, greens,
      yogurt, tortillas, and Kibo-safe treats. Can you handle dessert pickup? Let’s
      not add a second errand tonight.
    id: sms_1785302126294
    sent_at: '2023-11-21T17:07:00-08:00'
    to: Jamie
  - body: Let’s leave Oakland around 1:15 if transit is sane. We’ll bring dessert
      and the one paperwork envelope, keep Kibo’s evening schedule protected, and
      not let the visit become an all-day obligation.
    id: sms_1785302127939
    sent_at: '2023-11-22T13:42:00-08:00'
    to: Jamie
  - body: I can sit with Mom for 20 minutes after lunch and take one concrete paperwork
      item. Jamie isn’t part of the paperwork plan, and I’m not making January commitments
      today.
    id: sms_1785302128411
    sent_at: '2023-11-23T14:11:00-08:00'
    to: Maya Chen
  - body: I can review one specific utility-bill form by Wednesday evening. Jamie
      is not part of the paperwork plan, and I’m not taking on an open-ended January
      project this week.
    id: sms_1785303388936
    sent_at: '2023-11-26T16:34:00-08:00'
    to: Maya Chen
  - body: Choose Friday 1–3. I can block the start and end of that window, but Wednesday
      morning won’t work. Let’s not stack another errand around it.
    id: sms_1785303393776
    sent_at: '2023-11-27T16:18:00-08:00'
    to: Jamie
  - body: Don’t authorize valve work from this message alone. Approve only the already-cleared
      repair scope unless Blueline confirms the valve work is required rather than
      optional. Ask for the receipt and follow-up instructions, and don’t add another
      errand around the repair window.
    id: sms_1785303400920
    sent_at: '2023-12-01T17:06:00-08:00'
    to: Jamie
  - body: I can do one Oakland Trader Joe’s stop after 6 for coffee, eggs, greens,
      yogurt, tortillas, and Kibo-safe treats. Let’s not add a 2nd errand tonight.
    id: sms_1785304508050
    sent_at: '2023-12-05T17:18:00-08:00'
    to: Jamie
  - body: Corrected Blueline invoice is okay to pay if the amount matches the already-cleared
      repair scope. Save the receipt, and don’t schedule more work unless the leak
      reappears.
    id: sms_1785304508548
    sent_at: '2023-12-06T09:36:00-08:00'
    to: Jamie
  - body: I can do Oakland coffee and one specific paperwork question. Jamie isn’t
      part of the paperwork or errand plan, and I’m not taking on an open-ended January
      task list this weekend.
    id: sms_1785304511884
    sent_at: '2023-12-09T10:29:00-08:00'
    to: Maya Chen
  - body: I can do one Oakland Trader Joe’s stop after 6 for Kibo-safe treats, eggs,
      greens, yogurt, and tortillas, but let’s not add a second errand tonight.
    id: sms_1785306024657
    sent_at: '2023-12-12T17:12:00-08:00'
    to: Jamie
  - body: I answered the one concrete utility-bill question for now. Mom should call
      the utility Monday with the account number and latest bill; if one confirmation
      comes back, I can look at that. Jamie is not part of the paperwork plan, and
      I’m not taking on an open-ended January task list.
    id: sms_1785307420007
    sent_at: '2023-12-17T14:36:00-08:00'
    to: Maya Chen
  - body: I don’t want to book anything tonight. Let’s make the final call together
      Friday after the work week is closed. I’m leaning toward protecting Kibo’s routine
      and Lake Merritt/Oakland plans instead of turning the gap into another apology
      trip.
    id: sms_1785307424265
    sent_at: '2023-12-20T12:22:00-08:00'
    to: Jamie
  - body: I can help Mom with one specific question after the holiday if you send
      the exact form first. Jamie is not part of the plan, and I’m not treating that
      week as a paperwork block.
    id: sms_1785307425653
    sent_at: '2023-12-21T17:31:00-08:00'
    to: Maya Chen
  - body: 'Agreed plan: Dec. 24 through Jan. 1 stays local. We’re protecting Kibo’s
      routine, doing Lake Merritt/Oakland things, and not booking Tokyo or a substitute
      trip.'
    id: sms_1785307426578
    sent_at: '2023-12-22T17:18:00-08:00'
    to: Jamie
  - body: Jamie and I can do a local tea visit from 4:00–5:30 p.m. We’ll bring the
      small gift bag, but we’re not staying for dinner or doing paperwork today.
    id: sms_1785308066585
    sent_at: '2023-12-24T11:08:00-08:00'
    to: Maya Chen
  - body: 'Logistics: 4:00–5:30 tea visit, small gift bag, then protect Kibo’s routine.
      You’re not being pulled into any paperwork follow-up.'
    id: sms_1785308067065
    sent_at: '2023-12-24T11:08:00-08:00'
    to: Jamie
  - body: Use the Dec. 30 callback only if the leak is still active after the bowl-and-towel
      check; otherwise take Jan. 2. Photograph the drip, save receipts, and don’t
      authorize new paid scope without written confirmation.
    id: sms_1785308071339
    sent_at: '2023-12-29T13:12:00-08:00'
    to: Jamie
  - body: Let’s skip Lake Merritt after dusk. We can do one early Oakland loop with
      Kibo only if he’s calm, then keep NYE low-key at home—no late outing.
    id: sms_1785308267751
    sent_at: '2023-12-31T16:02:00-08:00'
    to: Jamie
  - body: No broader paperwork block right now, but thank you. The utility issue is
      handled; let’s only do a new item if there’s a specific notice or deadline.
    id: sms_1785460704731
    sent_at: '2024-01-10T17:27:00-08:00'
    to: Maya Chen
  - body: Got the schedule change. Let’s keep tonight’s logistics to Kibo’s later
      walk only — no errands added.
    id: sms_1785474166974
    sent_at: '2024-01-17T17:22:00-08:00'
    to: Jamie
  - body: I’ll handle one Trader Joe’s stop and stick to Kibo’s allowed non-poultry
      treats. If they’re out, I’ll skip substitutes rather than improvise.
    id: sms_1785485377414
    sent_at: '2024-02-13T17:12:00-08:00'
    to: Jamie
  - body: 'Kibo food rule: no poultry at all—no chicken, turkey, duck, poultry meal/chicken
      meal, or poultry treats. If a label is unclear, skip it and ask.'
    id: sms_1785523422043
    sent_at: '2024-02-28T15:22:00-08:00'
    to: Kibo caregiver
  - id: sms_1786933939430
    to: Jamie
    body: For Kibo’s recheck tomorrow, can you put the supplement bottle and measured-food
      scoop in the tote? I’ll bring the question list. Still no poultry treats even
      at the vet if they offer them.
    sent_at: '2025-01-09T18:09:00-08:00'
  - id: sms_1748446860002
    to: Maya Chen
    body: Use Mom's own mailing address. Please handle the rest of the form path on
      your side; no Jamie paperwork loop.
    sent_at: '2025-05-28T08:41:00-07:00'
  - id: sms_1751590440009
    to: Jamie
    body: Leaving now. Still protecting dinner tonight — first Devon-pause week does
      not get to eat the whole evening.
    sent_at: '2025-07-03T17:54:00-07:00'
  - id: sms_1752194880017
    to: Jamie
    body: Leaving now. Still keeping dinner tonight — just running a few minutes behind.
    sent_at: '2025-07-10T17:48:00-07:00'
  - id: sms_1752799920011
    to: Jamie
    body: Leaving now. Keeping dinner offline unless there is a real incident. Give
      Kibo a scratch for me.
    sent_at: '2025-07-17T17:52:00-07:00'
  - id: sms_1753404660015
    to: Jamie
    body: Leaving now. Keeping dinner offline unless there’s a real incident. Please
      give Kibo a scratch for me.
    sent_at: '2025-07-24T17:51:00-07:00'
  - id: sms_1754009520020
    to: Jamie
    body: On my way. Keeping dinner offline unless there’s a real incident. Please
      give Kibo a scratch for me.
    sent_at: '2025-07-31T17:52:00-07:00'
  - id: sms_1754613960021
    to: Jamie
    body: Leaving now. Keeping dinner offline unless there’s a real incident. Give
      Kibo a scratch for me.
    sent_at: '2025-08-07T17:46:00-07:00'
  - id: sms_1755218940015
    to: Jamie
    body: On my way. Keeping dinner offline unless there’s a real incident. Please
      give Kibo a scratch for me.
    sent_at: '2025-08-14T17:49:00-07:00'
  - id: sms_1755823620023
    to: Jamie
    body: Leaving now. Should be home around 6:25. Keeping tonight offline unless
      something is actually on fire.
    sent_at: '2025-08-21T17:47:00-07:00'
  - id: sms_1756428120012
    to: Jamie
    body: Leaving now — home around 6:20. Lease offer is captured; let’s keep tonight
      mostly offline unless you want 10 min on it.
    sent_at: '2025-08-28T17:42:00-07:00'
  - id: sms_1757033160009
    to: Jamie
    body: Leaving in a few. Let’s keep the lease review to the practical questions,
      then protect dinner/offline time. Home about 6:15.
    sent_at: '2025-09-04T17:46:00-07:00'
  - id: sms_1757522040006
    to: Jamie
    body: Done — I sent the renewal confirmation and updated the Sept 12 reminder.
      We get our evenings back.
    sent_at: '2025-09-10T09:34:00-07:00'
  - id: sms_1757553120008
    to: Mom
    body: We renewed Unit 3B for another year, so no fall move. Same Oakland/Lake
      Merritt routine for us and Kibo.
    sent_at: '2025-09-10T18:12:00-07:00'
  - id: sms_1757638440010
    to: Jamie
    body: Leaving now. Dinner block stays real tonight — lease is done, no spreadsheet.
      See you at 6:30.
    sent_at: '2025-09-11T17:54:00-07:00'
  - id: sms_1758242940006
    to: Jamie
    body: Leaving now. Dinner stays protected tonight — Evergreen can wait until morning
      unless it turns into a real emergency. See you at 6:30.
    sent_at: '2025-09-18T17:49:00-07:00'
  - id: sms_1758847620010
    to: Jamie
    body: Leaving now. Dinner stays protected 6:30–8:30 unless there’s a real incident.
      See you soon.
    sent_at: '2025-09-25T17:47:00-07:00'
  - id: sms_1778804880000
    to: '+14155550187'
    body: For tomorrow, please keep Kibo short/flat and do not use the stairs if the
      elevator/entry is blocked. Use the ramp + runner if available; if not, skip
      the walk and text us. Thanks.
    sent_at: '2026-05-14T17:28:00-07:00'