TaharaSmart calculation methodology

Source facts

The system stores events entered by the user Results calculated from those events remain derived results and are not stored as though the user actually performed them

Time and location

When a calculation depends on an Onah, the system uses the event time, relevant time zone and location to determine the Hebrew date and relevant sunrise or sunset times

Minhag and settings

Your recorded events remain separate from calculated dates Calculation changes use your selected scope; input errors are shown before saving

Recalculation

When a relevant event is created, edited or deleted, or when relevant settings change, results can be recalculated from the source facts A previously calculated result does not become authoritative merely because it existed earlier

Your recorded events remain separate from calculated dates Calculation changes use your selected scope; input errors are shown before saving

Date, time and location determine the onah Missing input is shown as an input error A stored event that cannot be resolved must be corrected before the calendar updates; a failed calculation is not an empty calendar

Calculated eligibility vs an action actually completed

An eligible date or available action displayed on the calendar is not necessarily proof that the action occurred Hefsek Taharah and actual Tevilah are examples of facts that require the relevant user report or confirmation in the product flow

Custom settings allow separate choices for calendar concerns and waiting days A calculation change is saved after an explicit choice: from now on, preserving an onah already underway, or throughout history Both choices preserve recorded facts Deleting a timeline start after explicit confirmation also deletes its dependent taharah reports, while preserving independent notes and the next timeline