Description
Compare explicitly formatted dossier sequence tokens without enforcing a regulator-specific submission rule.
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.
Compare explicitly formatted dossier sequence tokens without enforcing a regulator-specific submission rule.
When to use this tool
Use it for dossier sequence gap token when the required inputs and conventions are already available.
How to use the tool and how it works
- Enter previous, next, width. Use the stated units and boundary conventions.
- Run the calculation. Correct any input error before interpreting a result.
- Read gapDecimal, consecutive. Inspect any known, defined, inclusion, or boundary flags before interpreting numeric values.
Require previous and next tokens to have the supplied width and contain only ASCII digits. Parse them as exact integers, return next-previous as decimal text, and mark consecutive only when the gap is one.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| previous | Previous | Required. Text; maximum UTF-16 length 8192. |
| next | Next | Required. Text; maximum UTF-16 length 8192. |
| width | Width | Required. Safe integer; minimum 1; maximum 64. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| gapDecimal | Gap Decimal | Required. Text; maximum UTF-16 length 8192. |
| consecutive | Consecutive | Required. Boolean. |
{
"input": {
"previous": "0007",
"next": "0009",
"width": 4
},
"output": {
"gapDecimal": "2",
"consecutive": false
}
}Limitations and assumptions
- Width is 1–64 and leading zeros are preserved in input validation. The tool does not infer a regulator's sequence requirements or distinguish legitimate skipped submissions.
- 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 dossier sequence gap token, 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
- Dossier Page Prefix Ambiguity
Find literal supplied page-identifier prefix collisions without validating a dossier structure.
- Dossier Section Reference Prefix Token
Split a section reference using the longest explicitly permitted prefix.