Description
Compare supplied public rule dates under an explicit endpoint policy without checking current law.
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 supplied public rule dates under an explicit endpoint policy without checking current law.
When to use this tool
Use it for source rule effective date margin when the required inputs and conventions are already available.
How to use the tool and how it works
- Enter effectiveDate, evaluationDate, inclusive. Use the stated units and boundary conventions.
- Run the calculation. Correct any input error before interpreting a result.
- Read daysSinceEffective, effectiveUnderRule. Inspect any known, defined, inclusion, or boundary flags before interpreting numeric values.
Validate effectiveDate and evaluationDate as exact ISO calendar dates, subtract them in whole days, and apply the supplied inclusive policy: zero or more days if inclusive, strictly positive otherwise.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| effectiveDate | Effective Date | Required. Text; maximum UTF-16 length 8192. |
| evaluationDate | Evaluation Date | Required. Text; maximum UTF-16 length 8192. |
| inclusive | Inclusive | Required. Boolean. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| daysSinceEffective | Days Since Effective | Required. Safe integer. |
| effectiveUnderRule | Effective Under Rule | Required. Boolean. |
{
"input": {
"effectiveDate": "2024-01-01",
"evaluationDate": "2024-01-10",
"inclusive": true
},
"output": {
"daysSinceEffective": 9,
"effectiveUnderRule": true
}
}Limitations and assumptions
- The dates are inputs rather than verified current law. The tool does not select a jurisdiction, interpret transitional provisions, or account for times of day or business-day rules.
- 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 source rule effective date margin, 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.