Liturgical Day Origin Gap Tool

Description

Compare explicit day-origin conventions without inferring a religious calendar or sunset time.

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 explicit day-origin conventions without inferring a religious calendar or sunset time.

When to use this tool

Use it for liturgical day origin gap when the required inputs and conventions are already available.

How to use the tool and how it works

Enter eventSeconds, firstOriginSeconds, secondOriginSeconds, secondsPerDay. Use the stated units and boundary conventions.
Run the calculation. Correct any input error before interpreting a result.
Read firstDayDecimal, secondDayDecimal, originDayGapDecimal. Inspect any known, defined, inclusion, or boundary flags before interpreting numeric values.

For each supplied day origin, calculate floor((eventSeconds-originSeconds)/secondsPerDay), require safe-integer results, and return both day indexes and their exact integer difference as decimal text.^[1]

Input field	Meaning and units	Accepted input
eventSeconds	Event Seconds	Required. Finite number.
firstOriginSeconds	First Origin Seconds	Required. Finite number.
secondOriginSeconds	Second Origin Seconds	Required. Finite number.
secondsPerDay	Seconds Per Day	Required. Finite number; strictly above 0.

Output field	Interpretation	Returned shape
firstDayDecimal	Integer day coordinate relative to firstOriginSeconds, returned as decimal text.	Required. Text; maximum UTF-16 length 8192.
secondDayDecimal	Integer day coordinate relative to secondOriginSeconds, returned as decimal text.	Required. Text; maximum UTF-16 length 8192.
originDayGapDecimal	Origin Day Gap Decimal	Required. Text; maximum UTF-16 length 8192.

json

{
  "input": {
    "eventSeconds": 100,
    "firstOriginSeconds": 0,
    "secondOriginSeconds": 50,
    "secondsPerDay": 100
  },
  "output": {
    "firstDayDecimal": "1",
    "secondDayDecimal": "0",
    "originDayGapDecimal": "-1"
  }
}

Limitations and assumptions

The common day length must be positive. Floor assigns negative offsets to earlier days; no religious calendar, sunset, leap-second, or local-time convention is inferred.
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 liturgical day origin gap, 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

Calculation and input contract: religious-studies/liturgical-day-origin-gap — tool.io

Similar or alternative tools

Liturgical Cycle Index Offset
Shift a caller-defined cycle index without inferring a religious calendar.
Edition Verse Range Length
Count integer verse indices in one supplied edition and chapter under explicit endpoint rules.