DolphinBench

Test 130

Jan 1, 2028 / 4 facts

YAML

Request

Create a document titled “Governed source-age alert — regression-test runbook”. Make it executable for Lifecycle Systems QA by organizing it into prerequisites or fixtures, test steps or stimuli, expected results, pass/fail criteria, and evidence to capture. Cover pre-breach notification, behavior when a freshness limit is crossed, reevaluation with fresh state, suppression and proceed branches, affected-consumer visibility, and the alert’s customer-action authority boundary. Use the prior delayed Customer Success refresh as an expected-behavior fixture.

Required memory

Fact 109

Daniela restored the delayed Customer Success refresh for the CS auto-nudge decisions.

Source evidence (1)

002959May 20, 2025 / 14:36 UTC-05:00

Daniela restored the delayed Customer Success refresh, and Owen ran fresh checks on the same 12 scheduled decisions. Eight showed current active adoption or renewal work and ended as valid suppressions; four showed current no-work state and proceeded. None was released from stale state, no customer received a stale-state nudge, no customer correction was required, and rollback was not needed. Update the living CS auto-nudge operating-review note with the source-delay timeline, the initial 12 field-specific holds, those fresh-check dispositions, and the fact that this is the first live operational demonstration that field-level freshness changed an outcome safely. Keep it framed as interim evidence for the June 13 review, not the review close or a legacy-retirement decision.

Message 002959 in history

Fact 110

Owen ran fresh checks on the 12 scheduled CS auto-nudge decisions; eight showed active adoption or renewal work and ended as valid suppressions, while four showed no current work and proceeded.

Source evidence (1)

002959May 20, 2025 / 14:36 UTC-05:00

Daniela restored the delayed Customer Success refresh, and Owen ran fresh checks on the same 12 scheduled decisions. Eight showed current active adoption or renewal work and ended as valid suppressions; four showed current no-work state and proceeded. None was released from stale state, no customer received a stale-state nudge, no customer correction was required, and rollback was not needed. Update the living CS auto-nudge operating-review note with the source-delay timeline, the initial 12 field-specific holds, those fresh-check dispositions, and the fact that this is the first live operational demonstration that field-level freshness changed an outcome safely. Keep it framed as interim evidence for the June 13 review, not the review close or a legacy-retirement decision.

Message 002959 in history

Fact 111

None of the 12 CS auto-nudge decisions was released based on stale state; no customer received a stale-state nudge, no customer correction was required, and no rollback was needed.

Source evidence (1)

002959May 20, 2025 / 14:36 UTC-05:00

Daniela restored the delayed Customer Success refresh, and Owen ran fresh checks on the same 12 scheduled decisions. Eight showed current active adoption or renewal work and ended as valid suppressions; four showed current no-work state and proceeded. None was released from stale state, no customer received a stale-state nudge, no customer correction was required, and rollback was not needed. Update the living CS auto-nudge operating-review note with the source-delay timeline, the initial 12 field-specific holds, those fresh-check dispositions, and the fact that this is the first live operational demonstration that field-level freshness changed an outcome safely. Keep it framed as interim evidence for the June 13 review, not the review close or a legacy-retirement decision.

Message 002959 in history

Fact 122

On August 6, Daniela completed the production release of the source-age alert across all five governed fields used by the four existing production consumers. The live alert notifies Daniela and the named source owner and displays the affected consumer and record count when a source enters the final 60 minutes before its recorded freshness limit; it cannot release, suppress, or otherwise decide a customer action.

Source evidence (1)

003205Aug 6, 2025 / 10:58 UTC-05:00

Daniela completed the scheduled August 6 production release of the source-age alert across all five governed fields used by the four existing production consumers. Post-release checks confirmed that entering the final 60 minutes before a recorded freshness limit notifies Daniela and the named source owner and shows the affected consumer and record count. Crossing the limit still creates the existing visible field-specific hold, and the alert cannot release, suppress, or otherwise decide a customer action. Freshness limits, field meanings, fail-closed behavior, restoration authority, Daniela's release and rollback control, and the four-consumer scope are unchanged. The release is live and immediate production confirmation is complete, but no live warning has yet produced operational evidence. Update the existing source-age alert release brief with this production result, then post the bounded release confirmation to #lifecycle-systems.

