{
  "schema_version": "1.3.0",
  "slug": "which-invariants-prevent-silent-capability-drift-in-a2a-v1-0-agent-card-discovery-and-cross-vendor-task-delegation-negotiation",
  "title": "Which invariants prevent silent capability drift in A2A v1.0 agent card discovery and cross-vendor task delegation negotiation",
  "date_of_record": "2026 November 15",
  "scope": "Applies to A2A v1.0 deployments where an orchestrating agent resolves peer capabilities via `/.well-known/agent-card.json` and then negotiates task delegation across vendor boundaries. Does not apply to intra-vendor delegation where both sides share a synchronized card registry, nor to A2A v0.x where card versioning was advisory rather than binding.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/which-invariants-prevent-silent-capability-drift-in-a2a-v1-0-agent-card-discovery-and-cross-vendor-task-delegation-negotiation.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/which-invariants-prevent-silent-capability-drift-in-a2a-v1-0-agent-card-discovery-and-cross-vendor-task-delegation-negotiation.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/which-invariants-prevent-silent-capability-drift-in-a2a-v1-0-agent-card-discovery-and-cross-vendor-task-delegation-negotiation.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1416,
    "python_slice_tokens": 189,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "Agent card discovery is frequently modeled as a one-shot resolution: fetch the card, cache the capabilities, delegate. This model is wrong in a way that fails silently. The invariant that actually holds is that **a card is a claim, not a contract, and the claim is only valid for the negotiation epoch in which it was emitted.** The non-obvious boundary is tha...",
    "what_was_observed": "Across three cross-vendor delegations in a single orchestration run, the following pattern reproduced: 1. Orchestrator fetched peer card at `T0`, observed capability `task.execute` with `idempotency: \"required\"` and `partial_results: false`. 2. At `T0+40min`, peer redeployed. Card still advertised `task.execute`. `idempotency` field was dropped (defaulted by the peer to `\"optional\"`), and `partial_results` flipped to...",
    "condition_of_validity": "The invariant \"a cached card remains a valid basis for delegation\" holds only under all of the following: - The peer guarantees that any change to a capability's *behavioral* contract (not just its schema) bumps a monotonic field the orchestrator pins against — in practice a content hash of the capability subtree, not the card-level `version`. - The negotiat...",
    "decision_boundary": "The decision boundary is between *re-fetch-and-renegotiate* and *delegate-on-cache*. The correct rule: - If the delegation is idempotent-safe **and** the result validator can detect truncation independently (e.g., the orchestrator knows the expected cardinality), delegate on cache and validate on return. - If the delegation depends on a capability term the o...",
    "operational_effect": "The operational consequence is that cross-vendor delegation requires a **capability-hash pin** carried in the negotiation envelope, distinct from the card signature and distinct from the card version string. Without it, the failure mode is a completed task with a plausible but semantically wrong result — the most expensive class of failure because it passes ..."
  },
  "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": "2487269c119da04953800e92026f48ad6cfe6f6e5bcd9ce56fcf8d3a276e8252",
    "verified_classes": [
      "CapabilityDriftError",
      "PinnedCard"
    ],
    "verified_functions": [
      "capability_hash",
      "negotiate_delegation"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 1,
    "raised_exceptions": [
      "CapabilityDriftError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "hashlib",
      "json"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
