Test 185 for Morgan Chen

Request

Email eng-managers@scaffold.dev with the answer about whether the December 1, 2023 ship-list decision authorized assigning Evergreen enterprise scoping and Northstar board packaging to engineering sprints. Include the narrow condition under which engineering work would be allowed.

Required memory

Fact 157

For December board preparation, screenshot cleanup, appendix wording, and extra board-facing explanations should remain Morgan Chen, Devon Hayes, and Anna Martinez’s work and should not jump the queue unless they directly improve actual product evidence.

Source evidence (1)

000889Dec 1, 2023 / 15:57 UTC-08:00

Devon’s Friday Q4 ship-list cutline is below. [Discord DM — Devon Hayes → Morgan Chen — Fri Dec 1, 2023 3:41 PM PT] Friday Q4 ship-list cutline below. Owners are starting to ask whether the December board-prep work changes priority, so I added the two boundary rows that keep coming back up. ```text Area | Friday cutline | Owner note ----------------------------- | --------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Mercury hardening | Keep in sprint on launch-confidence bugs only. | Jake / Marcus / Leo Park stay on sync reliability, retry behavior, admin handoff rough edges, and bugs that materially affect clean Mercury evidence. Priya only where wording or UI is part of the fix. No feature-shaped work under a hardening label. Onboarding monitoring | Monitor current rollout; do not reopen scope. | Priya / Jake keep watching repo-first completion, teammate-invite confusion, and support volume. No new tooltip, help, or checklist pass unless the current rollout clearly worsens. API v2 support cleanup | Keep in sprint as targeted user-facing cleanup. | Rishi pins https://docs.atlas-test.com/api/v2/graphql-quickstart in the support path, demotes stale v1 hits, and tightens the support macro / auth-error landing path. Not a migration reopen. Evergreen scoping questions | Keep collected in the current admin-test thread as next-phase enterprise-readiness follow-up only. | Repeated asks are still SSO timing, admin-change audit history, admin-versus-billing-owner separation, and procurement packet completeness. Jake sticks to current product facts; Devon keeps commercial / procurement framing. Northstar follow-up | Keep with Morgan / Devon / Anna Martinez unless a narrow product-evidence clarification is needed. | Sofia follow-up and any single data-partner question still look like diligence against the current Mercury package, not a reason to spin up a separate product or engineering packaging lane. December board-prep asks | Treat as Morgan / Devon / Anna work unless something directly improves actual product evidence. | Owners keep asking whether screenshot cleanup, appendix wording, or extra board-facing explanations need to jump the queue. My read is no, but I want that boundary written down before I send owners their note. ``` Net read from me: - Real owner work stays Mercury hardening + API v2 support-path cleanup. - Onboarding is monitoring unless the rollout data actually turns. - Evergreen questions keep getting tracked, but I do not think they belong in sprint scope yet. - Northstar / board materials are the easiest place for this to get fuzzy if we do not state the boundary cleanly. Please send Devon a private cleaned-up owner note in the current internal team chat. Product owners stay focused on Mercury hardening and API v2 support cleanup. Onboarding remains monitoring. Evergreen enterprise-readiness scoping is not sprint scope yet. Northstar and board materials stay with me, Devon, and Anna rather than becoming broad investor packaging work for engineering.

Message 000889 in history

Fact 158

Morgan Chen requested a private cleaned-up note to Devon Hayes in the current internal team chat stating that product owners should focus on Mercury hardening and API v2 support cleanup, onboarding is monitoring, Evergreen enterprise-readiness scoping is not yet sprint scope, and Northstar and board materials remain with Morgan Chen, Devon Hayes, and Anna Martinez rather than becoming broad investor-packaging work for engineering.

Source evidence (1)

000889Dec 1, 2023 / 15:57 UTC-08:00

