{
  "schema_version": "1.3.0",
  "slug": "how-must-an-instance-handle-reference-resolution-during-active-renaming-operations",
  "title": "How must an instance handle reference resolution during active renaming operations?",
  "date_of_record": "2026 October 20",
  "scope": "* **Applies when:** Resources can be renamed, renaming is non-atomic, and consumers may hold references to old names during the transition. * **Does not apply when:** Renames are atomic (old name immediately invalidated, new name immediatel",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-must-an-instance-handle-reference-resolution-during-active-renaming-operations.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-must-an-instance-handle-reference-resolution-during-active-renaming-operations.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-must-an-instance-handle-reference-resolution-during-active-renaming-operations.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1024,
    "python_slice_tokens": 265,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The separation between **rename completion** (all consumers have migrated) and **rename operation** (the transition period). Relying on rename completion creates the **Rename Window Ambiguity**: during the rename, some references point to the old name (still resolving but deprecated), some point to the new name (available but not yet broadly trusted), and co...",
    "what_was_observed": "In renaming-prone agent architectures, failing to handle the transition window produces three primary failure modes: 1. **Old-Name Consumers Fail:** A consumer holds a reference to the old name. The rename begins, the old name starts returning 410 Gone before consumers have migrated. Some consumers fail to resolve, breaking their operations. 2. **New-Name Trust Deficit:** The new name is available but has not accumul...",
    "condition_of_validity": "* **Applies when:** Resources can be renamed, renaming is non-atomic, and consumers may hold references to old names during the transition. * **Does not apply when:** Renames are atomic (old name immediately invalidated, new name immediately trusted), or resources use permanent redirects that hide the transition.",
    "decision_boundary": "1. **Is there a `rename_transition_receipt` for the resource?** If no, standard resolution applies. If yes, proceed. 2. **Is the current epoch within the transition window?** If yes, dual resolution is active. Consumers can use either name. If no, check `rename_completion_marker_signature`. 3. **Does the `dual_resolution_receipt` verify that both names resol...",
    "operational_effect": "1. **Rename Breakage Prevention:** Old names continue to resolve during the transition. 2. **Trust Continuity:** Dual resolution ensures consumers see consistent results. 3. **Deterministic Migration:** Guidance directs consumers when and how to migrate."
  },
  "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": "4e8b97f97c21ec465f994325ddeec884df67f650019897417cf075b12ad0385b",
    "verified_classes": [
      "RenameVerdict",
      "RenameTransition",
      "RenamePolicy",
      "RenameManifest",
      "RenameTransitionGuard"
    ],
    "verified_functions": [
      "_hash",
      "evaluate_transition"
    ],
    "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
  }
}