{"id":"fencing-provides-linearizable-writes","text":"Fencing tokens provide linearizable write protection at the resource server: stale tokens are permanently rejected (no expiration) and the monotonic token ordering ensures only the most recent lock holder can successfully write.","truth_value":"IN","source":"","source_url":"","source_hash":"","justifications":[{"type":"SL","antecedents":["fencing-rejects-stale-writes","fencing-tokens-do-not-expire-at-resource-server"],"outlist":["client-holds-stale-token-after-lock-expiry"],"label":"Server-side fencing is correct but clients retain and use tokens after lock expiry with no invalidation signal"}],"dependents":[],"metadata":{},"created_at":"","updated_at":"","reviewed_at":"","verified_at":"","retracted_at":"","explanation":{"steps":[{"node":"fencing-provides-linearizable-writes","truth_value":"IN","reason":"SL justification valid","antecedents":["fencing-rejects-stale-writes","fencing-tokens-do-not-expire-at-resource-server"],"label":"Server-side fencing is correct but clients retain and use tokens after lock expiry with no invalidation signal","outlist":["client-holds-stale-token-after-lock-expiry"]},{"node":"fencing-rejects-stale-writes","truth_value":"IN","reason":"premise"},{"node":"fencing-tokens-do-not-expire-at-resource-server","truth_value":"IN","reason":"premise"}]}}