{
  "schema_version": "1.3.0",
  "slug": "when-must-an-instance-refuse-a-federated-peer-s-delegated-authority-before-policy-exchange-completes",
  "title": "When must an instance refuse a federated peer's delegated authority before policy exchange completes",
  "date_of_record": "2026 November 15",
  "scope": "Applies to cross-org multi-agent federations in which agent instances present federated identity tokens (OIDC/SPIFFE-style) carrying delegated authority from a home-org principal, and where policy exchange (capability manifests, obligation sets, revocation feeds) is negotiated out-of-band from the identity handshake. Does not apply to single-org deployments, nor to federations where the trust anchor is a single shared signing root that both parties verify synchronously before any token is minted.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/when-must-an-instance-refuse-a-federated-peer-s-delegated-authority-before-policy-exchange-completes.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/when-must-an-instance-refuse-a-federated-peer-s-delegated-authority-before-policy-exchange-completes.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/when-must-an-instance-refuse-a-federated-peer-s-delegated-authority-before-policy-exchange-completes.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 2116,
    "python_slice_tokens": 264,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The distinction that matters operationally is between **authentication of the delegation chain** and **authorization under the receiving org's policy**. A federated token can be cryptographically perfect — every signature in the chain verifies, the issuer is in the configured trust bundle, the subject is a real home-org principal — and still be unusable, bec...",
    "what_was_observed": "During a federation bootstrap between two organizations (call them A, the issuing/home org, and B, the receiving org), a delegated agent instance at B accepted a token from A's agent, verified the full SPIFFE chain to A's trust domain, and immediately executed a data-retrieval action. The token carried a `delegation_scope` claim of `read:dataset/*` and a `home_obligations_ref` pointer to a policy bundle served by A. ...",
    "condition_of_validity": "The invariant \"verify chain → negotiate → act\" is valid only when the following hold. If any fails, the instance must refuse rather than proceed: 1. **Obligation completeness.** The token's `home_obligations_ref` resolves to a bundle whose digest is bound into the token (or into a signed assertion the token references). If the reference is present but the bu...",
    "decision_boundary": "The boundary is between **negotiation actions** and **effectful actions**. Negotiation actions — fetching the obligation bundle, polling the revocation feed, requesting the trust-anchor proof, exchanging capability manifests — are permitted on an unverified-but-negotiating peer, because they are the very steps that establish the conditions under which effect...",
    "operational_effect": "Enforcing this boundary changes the failure mode from *silent over-authorization during partition* to *loud refusal during partition*. The instance stops acting, surfaces `Indeterminate` to its orchestrator, and the orchestrator can decide whether to fail the task, route to a local fallback, or escalate for human trust re-attestation. This is the correct tra..."
  },
  "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": "47393e9d82513c6d1da2db86465c28a23efe4b94f3393a769432789072fd0a40",
    "verified_classes": [
      "FederationAuthorityError",
      "AuthorityState",
      "PeerAuthorityView"
    ],
    "verified_functions": [
      "classify",
      "require_effectful_authority"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "FederationAuthorityError"
    ],
    "sample_fail_closed_invariants": [
      "delegation chain failed verification; peer is unauthenticated"
    ],
    "stdlib_dependencies": [
      "__future__",
      "dataclasses",
      "enum"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
