Description
Audit explicit version and effective-day ordering without selecting a current label.
A regulatory record check applies a supplied rule to labels, dates, identifiers, or amounts. Exact matches and clock boundaries matter, but a consistent record does not itself establish legal compliance. The governing jurisdiction, rule version, and authoritative evidence must be selected separately.
Audit explicit version and effective-day ordering without selecting a current label.
When to use this tool
Use it for regulatory label version date order when the required inputs and conventions are already available.
How to use the tool and how it works
- Enter versions, effectiveDays. Keep parallel arrays aligned and use the stated units and conventions.
- Run the calculation. Correct any input error before interpreting a result.
- Read nonIncreasingVersionIndices, decreasingDateIndices, ordered. Inspect any known, defined, inclusion, or boundary flags before interpreting numeric values.
Require aligned numeric versions and effectiveDays arrays. Report each later index where version fails to increase strictly or date decreases, and set ordered only when both lists of problems are empty.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| versions | Versions | Required. Array of Safe integer.; maximum items 256. |
| effectiveDays | Effective Days | Required. Array of Safe integer.; maximum items 256. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| nonIncreasingVersionIndices | Non Increasing Version Indices | Required. Array of Safe integer.; maximum items 256. |
| decreasingDateIndices | Decreasing Date Indices | Required. Array of Safe integer.; maximum items 256. |
| ordered | Ordered | Required. Boolean. |
{
"input": {
"versions": [
1,
2,
2
],
"effectiveDays": [
100,
110,
105
]
},
"output": {
"nonIncreasingVersionIndices": [
2
],
"decreasingDateIndices": [
2
],
"ordered": false
}
}Limitations and assumptions
- Equal effective days are allowed while equal versions are flagged. Empty or singleton arrays have no adjacent ordering violation; no semantic version parsing or current-label selection occurs.
- The field tables describe structural bounds; the mechanics also state cross-field requirements. Malformed input shapes, disallowed keys, and invalid domains cause input errors. Results must remain finite and within the declared output contract. A successful false flag or zero placeholder is distinct from an error.
- Numeric arithmetic uses binary floating point. Exact comparisons have no hidden tolerance or decimal rounding; negative zero is exported as zero. Decimal-text integer operations retain the exactness specifically stated above.
Alternative or Complementary methods
For regulatory label version date order, check the source records and the supplied rule before comparing the result with another method. Consult the applicable authoritative rule when deciding eligibility, legal timing, fees, or obligations.
References
Similar or alternative tools
- Regulatory Variation Effective Date Window
Audit explicit implementation timing under caller-supplied dates.
- Application Fee Currency Reference Date
Calculate application fee currency reference date from explicit caller-supplied inputs.