···2828on Node.js, `TID.now()` relies on the system's real-time clock for microsecond precision where
2929available, falling back to millisecond precision otherwise.
30303131-`TID.now()` is not monotonic — TIDs must track wall clock time, so if the clock is adjusted
3232-backward, the generated TIDs will follow. within a single process, rapid successive calls that
3333-observe the same timestamp will increment instead of reusing it to avoid collisions.
3131+`TID.now()` is not monotonic — TIDs encode wall clock time, so the generator must follow clock
3232+corrections rather than preserve ordering. enforcing monotonicity on devices with unreliable clocks
3333+(e.g. phones) would leave the generator permanently stuck at the wrong time after a correction. the
3434+only exception is rapid successive calls within a single process that observe the same timestamp,
3535+where it increments instead of reusing it to avoid collisions.
34363537### parsing TIDs
3638