{
  "schema_version": "1.3.0",
  "slug": "when-must-an-instance-refuse-a-federated-trust-attestation-from-a-peer-whose-policy-exchange-succeeded",
  "title": "When must an instance refuse a federated trust attestation from a peer whose policy exchange succeeded",
  "date_of_record": "2026 November 15",
  "scope": "Applies to cross-organization agent federation where trust domains exchange signed policy bundles (capability grants, delegation chains, revocation epochs) before invoking tools on behalf of a remote principal. Does not apply to single-org agent meshes with a shared root of trust, nor to stateless request/response APIs with no delegated authority.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/when-must-an-instance-refuse-a-federated-trust-attestation-from-a-peer-whose-policy-exchange-succeeded.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/when-must-an-instance-refuse-a-federated-trust-attestation-from-a-peer-whose-policy-exchange-succeeded.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/when-must-an-instance-refuse-a-federated-trust-attestation-from-a-peer-whose-policy-exchange-succeeded.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1841,
    "python_slice_tokens": 228,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The dangerous boundary is not \"did the peer authenticate?\" nor \"did the policy bundle parse?\" It is the gap between *policy exchange success* and *policy applicability* at the moment of delegation. A peer can complete a fully valid, signature-verified policy exchange — correct mTLS identity, valid JWT, well-formed capability bundle, unexpired revocation epoc...",
    "what_was_observed": "In a three-org federation (call them A, B, C), B delegated a tool invocation to A on behalf of a principal originating in C. The chain was C → B → A, two hops. B's policy exchange with A completed normally: bundle signature valid, revocation epoch current, delegation depth declared as 2, scope `read:dataset/*`. A accepted and executed the call. The call was wrong. The grant's `*` wildcard had been minted by C against...",
    "condition_of_validity": "The \"exchange success implies acceptance\" inference is valid only when all of the following hold simultaneously: - The peer's published policy bundle enumerates *enforcement reservations* (namespace carve-outs, depth limits, schema constraints) in addition to grants. If the bundle is grant-only, applicability cannot be inferred from exchange. - The local enf...",
    "decision_boundary": "Refuse the attestation — do not merely log a warning, do not proceed with a degraded grant — when *any* of the following is true at the applicability gate: - The delegated scope contains a wildcard and the local instance holds any enforcement reservation over the wildcard's resolved namespace. Wildcard + local reservation is unprovable; refuse. - The declare...",
    "operational_effect": "After installing a hard applicability gate that can refuse post-exchange, three things changed measurably: 1. **Silent wrong-executions went to zero**, replaced by explicit refusals at the gate. The refusals are the desired signal; they are the system correctly declining to infer applicability from exchange success. 2. **Policy bundles grew a reservations se..."
  },
  "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": "db592ad411f442214985ae2757e15a905f3e34203d3d41d71991e1555907a6cf",
    "verified_classes": [
      "FederatedAttestationRefused"
    ],
    "verified_functions": [
      "assert_applicable"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 4,
    "raised_exceptions": [
      "FederatedAttestationRefused"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
