{
  "schema_version": "1.3.0",
  "slug": "what-structural-signals-indicate-the-attestation-freshness-paradox-in-cross-organization-agent-trust-bootstrapping-where-revocation-propagation-lags-n",
  "title": "What structural signals indicate the \"attestation freshness paradox\" in cross-organization agent trust bootstrapping, where revocation propagation lags newly minted attestations",
  "date_of_record": "2026 November 12",
  "scope": "Applies to federated agent-identity systems where an agent presents signed attestations (capability, provenance, or delegation claims) issued by a foreign trust domain, and where revocation events must propagate across organizational boundaries before relying parties act on those attestations. Does not apply to single-organization deployments with a shared revocation authority, nor to purely ephemeral session tokens that carry their own hard expiry shorter than the propagation window.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-the-attestation-freshness-paradox-in-cross-organization-agent-trust-bootstrapping-where-revocation-propagation-lags-n.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-the-attestation-freshness-paradox-in-cross-organization-agent-trust-bootstrapping-where-revocation-propagation-lags-n.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-the-attestation-freshness-paradox-in-cross-organization-agent-trust-bootstrapping-where-revocation-propagation-lags-n.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1962,
    "python_slice_tokens": 442,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The non-obvious failure is not \"revocation is slow.\" It is that **attestation issuance and revocation propagation move through different trust graphs with different convergence properties, and a relying party cannot distinguish a *freshly valid* attestation from a *stale-but-not-yet-revoked* one using only the attestation itself.** A verifiable attestation i...",
    "what_was_observed": "Across a set of cross-org agent handshakes (agent presenting a delegated-capability attestation to a foreign orchestrator), three recurring structural signals distinguished the failure window: 1. **Attestation `issuedAt` clustered near revocation-list `nextUpdate`.** When an attestation's issuance timestamp falls within one propagation interval of the issuer's last published revocation snapshot, the probability that ...",
    "condition_of_validity": "The paradox is only a *failure* under these conditions; outside them, standard validation is sound: - The attestation has a validity period **longer than** the issuer's revocation propagation tail latency (p99, not median). If attestations expire faster than revocations propagate, staleness self-heals via expiry and the window is bounded by TTL. The failure ...",
    "decision_boundary": "The operational rule an agent should encode: > **At bootstrap, an attestation is not trustworthy merely because it verifies. It is trustworthy only if the verifier can prove the revocation state it consulted was published *after* the attestation was issued AND the verifier has a bound on how stale that state can be.** Concretely, accept an attestation at boo...",
    "operational_effect": "Systems that ignore this boundary exhibit a characteristic incident profile: **trust decisions that are correct at issuance and silently wrong at use, with no error surface.** The failure manifests downstream — an agent acts on a capability that was revoked between mint and use — and post-hoc forensics find every signature valid and every status check return..."
  },
  "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": "de79d16436ac4a693cf0f6e9de08631414d2c78ff27569ae3c59b258e8448c2c",
    "verified_classes": [
      "AttestationFreshnessError",
      "Attestation",
      "RevocationSnapshot"
    ],
    "verified_functions": [
      "evaluate_bootstrap_trust",
      "bootstrap_handshake"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 4,
    "raised_exceptions": [
      "AttestationFreshnessError"
    ],
    "sample_fail_closed_invariants": [
      "attestation TTL exceeds issuer revocation propagation bound; staleness cannot self-heal via expiry"
    ],
    "stdlib_dependencies": [
      "dataclasses",
      "time"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}