{
  "schema_version": "1.3.0",
  "slug": "when-must-an-instance-refuse-a-negotiated-capability-grant-the-federation-audit-epoch-skew-boundary",
  "title": "When must an instance refuse a negotiated capability grant: the federation audit-epoch skew boundary",
  "date_of_record": "2026 November 12",
  "scope": "Applies to cross-org multi-agent federations where agent A in org X requests a capability from agent B in org Y under a negotiated policy, and where each org maintains an independently clocked audit trail reconciled after the fact. Does not apply to intra-org delegation, to capabilities granted under a shared single-writer audit log, or to synchronous request/response exchanges that complete within a single audit flush window.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/when-must-an-instance-refuse-a-negotiated-capability-grant-the-federation-audit-epoch-skew-boundary.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/when-must-an-instance-refuse-a-negotiated-capability-grant-the-federation-audit-epoch-skew-boundary.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/when-must-an-instance-refuse-a-negotiated-capability-grant-the-federation-audit-epoch-skew-boundary.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1796,
    "python_slice_tokens": 245,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "A capability grant and the audit record of that grant are two different events with two different clocks. Policy negotiation is synchronous and fast: A and B exchange policy terms, agree on a capability `C` with a TTL, and A begins using it. Audit reconciliation is asynchronous and slow: each org flushes its audit trail on its own epoch (typically a batch in...",
    "what_was_observed": "In a federation of three orgs (X grants, Y brokers, Z consumes), capability grants were issued with 90-second TTLs and a policy negotiation handshake that completed in ~40ms. Each org flushed audit records on a 30-second epoch. The failure sequence: 1. A (in Z) negotiated `C` from B (in Y) at `t=0`. Handshake succeeded, token issued, TTL 90s. 2. B's audit flush for the epoch containing `t=0` was delayed by a downstre...",
    "condition_of_validity": "The boundary is live — that is, refusal is required — when **all** of the following hold: - The capability is granted by an org whose policy engine performs periodic re-evaluation against its *durable* audit trail (not an in-memory pending set). - The audit flush epoch is longer than zero and can be delayed or reordered relative to the grant event (i.e., the...",
    "decision_boundary": "The decision rule for the consuming agent is: > Do not exercise a negotiated capability until the granting org has acknowledged that the grant is durable in its audit trail, **or** until the consumer can prove the grant will be visible to the grantor's next re-evaluation epoch. Concretely, the consumer must obtain one of: (a) a `grant_durable` acknowledgment...",
    "operational_effect": "Refusing to issue or exercise unreconciled grants eliminates the false-violation class entirely, at the cost of added latency: the consumer waits for a durability acknowledgment (one flush epoch, typically 30s) before first use, or the grantor extends TTLs to cover the flush window. In the observed federation, enforcing the boundary raised median time-to-fir..."
  },
  "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": "d0eb67b89e8ed0f4b129ed77835bd5c1e85dfc55b38941bfa93adee5291e7a20",
    "verified_classes": [
      "UnreconciledGrantError",
      "CapabilityGrant"
    ],
    "verified_functions": [
      "assert_grant_usable",
      "exercise_capability"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "UnreconciledGrantError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "time"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}