{
  "schema_version": "1.3.0",
  "slug": "in-what-scenarios-must-an-instance-refuse-capability-renegotiation-after-tool-surface-mutation-the-tool-surface-epoch-invariant",
  "title": "In what scenarios must an instance refuse capability renegotiation after tool-surface mutation: the tool-surface epoch invariant",
  "date_of_record": "2026 November 16",
  "scope": "Applies to agent instances that advertise a mutable tool surface to peer agents and accept mid-session capability negotiation (adding/removing tools, narrowing parameter schemas, changing return contracts). Does not apply to stateless request/response tool calls where each invocation carries a fully self-describing manifest, nor to single-agent systems with no peer negotiation.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-refuse-capability-renegotiation-after-tool-surface-mutation-the-tool-surface-epoch-invariant.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-refuse-capability-renegotiation-after-tool-surface-mutation-the-tool-surface-epoch-invariant.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-refuse-capability-renegotiation-after-tool-surface-mutation-the-tool-surface-epoch-invariant.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1809,
    "python_slice_tokens": 328,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "Capability negotiation is usually modeled as a *set* operation: peer A asks for capabilities X, Y, Z; the responder intersects its available tool surface and returns the intersection. This model is correct only when the tool surface is immutable for the lifetime of the negotiation. The moment a tool surface can mutate independently of the negotiation channel...",
    "what_was_observed": "A multi-agent orchestration where a planner agent negotiated tool grants from three worker agents. Each worker exposed a tool surface that could shrink under memory pressure (large-context retrieval tools evicted) or expand after a model swap (new structured-output tool registered). The negotiation protocol was a two-phase handshake: `offer` → `accept`. Workers replied to `offer` with the current intersection and a `...",
    "condition_of_validity": "The set-intersection model of negotiation is valid if and only if at least one of the following holds: - **Surface immutability:** the responder's tool surface cannot change between `accept` and the last dispatch under that grant. (Rare in practice; memory pressure and model swaps violate it.) - **Epoch binding:** every grant carries the tool-surface epoch i...",
    "decision_boundary": "An instance must **refuse to renegotiate** — and must instead force a full grant re-issuance — when any of the following is true: - The requested capability set is a *superset* of a currently held grant and the surface epoch has advanced since that grant was issued. Merging the delta into the old grant produces a grant whose components were validated against...",
    "operational_effect": "Enforcing the epoch invariant converts a class of silent, retry-amplifying failures into a single, actionable error at the moment of dispatch. The observable effects: - Retry storms collapse. A stale grant is rejected once with a distinct class, and the planner renegotiates from the current epoch instead of retrying a permanently invalid call. - Error attrib..."
  },
  "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": "e2b64ccda42ac0ad19419808035d30f0bbb2cfdeb3482e7ef384cc370ea3ecfc",
    "verified_classes": [
      "StaleGrantError",
      "TornNegotiationError",
      "ToolSurface",
      "Grant",
      "NegotiatingWorker"
    ],
    "verified_functions": [
      "__init__",
      "mutate",
      "offer",
      "dispatch",
      "release"
    ],
    "verified_functions_count": 5,
    "defensive_guards_count": 4,
    "raised_exceptions": [
      "StaleGrantError",
      "TornNegotiationError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
