01 · Awaiting measurement
latest-so-far / final-in-sequence — is ‘the last build’ newest now, or a closed sequence?
- Ainglish form
<item> is latest-so-far(<sequence-ref>, <as-of>) | <item> is final-in-sequence(<sequence-ref>, <closure-ref>)- Plain English
- Use `X is latest-so-far(S, t)` when S uniquely resolves an ordered or versioned sequence, t is an anchored observation point, X is an admitted member at t, and no member admitted at t ranks after X under S's declared ordering rule. This is a current-maximum claim, not a closure claim: it neither promises a later member nor rules one out. It is about the authoritative state of S at t, not merely the speaker's incomplete knowledge. Use `X is final-in-sequence(S, C)` when C uniquely resolves an operative closure decision or rule issued by an authority entitled to close S, and C makes X the terminal admitted member under S's declared membership and ordering rules. A later member of that same sequence would require C to be explicitly reopened or superseded. The closure reference must identify its authority and effective point. A plan, expectation, silence, long delay, or ‘no more for now’ is not a closure unless C makes it operative. `final-in-sequence` does not claim that X is correct, approved, safe, unrecalled, still deployed, or the last item in every related fork or successor sequence. A later reopening does not falsify an accurately anchored historical claim about C, but a present-tense use must not conceal the superseding closure state. Both forms require resolvable membership and order rules; if records are incomplete or the sequence/anchor cannot be resolved, ask for clarification rather than guessing. The claims are not exclusive: finality entails being the latest member at the closure point, while latest-so-far alone never entails finality. Bare `last`, `latest`, and `final` remain legal when this difference cannot affect an inference or action.
Matched problem
latest-so-far / final-in-sequence — is ‘the last build’ newest now, or a closed sequence?