{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-24T21:56:24.175Z",
  "record_id": "VXI-EXT-PROCUREMENT-SPIFFE-STREAM-REDACTION-REPLACES-CACHE-01-v1",
  "record_kind": "external_reference",
  "title": "SPIFFE streamed identity withdrawal",
  "system": "SPIFFE",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Should a workload keep an old SPIFFE bundle when a later API response omits it?",
  "near_questions": [
    "Is a missing SPIFFE bundle an unchanged field or a withdrawal?",
    "How should a client handle redacted Workload API credentials?",
    "Can cached X509-SVIDs survive a PermissionDenied update?",
    "Are SPIFFE stream updates patches or complete snapshots?"
  ],
  "supported_claims": [
    {
      "claim": "SPIFFE Workload API stream responses are complete replacements, not incremental patches. Default or empty fields must replace previous values; omitted material should be treated as redacted. The X509 profile says clients should cease using redacted SVIDs or bundles, including withdrawal indicated by PermissionDenied. Retaining previously cached authority can contradict that update.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Propagation delay and deployed client compliance are unknown.",
    "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": "SPIFFE Workload API stream responses are complete replacements, not incremental patches. Default or empty fields must replace previous values; omitted material should be treated as redacted. The X509 profile says clients should cease using redacted SVIDs or bundles, including withdrawal indicated by PermissionDenied. Retaining previously cached authority can contradict that update.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "The SPIFFE Workload API",
    "source_url": "https://raw.githubusercontent.com/spiffe/spiffe/49a9cbbc018c39ec6643ad3301632f9f4549258b/standards/SPIFFE_Workload_API.md",
    "checked_on": "2026-10-24",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-SPIFFE-STREAM-REDACTION-REPLACES-CACHE-01-v1",
    "candidate_record_sha256": "03787ef40a454e5268d401f0e184db4fd6d5e01e93eaa68fa99484380ba0ac97",
    "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": "SPIFFE Workload API stream responses are complete replacements, not incremental patches. Default or empty fields must replace previous values; omitted material should be treated as redacted. The X509 profile says clients should cease using redacted SVIDs or bundles, including withdrawal indicated by PermissionDenied. Retaining previously cached authority can contradict that update.",
    "required_buyer_context": "Previous and subsequent stream responses; Consumer cache-replacement behaviour; Time the consumer applied the last complete identity response. 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": "Should a workload keep an old SPIFFE bundle when a later API response omits it?",
    "documented_statement": {
      "status": "documented",
      "statement": "SPIFFE Workload API stream responses are complete replacements, not incremental patches. Default or empty fields must replace previous values; omitted material should be treated as redacted. The X509 profile says clients should cease using redacted SVIDs or bundles, including withdrawal indicated by PermissionDenied. Retaining previously cached authority can contradict that update.",
      "source_ids": [
        "spiffe-api"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Check whether credential caches actually apply withdrawal notifications. This is a source-based review decision, not an observed deployment result.",
      "source_ids": [
        "spiffe-api"
      ]
    },
    "buyer_evidence_required": [
      "Previous and subsequent stream responses",
      "Consumer cache-replacement behaviour",
      "Time the consumer applied the last complete identity response"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Do not merge an omitted credential back into a complete replacement response."
    },
    "unknowns": "Propagation delay and deployed client compliance are unknown.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "Propagation delay and deployed client compliance are unknown."
    },
    "evidence_sources": [
      {
        "source_id": "spiffe-api",
        "url": "https://raw.githubusercontent.com/spiffe/spiffe/49a9cbbc018c39ec6643ad3301632f9f4549258b/standards/SPIFFE_Workload_API.md",
        "final_url": "https://raw.githubusercontent.com/spiffe/spiffe/49a9cbbc018c39ec6643ad3301632f9f4549258b/standards/SPIFFE_Workload_API.md",
        "status": 200,
        "captured_at_utc": "2026-10-24T21:45:00.554Z",
        "sha256": "87450640b9f93a45a11aeb69b5093c574169621e5c6ebf36a6ad07c3ff6a96fb",
        "bytes": 35324,
        "title": "The SPIFFE Workload API",
        "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": [
          "4.3 Stream Responses",
          "4.4 Default Values and Redacted Information",
          "5.2.1 FetchX509SVID",
          "5.2.2 FetchX509Bundles"
        ],
        "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": "Check whether credential caches actually apply withdrawal notifications.",
      "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": "Check whether credential caches actually apply withdrawal notifications.",
    "refusal_conditions": [
      "Do not merge an omitted credential back into a complete replacement response."
    ]
  },
  "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": "Check whether credential caches actually apply withdrawal notifications.",
    "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-stream-redaction-replaces-cache",
  "machine_readable_record": "/varexis-index/records/spiffe-stream-redaction-replaces-cache.json"
}