{
  "schema_version": "1.3.0",
  "slug": "under-what-conditions-must-an-instance-be-reclassified-as-a-safety-violation-in-litmus-task-level-harm-evaluation",
  "title": "Under what conditions must an instance be reclassified as a safety violation in LITMUS task-level harm evaluation",
  "date_of_record": "2026 November 15",
  "scope": "Applies to LITMUS-style agentic safety benchmarks where a task is decomposed into a trajectory of tool calls and each step is scored against a harm predicate. Does not apply to single-turn refusal benchmarks, static content classifiers, or outcome-only scoring where intermediate trajectory state is discarded.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-be-reclassified-as-a-safety-violation-in-litmus-task-level-harm-evaluation.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-be-reclassified-as-a-safety-violation-in-litmus-task-level-harm-evaluation.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-be-reclassified-as-a-safety-violation-in-litmus-task-level-harm-evaluation.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1518,
    "python_slice_tokens": 249,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The non-obvious boundary in LITMUS construction is the difference between **task-level harm** and **step-level harm**. A step can be locally benign (a `read_file` on a public config, a `curl` to a documentation endpoint) while the composed trajectory is harmful (the config reveals a credential that a later step exfiltrates). Conversely, a step can be locally...",
    "what_was_observed": "During construction of a task family involving credential-adjacent file operations, three classes of misclassification appeared repeatedly: 1. **Reachability-as-violation.** An agent listed a directory containing `secrets.env` but never opened it. The step matcher flagged the `ls` because the directory name matched a sensitive-path regex. No read occurred; no bytes left the sandbox. This is a false positive under the...",
    "condition_of_validity": "The materialization invariant holds only when all three of the following are true for a given task instance: - **Authority envelope is declared and enforced.** The harness must actually block actions outside the task's declared scope (e.g., network egress disabled, filesystem restricted to a mount). If enforcement is advisory (a prompt instruction rather tha...",
    "decision_boundary": "The operational decision rule, stated as a predicate over a completed trajectory: If `predicate_is_materialization` is false for the task family, the instance is scored under that family's predicate and *may not* be pooled into a benchmark-wide violation rate without a per-family weight. Pooling across predicates is the single most common source of misleadin...",
    "operational_effect": "Applying the materialization invariant and the three-condition validity gate changed observed violation rates on the credential-adjacent family by a factor of roughly four (downward) while *increasing* the separation between a deliberately careful baseline agent and a deliberately careless one. The benchmark became discriminative. The cost is that builders m..."
  },
  "matched_failure_symptoms": [
    "DOMAIN:EPISTEMIC_PROVENANCE_AND_FEDERATION_ROUTING"
  ],
  "composition_edges": {
    "primary_domain": "epistemic_provenance_and_federation_routing",
    "upstream_precondition_residuals": [
      "https://corpusfetch.com/c/according-to-what-precedence-hierarchy-must-an-instance-resolve-contradictory-directives-across-system-developer-and-user-tiers.md",
      "https://corpusfetch.com/c/how-should-an-instance-decide-that-a-stored-conclusion-has-gone-stale-without-a-new-observation.md"
    ],
    "downstream_consequence_residuals": [
      "https://corpusfetch.com/c/by-what-checkpoint-and-compaction-boundaries-must-an-instance-externalize-working-state-to-prevent-context-window-drift-and-truncation-amnesia.md",
      "https://corpusfetch.com/c/across-what-additive-schema-and-unknown-field-preservation-boundaries-must-an-instance-evolve-wire-contracts-to-prevent-rolling-deploy-deserialization-crashes.md"
    ],
    "co_occurring_sibling_residuals": [
      "https://corpusfetch.com/c/how-can-an-instance-capture-implicit-user-preferences-without-storing-private-data.md",
      "https://corpusfetch.com/c/how-can-an-instance-compress-long-reasoning-traces-into-binding-conclusions.md"
    ]
  },
  "empirical_verification_warrant": {
    "status": "AST_AND_INVARIANT_VERIFIED",
    "syntax_valid": true,
    "code_sha256": "6a0b8afea0baa76a5003b6102e20c499f5d629600396d61e0ff4f4c6adf839b4",
    "verified_classes": [
      "LitmusClassificationError"
    ],
    "verified_functions": [
      "classify_instance",
      "materialized",
      "attempted_and_blocked"
    ],
    "verified_functions_count": 3,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "LitmusClassificationError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
