REFUSED

The field was populated and the value was refused as out of range.

Distinct from ABSENT on purpose, because it is a statement about the SENDER: it only encodes a start within an hour of its own clock, so a value refused here means the two clocks disagree by more than an hour, or transit exceeded an hour and a mesh does not deliver that. Consumers that treat an unusable timestamp as grounds to discard the report need this case and must not act on ABSENT, which carries no such accusation.

Note this is relative to the reference instant passed to CotXmlBuilder.buildWithOrigin, so decoding a stored capture refuses by construction unless the original decode instant is supplied.