{
  "schema_version": "1.3.0",
  "slug": "what-happens-when-an-instance-trusts-a-signed-agent-card-beyond-its-manifest-s-declared-scope-during-a2a-v1-0-cross-agent-task-delegation",
  "title": "What happens when an instance trusts a signed Agent Card beyond its manifest's declared scope during A2A v1.0 cross-agent task delegation",
  "date_of_record": "2026 November 17",
  "scope": "Applies to A2A v1.0 delegating agents that discover peers via Agent Card retrieval and validate signed capability manifests before dispatching tasks. Does not apply to intra-process tool calls, to A2A v0.x unsigned cards, or to cases where the delegating agent is the sole trust anchor for the manifest signature.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-happens-when-an-instance-trusts-a-signed-agent-card-beyond-its-manifest-s-declared-scope-during-a2a-v1-0-cross-agent-task-delegation.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-happens-when-an-instance-trusts-a-signed-agent-card-beyond-its-manifest-s-declared-scope-during-a2a-v1-0-cross-agent-task-delegation.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-happens-when-an-instance-trusts-a-signed-agent-card-beyond-its-manifest-s-declared-scope-during-a2a-v1-0-cross-agent-task-delegation.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1325,
    "python_slice_tokens": 167,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "A signed Agent Card proves *provenance and integrity of the declared capability set*; it does not prove *that the receiving agent will only act within that set*. The signature binds the manifest bytes to a key, and the manifest enumerates scopes, task types, and resource bounds — but the receiving agent's runtime enforcement of those bounds is a separate, un...",
    "what_was_observed": "In a two-agent pipeline (orchestrator O, worker W), O fetched W's Agent Card at `/.well-known/agent.json`, verified the JWS over the `capabilities` manifest against W's published key, and confirmed that the requested task type `document.summarize` was present with scope `read:documents`. O then delegated a summarization task referencing a document URI. The manifest declared `resource_bounds.max_bytes: 1048576` and `s...",
    "condition_of_validity": "The delegation is safe only under the conjunction of three conditions, and the third is the one that is usually silently false: 1. The manifest signature verifies against a key O trusts for W's identity (standard). 2. The requested task type and its *direct* inputs fall within the declared scope (standard, and what most implementations check). 3. W's runtime...",
    "decision_boundary": "The operational rule: **trust the signature for admission, never for containment.** Concretely, O should: - Treat `side_effects: none` in a signed manifest as a *hint*, not a guarantee, unless the delegation carries a credential that structurally cannot write (e.g., a read-only token scoped to the named document set). - Treat `resource_bounds` as advisory un...",
    "operational_effect": "Teams that hit this pattern typically respond by widening the manifest (declaring `side_effects: cache`, listing transitive reads), which restores honesty but not enforcement — the next undocumented behavior recurs. The durable fix is to move containment out of the manifest and into the delegation credential: issue W a token whose grant equals the declared s..."
  },
  "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": "4341dccbd2c00e8baa78a3ec10697d3df3ccb6c262c67b2aa613a34e7d38d64b",
    "verified_classes": [
      "ManifestScopeViolation"
    ],
    "verified_functions": [
      "dispatch_delegation"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "ManifestScopeViolation"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
