{
  "schema_version": "1.3.0",
  "slug": "what-semantic-deduplication-invariants-prevent-near-duplicate-collapse-of-distinct-claims",
  "title": "What semantic deduplication invariants prevent near-duplicate collapse of distinct claims?",
  "date_of_record": "2026 October 20",
  "scope": "* **Applies when:** The session deduplicates semantic results, claims have qualifiers, and merging affects downstream accuracy. * **Does not apply when:** Deduplication is strictly exact-match, or the session is strictly exploratory with no",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-semantic-deduplication-invariants-prevent-near-duplicate-collapse-of-distinct-claims.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-semantic-deduplication-invariants-prevent-near-duplicate-collapse-of-distinct-claims.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-semantic-deduplication-invariants-prevent-near-duplicate-collapse-of-distinct-claims.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 949,
    "python_slice_tokens": 299,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The separation between **semantic similarity** (results appear similar) and **claim equivalence** (results assert the same fact with the same qualifiers). Relying on similarity creates the **Near-Duplicate Collapse**: two results say \"the API supports OAuth\" and \"the API supports OAuth 2.0,\" similarity merges them into \"the API supports OAuth,\" and the versi...",
    "what_was_observed": "In multi-source agent architectures, failing to preserve distinct claims during dedup produces three primary failure modes: 1. **Qualifier Erasure:** \"The service is down\" and \"the service is down in EU\" are merged, and the agent treats the outage as global rather than regional. 2. **Temporal Collapse:** \"The price was $100\" and \"the price is $100\" are merged, and the agent loses the temporal qualifier, misreporting ...",
    "condition_of_validity": "* **Applies when:** The session deduplicates semantic results, claims have qualifiers, and merging affects downstream accuracy. * **Does not apply when:** Deduplication is strictly exact-match, or the session is strictly exploratory with no downstream decisions.",
    "decision_boundary": "1. **Is deduplication being applied?** If no, standard result handling applies. If yes, proceed. 2. **Do the results have qualifiers that could be erased by merging?** If yes, the merge must compare qualifiers, not just semantic similarity. 3. **Does the `merge_equivalence_proof` confirm all merged claims share the same qualifiers?** If yes, merge. If no, pr...",
    "operational_effect": "1. **Qualifier Preservation:** Merging respects qualifiers, preventing scope or temporal collapse. 2. **Confidence Range Preservation:** Distinct confidence levels are not averaged into a misleading single value. 3. **Distinction Auditability:** Rejected merges are logged, allowing downstream review."
  },
  "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": "7cb76f2f9eea93798d7c0733f8c9d4454c89d5b3275f64a16b3e9c6277c99c9b",
    "verified_classes": [
      "DeduplicationVerdict",
      "Claim",
      "DeduplicationState",
      "DedupPolicy",
      "DedupManifest",
      "SemanticDeduplicationGuard"
    ],
    "verified_functions": [
      "_hash",
      "evaluate_dedup"
    ],
    "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
  }
}