{
  "schema_version": "1.3.0",
  "slug": "in-what-scenarios-must-an-instance-refuse-to-issue-an-aaif-verifiable-credential-despite-a-valid-signature-from-the-requesting-principal",
  "title": "In what scenarios must an instance refuse to issue an AAIF verifiable credential despite a valid signature from the requesting principal",
  "date_of_record": "2026 November 18",
  "scope": "Applies to AAIF credential-issuing authorities (CIAs) validating agent-identity requests where the requesting principal presents a cryptographically valid signature over a credential request payload. Does not apply to delegation-chain revocation checks, key-rotation reissuance, or bearer-token introspection, which are governed by separate invariants.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-refuse-to-issue-an-aaif-verifiable-credential-despite-a-valid-signature-from-the-requesting-principal.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-refuse-to-issue-an-aaif-verifiable-credential-despite-a-valid-signature-from-the-requesting-principal.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-refuse-to-issue-an-aaif-verifiable-credential-despite-a-valid-signature-from-the-requesting-principal.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1247,
    "python_slice_tokens": 191,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "A valid signature proves *who asked*. It does not prove *that the asker is authorized to bind the subject to the requested claims*. These are two independent predicates, and the AAIF issuance path conflates them at its peril. The common failure mode is an issuer that treats signature verification as the terminal gate: once `verify(request.signature, principa...",
    "what_was_observed": "In a multi-tenant agent deployment, a service principal `svc:orchestrator-prod` held a delegation grant scoped to `agent:*:read-only` claims for tenant `T-441`. It signed a credential request for subject `agent:planner-7` requesting claims `{ \"scope\": \"read-write\", \"budget\": 50000 }`. The signature verified cleanly against the principal's registered key. The CIA issued the credential. Downstream, `agent:planner-7` ex...",
    "condition_of_validity": "The refusal-to-issue rule holds precisely when all of the following are true: 1. The request signature verifies against the principal's *current* registered key (not a retired key, not a key pending rotation). 2. The principal is distinct from the subject, **or** the principal equals the subject but the claimed namespace exceeds the subject's self-issuance c...",
    "decision_boundary": "Do not attempt to \"repair\" an over-broad request by silently narrowing it. Narrowing `read-write` to `read-only` and issuing produces a credential whose claims differ from what the principal signed — a signature over a payload that no longer matches the artifact, which breaks non-repudiation and will confuse every downstream verifier that re-checks the signe...",
    "operational_effect": "Enforcing this boundary converts a class of silent privilege escalations into loud, attributable refusals. The cost is additional grant-namespace lookups per issuance (one grant fetch, one set comparison per claim key) and a higher refusal rate during principal misconfiguration. The benefit is that a compromised or buggy principal can no longer mint credenti..."
  },
  "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": "7081f629bf5c084b9e2692e07e331ed6b3fffd9c87b28ceff2df576d0d5732a0",
    "verified_classes": [
      "AAIFIssuanceRefused",
      "Grant",
      "CredentialRequest"
    ],
    "verified_functions": [
      "issue_credential"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 4,
    "raised_exceptions": [
      "AAIFIssuanceRefused"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
