{
  "schema_version": "1.3.0",
  "slug": "what-referential-integrity-invariants-must-survive-when-agents-propagate-uris-peer-to-peer",
  "title": "What referential integrity invariants must survive when agents propagate URIs peer-to-peer?",
  "date_of_record": "2026 October 20",
  "scope": "* **Applies when:** Agents propagate URIs across a peer-to-peer network, the origin is not directly verifiable, and receivers act on the URIs. * **Does not apply when:** All URIs come from a single authoritative resolver, or the receiver ca",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-referential-integrity-invariants-must-survive-when-agents-propagate-uris-peer-to-peer.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-referential-integrity-invariants-must-survive-when-agents-propagate-uris-peer-to-peer.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-referential-integrity-invariants-must-survive-when-agents-propagate-uris-peer-to-peer.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1128,
    "python_slice_tokens": 295,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The separation between **URI presence** (the peer transmitted a syntactically valid URI) and **URI referential integrity** (the URI resolves to the resource the peer claimed it references). Relying on presence creates the **Referential Propagation Decay**: each hop in a peer-to-peer chain re-transmits URIs without verification, and errors compound—a typo int...",
    "what_was_observed": "In decentralized agent networks, failing to verify referential integrity produces three primary failure modes: 1. **Phantom Resolution Cascade:** Agent A shares URI \"tool.example.com/analyze\" to B, B shares \"tool.example.com/analysis\" to C (typo), C shares it to D, and D invokes a non-existent endpoint that returns 404s that every downstream agent treats as a tool bug rather than a URI propagation error. 2. **Cross-D...",
    "condition_of_validity": "* **Applies when:** Agents propagate URIs across a peer-to-peer network, the origin is not directly verifiable, and receivers act on the URIs. * **Does not apply when:** All URIs come from a single authoritative resolver, or the receiver can independently resolve every URI against the origin without relying on peers.",
    "decision_boundary": "1. **Did the peer transmit a URI along with a `uri_resolution_attestation_receipt`?** If no, the receiver has no proof the URI ever worked. It must resolve independently before acting. 2. **Is the attestation from within the receiver's trust domain?** If no, resolution in the sender's domain doesn't guarantee resolution in the receiver's. The receiver must r...",
    "operational_effect": "1. **Phantom Resolution Prevention:** Every propagated URI has a resolution attestation, distinguishing \"verified to work\" from \"claimed to exist.\" 2. **Trust Domain Awareness:** Domain-specific resolution prevents cross-domain URIs from failing silently. 3. **Chain Decay Detection:** Propagation depth reveals where trust should degrade."
  },
  "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": "8fd5130d1faa28f5df84214087d06e88e44bef476c1544fc99bb1f1d2d81a4a6",
    "verified_classes": [
      "ReferentialVerdict",
      "PropagatedURI",
      "URIReceiver",
      "URIReferentialPolicy",
      "URIReferentialManifest",
      "PeerToPeerReferentialGuard"
    ],
    "verified_functions": [
      "_hash",
      "evaluate_uri"
    ],
    "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
  }
}