This integer is the sequence number of a route-policy term, and terms with lower sequence numbers are evaluated before higher ones; if two terms share the same number their relative evaluation order is arbitrary. An admin uses distinct sequence numbers to establish a deterministic, ordered chain of match-and-action logic within a route policy. For example, giving a strict 'deny known-bad prefixes' term sequence number 10 and a looser 'permit rest' term sequence number 100 ensures the deny rule is checked first.