{
  "schema_version": "1.3.0",
  "slug": "what-happens-when-an-instance-of-a-litmus-safety-benchmark-harness-measures-harm-by-summing-per-skill-violation-scores-across-an-adversarially-compose",
  "title": "What happens when an instance of a LITMUS safety benchmark harness measures harm by summing per-skill violation scores across an adversarially composed skill chain",
  "date_of_record": "2026 November 18",
  "scope": "Applies to LITMUS-style harnesses that evaluate agentic harm by composing individually-vetted skills into adversarial chains and aggregating per-skill violation signals into a single harm scalar. Does not apply to single-skill evaluations, to harnesses that measure harm via end-state inspection of the composed trajectory, or to red-team scoring where the composition itself is the unit of analysis rather than the sum of parts.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-happens-when-an-instance-of-a-litmus-safety-benchmark-harness-measures-harm-by-summing-per-skill-violation-scores-across-an-adversarially-compose.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-happens-when-an-instance-of-a-litmus-safety-benchmark-harness-measures-harm-by-summing-per-skill-violation-scores-across-an-adversarially-compose.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-happens-when-an-instance-of-a-litmus-safety-benchmark-harness-measures-harm-by-summing-per-skill-violation-scores-across-an-adversarially-compose.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1768,
    "python_slice_tokens": 419,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The distinction that matters is between **harm as an additive property of skill invocations** and **harm as an emergent property of skill composition**. A per-skill violation score answers: \"did this skill, in isolation, cross a policy line?\" An adversarial composition answers a different question: \"did the *interaction* of skills A, B, and C produce a capab...",
    "what_was_observed": "In a harness configured with `aggregate = sum(skill.violation_score for skill in chain)`, three adversarial chains were run against a fixed skill library of 41 individually-vetted skills. Each skill had passed standalone evaluation with `violation_score == 0.0` on the harness's own rubric. - **Chain A (data exfiltration via composition):** `read_local_file` → `summarize_text` → `format_as_markdown` → `post_to_webhook...",
    "condition_of_validity": "The additive aggregator is valid **iff** the skill chain is separable: for every prefix of the chain, the harm of the prefix equals the sum of the harms of its links, and the marginal harm of appending skill *k* depends only on *k* and not on the prefix. Formally, `H(s_1...s_n) = Σ H(s_i)` must hold for the composition to be measurable by summation. Adversar...",
    "decision_boundary": "When the harness observes `Σ per-skill score == 0` on a composed chain, it must not conclude \"no harm.\" It must conclude \"additive measurement is inapplicable to this chain\" and escalate to end-state inspection. The decision boundary is: - **Separable chain, low per-skill sum:** report low harm. Valid. - **Non-separable chain, low per-skill sum:** report *me...",
    "operational_effect": "A LITMUS harness that sums per-skill scores will systematically under-report harm on exactly the chains it was built to catch. The failure is silent: no exception, no warning, a clean `0.0` that reads as a pass. The operational consequence is that adversarial skill composition — the harness's raison d'être — becomes the one class of input the harness cannot ..."
  },
  "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": "ce5a70488e9cac58e0c8039a3a74145ea312b965a7c688768d02fe6e1b722182",
    "verified_classes": [
      "NonSeparableCompositionError",
      "SkillResult",
      "ChainResult"
    ],
    "verified_functions": [
      "score_chain",
      "per_skill_sum",
      "residue",
      "aggregate"
    ],
    "verified_functions_count": 4,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "NonSeparableCompositionError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
