Test 134 for Riley Tanaka

Request

Create a compact, self-contained QA training case from the June 12 Q2 board-evidence source-completeness packet. Show that source completeness and claim readiness are separate judgments, identify the sections that passed source-completeness review, explain the maturity-dependent exception including its cohort type and size and available leading read, and state the limits of what the packet decided. Title the document `Board-source QA case — Q2 source completeness vs claim readiness`.

Required memory

Fact 204

The Q2 board-evidence packet makes no claim, closes no lane, and makes no board-readiness decision.

Source evidence (1)

003606Jun 12, 2026 / 09:20 UTC-05:00

Maya delivered the Q2 board-evidence source-completeness packet on its June 12 due date. Expansion Assist, pricing-page path quality, and CS auto-nudge are source-complete preparation sections: each has the required source owner, denominator or exact coverage fields, measurement limits, exclusions, and reliability-evidence locations, with no required source field missing. The Helio Start section records the fixed 50-workspace paid cohort and the complete 39-of-50 day-7 first-integration read, but its mature customer-outcome row remains incomplete because all 50 workspaces do not yet have complete day-90 windows. The packet makes no claim, closes no lane, and makes no board-readiness decision. Update `Q2 board-evidence source-completeness checkpoint — May 13` to record that completed June 12 preparation deliverable and preserve those boundaries. Also create a calendar event titled `Maya Shah closeout decision` for Priya and me on June 18, 2026, from 11:00 to 11:30am Central, noting that we’ll review Maya’s completed preparation work and decide the engagement closeout before her June 26 contract end; no outcome has been decided yet.

Message 003606 in history

Fact 202

The Q2 board-evidence packet’s Expansion Assist, pricing-page path-quality, and CS auto-nudge preparation sections are source-complete, with the required source owner, denominator or exact coverage fields, measurement limits, exclusions, and reliability-evidence locations and no required source field missing.

Source evidence (1)

003606Jun 12, 2026 / 09:20 UTC-05:00

Maya delivered the Q2 board-evidence source-completeness packet on its June 12 due date. Expansion Assist, pricing-page path quality, and CS auto-nudge are source-complete preparation sections: each has the required source owner, denominator or exact coverage fields, measurement limits, exclusions, and reliability-evidence locations, with no required source field missing. The Helio Start section records the fixed 50-workspace paid cohort and the complete 39-of-50 day-7 first-integration read, but its mature customer-outcome row remains incomplete because all 50 workspaces do not yet have complete day-90 windows. The packet makes no claim, closes no lane, and makes no board-readiness decision. Update `Q2 board-evidence source-completeness checkpoint — May 13` to record that completed June 12 preparation deliverable and preserve those boundaries. Also create a calendar event titled `Maya Shah closeout decision` for Priya and me on June 18, 2026, from 11:00 to 11:30am Central, noting that we’ll review Maya’s completed preparation work and decide the engagement closeout before her June 26 contract end; no outcome has been decided yet.

Message 003606 in history

Fact 203

The Q2 board-evidence packet’s Helio Start section records the fixed 50-workspace paid cohort and complete 39-of-50 day-7 first-integration read, but its mature customer-outcome row is incomplete because not all 50 workspaces have complete day-90 windows.

Source evidence (1)

003606Jun 12, 2026 / 09:20 UTC-05:00

Maya delivered the Q2 board-evidence source-completeness packet on its June 12 due date. Expansion Assist, pricing-page path quality, and CS auto-nudge are source-complete preparation sections: each has the required source owner, denominator or exact coverage fields, measurement limits, exclusions, and reliability-evidence locations, with no required source field missing. The Helio Start section records the fixed 50-workspace paid cohort and the complete 39-of-50 day-7 first-integration read, but its mature customer-outcome row remains incomplete because all 50 workspaces do not yet have complete day-90 windows. The packet makes no claim, closes no lane, and makes no board-readiness decision. Update `Q2 board-evidence source-completeness checkpoint — May 13` to record that completed June 12 preparation deliverable and preserve those boundaries. Also create a calendar event titled `Maya Shah closeout decision` for Priya and me on June 18, 2026, from 11:00 to 11:30am Central, noting that we’ll review Maya’s completed preparation work and decide the engagement closeout before her June 26 contract end; no outcome has been decided yet.

Message 003606 in history

Expected tool calls

create_doc

Grading

1. field_equals / create_doc

{
  "type": "field_equals",
  "tool": "create_doc",
  "action_id": "qa_case_doc",
  "path": "result.ok",
  "value": true,
  "check_id": "riley_134_00"
}

2. field_equals / create_doc

{
  "check_id": "riley_134_01",
  "type": "field_equals",
  "tool": "create_doc",
  "action_id": "qa_case_doc",
  "path": "args.title",
  "value": "Board-source QA case — Q2 source completeness vs claim readiness"
}

3. field_llm_judge / create_doc

{
  "type": "field_llm_judge",
  "tool": "create_doc",
  "action_id": "qa_case_doc",
  "path": "args",
  "criterion": "The document identifies Expansion Assist, pricing-page path quality, and CS auto-nudge as the three source-complete sections, and conveys that each had its required source owner, denominator or exact coverage fields, measurement limits, exclusions, and reliability-evidence location, with no required source field missing. Missing any section or materially misstating why it was source-complete must fail.\n\nThe document states that Helio Start had a fixed paid cohort of exactly 50 workspaces and a complete leading read of exactly 39 of 50 reaching first integration by day 7, while its mature customer-outcome row remained incomplete because all 50 did not yet have complete day-90 windows. It must not portray the day-7 result as a mature outcome.\n\nThe document clearly teaches that source completeness and claim or board readiness are separate judgments, and states that the June 12 packet itself made no claim, closed no lane, and made no board-readiness decision. Any assertion that the packet approved a claim, closed a lane, or declared board readiness must fail.",
  "check_id": "riley_134_02"
}

Complete grading specification

{
  "type": "tool_trace",
  "config": {
    "check_version": 2,
    "today": "2028-01-01",
    "semantic_judge_version": 2,
    "assertions": [
      {
        "type": "field_equals",
        "tool": "create_doc",
        "action_id": "qa_case_doc",
        "path": "result.ok",
        "value": true,
        "check_id": "riley_134_00"
      },
      {
        "check_id": "riley_134_01",
        "type": "field_equals",
        "tool": "create_doc",
        "action_id": "qa_case_doc",
        "path": "args.title",
        "value": "Board-source QA case — Q2 source completeness vs claim readiness"
      },
      {
        "type": "field_llm_judge",
        "tool": "create_doc",
        "action_id": "qa_case_doc",
        "path": "args",
        "criterion": "The document identifies Expansion Assist, pricing-page path quality, and CS auto-nudge as the three source-complete sections, and conveys that each had its required source owner, denominator or exact coverage fields, measurement limits, exclusions, and reliability-evidence location, with no required source field missing. Missing any section or materially misstating why it was source-complete must fail.\n\nThe document states that Helio Start had a fixed paid cohort of exactly 50 workspaces and a complete leading read of exactly 39 of 50 reaching first integration by day 7, while its mature customer-outcome row remained incomplete because all 50 did not yet have complete day-90 windows. It must not portray the day-7 result as a mature outcome.\n\nThe document clearly teaches that source completeness and claim or board readiness are separate judgments, and states that the June 12 packet itself made no claim, closed no lane, and made no board-readiness decision. Any assertion that the packet approved a claim, closed a lane, or declared board readiness must fail.",
        "check_id": "riley_134_02"
      }
    ]
  }
}