Description
Compare supplied absolute-day indices after an explicit calendar shift, without assigning an observance date.
Text references and observance records depend on an explicit edition, numbering system, time origin, or supplied calendar convention. Literal identifiers can be counted or compared without interpreting a text or establishing a religious observance rule.
Compare supplied absolute-day indices after an explicit calendar shift, without assigning an observance date.
When to use this tool
Use it for public calendar observance offset when the required inputs and conventions are already available.
How to use the tool and how it works
- Enter observanceDay, referenceDay, suppliedCalendarShift. Use the stated units and boundary conventions.
- Run the calculation. Correct any input error before interpreting a result.
- Read offsetDays. Inspect any known, defined, inclusion, or boundary flags before interpreting numeric values.
Return observanceDay+suppliedCalendarShift-referenceDay using caller-resolved absolute-day indexes and a matching shift convention.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| observanceDay | Observance Day | Required. Safe integer. |
| referenceDay | Reference Day | Required. Safe integer. |
| suppliedCalendarShift | Supplied Calendar Shift | Required. Safe integer. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| offsetDays | Offset Days | Required. Safe integer. |
{
"input": {
"observanceDay": 120,
"referenceDay": 100,
"suppliedCalendarShift": -1
},
"output": {
"offsetDays": 19
}
}Limitations and assumptions
- The tool neither converts religious calendars nor assigns an observance date. Consistent origins and day units are required for the difference to be meaningful.
- 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 public calendar observance offset, check the source records and the supplied rule before comparing the result with another method. Use a separate evidence or method review when arithmetic consistency alone cannot establish the required conclusion.
References
Similar or alternative tools
- Liturgical Cycle Index Offset
Shift a caller-defined cycle index without inferring a religious calendar.
- Public Fast Midnight Duration Token
Elapsed minutes from supplied clock values and explicit day crossings; no religious observance schedule is determined.