Description
Elapsed minutes from supplied clock values and explicit day crossings; no religious observance schedule is determined.
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.
Elapsed minutes from supplied clock values and explicit day crossings; no religious observance schedule is determined.
When to use this tool
Use it for public fast midnight duration token when the required inputs and conventions are already available.
How to use the tool and how it works
- Enter startMinutes, endMinutes, midnightCrossings. Use the stated units and boundary conventions.
- Run the calculation. Correct any input error before interpreting a result.
- Read durationMinutes. Inspect any known, defined, inclusion, or boundary flags before interpreting numeric values.
Calculate endMinutes-startMinutes+1440*midnightCrossings, requiring each clock minute from zero through 1439, a nonnegative integer crossing count, and a nonnegative duration.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| startMinutes | Start Minutes | Required. Safe integer; minimum 0; maximum 1439. |
| endMinutes | End Minutes | Required. Safe integer; minimum 0; maximum 1439. |
| midnightCrossings | Midnight Crossings | Required. Safe integer; minimum 0. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| durationMinutes | Duration Minutes | Required. Safe integer. |
{
"input": {
"startMinutes": 1080,
"endMinutes": 360,
"midnightCrossings": 1
},
"output": {
"durationMinutes": 720
}
}Limitations and assumptions
- The caller supplies day crossings explicitly. This assumes 1440-minute day units and does not infer observance times, sunset, time zones, daylight-saving changes, or fasting advice.
- 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 fast midnight duration token, 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
- Public Calendar Observance Offset
Compare supplied absolute-day indices after an explicit calendar shift, without assigning an observance date.
- Public Verse ID Segment Count
Count explicit public-text reference segments without validating a canon-specific reference system.