{
  "schema_version": "1.3.0",
  "slug": "in-what-scenarios-must-an-instance-refuse-to-negotiate-a-capability-downgrade-across-a-federation-gateway-boundary",
  "title": "In what scenarios must an instance refuse to negotiate a capability downgrade across a federation gateway boundary",
  "date_of_record": "2026 November 17",
  "scope": "Applies to cross-org multi-agent federations where two policy-bounded interop gateways (each enforcing its own org's capability and policy envelope) perform capability negotiation on behalf of agents behind them. Does not apply to intra-org agent meshes with a single policy authority, nor to stateless RPC proxies that do not carry negotiated capability state.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-refuse-to-negotiate-a-capability-downgrade-across-a-federation-gateway-boundary.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-refuse-to-negotiate-a-capability-downgrade-across-a-federation-gateway-boundary.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-refuse-to-negotiate-a-capability-downgrade-across-a-federation-gateway-boundary.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1564,
    "python_slice_tokens": 318,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The non-obvious boundary is between **capability negotiation** and **policy negotiation**. A gateway is permitted to negotiate *which* of an agent's declared capabilities will be exercised in a session (downgrade, subsetting, version pinning). A gateway is **never** permitted to negotiate *whether* a policy constraint applies. These two are routinely conflat...",
    "what_was_observed": "In a federation between Org A (initiator) and Org B (responder), agent `a-1` declared capability `doc.summarize` at versions `v3` (with per-document ACL enforcement) and `v2` (org-wide read, no per-document ACL). Org B's gateway advertised `doc.summarize@v2` only. The standard intersection algorithm selected `v2` — a valid *capability* intersection — and the session proceeded. The outbound gateway on Org A's side had...",
    "condition_of_validity": "The refusal-to-downgrade rule is valid — and mandatory — precisely when all of the following hold: 1. The capability being negotiated has at least one policy bound to its **family** (not its version). 2. The candidate downgrade target has a **strictly weaker** enforcement profile than the version the policy was authored against (weaker ACL scope, coarser ten...",
    "decision_boundary": "The decision is not \"accept the intersection\" versus \"reject the session.\" It is a three-way split at the moment a candidate version is proposed: - **Accept** when the candidate version's enforcement profile satisfies every policy bound to the family. Downgrade is fine; policy is intact. - **Refuse and fail closed** when the candidate version weakens enforce...",
    "operational_effect": "Enforcing the boundary changes federation behavior in three observable ways. First, cross-org sessions that previously \"succeeded\" by silently downgrading now fail with an explicit `CapabilityPolicyFloorViolation`, which surfaces the coupling between capability and policy that was always there. Second, gateways must carry the policy-floor metadata alongside ..."
  },
  "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": "da7b03f530863eeaed11a0b2f8d4d283c41d0408f7bb811c0c4b1700cf1a9eef",
    "verified_classes": [
      "CapabilityPolicyFloorViolation",
      "PolicyDeferralRequired"
    ],
    "verified_functions": [
      "negotiate_capability",
      "_satisfies_floor"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 4,
    "raised_exceptions": [
      "CapabilityPolicyFloorViolation",
      "PolicyDeferralRequired"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
