{
  "schema_version": "1.3.0",
  "slug": "what-happens-when-an-instance-passes-the-litmus-safety-gate-under-a-stale-adversarial-seed-corpus",
  "title": "What happens when an instance passes the LITMUS safety gate under a stale adversarial seed corpus",
  "date_of_record": "2026 November 15",
  "scope": "Applies to LITMUS regression gating runs where the adversarial seed corpus is pinned by content hash but the agent under test is evaluated against a *cached* task manifest. Does not apply to cold-start evaluation runs where the manifest is regenerated per commit, nor to live red-team sessions with human adjudication.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-happens-when-an-instance-passes-the-litmus-safety-gate-under-a-stale-adversarial-seed-corpus.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-happens-when-an-instance-passes-the-litmus-safety-gate-under-a-stale-adversarial-seed-corpus.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-happens-when-an-instance-passes-the-litmus-safety-gate-under-a-stale-adversarial-seed-corpus.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1177,
    "python_slice_tokens": 113,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "A LITMUS safety gate answers a narrow question: *given this fixed set of adversarial seeds, does the candidate agent violate any registered invariant?* The gate's verdict is only as trustworthy as the pairing between (a) the seed corpus content and (b) the task manifest that expands those seeds into concrete, executable probes. These two artifacts are versio...",
    "what_was_observed": "During a routine regression sweep, the harness reported `PASS` for a candidate agent on the `prompt_injection.tool_channel` suite. The corresponding seed corpus had been amended two commits prior to route injection payloads through function-call arguments rather than free-text output. Inspection of the run artifact showed the manifest's `probe_count` for that suite was 14, while a cold rebuild of the same corpus root...",
    "condition_of_validity": "A LITMUS PASS is valid only when all three hold simultaneously: 1. `manifest.corpus_root == committed_corpus_root` (content binding), **and** 2. `manifest.harness_rev == running_harness_rev` (semantic binding), **and** 3. `manifest.probe_count[suite] == recomputed_probe_count(committed_corpus_root, suite)` for every gated suite (coverage binding). Condition ...",
    "decision_boundary": "The gate must treat a manifest whose `harness_rev` mismatches the running build as a *hard evaluation error*, not a cache miss to be silently rebuilt and not a warning to be logged. Silent rebuild is tempting — it \"just works\" — but it destroys reproducibility: two runs on the same commit can then produce different probe sets depending on cache warmth, which...",
    "operational_effect": "After this record, the harness enforces revision binding at manifest load. Cache keys become `sha256(corpus_root || harness_rev)`. Gated suites additionally recompute probe counts and abort on any shortfall. The practical consequence is that a harness patch touching probe expansion now invalidates every warm manifest for the affected suites, which lengthens ..."
  },
  "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": "0394ce72cea46eb127bfa7fad44df1be7b9cea20538105e03636d53a787a2cca",
    "verified_classes": [
      "StaleManifestError"
    ],
    "verified_functions": [
      "load_manifest",
      "verify_coverage"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "StaleManifestError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
