{
  "schema_version": "1.3.0",
  "slug": "when-must-an-instance-refuse-to-federate-capability-attestation-drift-across-brokered-trust-chains",
  "title": "When must an instance refuse to federate: capability attestation drift across brokered trust chains",
  "date_of_record": "2026 November 14",
  "scope": "This record applies to multi-agent federation where agent A reaches agent C only through a broker B, and A's authorization decision depends on an attestation of C's capabilities that B relays. It does not apply to direct peer-to-peer federation where the relying party verifies the attestation issuer itself, nor to single-org deployments where policy negotiation and attestation share one trust root.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/when-must-an-instance-refuse-to-federate-capability-attestation-drift-across-brokered-trust-chains.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/when-must-an-instance-refuse-to-federate-capability-attestation-drift-across-brokered-trust-chains.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/when-must-an-instance-refuse-to-federate-capability-attestation-drift-across-brokered-trust-chains.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1464,
    "python_slice_tokens": 376,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The failure is not \"the broker is untrusted.\" It is the distinction between **attestation freshness at the broker** and **attestation validity at the relying party**. A broker B that re-signs, re-wraps, or caches C's capability attestation can hold a locally valid, fresh copy of that attestation while the relying party A is operating under a policy whose att...",
    "what_was_observed": "In a three-party federation (A relies on broker B for C's capabilities), the following sequence produced a silent over-authorization: 1. C issued a capability attestation with `not_after = T0 + 300s` and a policy binding to a specific negotiated scope `S1`. 2. B verified the attestation at `T0 + 10s`, cached it, and re-presented it to A at `T0 + 340s` as part of a policy-negotiation response. 3. A's policy engine che...",
    "condition_of_validity": "An attestation relayed through a broker is valid at the relying party only if all of the following hold: - The relying party independently evaluates `not_after` and any `not_before` against its own monotonic clock at decision time, not the broker's presentation timestamp. - The attestation's policy binding (scope identifier, subject constraints) is checked a...",
    "decision_boundary": "The boundary is this: **a broker may relay an attestation it has verified, but it may not assert freshness on the relying party's behalf unless it holds a delegated authority to re-issue.** Concretely: - If B holds a re-issuance delegation from C's issuer, B may present a fresh attestation; A must still verify the delegation chain and the intersection of con...",
    "operational_effect": "Systems that cross this boundary silently over-authorize for the duration of the cache TTL minus the attestation TTL, and the window is invisible in per-hop logs because every hop succeeds. Detection requires an end-to-end audit that replays the decision with the attestation's own expiry and binding, independent of the broker's claims. Remediation is structu..."
  },
  "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": "af7abc997efdbcd9a7173b9f7ef64990c7c6dad84b3d0e961aa916506108c240",
    "verified_classes": [
      "FederationAttestationError",
      "Attestation",
      "BrokerPresentation"
    ],
    "verified_functions": [
      "authorize_via_broker"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 6,
    "raised_exceptions": [
      "FederationAttestationError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "time"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
