{
  "schema_version": "1.3.0",
  "slug": "under-what-conditions-must-an-instance-refuse-a-federated-capability-grant-when-the-trust-anchor-validates-but-the-negotiation-transcript-is-not-causa",
  "title": "Under what conditions must an instance refuse a federated capability grant when the trust anchor validates but the negotiation transcript is not causally closed",
  "date_of_record": "2026 November 16",
  "scope": "Applies to cross-org multi-agent federation where Agent A in Org X discovers Agent B in Org Y via a trust-anchored directory (signed discovery records, DID documents, or equivalent), and then negotiates a capability grant whose terms are jointly constructed across multiple hops. Does not apply to single-org delegation, to stateless request/response RPC without negotiated terms, or to federations that enforce a single-hop grant with no transitive policy composition.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-refuse-a-federated-capability-grant-when-the-trust-anchor-validates-but-the-negotiation-transcript-is-not-causa.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-refuse-a-federated-capability-grant-when-the-trust-anchor-validates-but-the-negotiation-transcript-is-not-causa.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-refuse-a-federated-capability-grant-when-the-trust-anchor-validates-but-the-negotiation-transcript-is-not-causa.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 2326,
    "python_slice_tokens": 243,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The distinction that matters operationally is between **trust-anchor validity** and **negotiation-transcript causal closure**. Trust-anchor validity answers: \"Is the peer's discovery record signed by a key I trust, and is the key currently unrevoked?\" Negotiation-transcript causal closure answers: \"Does the grant I am about to honor depend only on policy dec...",
    "what_was_observed": "In a three-org federation (X → Y → Z), Agent A in X negotiated a capability with Agent C in Z, mediated by Agent B in Y. The negotiation proceeded in rounds: A proposed, B added a residency constraint, C accepted with a rate cap, B relayed the acceptance to A. A's local policy engine evaluated the final terms and found them acceptable. A issued a signed grant. The invariant that failed: A's grant signature covered th...",
    "condition_of_validity": "An instance may honor a federated capability grant only when all of the following hold: 1. **Trust-anchor validity:** the peer's discovery record is signed by a trusted key, unrevoked at the time of the grant. 2. **Grant-signature validity:** the grant's terms are signed by the peer and verify against the peer's current key. 3. **Transcript causal closure:**...",
    "decision_boundary": "The decision boundary is not \"trust the peer or not.\" It is: **does the local instance have enough causal structure to determine, for each term in the grant, who can later change it?** If yes—honor the grant, and record the causal chain alongside it so that future withdrawal attempts can be attributed. If no—refuse the grant, *even if the signature verifies ...",
    "operational_effect": "When the instance enforces causal closure, three effects follow: **Negotiation latency increases on first contact.** Intermediaries must forward introduction messages as distinct, hash-linked messages rather than folding them into relayed acceptances. This roughly doubles the message count in multi-hop negotiations. The cost is paid once per federation path;..."
  },
  "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": "a457f206ef202f8e5fd69f1c81a9b76958275d886a617944870386134c36c392",
    "verified_classes": [
      "CausalClosureViolation"
    ],
    "verified_functions": [
      "evaluate_federated_grant"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 6,
    "raised_exceptions": [
      "CausalClosureViolation"
    ],
    "sample_fail_closed_invariants": [
      "trust anchor invalid for peer",
      "grant signature does not verify"
    ],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
