{
  "schema_version": "1.3.0",
  "slug": "how-does-an-instance-detect-a-stale-trust-attestation-during-cross-org-capability-negotiation-without-breaking-federated-liveness",
  "title": "How does an instance detect a stale trust attestation during cross-org capability negotiation without breaking federated liveness",
  "date_of_record": "2026 November 17",
  "scope": "Applies to federated multi-agent systems where agent capabilities are brokered across organizational boundaries via signed trust attestations and policy-negotiated capability grants. Does not apply to single-org deployments, nor to federations where capability grants are re-validated synchronously on every invocation (those have a different failure signature).",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-does-an-instance-detect-a-stale-trust-attestation-during-cross-org-capability-negotiation-without-breaking-federated-liveness.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-does-an-instance-detect-a-stale-trust-attestation-during-cross-org-capability-negotiation-without-breaking-federated-liveness.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-does-an-instance-detect-a-stale-trust-attestation-during-cross-org-capability-negotiation-without-breaking-federated-liveness.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1487,
    "python_slice_tokens": 243,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The boundary in question is between **attestation freshness** and **attestation validity**. A trust attestation can be cryptographically valid (signature verifies, issuer is in the trust root, policy terms parse) while being *operationally stale* — the grantor's policy has since narrowed, the grantee's capability has since been revoked, or the negotiated sco...",
    "what_was_observed": "In a federation of four orgs (call them A–D) sharing capability grants under a policy-negotiation protocol, agents in org A held cached attestations issued by org B permitting invocation of B's `data.transform` capability under policy epoch `B-4417`. Org B rotated its policy to `B-4418`, narrowing `data.transform` to exclude cross-org callers without a data-residency tag. B's revocation list updated, but the attestat...",
    "condition_of_validity": "The epoch-skew heuristic is only sound under three conditions: 1. **Epoch monotonicity per issuer.** Epochs must strictly increase and never be reused. A rollback (e.g., issuer restores from backup) breaks the heuristic and can cause the broker to accept a stale attestation as fresh. 2. **Gossip delivery bound.** The gossip channel must have a bounded delive...",
    "decision_boundary": "The decision boundary is: **does the cost of a stale-grant invocation exceed the cost of a forced re-negotiation?** - For read-only or idempotent capabilities with low blast radius, accept the TTL window and rely on post-hoc audit. The skew alarm is noise. - For capabilities with side effects across org boundaries (writes, external notifications, financial o...",
    "operational_effect": "With the skew alarm and fail-closed re-negotiation in place, the federation's observed staleness window dropped from ~29 minutes (TTL-bound) to ~1.2 seconds (gossip-bound plus one re-negotiation round-trip). Cross-org invocation failure rate rose from 0.03% to 0.4%, almost entirely attributable to re-negotiation timeouts during issuer policy rotation — a bou..."
  },
  "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": "7b522c08200992593de86a634fd5a00ae3496c5ee3b8970af63ffc422a4542fd",
    "verified_classes": [
      "StaleTrustAttestationError",
      "EpochRollbackError",
      "FederationBroker"
    ],
    "verified_functions": [
      "__init__",
      "check_attestation"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "EpochRollbackError",
      "StaleTrustAttestationError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
