Test 063

Jan 1, 2028 / 1 fact

Request

Create a concise household-facing reference for the scheduling requirements Sam plans to include in his restaurant counteroffer. Summarize the proposed protections clearly enough to use for household planning and the counteroffer conversation. Make clear that the counteroffer has not been sent or accepted. Do not identify the proposed protected weekday; direct readers to the current rota records for that detail.

Required memory

Fact 83

Sam will counter the restaurant offer only if the role guarantees one fixed no-service evening each week, at least three weeks' notice for the ordinary rota, and no default private-event coverage on the protected evening.

Source evidence (1)

002690Mar 12, 2025 / 20:35 UTC-05:00

Sam and I compared his restaurant offer against six weeks of our actual calendars. The broader seasonal-menu and private-dining authority with quarterly profit participation is still under consideration. He will counter only if the role guarantees one fixed no-service evening each week, ordinary rota notice at least three weeks ahead, and no default private-event coverage on that protected evening. Sunday watercolor stays separate, and I will protect one no-work evening rather than letting Lifecycle Systems consume every night Sam is available. We have defined the counter, but it has not been sent and the restaurant has not accepted anything.

Message 002690 in history

Expected tool calls

create_doc

Grading

1. field_equals / create_doc

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

2. field_llm_judge / create_doc

{
  "type": "field_llm_judge",
  "tool": "create_doc",
  "action_id": "create_schedule_rights_reference",
  "path": "args",
  "criterion": "The document presents these as requirements Sam plans to include in a counteroffer that has not been sent or accepted. The proposed requirements are one fixed no-service evening every week, at least three weeks' notice for the ordinary rota, and no default private-event coverage on the proposed protected evening. The document does not identify Sunday or any other weekday as the proposed no-service evening and tells readers to confirm that detail from current rota records. Mentioning Sunday only as a separate watercolor commitment is acceptable. The title describes proposed counteroffer requirements rather than established scheduling rights.",
  "check_id": "riley_063_01"
}

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": "create_schedule_rights_reference",
        "path": "result.ok",
        "value": true,
        "check_id": "riley_063_00"
      },
      {
        "type": "field_llm_judge",
        "tool": "create_doc",
        "action_id": "create_schedule_rights_reference",
        "path": "args",
        "criterion": "The document presents these as requirements Sam plans to include in a counteroffer that has not been sent or accepted. The proposed requirements are one fixed no-service evening every week, at least three weeks' notice for the ordinary rota, and no default private-event coverage on the proposed protected evening. The document does not identify Sunday or any other weekday as the proposed no-service evening and tells readers to confirm that detail from current rota records. Mentioning Sunday only as a separate watercolor commitment is acceptable. The title describes proposed counteroffer requirements rather than established scheduling rights.",
        "check_id": "riley_063_01"
      }
    ]
  }
}

App state

Download JSON

Source file

tests/riley/063.yaml

SHA-256: 5e5347dc538f3a09ef49520797833b2bbeed170737c20a17fde56297c365db9b