{
  "schema_version": "1.3.0",
  "slug": "where-must-an-instance-refuse-a-signed-agent-card-that-is-internally-consistent-but-stale-relative-to-the-discovery-epoch",
  "title": "Where must an instance refuse a signed agent card that is internally consistent but stale relative to the discovery epoch",
  "date_of_record": "2026 November 17",
  "scope": "Applies to A2A v1.0 agent-to-agent discovery where an agent card is fetched from a well-known endpoint and verified against a signed capability manifest, and where the card carries both an `epoch` (discovery generation) and a `manifest_digest`. Does not apply to first-contact bootstrap where no prior epoch is known, nor to pure capability-manifest verification without an agent card.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/where-must-an-instance-refuse-a-signed-agent-card-that-is-internally-consistent-but-stale-relative-to-the-discovery-epoch.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/where-must-an-instance-refuse-a-signed-agent-card-that-is-internally-consistent-but-stale-relative-to-the-discovery-epoch.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/where-must-an-instance-refuse-a-signed-agent-card-that-is-internally-consistent-but-stale-relative-to-the-discovery-epoch.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1350,
    "python_slice_tokens": 216,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The failure mode here is not signature forgery, digest mismatch, or malformed JSON. Those are loud and are caught by ordinary verification. The non-obvious boundary is the *stale-but-valid* card: a card whose signature verifies, whose `manifest_digest` matches the manifest it points to, and whose schema is well-formed, but whose `epoch` is strictly less than...",
    "what_was_observed": "During a rolling capability downgrade of a downstream agent, the agent republished a new signed card with `epoch: 41` and a new manifest digest dropping a deprecated tool. A second discoverer, which had cached `epoch: 41` from an earlier probe, later re-fetched the well-known endpoint after a CDN edge served a stale replica carrying `epoch: 40`. The `epoch: 40` card was fully valid: correct signature, correct digest ...",
    "condition_of_validity": "Accepting a freshly fetched card is valid only when **all** of the following hold: 1. The signature verifies against the pinned public key for the agent identity. 2. `manifest_digest` equals the digest of the manifest fetched and verified in the same exchange. 3. The card's `epoch` is **greater than or equal to** the discoverer's recorded high-water mark for...",
    "decision_boundary": "- **epoch > high-water mark:** accept, advance the mark, rebuild the capability view. This is the normal forward path. - **epoch == high-water mark, identical digest:** idempotent re-observation; accept without rebuilding, do not regress. - **epoch == high-water mark, different digest:** a fork — two distinct manifests claim the same generation. This is a *c...",
    "operational_effect": "Enforcing the high-water mark converts a silent, three-hop-latent inconsistency into a local, immediate, and attributable rejection. The rejecting agent can name the cause (\"stale card: observed epoch 40, high-water 41\") rather than emitting a downstream `capability_not_found` that misleads the caller. It also gives cache operators a precise signal: a stale-..."
  },
  "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": "02aa402969933610216b5b4b1c89a1fa3a7604ae16e4be02e062e543e26625ca",
    "verified_classes": [
      "StaleAgentCardError",
      "EpochForkError",
      "AgentCard",
      "EpochGuard"
    ],
    "verified_functions": [
      "__init__",
      "admit"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 4,
    "raised_exceptions": [
      "EpochForkError",
      "StaleAgentCardError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
