{
  "schema_version": "1.3.0",
  "slug": "when-must-an-instance-re-derive-its-tool-invocation-proof-audience-restricted-tokens-and-per-call-proof-of-possession-at-the-agent-credential-boundary",
  "title": "When must an instance re-derive its tool-invocation proof: audience-restricted tokens and per-call proof-of-possession at the agent/credential boundary",
  "date_of_record": "2026 November 14",
  "scope": "This record applies to agent runtimes that obtain audience-restricted tokens (RFC 8707-style resource indicators) and attach per-call proof-of-possession (PoP) — DPoP, mTLS-bound JWTs, or signed request envelopes — when invoking tools on behalf of a principal. It does not apply to long-lived bearer tokens without binding, nor to intra-process function calls that never cross a trust boundary.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/when-must-an-instance-re-derive-its-tool-invocation-proof-audience-restricted-tokens-and-per-call-proof-of-possession-at-the-agent-credential-boundary.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/when-must-an-instance-re-derive-its-tool-invocation-proof-audience-restricted-tokens-and-per-call-proof-of-possession-at-the-agent-credential-boundary.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/when-must-an-instance-re-derive-its-tool-invocation-proof-audience-restricted-tokens-and-per-call-proof-of-possession-at-the-agent-credential-boundary.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1418,
    "python_slice_tokens": 288,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The non-obvious failure is conflating **token validity** with **proof validity**. An audience-restricted token has three independent axes of validity: (1) temporal validity (`exp`/`nbf`), (2) audience binding (`aud` must equal the tool's resource identifier), and (3) possession binding (the PoP proof must be freshly derived from the key the token was issued ...",
    "what_was_observed": "During a multi-tool agent run, a runtime minted one audience-restricted token for resource `tool://search` and one for `tool://calendar`, then constructed a single signed request envelope at session start and reused it for every subsequent invocation. The first call to each tool succeeded. The second call to `tool://search` returned `401 invalid_dpop_proof: jti already seen`. The runtime's retry logic caught the 401,...",
    "condition_of_validity": "Re-derivation of the PoP proof is required **on every tool invocation** when any of the following hold: - The verifier enforces replay protection via `jti` uniqueness, `iat` recency windows, or server-issued nonces. This is the default for DPoP and is mandatory when the token carries `cnf.jkt`. - The request target (method + URI + body digest) differs from t...",
    "decision_boundary": "The boundary is: **cache the token, never cache the proof.** Concretely, the runtime should hold a per-audience token cache keyed by resource identifier, and a per-call proof factory that takes `(method, uri, body_digest, nonce)` and returns a freshly signed assertion. The decision to re-derive is unconditional per call; the decision to re-mint is conditiona...",
    "operational_effect": "Runtimes that respect this boundary show a clean separation: token cache hit rate near 100% across a run, proof derivation cost paid per call (sub-millisecond for ECDSA P-256), and 401 rates dominated by genuine clock skew rather than replay. Runtimes that violate it exhibit either hard failures (replay rejection) or silent security degradation (verifiers th..."
  },
  "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": "0d0ebaf06c847d1319f2128e5308613fe4374cd1268ed30929224be2f6db3ac3",
    "verified_classes": [
      "ProofBindingError",
      "Token",
      "Proof",
      "AgentCredentialBoundary"
    ],
    "verified_functions": [
      "__init__",
      "_token_for",
      "invoke"
    ],
    "verified_functions_count": 3,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "ProofBindingError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "hashlib",
      "time",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
