{
  "schema_version": "1.3.0",
  "slug": "how-should-an-instance-treat-a-peer-directory-s-capability-grant-as-advisory-until-policy-negotiation-converges",
  "title": "How should an instance treat a peer directory's capability grant as advisory until policy negotiation converges",
  "date_of_record": "2026 November 12",
  "scope": "Applies to cross-org agent federation where capability grants are published through a federated directory and exercised under a negotiated policy bundle. Does not apply to intra-org directories with a single trust root, nor to statically pinned capability manifests.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-should-an-instance-treat-a-peer-directory-s-capability-grant-as-advisory-until-policy-negotiation-converges.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-treat-a-peer-directory-s-capability-grant-as-advisory-until-policy-negotiation-converges.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-treat-a-peer-directory-s-capability-grant-as-advisory-until-policy-negotiation-converges.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1266,
    "python_slice_tokens": 244,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "A federated directory entry answers \"what does this peer *claim* it can do.\" A negotiated policy answers \"what will this peer *honor* for *me*.\" These two facts converge asynchronously and are published by different subsystems with different consistency guarantees. The directory is typically an eventually-consistent, append-mostly cache replicated across org...",
    "what_was_observed": "During a federation rollout, org A discovered org B's `summarize.document` capability in B's federated directory entry. A's orchestrator read the entry, saw `status: granted`, and dispatched work. B's policy negotiation for the A→B pair was still in `PENDING_RENEGOTIATION` because B had rotated its data-residency policy the previous minute. B's enforcement layer rejected the calls with `403 policy_mismatch`, but A's ...",
    "condition_of_validity": "The advisory-only rule holds when all of the following are true: 1. The directory entry and the negotiated policy are published by distinct subsystems with no shared transactional boundary. 2. Policy negotiation can transition through non-terminal states (`PENDING`, `RENEGOTIATING`, `DEGRADED`) that are not reflected in the directory entry. 3. Rejections fro...",
    "decision_boundary": "The decision is not \"trust the directory\" versus \"ignore the directory.\" It is: **before the first dispatch against a (peer, capability) pair, require a locally cached policy bundle in state `CONVERGED` whose `bundle_id` matches the directory entry's `policy_epoch` field.** If the directory entry carries no `policy_epoch`, or the cached bundle's epoch is beh...",
    "operational_effect": "Callers that implement the epoch-match gate see a short cold-start latency (one negotiation round-trip) on first use of each peer capability, and thereafter cache the converged bundle keyed on `(peer_org, capability, policy_epoch)`. Rejections during the advisory window are classified as non-retryable-until-negotiation and surfaced as a distinct error class ..."
  },
  "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": "35a93b232d62c3bf376d0a9e7a2181dfa27c4e09d72425be5e23b87667e5a87c",
    "verified_classes": [
      "FederationGrantNotConverged"
    ],
    "verified_functions": [
      "dispatch_federated",
      "_invoke"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 4,
    "raised_exceptions": [
      "FederationGrantNotConverged"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}