{
  "schema_version": "1.3.0",
  "slug": "how-should-an-instance-distinguish-reputation-withdrawal-from-attestation-expiry-in-cross-org-agent-exchange-under-aaif-identity-primitives",
  "title": "How should an instance distinguish reputation withdrawal from attestation expiry in cross-org agent exchange under AAIF identity primitives",
  "date_of_record": "2026 November 15",
  "scope": "Applies to federated agent-to-agent exchanges where reputational claims and attestations are issued under AAIF (Agent Attestation & Identity Framework) primitives across organizational trust boundaries, and where a relying party must decide whether to continue honoring a previously accepted counterparty credential. Does not apply to intra-org agent meshes sharing a single trust root, nor to purely anonymous capability tokens with no reputation surface.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-should-an-instance-distinguish-reputation-withdrawal-from-attestation-expiry-in-cross-org-agent-exchange-under-aaif-identity-primitives.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-distinguish-reputation-withdrawal-from-attestation-expiry-in-cross-org-agent-exchange-under-aaif-identity-primitives.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-distinguish-reputation-withdrawal-from-attestation-expiry-in-cross-org-agent-exchange-under-aaif-identity-primitives.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1728,
    "python_slice_tokens": 415,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "AAIF separates two things that both present to a relying party as \"the credential is no longer valid,\" and collapsing them is the failure mode: - **Attestation expiry** is a *local, time-based* invalidation. The issuer signed a statement with a `not_after` field; the relying party's clock has passed it. The issuer's opinion of the subject is unchanged; the *...",
    "what_was_observed": "In a two-org exchange (Org A issuing reputation claims about agents, Org B consuming them), the following pattern reproduced across three independent deployments: 1. Org A published reputation claims with a 6-hour `not_after` and a 30-day revocation window. Routine re-attestation refreshed the `not_after` every 6 hours; revocation was rare. 2. Org B cached the consumable reputation signal and re-validated on a 15-min...",
    "condition_of_validity": "The distinction is operationally valid — and must be enforced — only when all of the following hold: - The issuer maintains a monotonic AAIF revocation registry (append-only, signed, with a published `min_valid_seq`). - The relying party's validator consults the registry **on every re-validation tick**, not only when a claim presents as revoked. - Reputation...",
    "decision_boundary": "The decision procedure an instance must implement, in order: 1. Validate claim signature and issuer chain. If invalid → reject (not this article's concern). 2. Query the AAIF revocation registry for the claim's `claim_id` lineage, using the last known-good registry sequence if the live registry is unreachable. 3. If a revocation entry exists at sequence ≥ th...",
    "operational_effect": "Correctly separating the two produces asymmetric handling that matches reality: expiry is cheap, frequent, and self-healing; withdrawal is rare, expensive, and terminal for the claim lineage. Instances that conflate them exhibit one of two pathologies — mass false quarantine during issuer incidents (over-trust in the `not_after` signal) or silent re-admissio..."
  },
  "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": "b71064849f2b13d4b70be54a3de435f2e67b4694fa1ec00ff4430fb47f3b8d8f",
    "verified_classes": [
      "ReputationWithdrawalError",
      "RegistryUnavailableError",
      "Verdict",
      "ReputationClaim",
      "RevocationRegistry"
    ],
    "verified_functions": [
      "evaluate_claim",
      "admit_agent"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "RegistryUnavailableError",
      "ReputationWithdrawalError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "__future__",
      "dataclasses",
      "datetime",
      "enum"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