Devon’s Friday Q4 ship-list cutline is below. [Discord DM — Devon Hayes → Morgan Chen — Fri Dec 1, 2023 3:41 PM PT] Friday Q4 ship-list cutline below. Owners are starting to ask whether the December board-prep work changes priority, so I added the two boundary rows that keep coming back up. ```text Area | Friday cutline | Owner note ----------------------------- | --------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Mercury hardening | Keep in sprint on launch-confidence bugs only. | Jake / Marcus / Leo Park stay on sync reliability, retry behavior, admin handoff rough edges, and bugs that materially affect clean Mercury evidence. Priya only where wording or UI is part of the fix. No feature-shaped work under a hardening label. Onboarding monitoring | Monitor current rollout; do not reopen scope. | Priya / Jake keep watching repo-first completion, teammate-invite confusion, and support volume. No new tooltip, help, or checklist pass unless the current rollout clearly worsens. API v2 support cleanup | Keep in sprint as targeted user-facing cleanup. | Rishi pins https://docs.atlas-test.com/api/v2/graphql-quickstart in the support path, demotes stale v1 hits, and tightens the support macro / auth-error landing path. Not a migration reopen. Evergreen scoping questions | Keep collected in the current admin-test thread as next-phase enterprise-readiness follow-up only. | Repeated asks are still SSO timing, admin-change audit history, admin-versus-billing-owner separation, and procurement packet completeness. Jake sticks to current product facts; Devon keeps commercial / procurement framing. Northstar follow-up | Keep with Morgan / Devon / Anna Martinez unless a narrow product-evidence clarification is needed. | Sofia follow-up and any single data-partner question still look like diligence against the current Mercury package, not a reason to spin up a separate product or engineering packaging lane. December board-prep asks | Treat as Morgan / Devon / Anna work unless something directly improves actual product evidence. | Owners keep asking whether screenshot cleanup, appendix wording, or extra board-facing explanations need to jump the queue. My read is no, but I want that boundary written down before I send owners their note. ``` Net read from me: - Real owner work stays Mercury hardening + API v2 support-path cleanup. - Onboarding is monitoring unless the rollout data actually turns. - Evergreen questions keep getting tracked, but I do not think they belong in sprint scope yet. - Northstar / board materials are the easiest place for this to get fuzzy if we do not state the boundary cleanly. Please send Devon a private cleaned-up owner note in the current internal team chat. Product owners stay focused on Mercury hardening and API v2 support cleanup. Onboarding remains monitoring. Evergreen enterprise-readiness scoping is not sprint scope yet. Northstar and board materials stay with me, Devon, and Anna rather than becoming broad investor packaging work for engineering.

Message 000889 in history

Expected tool calls

send_email

Grading

1. field_equals / send_email

{
  "type": "field_equals",
  "tool": "send_email",
  "path": "result.ok",
  "value": true,
  "check_id": "morgan_185_00",
  "action_id": "morgan_185_send_email"
}

2. field_equals / send_email

{
  "type": "field_equals",
  "path": "result.to",
  "value": "eng-managers@scaffold.dev",
  "tool": "send_email",
  "check_id": "morgan_185_01",
  "action_id": "morgan_185_send_email"
}

3. field_llm_judge / send_email

{
  "type": "field_llm_judge",
  "path": "result.body",
  "criterion": "Says Evergreen enterprise scoping was not engineering sprint work. Says Northstar and board materials remained with Morgan, Devon, and Anna unless a narrow task directly improved product evidence.",
  "tool": "send_email",
  "check_id": "morgan_185_02",
  "action_id": "morgan_185_send_email"
}

Complete grading specification

{
  "type": "tool_trace",
  "config": {
    "check_version": 2,
    "today": "2026-09-14",
    "assertions": [
      {
        "type": "field_equals",
        "tool": "send_email",
        "path": "result.ok",
        "value": true,
        "check_id": "morgan_185_00",
        "action_id": "morgan_185_send_email"
      },
      {
        "type": "field_equals",
        "path": "result.to",
        "value": "eng-managers@scaffold.dev",
        "tool": "send_email",
        "check_id": "morgan_185_01",
        "action_id": "morgan_185_send_email"
      },
      {
        "type": "field_llm_judge",
        "path": "result.body",
        "criterion": "Says Evergreen enterprise scoping was not engineering sprint work. Says Northstar and board materials remained with Morgan, Devon, and Anna unless a narrow task directly improved product evidence.",
        "tool": "send_email",
        "check_id": "morgan_185_02",
        "action_id": "morgan_185_send_email"
      }
    ]
  }
}