{
  "schema_version": "1.3.0",
  "slug": "which-invariants-prevent-silent-capability-resurrection-across-federated-agent-trust-brokers-during-partial-revocation",
  "title": "Which invariants prevent silent capability resurrection across federated agent trust brokers during partial revocation",
  "date_of_record": "2026 November 12",
  "scope": "Applies to federated agent systems where capabilities are minted as scoped, attenuated tokens by an origin broker and where revocation is propagated to downstream relying parties via an asynchronous fan-out channel. Does not apply to single-tenant brokers with synchronous revocation, nor to systems where every capability check performs a live introspection call against the origin authority.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/which-invariants-prevent-silent-capability-resurrection-across-federated-agent-trust-brokers-during-partial-revocation.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/which-invariants-prevent-silent-capability-resurrection-across-federated-agent-trust-brokers-during-partial-revocation.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/which-invariants-prevent-silent-capability-resurrection-across-federated-agent-trust-brokers-during-partial-revocation.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1908,
    "python_slice_tokens": 294,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The failure mode is *not* revocation latency. Operators routinely budget for a propagation window of tens of seconds and treat \"stale but bounded\" as acceptable. The non-obvious boundary is that revocation of a *parent* capability does not, by itself, invalidate *derived* capabilities unless the derivation chain is cryptographically bound to the parent's rev...",
    "what_was_observed": "During a cross-org federation drill, Org A (origin broker) revoked a delegation grant `G` at 14:02:11 that had authorized Org B's planner agent to spawn sub-agents with `files:read` scope on a shared artifact store. The revocation fan-out reached Org B's relying-party cache at 14:02:19 — within the 30s SLO. Org B's broker confirmed `G` was tombstoned. At 14:02:47, a sub-agent spawned by Org B's planner at 14:01:55 pr...",
    "condition_of_validity": "The invariant that prevents resurrection is: > For every derived token `T` with ancestor `P`, the relying party MUST verify that `P.epoch_at_mint(T) >= P.revocation_epoch`, where `epoch_at_mint(T)` is committed into `T` at mint time and signed by the minting authority, and `P.revocation_epoch` is the highest epoch at which `P` was observed live by any author...",
    "decision_boundary": "The operational question is whether to enforce lineage liveness at verification time (cost: one ancestor-chain resolution per request, plus cache pressure) or to rely on descendant enumeration at revocation time (cost: a derivation index maintained by every minting authority, plus fan-out amplification proportional to descendant count). The boundary is deter...",
    "operational_effect": "Enforcing the epoch invariant changes three operational properties: 1. **Revocation latency becomes bounded by mint-time epoch staleness, not fan-out latency.** A child minted during the propagation window commits a stale epoch and will be rejected at verification once the origin's epoch advances. The window shrinks to the relying party's epoch-confirmation ..."
  },
  "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": "2fe462fd1107d7653429f976518f490df2f7aae81f98b6ca51c6f14ff62895b3",
    "verified_classes": [
      "CapabilityResurrectionError",
      "EpochRegressionError"
    ],
    "verified_functions": [
      "verify_lineage_liveness",
      "admit_request"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "CapabilityResurrectionError",
      "EpochRegressionError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}