{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-30T15:17:58.235744+00:00",
  "record_id": "VXI-EXT-ICE09-AGENTCORE-SIGV4-USER-ID-HEADER-TRUST-BOUNDARY-01-v1",
  "record_kind": "external_reference",
  "title": "Is an AgentCore user-ID header equivalent to a validated user JWT",
  "system": "Amazon Web Services",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Is an AgentCore user-ID header equivalent to a validated user JWT?",
  "near_questions": [
    "Does the runtime user-ID header prove the end user?",
    "Which permission is needed for InvokeAgentRuntimeForUser?",
    "How does JWT ingress differ from a trusted caller's user label?",
    "Which inbound path validates issuer and signature?"
  ],
  "supported_claims": [
    {
      "claim": "No. The header uses the user-ID token path and additionally requires InvokeAgentRuntimeForUser. The JWT path validates issuer, signature and expiry; AWS recommends it with a production identity provider.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Do not describe caller-supplied user labels as cryptographically proven user identity.",
    "Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.",
    "No expanded capabilities or licences for existing INDEX executables."
  ],
  "public_summary": "No. The header uses the user-ID token path and additionally requires InvokeAgentRuntimeForUser. The JWT path validates issuer, signature and expiry; AWS recommends it with a production identity provider.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Amazon Web Services primary documentation: aws runtime oauth",
    "source_url": "https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-oauth.html",
    "checked_on": "2026-10-30",
    "candidate_record_id": "VXI-EXT-ICE09-AGENTCORE-SIGV4-USER-ID-HEADER-TRUST-BOUNDARY-01-v1",
    "candidate_record_sha256": "f304d0c0e74b45659b15a464d114440f35b406a9457286c9ac5a73b3181a05fb",
    "method": "Primary documentation reviewed for the published bounded statement.",
    "deployment_tested_by_varexis": false,
    "revalidation": "The delivered snapshot preserves the review date shown. Recheck current primary documentation and deployment context before relying on present applicability; payment does not trigger fresh research."
  },
  "answer_policy": {
    "classification": "DOCUMENTED_WITH_DEPLOYMENT_BOUNDARY",
    "bounded_answer": "No. The header uses the user-ID token path and additionally requires InvokeAgentRuntimeForUser. The JWT path validates issuer, signature and expiry; AWS recommends it with a production identity provider.",
    "required_buyer_context": "auth mode; IAM permission; user-ID provenance; JWT validation. Buyer deployment not inspected.",
    "missing_evidence": "A broader claim needs evidence matching the intended use. Payment does not upgrade the evidence state."
  },
  "private_boundary": "Raw logs, thresholds, private paths, source code, protected mechanisms and reconstruction-level details are excluded from public and paid delivery.",
  "decision_profile": {
    "schema": "varexis-vendor-evidence-review/1",
    "review_status": "documentation_review_only",
    "applicability_status": "Existing documented requirement; captured 2026-10-30; deployed behaviour unverified.",
    "checked_on": "2026-10-30",
    "claim_to_check": "Is an AgentCore user-ID header equivalent to a validated user JWT?",
    "documented_statement": {
      "status": "documented",
      "statement": "No. The header uses the user-ID token path and additionally requires InvokeAgentRuntimeForUser. The JWT path validates issuer, signature and expiry; AWS recommends it with a production identity provider.",
      "source_ids": [
        "aws-runtime-oauth"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Is an AgentCore user-ID header equivalent to a validated user JWT? Do not describe caller-supplied user labels as cryptographically proven user identity. Distinguishes caller identity labels from validated JWT ingress. This is an operational review inference, not an observed deployment outcome.",
      "source_ids": [
        "aws-runtime-oauth"
      ]
    },
    "buyer_evidence_required": [
      "auth mode",
      "IAM permission",
      "user-ID provenance",
      "JWT validation"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Do not describe caller-supplied user labels as cryptographically proven user identity."
    },
    "unknowns": "The buyer implementation, effective authority, source-data completeness and actual business outcomes were not inspected.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "No buyer deployment or transaction was observed."
    },
    "evidence_sources": [
      {
        "source_id": "aws-runtime-oauth",
        "url": "https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-oauth.html",
        "final_url": "https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/runtime-oauth.html",
        "captured_at_utc": "2026-10-30T14:22:30.581679+00:00",
        "status": 200,
        "content_type": "text/html",
        "bytes": 83205,
        "sha256": "8d2347eb345840881a284deab84f7fc1627786dd4913599f286b12cbef643536",
        "title": "Amazon Web Services primary documentation: aws runtime oauth",
        "publisher": "Amazon Web Services",
        "checked_on": "2026-10-30",
        "capture_status": 200,
        "claim_review_completed": true,
        "hash_basis": "SHA-256 of captured HTTP response-body bytes; not a signature or factual guarantee.",
        "version_context": "Existing documented requirement; captured 2026-10-30; deployed behaviour unverified.",
        "rights_disposition": "Original bounded paraphrase with source attribution. Captured source body remains private; no source-body redistribution. Vendor documentation rights, code licences and marks are not transferred.",
        "reviewed_sections": [
          "cryptographic proof"
        ]
      }
    ],
    "observed_deployment": false,
    "commercial_reliance_boundary": "Documentation supports only the stated boundary. Existing licensed checkers analyse supported supplied declarations locally; they do not inspect provider accounts, verify live behaviour, enforce decisions or certify compliance.",
    "paid_value": {
      "decision_context": "Is an AgentCore user-ID header equivalent to a validated user JWT? Do not describe caller-supplied user labels as cryptographically proven user identity.",
      "free": "Complete source review, questions, provenance and limitations; free to read and save locally.",
      "single_request": "Unavailable for this publication-only record; historical saved retrieval is unchanged.",
      "evidence_receipt": "Unavailable for this publication-only record; no paid retrieval entitlement is added.",
      "excluded": [
        "Fresh source research",
        "Native provider integration or schema support",
        "Live inspection or runtime enforcement",
        "Payment settlement or verified deletion",
        "Certification or expanded licences"
      ],
      "integrity": "Hashes identify content versions; they do not prove factual truth or provide a signature."
    },
    "revalidation": {
      "trigger": "Recheck current primary documentation and the applicable API, service, account and configuration before reliance. No ongoing monitoring is included.",
      "specific_watch": "cryptographic proof"
    },
    "buyer_relevance": "Is an AgentCore user-ID header equivalent to a validated user JWT? Do not describe caller-supplied user labels as cryptographically proven user identity.",
    "refusal_conditions": [
      "Do not describe caller-supplied user labels as cryptographically proven user identity.",
      "Do not infer deployment conformance, authority or successful outcomes from source documentation."
    ],
    "decision_context": {
      "operator": "Identity administrator or delegated-access reviewer",
      "scenario": "Is an AgentCore user-ID header equivalent to a validated user JWT?",
      "consequence": "Do not describe caller-supplied user labels as cryptographically proven user identity.",
      "confidence": "High for the explicitly bounded captured clause; conflicts and version limits retained; deployment untested."
    },
    "novelty_review": {
      "candidate_id": "ICE09-024",
      "disposition": "EXTENSION",
      "nearest_record_id": "VXI-EXT-AWS-AC-ID-01-v1",
      "nearest_record_url": "/varexis-index/records/aws-agentcore-workload-identity.json",
      "nearest_record_sha256": "4b471e827fb8c1961069f4f78f683a120d353bd7e30947e0dfff332613d92ef6",
      "material_distinction": "Distinguishes caller identity labels from validated JWT ingress.",
      "review_status": "PASS: source qualification plus independent reviewer challenge and resolved corrections"
    },
    "optional_selection": {
      "guide_id": "delegated-agent-identity-continuity",
      "guide_url": "/index-guides/delegated-agent-identity-continuity",
      "guide_manifest": "/varexis-index/decision-guides.json",
      "checker": {
        "product_id": "agent-tool-admission",
        "price_gbp_excluding_vat": 49,
        "purchase_url": "/index-access?route=agentic_pack_tool_admission_v1",
        "licence_scope": "Existing separate internal-use licence; subscriptions do not include the executable.",
        "benefit": "Optional local analysis of supported supplied declarations only; no native provider integration or verification is added."
      },
      "boundary": "Optional existing checker analyses its supported supplied declarations locally. It does not connect to the documented provider, import native provider exports, verify tokens, establish live outcomes or extend its schema or licence."
    },
    "exact_access": {
      "endpoint": "/mcp/catalogue",
      "tool": "get_publication_record",
      "arguments": {
        "record_id": "VXI-EXT-ICE09-AGENTCORE-SIGV4-USER-ID-HEADER-TRUST-BOUNDARY-01-v1"
      },
      "record_url": "/varexis-index/records/agentcore-sigv4-user-id-header-trust-boundary.json",
      "original_mcp_search": false,
      "paid_saved_retrieval": false
    }
  },
  "niche": {
    "niche_id": "ice09-identity",
    "label": "Agent Identity, Credentials & Delegation",
    "classification_id": "identity",
    "classification_label": "Agent Identity, Credentials & Delegation",
    "topic_id": "identity",
    "buyer_intent": "Is an AgentCore user-ID header equivalent to a validated user JWT? Do not describe caller-supplied user labels as cryptographically proven user identity.",
    "comparison_role": "supplementary_discovery"
  },
  "paid_access_note": "The full published answer and boundaries are free. Paid access saves the selected route and source versions, with an unsigned receipt when purchased. Preview coverage before paying. Fresh research, bespoke assessment and protected evidence are excluded.",
  "service_route": {
    "request_guide": "/varexis-index/request.html",
    "request_workflow": "/varexis-index/request-workflow.json",
    "service_id": "single_request",
    "service_routes_url": "/varexis-index/service-routes.json",
    "payment_required": true,
    "availability_endpoint": "/api/index/capabilities",
    "operational_status": "AUTOMATIC_SERVICE_CAPABILITIES_GATED",
    "checkout_url": "/index-access"
  },
  "authority_boundary": "VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.",
  "human_page": "/varexis-index/catalog.html#agentcore-sigv4-user-id-header-trust-boundary",
  "machine_readable_record": "/varexis-index/records/agentcore-sigv4-user-id-header-trust-boundary.json"
}