The fencing token originates from a classic distributed lock paper; the core idea is that the lock service returns a monotonically increasing token each time it grants the lock, the client carries this token when accessing downstream resources, and downstream resources only accept requests whose token is no less than the maximum value seen, thereby cutting off stale writes.