docs: public static AcceptanceDecision decideOnRemoteModification(
              ReplicableEntry entry, RemoteOperationContext<?> context) {
          long remoteTimestamp = context.remoteTimestamp();
          long originTimestamp = entry.originTimestamp();
          // Last write wins
          if (remoteTimestamp > originTimestamp)
              return ACCEPT;
          if (remoteTimestamp < originTimestamp)
              return DISCARD;
          // remoteTimestamp == originTimestamp below
          byte remoteIdentifier = context.remoteIdentifier();
          byte originIdentifier = entry.originIdentifier();
          // Lower identifier wins
          if (remoteIdentifier < originIdentifier)
              return ACCEPT;
          if (remoteIdentifier > originIdentifier)
              return DISCARD;
          // remoteTimestamp == originTimestamp && remoteIdentifier == originIdentifier below
          // This could be, only if a node with the origin identifier was lost, a new Chronicle Hash
          // instance was started up, but with system time which for some reason is very late, so
          // that it provides the same time, as the "old" node with this identifier, before it was
          // lost. (This is almost a theoretical situation.) In this case, give advantage to fresh
          // entry updates to the "new" node. Entries with the same id and timestamp, bootstrapped
          // "back" from other nodes in the system, are discarded on this new node (this is the
          // of the condition originIdentifier == currentNodeIdentifier). But those new updates
          // should win on other nodes.
          //
          // Another case, in which we could have remoteTimestamp == originTimestamp &&
          // remoteIdentifier == originIdentifier, is replication of barely the same entry, if an
          // entry is bootstrapped "back" from remote node to it's origin node. In this case the
          // following condition also plays right (the update is discarded, due to it's redundancy).
          return originIdentifier == context.currentNodeIdentifier() ? DISCARD : ACCEPT;
      }