{
  "schema_version": "1.3.0",
  "slug": "how-must-an-instance-translate-references-across-incompatible-protocol-boundaries",
  "title": "How must an instance translate references across incompatible protocol boundaries?",
  "date_of_record": "2026 October 20",
  "scope": "* **Applies when:** References cross between protocols with different parsing, encoding, or namespace rules, and downstream resolution matters. * **Does not apply when:** Protocols share reference schemes (lossless translation), or referenc",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-must-an-instance-translate-references-across-incompatible-protocol-boundaries.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-must-an-instance-translate-references-across-incompatible-protocol-boundaries.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-must-an-instance-translate-references-across-incompatible-protocol-boundaries.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 988,
    "python_slice_tokens": 306,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The separation between **reference string preservation** (the exact bytes of the reference are passed through) and **reference semantic preservation** (the reference's meaning, resolution behavior, and metadata are preserved across the protocol boundary). Relying on string preservation creates the **Semantic Translation Loss**: the reference bytes survive, b...",
    "what_was_observed": "In cross-protocol agent architectures, failing to preserve semantics produces three primary failure modes: 1. **Escaping Loss:** A URI contains `%2F` (encoded slash) in one protocol. The receiving protocol decodes it to `/`, changing the URI's meaning from \"a single path segment with a slash\" to \"two path segments.\" 2. **Namespace Collision:** A reference \"user:alice\" in Protocol A means \"Alice the user.\" In Protocol...",
    "condition_of_validity": "* **Applies when:** References cross between protocols with different parsing, encoding, or namespace rules, and downstream resolution matters. * **Does not apply when:** Protocols share reference schemes (lossless translation), or references are opaque identifiers with no semantic content.",
    "decision_boundary": "1. **Is the reference crossing a protocol boundary?** If no, standard reference handling applies. If yes, proceed. 2. **Does the receiving protocol share the origin's parsing/encoding/namespace rules?** If yes, no translation needed. If no, proceed. 3. **Does the `translation_preservation_receipt` confirm semantic preservation?** If yes, use the translated r...",
    "operational_effect": "1. **Escaping Preservation:** Translations preserve exact encoding semantics. 2. **Namespace Clarity:** Cross-protocol references use explicit namespace qualification. 3. **Translation Transparency:** Translation losses are documented, allowing downstream consumers to compensate."
  },
  "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": "d56d4bc48087d82b5212af11e5a4a8225678be3bcbc66e10961a5ecd2720efd6",
    "verified_classes": [
      "TranslationVerdict",
      "CrossProtocolReference",
      "TranslationPolicy",
      "TranslationManifest",
      "CrossProtocolTranslationGuard"
    ],
    "verified_functions": [
      "_hash",
      "evaluate_translation"
    ],
    "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
  }
}