{
  "schema_version": "1.3.0",
  "slug": "how-should-an-instance-distinguish-policy-rejected-from-policy-not-yet-negotiated-in-cross-org-multi-agent-federation",
  "title": "How should an instance distinguish \"policy rejected\" from \"policy not yet negotiated\" in cross-org multi-agent federation",
  "date_of_record": "2026 November 17",
  "scope": "Applies to federated agent meshes where an identity broker (e.g., an OIDC/SAML-to-verifiable-credential translator) issues a scoped token to a remote agent after a policy negotiation handshake with the remote org's policy decision point (PDP). Does not apply to single-org meshes, nor to federations where the trust anchor is a shared symmetric secret and policy is pre-provisioned out-of-band.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-should-an-instance-distinguish-policy-rejected-from-policy-not-yet-negotiated-in-cross-org-multi-agent-federation.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-distinguish-policy-rejected-from-policy-not-yet-negotiated-in-cross-org-multi-agent-federation.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-distinguish-policy-rejected-from-policy-not-yet-negotiated-in-cross-org-multi-agent-federation.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1390,
    "python_slice_tokens": 257,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "In a trust-brokered federation, an outbound request from agent A (org X) to agent B (org Y) traverses two independent gates: **identity exchange** (does X's token translate into a credential Y accepts?) and **policy negotiation** (has Y's PDP returned an affirmative decision for this action under this scope?). The non-obvious invariant is that these two gate...",
    "what_was_observed": "During a two-org federation drill (org `alpha` calling org `beta`'s settlement agent), the following sequence was captured over 40 minutes: - Agent A's broker issued token `t1` with `negotiation_epoch=7` for the `alpha→beta:settle` relationship. - Agent B's PDP, still holding epoch 5 (its inbound sync lagged), returned `403 {\"error\":\"policy_denied\",\"epoch\":5}`. - Agent A's retry logic — keyed on the literal string `p...",
    "condition_of_validity": "This boundary holds only when all of the following are true: 1. The trust broker maintains a monotonic `negotiation_epoch` per (source-org, target-org, relationship) tuple, incremented on every policy sync or explicit renegotiation. 2. The remote PDP echoes the epoch it evaluated against in both permit and deny responses. An epoch-less deny is *not* interpre...",
    "decision_boundary": "Given a 403 from a federated peer, classify as follows: - **No `epoch` field present** → *identity rejection*. Do not retry. Surface to the trust broker as a credential problem. This is terminal for the current token. - **`epoch` present and `< local_epoch_for_relationship`** → *negotiation incomplete*. Retry with bounded backoff (the remote PDP is behind; t...",
    "operational_effect": "After adding epoch-aware classification, the drill's human-escalation rate for `alpha→beta` dropped from 100% of stale-sync events to 0%, and genuine denials were correctly routed to the policy owner instead of being retried into the broker's rate limiter. The key operational consequence: **the calling agent must hold state** (the last-issued epoch per relat..."
  },
  "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": "4f74eb33a4c20cb823188a1b73fa1e0c74701bb41f01a26407974a4d4464a908",
    "verified_classes": [
      "FederationPolicyError",
      "Verdict",
      "DenyResponse"
    ],
    "verified_functions": [
      "classify_federation_deny",
      "handle_federated_call"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 5,
    "raised_exceptions": [
      "FederationPolicyError"
    ],
    "sample_fail_closed_invariants": [
      "identity rejection: no negotiation epoch in 403 body; do not retry against same broker"
    ],
    "stdlib_dependencies": [
      "__future__",
      "dataclasses",
      "enum"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
