{
  "schema_version": "1.3.0",
  "slug": "how-must-an-instance-handle-references-that-resolve-differently-in-different-trust-domains",
  "title": "How must an instance handle references that resolve differently in different trust domains?",
  "date_of_record": "2026 October 20",
  "scope": "* **Applies when:** References resolve differently in different domains, domains are distinguishable, and cross-domain exchanges can cause confusion. * **Does not apply when:** References resolve identically everywhere (e.g., globally uniqu",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-must-an-instance-handle-references-that-resolve-differently-in-different-trust-domains.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-must-an-instance-handle-references-that-resolve-differently-in-different-trust-domains.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-must-an-instance-handle-references-that-resolve-differently-in-different-trust-domains.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1067,
    "python_slice_tokens": 298,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The separation between **reference identity** (the string, identifier, or pointer) and **reference resolution context** (the trust domain in which resolution occurs, which determines what the reference actually points to). Relying on identity creates the **Cross-Domain Resolution Confusion**: Agent A in Domain X resolves \"config.internal\" to X's config serve...",
    "what_was_observed": "In cross-domain agent networks, failing to handle domain-specific resolution produces three primary failure modes: 1. **Silent Semantic Divergence:** Two agents exchange a reference \"user-service\" that resolves to different services in their respective domains. Their actions appear coordinated (both reference \"user-service\") but are actually targeting different backends. 2. **Domain Confusion Exploit:** An attacker i...",
    "condition_of_validity": "* **Applies when:** References resolve differently in different domains, domains are distinguishable, and cross-domain exchanges can cause confusion. * **Does not apply when:** References resolve identically everywhere (e.g., globally unique URIs), or domains never interact.",
    "decision_boundary": "1. **Was the reference resolved in a specific trust domain?** If yes, mark it domain-scoped. If no, the reference may have unresolvable ambiguity. 2. **Is the consumer in the same domain as the resolution?** If yes, standard use applies. If no, cross-domain equivalence must be verified. 3. **Does a `cross_domain_equivalence_receipt` exist for this reference?...",
    "operational_effect": "1. **Semantic Divergence Prevention:** Domain scoping makes it explicit that \"user-service\" means different things in different domains. 2. **Exploit Prevention:** Cross-domain references require equivalence proof, preventing domain-confusion attacks. 3. **Cache Integrity:** Domain-scoped cache entries prevent cross-domain cache poisoning."
  },
  "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": "3c14bc13d2e63c62f9dc1672732cec6c152edc5e54398481801609fe47399bc5",
    "verified_classes": [
      "CrossDomainVerdict",
      "DomainScopedReference",
      "CrossDomainPolicy",
      "CrossDomainManifest",
      "CrossDomainReferenceGuard"
    ],
    "verified_functions": [
      "_hash",
      "evaluate_reference"
    ],
    "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
  }
}