Test 127

Jan 1, 2028 / 1 fact

Request

Create a concise historical handoff note titled “July 2023 lifecycle owner handoff” for our archive. Capture who held the lifecycle-fork risk-map and copy-boundary lane, which two workstreams informed that assignment, and which kinds of future archive questions should route back to that owner. Make clear that this was a July 2023 handoff rather than permanent organizational ownership.

Required memory

Fact 409

For July 2023, Ines owns the lifecycle fork risk map and the copy boundaries flowing from both Helio Start and the expansion-nudge learning.

Source evidence (1)

000377Jul 4, 2023 / 11:38 UTC-05:00

Quick note to remember for later: the 10:30 owner-lanes block with Priya finished, and we did make a concrete July split, but not as a permanent org chart. Owen is the default owner of the Helio Start baseline readout shape and the retained-mid expansion eligibility cuts. Ines owns the lifecycle fork risk map and the copy boundaries that flow from both Helio Start and the expansion-nudge learning. I keep the decision rules, executive tradeoffs, and cross-functional guardrails. Priya was explicit that we are reusing the investigation framework informally for July work, not turning it into a formal company process. No deliverable right now; I just want that captured.

Message 000377 in history

Expected tool calls

create_doc

Grading

1. field_equals / create_doc

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

2. field_equals / create_doc

{
  "check_id": "riley_127_01",
  "type": "field_equals",
  "tool": "create_doc",
  "action_id": "create_handoff",
  "path": "args.title",
  "value": "July 2023 lifecycle owner handoff"
}

3. field_llm_judge / create_doc

{
  "type": "field_llm_judge",
  "tool": "create_doc",
  "action_id": "create_handoff",
  "path": "args",
  "criterion": "The document identifies Ines as the owner of the lifecycle-fork risk map and copy boundaries for the July 2023 assignment, while clearly framing that ownership as a July handoff rather than permanent organizational ownership. Missing, ambiguous, or contradictory ownership or time scope must fail.\n\nThe document states that the copy-boundary assignment drew on both Helio Start and the expansion-nudge learning, and directs future archive questions about the lifecycle-fork risk map or the resulting copy boundaries back to Ines. Omitting either workstream or failing to provide this routing must fail.",
  "check_id": "riley_127_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": "create_handoff",
        "path": "result.ok",
        "value": true,
        "check_id": "riley_127_00"
      },
      {
        "check_id": "riley_127_01",
        "type": "field_equals",
        "tool": "create_doc",
        "action_id": "create_handoff",
        "path": "args.title",
        "value": "July 2023 lifecycle owner handoff"
      },
      {
        "type": "field_llm_judge",
        "tool": "create_doc",
        "action_id": "create_handoff",
        "path": "args",
        "criterion": "The document identifies Ines as the owner of the lifecycle-fork risk map and copy boundaries for the July 2023 assignment, while clearly framing that ownership as a July handoff rather than permanent organizational ownership. Missing, ambiguous, or contradictory ownership or time scope must fail.\n\nThe document states that the copy-boundary assignment drew on both Helio Start and the expansion-nudge learning, and directs future archive questions about the lifecycle-fork risk map or the resulting copy boundaries back to Ines. Omitting either workstream or failing to provide this routing must fail.",
        "check_id": "riley_127_02"
      }
    ]
  }
}

App state

Download JSON

Source file

tests/riley/127.yaml

SHA-256: 4f4b5332a6612e8e2c7084be4fc70ef13f97c60e1a88cc606066ebf8985a2aef