Implementing 'Write follows Read' guarantee of causal consistency

Other MongoDB Topics MongoDB Server Development
2

A supplementary question.
I see that mongodb read concern handling does two checks.

  1. ClusterTime
    I assume, this is updated on each node through the cluster time gossip. If cluster time is not upto date and less than afterClusterTime value, the server returns an error. So client will need to try another server.
  2. OperationsTime
    If clusterTime is up-to-date, the server checks if operationTime is as up-to-date as the afterClusterTime value and if not, will always do a no-op write through the leader. (after a small wait to give a chance for secondaries to receive updates)
    So is it correct to say that read requests with afterClusterTime value greater than latest operation time, will always do a no-op write to push the clustertime and operation time to the value more than the afterClusterTime, and that way provide write follows read guarantee?