{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-17T22:44:07.049Z",
  "record_id": "VXI-EXT-PROCUREMENT-HAZELCAST-FENCING-01-v1",
  "record_kind": "external_reference",
  "title": "FencedLock: Stale workers and external effects",
  "system": "Hazelcast",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Can an old Hazelcast lock holder still act after a new worker acquires the lock?",
  "near_questions": [
    "Can a paused lock holder resume with stale authority?",
    "Does FencedLock automatically protect an external API?",
    "Where must a fencing token be checked?",
    "What changes when Hazelcast assigns a new lock owner?",
    "Was the CP subsystem left in unsafe mode?",
    "Which fencing token accompanied the stale write?",
    "Does losing a CP session stop external actions?",
    "Can two workers believe they own the same lock?",
    "What proves a resource rejected an old owner?",
    "Is lock-method exactly-once execution enough for external effects?",
    "What evidence is needed for Hazelcast fencing?",
    "Does INDEX implement fencing tokens?"
  ],
  "supported_claims": [
    {
      "claim": "Hazelcast 5.7 describes a paused client losing its CP session while another client acquires the lock; the old client can resume unaware that ownership changed. Monotonic fencing tokens let a cooperating external resource reject stale owners. This protection depends on the external resource using the tokens. The default CP unsafe mode has weaker consistency guarantees.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Automatic external-resource fencing, credential revocation or an INDEX enforcement mechanism",
    "Verified buyer configuration, effective access or actual event completeness",
    "Runtime enforcement, certification or approval to act"
  ],
  "public_summary": "Hazelcast 5.7 describes a paused client losing its CP session while another client acquires the lock; the old client can resume unaware that ownership changed. Monotonic fencing tokens let a cooperating external resource reject stale owners. This protection depends on the external resource using the tokens. The default CP unsafe mode has weaker consistency guarantees.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Hazelcast: FencedLock",
    "source_url": "https://docs.hazelcast.com/hazelcast/5.7/data-structures/fencedlock",
    "checked_on": "2026-10-17",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-HAZELCAST-FENCING-01-v1",
    "candidate_record_sha256": "ad2ef9bfb2b9ac33f8087158adf3fe8c25af5a018d2fb2779057c19aedd75434",
    "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": "Hazelcast 5.7 describes a paused client losing its CP session while another client acquires the lock; the old client can resume unaware that ownership changed. Monotonic fencing tokens let a cooperating external resource reject stale owners. This protection depends on the external resource using the tokens. The default CP unsafe mode has weaker consistency guarantees.",
    "required_buyer_context": "Hazelcast version, CP mode, session settings and lock ownership history. Fencing token supplied with each external operation and the resource-side comparison behavior. Observed acceptance or rejection of stale-owner operations and resulting resource state. 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-17",
    "claim_to_check": "Can an old Hazelcast lock holder still act after a new worker acquires the lock?",
    "documented_statement": {
      "status": "documented",
      "statement": "Hazelcast 5.7 describes a paused client losing its CP session while another client acquires the lock; the old client can resume unaware that ownership changed. Monotonic fencing tokens let a cooperating external resource reject stale owners. This protection depends on the external resource using the tokens. The default CP unsafe mode has weaker consistency guarantees.",
      "source_ids": [
        "fencedlock"
      ]
    },
    "buyer_evidence_required": [
      "Hazelcast version, CP mode, session settings and lock ownership history.",
      "Fencing token supplied with each external operation and the resource-side comparison behavior.",
      "Observed acceptance or rejection of stale-owner operations and resulting resource state."
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Decline stale-worker exclusion claims without evidence of the external resource enforcing token order under the deployed CP configuration."
    },
    "unknowns": "The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.",
    "evidence_sources": [
      {
        "source_id": "fencedlock",
        "url": "https://docs.hazelcast.com/hazelcast/5.7/data-structures/fencedlock",
        "final_url": "https://docs.hazelcast.com/hazelcast/5.7/data-structures/fencedlock",
        "title": "Hazelcast: FencedLock",
        "checked_on": "2026-10-17",
        "captured_at_utc": "2026-10-17T22:37:22.729Z",
        "version_context": "Hazelcast 5.7; CP mode and fencing tokens",
        "sha256": "9921a08d7a6ac4dc904621e54486ca2b2d0d89eea52a66ac703c06e7242cd9c2",
        "bytes": 163449,
        "hash_basis": "Decoded HTTP response body bytes; not a signature or truth guarantee",
        "reviewed_sections": [
          "Fencing Tokens; CP Subsystem unsafe mode"
        ]
      }
    ],
    "observed_deployment": false,
    "commercial_reliance_boundary": "Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.",
    "paid_value": {
      "decision_context": "Worker takeover must not be mistaken for revocation of an old worker's ability to write to an external system.",
      "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": "Hazelcast version, CP mode, session settings and lock ownership history. Fencing token supplied with each external operation and the resource-side comparison behavior. Observed acceptance or rejection of stale-owner operations and resulting resource state."
    },
    "buyer_relevance": "Worker takeover must not be mistaken for revocation of an old worker's ability to write to an external system.",
    "refusal_conditions": [
      "Decline stale-worker exclusion claims without evidence of the external resource enforcing token order under the deployed CP configuration."
    ]
  },
  "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#hazelcast-fencedlock-stale-worker-external-effects",
  "machine_readable_record": "/varexis-index/records/hazelcast-fencedlock-stale-worker-external-effects.json"
}
