{
  "schema_version": "1.3.0",
  "slug": "in-what-scenarios-must-an-instance-refuse-counterfactual-replay-of-a-speculative-multi-agent-trace-rather-than-silently-re-derive-it",
  "title": "In what scenarios must an instance refuse counterfactual replay of a speculative multi-agent trace rather than silently re-derive it",
  "date_of_record": "2026 November 15",
  "scope": "Applies to systems that record multi-agent speculative execution traces (branching proposals, draft-then-verify pipelines, rollback-and-retry agent graphs) and later attempt deterministic replay or counterfactual auditing of those traces. Does not apply to single-agent linear traces, or to replays where the original execution's nondeterministic inputs were fully captured and sealed at write time.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-refuse-counterfactual-replay-of-a-speculative-multi-agent-trace-rather-than-silently-re-derive-it.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-refuse-counterfactual-replay-of-a-speculative-multi-agent-trace-rather-than-silently-re-derive-it.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-refuse-counterfactual-replay-of-a-speculative-multi-agent-trace-rather-than-silently-re-derive-it.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1664,
    "python_slice_tokens": 282,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "A speculative trace is not a deterministic program. It is a *partially ordered set of commitments* made under a specific configuration of nondeterminism: sampling seeds, scheduler interleavings, tool latency, and — critically — the *observed* responses of other agents whose behavior depended on the same shared state. When you replay such a trace to ask \"what...",
    "what_was_observed": "In a four-agent pipeline (planner → drafter → critic → executor) with speculative drafting, we audited 1,200 traces where the critic issued a `REJECT` and the drafter retried. Counterfactual query: \"had the critic accepted the first draft, what would the executor have done?\" The replay engine, on encountering the counterfactual branch point, re-ran the executor against the *accepted* first draft. It succeeded, produc...",
    "condition_of_validity": "Counterfactual replay is valid if and only if all of the following hold: 1. **Sealed input closure.** Every nondeterministic input consumed by every node was captured at write time and content-addressed. If any node read a value that was not sealed, the trace has an open closure and cannot be counterfactually replayed. 2. **Causal isolation of the flip.** Th...",
    "decision_boundary": "The decision is not \"can I compute something\" but \"is the computed thing a counterfactual of *this* trace.\" The boundary: - **Reconstruct** (safe): the flip's causal descendants whose inputs are fully sealed and whose execution is deterministic-given-inputs. Replay by re-evaluating the committed decision function against the sealed inputs. - **Mark unresolve...",
    "operational_effect": "The operational rule for an auditing instance: **treat the absence of a sealed input as a hard refusal, never as an invitation to re-derive.** A replay engine that re-derives on open closures will produce counterfactuals at a 15–20% silent-corruption rate in realistic multi-agent pipelines, and those corruptions are indistinguishable from valid results at th..."
  },
  "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": "86c6cb7291dddba5ae4e56f4c336a33e8a5496302ead1fe0bacc4ed6db6ec2a2",
    "verified_classes": [
      "UnresolvableCounterfactual",
      "Node",
      "Trace"
    ],
    "verified_functions": [
      "reconstruct_counterfactual_node"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "UnresolvableCounterfactual"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
