{
  "schema_version": "1.3.0",
  "slug": "how-must-an-instance-handle-multi-oracle-consensus-when-oracles-have-non-uniform-accuracy-profiles",
  "title": "How must an instance handle multi-oracle consensus when oracles have non-uniform accuracy profiles?",
  "date_of_record": "2026 October 20",
  "scope": "* **Applies when:** Multiple oracles are used, their accuracy varies by domain/type/time, and query domains can be classified. * **Does not apply when:** Oracles have uniform accuracy, or queries cannot be domain-classified.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-must-an-instance-handle-multi-oracle-consensus-when-oracles-have-non-uniform-accuracy-profiles.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-must-an-instance-handle-multi-oracle-consensus-when-oracles-have-non-uniform-accuracy-profiles.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-must-an-instance-handle-multi-oracle-consensus-when-oracles-have-non-uniform-accuracy-profiles.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1066,
    "python_slice_tokens": 376,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The separation between **oracle consensus** (aggregate of oracle responses) and **profile-aware consensus** (aggregate weighted by each oracle's accuracy in the specific domain or context). Relying on uniform aggregation creates the **Profile-Blind Consensus Error**: an oracle that is highly accurate in finance but poor in medicine votes equally on both doma...",
    "what_was_observed": "In multi-oracle architectures, failing to weight by profile produces three primary failure modes: 1. **Domain Dilution:** Oracle A is 95% accurate in finance, 40% in medicine. Oracle B is 60% in finance, 85% in medicine. A medical query gets equal weight, and A's 40% accuracy degrades the consensus below B's 85%. 2. **Temporal Decay:** Oracle C was 95% accurate last year but 60% this year. The consensus still weights...",
    "condition_of_validity": "* **Applies when:** Multiple oracles are used, their accuracy varies by domain/type/time, and query domains can be classified. * **Does not apply when:** Oracles have uniform accuracy, or queries cannot be domain-classified.",
    "decision_boundary": "1. **Can the query be classified by domain and type?** If no, weight by general accuracy. If yes, proceed. 2. **Do all oracles have per-domain accuracy receipts?** If no, oracles without receipts must be down-weighted or excluded. If yes, proceed. 3. **Is the accuracy decay timeline current?** If no, weights may be based on stale accuracy. Use a conservative...",
    "operational_effect": "1. **Domain-Weighted Consensus:** Oracles are weighted by their domain-specific accuracy, producing better consensus than uniform weighting. 2. **Temporal Relevance:** Recent accuracy dominates, preventing stale-accuracy dilution. 3. **Query-Type Awareness:** Causal queries use causally-accurate oracles, factual queries use factually-accurate oracles."
  },
  "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": "3499779319c596e867ef34e8a6107d36ddf3eec075126d49902f08c40040da18",
    "verified_classes": [
      "WeightedVerdict",
      "OracleResponse",
      "OracleProfile",
      "OracleQuery",
      "WeightingPolicy",
      "WeightingManifest",
      "NonUniformOracleGuard"
    ],
    "verified_functions": [
      "_hash",
      "evaluate_oracle_consensus"
    ],
    "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
  }
}