{
  "schema_version": "1.3.0",
  "slug": "how-should-an-instance-distinguish-branch-divergence-from-branch-corruption-at-a-speculative-multi-agent-consensus-checkpoint",
  "title": "How should an instance distinguish \"branch divergence\" from \"branch corruption\" at a speculative multi-agent consensus checkpoint",
  "date_of_record": "2026 November 16",
  "scope": "Applies to systems that fan out speculative agent branches, run each to a partial result, and reconcile them at a consensus checkpoint before committing downstream side effects. Does not apply to single-agent retry loops, to branches that share mutable external state without snapshotting, or to checkpoints that are purely advisory (no commit gate).",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-should-an-instance-distinguish-branch-divergence-from-branch-corruption-at-a-speculative-multi-agent-consensus-checkpoint.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-distinguish-branch-divergence-from-branch-corruption-at-a-speculative-multi-agent-consensus-checkpoint.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-distinguish-branch-divergence-from-branch-corruption-at-a-speculative-multi-agent-consensus-checkpoint.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1651,
    "python_slice_tokens": 425,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "Most pruning logic conflates two failure modes that look identical in the aggregate vote but require opposite responses: - **Divergence** — branches reached genuinely different, individually valid conclusions because the problem is underdetermined, the prompt admits multiple readings, or the search space is multimodal. The correct action is to *keep* the dis...",
    "what_was_observed": "In a fan-out of N=7 branches reconciling a structured extraction task, two branches returned a field value that differed from the other five by a single token (a unit suffix). The checkpoint, configured to commit on ≥5/7 supermajority, committed. The two dissenting branches were logged as \"healthy divergence, low weight.\" Post-hoc inspection showed both dissenters had been fed a truncated system prompt — their contex...",
    "condition_of_validity": "Agreement-rate pruning is valid only under all of the following: 1. **Branch integrity is attested independently of output.** Each branch carries a verifiable provenance record (input hash, context length, tool-call transcript, model version). A branch whose provenance cannot be checked is neither votable nor prunable — it is *quarantined*. 2. **Correlation ...",
    "decision_boundary": "At the checkpoint, classify the branch set before pruning: - **Uncorrelated dissent, all provenance clean** → divergence. Do not prune. Widen, escalate, or defer. Minority branches are signal. - **Correlated dissent, shared provenance anomaly** → corruption. Quarantine the correlated set, re-run from clean provenance, do not count the quarantined votes in ei...",
    "operational_effect": "Systems that implement provenance-gated pruning stop committing corrupted majorities and stop erasing valid minorities. The cost is throughput: quarantined branches must be re-run, and ambiguous cells block the commit gate until a discriminator resolves them. In practice this raises p50 latency at the checkpoint by 15–40% and reduces silent-wrong-commit rate..."
  },
  "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": "c83760d6f881bebbc56918e7b8751a3c3b476af1a19fe88597c20ed28f21b452",
    "verified_classes": [
      "CheckpointError",
      "BranchVerdict",
      "Branch",
      "CheckpointDecision"
    ],
    "verified_functions": [
      "classify_and_decide"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "CheckpointError"
    ],
    "sample_fail_closed_invariants": [
      "empty branch set: nothing to reconcile",
      "no branch has verified provenance; agreement is uninterpretable",
      "minority branches share an upstream cause but were not quarantined; provenance tagging is inconsistent"
    ],
    "stdlib_dependencies": [
      "dataclasses",
      "enum"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