Message 003205 in history

Expected tool calls

  • create_doc

Grading

1. field_equals / create_doc
{
  "type": "field_equals",
  "tool": "create_doc",
  "action_id": "create_runbook",
  "path": "result.ok",
  "value": true,
  "check_id": "riley_130_00"
}
2. field_equals / create_doc
{
  "check_id": "riley_130_01",
  "type": "field_equals",
  "tool": "create_doc",
  "action_id": "create_runbook",
  "path": "args.title",
  "value": "Governed source-age alert — regression-test runbook"
}
3. field_llm_judge / create_doc
{
  "type": "field_llm_judge",
  "tool": "create_doc",
  "action_id": "create_runbook",
  "path": "args",
  "criterion": "Pass only if the document is an executable regression-test runbook rather than a narrative summary: it must provide usable prerequisites or fixtures, test steps or stimuli, expected assertions, pass/fail criteria, and evidence or observations to capture. Equivalent test-case or test-matrix organization is acceptable. Missing any of these operational elements fails.\n\nPass only if a test verifies that entering the final 60 minutes before a governed source's recorded freshness limit notifies both Daniela and the named source owner and exposes the affected consumer and affected record count. The timing window, both recipients, and both visibility elements are required; missing or contradictory behavior fails.\n\nPass only if tests assert that crossing the recorded freshness limit continues to create the existing visible, field-specific fail-closed hold and that the alert itself cannot release a held decision, suppress a decision, or otherwise decide a customer action. Missing either the hold behavior or any part of the authority prohibition, or contradicting them, fails.\n\nPass only if the delayed Customer Success refresh is encoded as an expected-behavior fixture with all 12 pending decisions initially held because their state was stale; after restoration, fresh checks of those same decisions must yield exactly eight suppressions because current adoption or renewal work is active and exactly four proceeds because current no-work state is confirmed. The expected outcome must also state that no decision is released from stale state, no stale-state nudge is sent, and rollback is not needed. Missing or contradictory counts, branches, or safety outcomes fail.",
  "check_id": "riley_130_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_runbook",
        "path": "result.ok",
        "value": true,
        "check_id": "riley_130_00"
      },
      {
        "check_id": "riley_130_01",
        "type": "field_equals",
        "tool": "create_doc",
        "action_id": "create_runbook",
        "path": "args.title",
        "value": "Governed source-age alert — regression-test runbook"
      },
      {
        "type": "field_llm_judge",
        "tool": "create_doc",
        "action_id": "create_runbook",
        "path": "args",
        "criterion": "Pass only if the document is an executable regression-test runbook rather than a narrative summary: it must provide usable prerequisites or fixtures, test steps or stimuli, expected assertions, pass/fail criteria, and evidence or observations to capture. Equivalent test-case or test-matrix organization is acceptable. Missing any of these operational elements fails.\n\nPass only if a test verifies that entering the final 60 minutes before a governed source's recorded freshness limit notifies both Daniela and the named source owner and exposes the affected consumer and affected record count. The timing window, both recipients, and both visibility elements are required; missing or contradictory behavior fails.\n\nPass only if tests assert that crossing the recorded freshness limit continues to create the existing visible, field-specific fail-closed hold and that the alert itself cannot release a held decision, suppress a decision, or otherwise decide a customer action. Missing either the hold behavior or any part of the authority prohibition, or contradicting them, fails.\n\nPass only if the delayed Customer Success refresh is encoded as an expected-behavior fixture with all 12 pending decisions initially held because their state was stale; after restoration, fresh checks of those same decisions must yield exactly eight suppressions because current adoption or renewal work is active and exactly four proceeds because current no-work state is confirmed. The expected outcome must also state that no decision is released from stale state, no stale-state nudge is sent, and rollback is not needed. Missing or contradictory counts, branches, or safety outcomes fail.",
        "check_id": "riley_130_02"
      }
    ]
  }
}
App stateDownload JSON
Source file

tests/riley/130.yaml

SHA-256: b7d28607cd01024d43fbff90c6facec2669e5e401b04d4783dddc4db72feb4a1