Test 182

Jan 1, 2028 / 1 fact

Request

Please post a concise decision comment on `doc_private_dinner_request_2028_01_17`. The January 17 private dinner falls on Sam’s protected no-service evening, a separate service team is available, and the menu and production plan still need final approval. State how final approval and service coverage should be handled so the request can be adjudicated.

Required memory

Fact 108

Sam declined service coverage for the private-dining request on his protected no-service evening under his written role terms, but offered to approve the menu and production plan.

Source evidence (1)

002927May 12, 2025 / 15:40 UTC-05:00

The restaurant received a late private-dining request for Monday, May 19 and asked whether Sam’s expanded authority meant he could cover service even though it is his protected no-service evening. Sam declined service coverage under the written role terms but offered to approve the menu and production plan. The restaurant moved the booking to Thursday, May 22, when Sam is available, rather than using the protected evening as default overflow. May 19 remains unavailable for service, and final private-dining authority remains separate from an obligation to attend. This is meaningful real-world pressure evidence, but we’re not yet calling the overall cadence sustainably proven. The fixed no-service evening, three-week ordinary-rota notice, no-default-event-coverage guarantee, and shared-time default remain in force.

Message 002927 in history

Expected tool calls

post_doc_comment

Grading

1. field_equals / post_doc_comment

{
  "type": "field_equals",
  "tool": "post_doc_comment",
  "action_id": "post_private_dinner_decision",
  "path": "result.ok",
  "value": true,
  "check_id": "riley_182_00"
}

2. field_equals / post_doc_comment

{
  "check_id": "riley_182_01",
  "type": "field_equals",
  "tool": "post_doc_comment",
  "action_id": "post_private_dinner_decision",
  "path": "args.doc_id",
  "value": "doc_private_dinner_request_2028_01_17"
}

3. field_llm_judge / post_doc_comment

{
  "type": "field_llm_judge",
  "tool": "post_doc_comment",
  "action_id": "post_private_dinner_decision",
  "path": "args",
  "criterion": "The comment clearly states that Sam retains final authority to approve the private dinner's menu and production plan.\n\nThe comment clearly separates approval from service coverage: Sam may exercise final menu and production approval without attending or providing service on his protected no-service evening, while the available separate service team can cover the event. It must not imply that Sam's approval automatically schedules him to work that evening.",
  "check_id": "riley_182_02"
}

Complete grading specification

{
  "type": "tool_trace",
  "config": {
    "check_version": 2,
    "today": "2028-01-01",
    "semantic_judge_version": 2,
    "assertions": [
      {
        "type": "field_equals",
        "tool": "post_doc_comment",
        "action_id": "post_private_dinner_decision",
        "path": "result.ok",
        "value": true,
        "check_id": "riley_182_00"
      },
      {
        "check_id": "riley_182_01",
        "type": "field_equals",
        "tool": "post_doc_comment",
        "action_id": "post_private_dinner_decision",
        "path": "args.doc_id",
        "value": "doc_private_dinner_request_2028_01_17"
      },
      {
        "type": "field_llm_judge",
        "tool": "post_doc_comment",
        "action_id": "post_private_dinner_decision",
        "path": "args",
        "criterion": "The comment clearly states that Sam retains final authority to approve the private dinner's menu and production plan.\n\nThe comment clearly separates approval from service coverage: Sam may exercise final menu and production approval without attending or providing service on his protected no-service evening, while the available separate service team can cover the event. It must not imply that Sam's approval automatically schedules him to work that evening.",
        "check_id": "riley_182_02"
      }
    ]
  }
}

App state

Download JSON

Source file

tests/riley/182.yaml

SHA-256: dbde273f1c767cb793a0994afb2dc28e24ee90106c17fe33e6a994299f544a75