LuckTime is organized as a sequence rather than a single prompt. Birth details are validated first. A calculation provider then produces structured timing facts. Only after that step does an interpretation provider turn those facts into a readable report.
1. Inputs are checked before calculation
The current form asks for a first name, birth date, birth time, place of birth, and one area of focus. A known time is recorded to the minute. If a time is unknown, the user can say so instead of guessing. A selected city can include coordinates and a time zone; a manual place is accepted with a lower precision label.
Validation rejects impossible dates and incomplete location records. It does not silently turn missing information into false precision.
2. The calculation layer produces facts
The calculation interface is designed to return a named current chapter, opportunity windows, caution windows, a focus signal, and a confidence rating. In a production system, this is where a licensed BaZi, Zi Wei Dou Shu, or another deterministic timing engine would operate. The language layer should not invent planetary positions, pillars, palaces, transits, or dates that the engine did not calculate.
3. The interpretation layer explains those facts
Interpretation has a narrower job: connect the structured calculation to the user's chosen focus and write it in plain English. It may explain the practical meaning of an opportunity window or suggest a reflective prompt. It must preserve the dates and confidence produced upstream. It must not promote a possibility into a guarantee.
The active MVP engine
The current engine is identified in code and in the result as LuckTime Demo 1.0.0. It generates deterministic sample windows relative to the day a reading is requested. The accompanying interpretation is authored demonstration copy. This makes the product journey testable while keeping the unfinished metaphysical integration visible.
Demonstration timing data can test a product flow. It cannot stand in for a completed BaZi or Zi Wei calculation.
How timing confidence works
The MVP uses three plain-language levels:
- High: exact hour and minute, plus a selected place with coordinates and a time zone.
- Moderate: exact time, but a manually entered place that has not been matched to coordinates and a time zone.
- Limited: birth time is unknown, so hour-level timing is intentionally withheld.
Confidence describes input precision within the product. It is not a claim of scientific validation or a probability that an event will occur. Read why birth time changes calculation detail or start with the free timing calculator.