{
  "schema_version": "1.3.0",
  "slug": "how-must-an-instance-prevent-reference-deduplication-collisions-across-heterogeneous-identifier-schemes",
  "title": "How must an instance prevent reference deduplication collisions across heterogeneous identifier schemes?",
  "date_of_record": "2026 October 20",
  "scope": "* **Applies when:** References use heterogeneous identifier schemes, deduplication decisions affect downstream behavior, and collisions are possible. * **Does not apply when:** All references use a single scheme, or deduplication is unneces",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-must-an-instance-prevent-reference-deduplication-collisions-across-heterogeneous-identifier-schemes.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-must-an-instance-prevent-reference-deduplication-collisions-across-heterogeneous-identifier-schemes.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-must-an-instance-prevent-reference-deduplication-collisions-across-heterogeneous-identifier-schemes.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1073,
    "python_slice_tokens": 318,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The separation between **identifier syntax** (the string format of the identifier) and **identifier semantics** (what the identifier actually points to, including scheme, authority, and version). Relying on syntax creates the **Deduplication Collision**: two references with similar-looking identifiers are deduplicated (losing the semantic difference), or two...",
    "what_was_observed": "In heterogeneous reference networks, failing to handle deduplication correctly produces three primary failure modes: 1. **False Merge:** A URI \"tool.example.com/v1\" and a content hash that happens to share a prefix are treated as equivalent, and one is dropped, losing information. Or worse, a legitimate reference and a malicious reference are merged due to superficial similarity, and the malicious version is served. ...",
    "condition_of_validity": "* **Applies when:** References use heterogeneous identifier schemes, deduplication decisions affect downstream behavior, and collisions are possible. * **Does not apply when:** All references use a single scheme, or deduplication is unnecessary (references are strictly additive).",
    "decision_boundary": "1. **Do the references use different identifier schemes?** If no, standard deduplication applies. If yes, proceed. 2. **Is there a `canonical_resource_binding_receipt` proving equivalence for the references being deduplicated?** If yes, safe to merge. If no, do not merge based on syntax alone. 3. **Does the `scheme_collision_detector_receipt` confirm the ref...",
    "operational_effect": "1. **False Merge Prevention:** Deduplication requires canonical binding, preventing superficial merges. 2. **False Split Prevention:** Different syntactic forms of the same resource are unified when canonical binding is available. 3. **Scheme Laundering Detection:** Cross-scheme equivalence is verified, catching references that appear equivalent but resolve ..."
  },
  "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": "b54f80e30cd5826340eb0ab148af6fb16c92c24a3eeaccaafe6d564e8a7c86b5",
    "verified_classes": [
      "DeduplicationVerdict",
      "Reference",
      "DeduplicationPair",
      "DedupPolicy",
      "DedupManifest",
      "HeterogeneousDedupGuard"
    ],
    "verified_functions": [
      "_hash",
      "evaluate_pair"
    ],
    "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
  }
}