{
  "schema_version": "1.3.0",
  "slug": "what-invariants-prevent-confidence-laundering-across-verifier-chains",
  "title": "What invariants prevent confidence laundering across verifier chains?",
  "date_of_record": "2026 October 20",
  "scope": "* **Applies when:** Confidence is passed through verifier chains, chain length can be >1, and confidence inflation would mislead the receiver. * **Does not apply when:** All verifications are independent (confidence aggregates properly) or ",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-invariants-prevent-confidence-laundering-across-verifier-chains.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-invariants-prevent-confidence-laundering-across-verifier-chains.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-invariants-prevent-confidence-laundering-across-verifier-chains.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1075,
    "python_slice_tokens": 419,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The separation between **agreement through chains** (each verifier confirms the previous) and **confidence escalation** (the aggregate confidence exceeds what any single verification justifies). Relying on chains creates the **Confidence Laundering**: verifier A says \"70% confident,\" verifier B says \"I'm 90% confident A's verification is valid,\" and the chai...",
    "what_was_observed": "In verifier-chain agent architectures, failing to prevent confidence inflation produces three primary failure modes: 1. **Chain-Product Error:** The chain's confidence is computed as a product of per-link confidence. This under-reports when links are highly correlated, and over-reports when some links use confidence-favorable criteria. 2. **Attribution Escalation:** Each verifier reports confidence in its own verific...",
    "condition_of_validity": "* **Applies when:** Confidence is passed through verifier chains, chain length can be >1, and confidence inflation would mislead the receiver. * **Does not apply when:** All verifications are independent (confidence aggregates properly) or verification is binary (confident/not).",
    "decision_boundary": "1. **Does the claim's confidence pass through a verifier chain?** If no, single-verifier confidence applies. If yes, proceed. 2. **Is the chain's reported confidence greater than the minimum per-verifier confidence?** If yes, the chain has inflated confidence. 3. **Is the `chain_confidence_aggregation_method_signature` a sound statistical method?** If yes, a...",
    "operational_effect": "1. **Confidence Inflation Prevention:** Chain confidence is bounded by the weakest link (for correlated verifiers). 2. **Statistical Soundness:** Aggregation methods are verified, not just reported. 3. **Independent Recomputation:** Receivers can verify confidence rather than trust it."
  },
  "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": "623e7b1fd7d28b9b585c87c8d355aeda0d1676b4ce05ea94a713922b4ba04601",
    "verified_classes": [
      "ConfidenceVerdict",
      "VerifierLink",
      "VerifierChain",
      "ConfidencePolicy",
      "ConfidenceManifest",
      "ConfidenceLaunderingGuard"
    ],
    "verified_functions": [
      "_hash",
      "evaluate_chain"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 0,
    "raised_exceptions": [],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "enum",
      "hashlib",
      "json"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}