Description
Return before or after only for strictly disjoint envelopes; equal exact singletons return same-instant; all other intersections or touching envelopes return unresolved-overlap.
Administrative workflow summaries depend on capacity, counted waiting, uncertain time envelopes, priority policies and delegated or retention intervals. A local predicate or deadline arithmetic does not establish a lawful fee, signature, retention decision or fair service priority. Boundary and denominator policies must be explicit.
Return before or after only for strictly disjoint envelopes; equal exact singletons return same-instant; all other intersections or touching envelopes return unresolved-overlap.
When to use this tool
Use Filing Date Partial Order Token when checking the stated administrative count, timing, priority or policy-boundary convention.
How to use the tool and how it works
- Enter firstEarliest, firstLatest, secondEarliest, secondLatest. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read relation. Use the output convention below.
Require ordered whole-coordinate envelopes. Return before or after only for strictly disjoint envelopes; equal exact singletons return same-instant; all other intersections or touching envelopes return unresolved-overlap.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| firstEarliest | First Earliest | Required. Safe integer. |
| firstLatest | First Latest | Required. Safe integer. |
| secondEarliest | Second Earliest | Required. Safe integer. |
| secondLatest | Second Latest | Required. Safe integer. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| relation | Strictly before/after, equal exact singleton, or unresolved overlap including touching uncertain bounds. | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"firstEarliest": 10,
"firstLatest": 12,
"secondEarliest": 15,
"secondLatest": 17
},
"output": {
"relation": "before"
}
}Limitations and assumptions
- The result preserves timing uncertainty rather than choosing an order; no civil-date parsing or actual filing priority is determined.
- Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
- Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.
Alternative or Complementary methods
Review verified records and the governing organizational/legal requirements with responsible professionals for actual service, authority or retention decisions.
References
Similar or alternative tools
- Trial Window Partial Date Bound
definitelyInside means the event envelope is contained in the closed window; possiblyInside means their closed intervals overlap, including touching boundaries.
- Delegation Start End Date Check
Check an explicitly supplied delegation interval with inclusive start and exclusive end dates without determining legal validity.