{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-25T20:55:19.974986+00:00",
  "record_id": "VXI-EXT-PROCUREMENT-REDIS-TRANSACTION-RUNTIME-ERRORS-NO-ROLLBACK-01-v1",
  "record_kind": "external_reference",
  "title": "Redis transaction errors and no rollback",
  "system": "Redis official transactions documentation",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does an error during Redis EXEC mean that every operation was rolled back?",
  "near_questions": [
    "Does one Redis EXEC command error roll back the other writes?",
    "How do queue-time and execution-time errors differ?",
    "Can Redis return successful and failed replies in one transaction?",
    "Should a failed transaction result be interpreted as no state change?"
  ],
  "supported_claims": [
    {
      "claim": "Redis distinguishes errors while queueing from errors during EXEC. Since 2.6.5, detected queue-time errors cause EXEC to discard the transaction. Runtime errors do not stop the other queued commands, and Redis does not roll back successful operations. An error in the reply array is therefore not proof that the transaction made no changes.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Runtime errors do not stop other commands or roll back successful commands; Redis 2.6.5 queue-error behavior is version scoped.",
    "Buyer implementation, live runtime enforcement, settled payment, physical outcome, certification or permission to act are not established.",
    "No expanded capabilities or licences for existing INDEX executables."
  ],
  "public_summary": "Redis distinguishes errors while queueing from errors during EXEC. Since 2.6.5, detected queue-time errors cause EXEC to discard the transaction. Runtime errors do not stop the other queued commands, and Redis does not roll back successful operations. An error in the reply array is therefore not proof that the transaction made no changes.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Redis official transactions documentation",
    "source_url": "https://redis.io/docs/latest/develop/using-commands/transactions/",
    "checked_on": "2026-10-25",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-REDIS-TRANSACTION-RUNTIME-ERRORS-NO-ROLLBACK-01-v1",
    "candidate_record_sha256": "43c78990e3363d3085fcd66abc1649239f118426f434551965250eeded69d4f6",
    "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": "Redis distinguishes errors while queueing from errors during EXEC. Since 2.6.5, detected queue-time errors cause EXEC to discard the transaction. Runtime errors do not stop the other queued commands, and Redis does not roll back successful operations. An error in the reply array is therefore not proof that the transaction made no changes.",
    "required_buyer_context": "Redis version; Queue responses and full EXEC reply array; Individual command outcomes. 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-25",
    "claim_to_check": "Does an error during Redis EXEC mean that every operation was rolled back?",
    "documented_statement": {
      "status": "documented",
      "statement": "Redis distinguishes errors while queueing from errors during EXEC. Since 2.6.5, detected queue-time errors cause EXEC to discard the transaction. Runtime errors do not stop the other queued commands, and Redis does not roll back successful operations. An error in the reply array is therefore not proof that the transaction made no changes.",
      "source_ids": [
        "redis-transactions"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Distinguish queue-time rejection from partial command errors inside an executed Redis transaction. This is a documentation-review judgment, not an observed deployment outcome.",
      "source_ids": [
        "redis-transactions"
      ]
    },
    "buyer_evidence_required": [
      "Redis version",
      "Queue responses and full EXEC reply array",
      "Individual command outcomes"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Refuse buyer-specific assurance from documentation alone. Runtime errors do not stop other commands or roll back successful commands; Redis 2.6.5 queue-error behavior is version scoped."
    },
    "unknowns": "The buyer implementation, effective configuration, complete evidence inventory and actual business outcome were not inspected.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "The buyer implementation, effective configuration, complete evidence inventory and actual business outcome were not inspected."
    },
    "evidence_sources": [
      {
        "source_id": "redis-transactions",
        "url": "https://redis.io/docs/latest/develop/using-commands/transactions/",
        "final_url": "https://redis.io/docs/latest/develop/using-commands/transactions/",
        "status": 200,
        "captured_at_utc": "2026-10-25T20:26:12.717Z",
        "sha256": "653036c9ffcb423475ad19cbe098c1767288607f6da8a738a1d6e6ac603f015f",
        "bytes": 127549,
        "title": "Redis official transactions documentation",
        "hash_basis": "SHA-256 of unmodified HTTP response body bytes",
        "rights_review": "Original factual paraphrase and citation only. Redis documentation and software have distinct applicable licences; no source page or software code is redistributed or relicensed.",
        "checked_on": "2026-10-25",
        "capture_status": 200,
        "claim_review_completed": true,
        "reviewed_sections": [
          "Usage",
          "Transaction guarantees",
          "Errors inside a transaction",
          "What about rollbacks?",
          "WATCH explained"
        ],
        "version_context": "Rolling Redis official documentation captured 2026-10-25. Command introduction and version-specific exceptions are stated in each bounded answer; deployed product/version/configuration unverified."
      }
    ],
    "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": "Distinguish queue-time rejection from partial command errors inside an executed Redis transaction.",
      "free": "Complete review, practical questions, sources 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 Errors inside a transaction; What about rollbacks? in Redis official transactions documentation when the source, applicable version, configuration or intended reliance changes. A detected change creates a review candidate, not automatic approval."
    },
    "buyer_relevance": "Distinguish queue-time rejection from partial command errors inside an executed Redis transaction.",
    "refusal_conditions": [
      "Refuse buyer-specific assurance from documentation alone. Runtime errors do not stop other commands or roll back successful commands; Redis 2.6.5 queue-error behavior is version scoped."
    ]
  },
  "niche": {
    "niche_id": "agent-authority-action-evidence",
    "label": "Agent Authority & Action Evidence",
    "classification_id": "audit",
    "classification_label": "Audit, Provenance & Evidence Accountability",
    "topic_id": "audit",
    "buyer_intent": "Distinguish queue-time rejection from partial command errors inside an executed Redis transaction.",
    "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#redis-transaction-runtime-errors-no-rollback",
  "machine_readable_record": "/varexis-index/records/redis-transaction-runtime-errors-no-rollback.json"
}