{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-24T21:56:24.175Z",
  "record_id": "VXI-EXT-PROCUREMENT-SPIFFE-JWT-JTI-REPLAY-BOUNDARY-01-v1",
  "record_kind": "external_reference",
  "title": "SPIFFE token replay and uniqueness",
  "system": "SPIFFE",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does a JWT-SVID jti claim make a SPIFFE workload token single-use?",
  "near_questions": [
    "Is a SPIFFE JWT identifier proof that replay is blocked?",
    "Can a JWT-SVID recipient reuse a token at another audience?",
    "Does SPIFFE require validators to remember every jti?",
    "What evidence supports single-use JWT-SVID acceptance?"
  ],
  "supported_claims": [
    {
      "claim": "The pinned JWT-SVID specification permits jti but does not require validators to track its uniqueness. JWT-SVIDs remain bearer tokens: audience and expiry constrain exposure without eliminating replay. A token with multiple audiences can be replayed by one recipient to another listed recipient. Single-use acceptance therefore needs separately evidenced controls.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "The buyer validator and replay state have not been tested.",
    "Authentication or a policy result does not establish business approval, safe tool behaviour or completed execution.",
    "Buyer deployment testing, live runtime enforcement, certification or permission to act",
    "Expanded capabilities or licences for existing INDEX executables"
  ],
  "public_summary": "The pinned JWT-SVID specification permits jti but does not require validators to track its uniqueness. JWT-SVIDs remain bearer tokens: audience and expiry constrain exposure without eliminating replay. A token with multiple audiences can be replayed by one recipient to another listed recipient. Single-use acceptance therefore needs separately evidenced controls.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "The JWT SPIFFE Verifiable Identity Document",
    "source_url": "https://raw.githubusercontent.com/spiffe/spiffe/49a9cbbc018c39ec6643ad3301632f9f4549258b/standards/JWT-SVID.md",
    "checked_on": "2026-10-24",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-SPIFFE-JWT-JTI-REPLAY-BOUNDARY-01-v1",
    "candidate_record_sha256": "aacb15098010d9be22f77cf6a256b5e10af5f400678c16e9f42818a5cb2df3d5",
    "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": "The pinned JWT-SVID specification permits jti but does not require validators to track its uniqueness. JWT-SVIDs remain bearer tokens: audience and expiry constrain exposure without eliminating replay. A token with multiple audiences can be replayed by one recipient to another listed recipient. Single-use acceptance therefore needs separately evidenced controls.",
    "required_buyer_context": "Token audiences, expiry and identifier; Validator replay-state design and request evidence; Approved receiver identity and token validation configuration. 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",
    "checked_on": "2026-10-24",
    "claim_to_check": "Does a JWT-SVID jti claim make a SPIFFE workload token single-use?",
    "documented_statement": {
      "status": "documented",
      "statement": "The pinned JWT-SVID specification permits jti but does not require validators to track its uniqueness. JWT-SVIDs remain bearer tokens: audience and expiry constrain exposure without eliminating replay. A token with multiple audiences can be replayed by one recipient to another listed recipient. Single-use acceptance therefore needs separately evidenced controls.",
      "source_ids": [
        "spiffe-jwt"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Decide whether a captured workload token can be reused for another tool call. This is a source-based review decision, not an observed deployment result.",
      "source_ids": [
        "spiffe-jwt"
      ]
    },
    "buyer_evidence_required": [
      "Token audiences, expiry and identifier",
      "Validator replay-state design and request evidence",
      "Approved receiver identity and token validation configuration"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Do not infer single-use protection from jti or a valid signature alone."
    },
    "unknowns": "The buyer validator and replay state have not been tested.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "The buyer validator and replay state have not been tested."
    },
    "evidence_sources": [
      {
        "source_id": "spiffe-jwt",
        "url": "https://raw.githubusercontent.com/spiffe/spiffe/49a9cbbc018c39ec6643ad3301632f9f4549258b/standards/JWT-SVID.md",
        "final_url": "https://raw.githubusercontent.com/spiffe/spiffe/49a9cbbc018c39ec6643ad3301632f9f4549258b/standards/JWT-SVID.md",
        "status": 200,
        "captured_at_utc": "2026-10-24T21:45:00.022Z",
        "sha256": "ee07b4e725221331e4e88f897067474b62703383da9587d994d0a47f53287dff",
        "bytes": 12058,
        "title": "The JWT SPIFFE Verifiable Identity Document",
        "hash_basis": "Decoded HTTP response body bytes",
        "rights_review": "Original factual paraphrase and source metadata only; Apache-2.0 repository captures retained privately and not redistributed.",
        "checked_on": "2026-10-24",
        "capture_status": 200,
        "claim_review_completed": true,
        "reviewed_sections": [
          "7.1 Replay Protection",
          "7.2 Audience"
        ],
        "version_context": "Pinned spiffe/spiffe revision 49a9cbbc018c39ec6643ad3301632f9f4549258b captured 2026-10-24. Documentation review, not evidence that a buyer implementation conforms."
      }
    ],
    "observed_deployment": false,
    "commercial_reliance_boundary": "Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.",
    "paid_value": {
      "decision_context": "Decide whether a captured workload token can be reused for another tool call.",
      "free": "Complete review, sources, practical questions and limitations; may be saved locally.",
      "single_request": "Existing server-saved version-bound route snapshot for later authenticated retrieval.",
      "evidence_receipt": "The same snapshot plus the existing unsigned delivery receipt.",
      "excluded": [
        "Fresh vendor research",
        "Continuous monitoring or change alerts",
        "Testing the buyer configuration",
        "Private evidence or vendor certification"
      ],
      "integrity": "Hashes identify content versions; they do not prove truth or provide a signature."
    },
    "revalidation": {
      "trigger": "A saved purchase does not recheck the source or buyer configuration.",
      "specific_watch": "Recheck the pinned source, actual implementation version, policy inputs and retained decision evidence before relying on a current outcome."
    },
    "buyer_relevance": "Decide whether a captured workload token can be reused for another tool call.",
    "refusal_conditions": [
      "Do not infer single-use protection from jti or a valid signature alone."
    ]
  },
  "niche": {
    "niche_id": "agent-authority-action-evidence",
    "label": "Agent Authority & Action Evidence",
    "classification_id": "identity",
    "classification_label": "Agent Identity, Credentials & Delegation",
    "topic_id": "identity",
    "buyer_intent": "Decide whether a captured workload token can be reused for another tool call.",
    "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#spiffe-jwt-jti-replay-boundary",
  "machine_readable_record": "/varexis-index/records/spiffe-jwt-jti-replay-boundary.json"
}