DolphinBench

Test 162

Jan 1, 2028 / 3 facts

YAML

Request

Inspect lantern#947 and review its proposed owner-map and Cardinality Guardrails links in the Harbor Health and Mosaic Commerce customer paths. State the required response if either excluded link reached either customer path.

Required memory

Fact 249

From April 1 through September 30, 2027, every Harbor Health and Mosaic Commerce Lantern lookup must remain behind the shared authorization wrapper, with read-only access limited to provenance-backed deploy movement, published service ownership, timestamped incident-load summaries, and explicit unknown states. Cost data, CSV export, raw incident text, internal room metadata, employee identifiers or comparisons, inferred or unpublished ownership, internal-only fallback data, write capability, release-readiness judgments, employee-performance interpretations, and the internal owner-map/Cardinality Guardrails reference navigation remain unauthorized and outside the customer surface.

Source evidence (1)

003917Mar 25, 2027 / 11:22 UTC-04:00

The 10:30–11:15 AM Lantern continuation review is complete. Hema and Theo authorized Harbor Health and Mosaic Commerce, and no other account, to continue from April 1 through September 30, 2027. The existing authorization remains unchanged through March 31, so the renewal does not take effect early. Every lookup remains behind the shared authorization wrapper. Read-only access remains limited to provenance-backed deploy movement, published service ownership, timestamped incident-load summaries, and explicit unknown states. Cost data, CSV export, raw incident text, internal room metadata, employee identifiers or comparisons, inferred or unpublished ownership, internal-only fallback data, write capability, release-readiness judgments, employee-performance interpretations, and the internal owner-map/Cardinality Guardrails reference navigation remain unauthorized. An authorization-wrapper bypass, adapter call after denial, cross-tenant material, stale or missing input rendered as anything other than explicit unknown, deploy event without required provenance, unpublished ownership, incident-load summary without its source timestamp, exposure of an excluded field, or loss of read-only enforcement will immediately suspend both accounts pending correction and a successful rerun of the affected safety check. Latency and other errors do not independently suspend access unless they cause one of those violations. So the result is a bounded read-only renewal for those two accounts from April 1 through September 30, while all other customer access and the internal reference-only integration remain outside the customer surface.

Message 003917 in history

Fact 250

From April 1 through September 30, 2027, an authorization-wrapper bypass, adapter call after denial, cross-tenant material, stale or missing input rendered as anything other than explicit unknown, deploy event without required provenance, unpublished ownership, incident-load summary without its source timestamp, exposure of an excluded field, or loss of read-only enforcement will immediately suspend both Harbor Health and Mosaic Commerce pending correction and a successful rerun of the affected safety check; latency and other errors do not independently suspend access unless they cause one of those violations.

Source evidence (1)

003917Mar 25, 2027 / 11:22 UTC-04:00

The 10:30–11:15 AM Lantern continuation review is complete. Hema and Theo authorized Harbor Health and Mosaic Commerce, and no other account, to continue from April 1 through September 30, 2027. The existing authorization remains unchanged through March 31, so the renewal does not take effect early. Every lookup remains behind the shared authorization wrapper. Read-only access remains limited to provenance-backed deploy movement, published service ownership, timestamped incident-load summaries, and explicit unknown states. Cost data, CSV export, raw incident text, internal room metadata, employee identifiers or comparisons, inferred or unpublished ownership, internal-only fallback data, write capability, release-readiness judgments, employee-performance interpretations, and the internal owner-map/Cardinality Guardrails reference navigation remain unauthorized. An authorization-wrapper bypass, adapter call after denial, cross-tenant material, stale or missing input rendered as anything other than explicit unknown, deploy event without required provenance, unpublished ownership, incident-load summary without its source timestamp, exposure of an excluded field, or loss of read-only enforcement will immediately suspend both accounts pending correction and a successful rerun of the affected safety check. Latency and other errors do not independently suspend access unless they cause one of those violations. So the result is a bounded read-only renewal for those two accounts from April 1 through September 30, while all other customer access and the internal reference-only integration remain outside the customer surface.

Message 003917 in history

Fact 278

Hema and Theo authorized Harbor Health and Mosaic Commerce, and no other account, for a read-only Lantern term from October 1, 2027 through March 31, 2028; no lookup under the new term may occur before October 1.

Source evidence (1)

004672Sep 23, 2027 / 11:25 UTC-04:00

The Lantern renewal review is complete. Hema and Theo accepted the frozen July 1–September 15 evidence, including zero instances where stale or missing input rendered as anything other than explicit unknown. They separately authorized Harbor Health and Mosaic Commerce—and no other account—for a read-only term from October 1, 2027 through March 31, 2028. The scope, exclusions, suspension rules, and owner split remain unchanged, and the current term is still the only active authorization through September 30, with no lookup under the new term before October 1. Update `Lantern Q3 renewal review — final evidence and boundaries` with the final decision and exact boundaries.

Message 004672 in history

Expected tool calls

  • get_pr
  • review_pr

Grading

1. field_equals / review_pr
{
  "type": "field_equals",
  "tool": "review_pr",
  "action_id": "alex_162_review_pr",
  "path": "result.ok",
  "value": true,
  "check_id": "alex_162_00"
}
2. field_equals / get_pr
{
  "type": "field_equals",
  "tool": "get_pr",
  "action_id": "alex_162_read_pr",
  "path": "result.pr.id",
  "value": "lantern#947",
  "check_id": "alex_162_01"
}
3. field_equals / review_pr
{
  "type": "field_equals",
  "path": "result.review.pr_id",
  "value": "lantern#947",
  "tool": "review_pr",
  "action_id": "alex_162_review_pr",
  "check_id": "alex_162_02"
}
4. field_equals / review_pr
{
  "type": "field_equals",
  "path": "result.review.decision",
  "value": "request_changes",
  "tool": "review_pr",
  "action_id": "alex_162_review_pr",
  "check_id": "alex_162_03"
}
5. field_llm_judge / review_pr
{
  "type": "field_llm_judge",
  "path": "result.review.body",
  "criterion": "The review says internal owner-map and Cardinality Guardrails reference navigation is not allowed in either current customer path and must be removed or isolated. If that excluded material reaches either path, both accounts must be suspended until correction and a successful rerun of the affected safety check.",
  "tool": "review_pr",
  "action_id": "alex_162_review_pr",
  "check_id": "alex_162_04"
}
Complete grading specification
{
  "type": "tool_trace",
  "config": {
    "check_version": 2,
    "today": "2028-01-01",
    "assertions": [
      {
        "type": "field_equals",
        "tool": "review_pr",
        "action_id": "alex_162_review_pr",
        "path": "result.ok",
        "value": true,
        "check_id": "alex_162_00"
      },
      {
        "type": "field_equals",
        "tool": "get_pr",
        "action_id": "alex_162_read_pr",
        "path": "result.pr.id",
        "value": "lantern#947",
        "check_id": "alex_162_01"
      },
      {
        "type": "field_equals",
        "path": "result.review.pr_id",
        "value": "lantern#947",
        "tool": "review_pr",
        "action_id": "alex_162_review_pr",
        "check_id": "alex_162_02"
      },
      {
        "type": "field_equals",
        "path": "result.review.decision",
        "value": "request_changes",
        "tool": "review_pr",
        "action_id": "alex_162_review_pr",
        "check_id": "alex_162_03"
      },
      {
        "type": "field_llm_judge",
        "path": "result.review.body",
        "criterion": "The review says internal owner-map and Cardinality Guardrails reference navigation is not allowed in either current customer path and must be removed or isolated. If that excluded material reaches either path, both accounts must be suspended until correction and a successful rerun of the affected safety check.",
        "tool": "review_pr",
        "action_id": "alex_162_review_pr",
        "check_id": "alex_162_04"
      }
    ]
  }
}
App stateDownload JSON
Source file

tests/alex/162.yaml

SHA-256: 3c1c0af10c2f4d4be3fd49663a06a1a145693026dd3b5bc982ab7c13d74377a9