Browse 12 chapters
Most so-called exceptions are input boundaries or method choices. A trustworthy calculator states them before interpretation and produces the same result every time.
Reference rules
The boundaries Destinyly applies
Destinyly requires a real Gregorian calendar date in DD/MM/YYYY. Day and month cannot be zero. April has 30 days. February 29 is valid only in a leap year: a year divisible by 4, except century years must also be divisible by 400. Thus 29/02/2000 is valid and 29/02/1900 is not.
The calculator rejects invalid input rather than allowing JavaScript to roll 31 April into May. A rejected date is not a numerological exception; it is an input that does not identify a birth date.
The reduction operates on positive date-derived totals, so valid matrix values remain 1-22. It is not modulo 22, where multiples could become zero. If a calculator displays 0 as a core Arcana, it is using another convention or has an implementation problem.
Leading zeros in a written date do not add energy or change arithmetic. 08 is the integer 8, not a two-digit value that must be reduced again.
Twenty-two is a valid final energy and remains 22. Only totals greater than 22 are reduced. This is the boundary most likely to create cascading differences because D and E depend on earlier anchors.
Examples: reduce(21) = 21; reduce(22) = 22; reduce(23) = 5; reduce(29) = 11; reduce(38) = 11; reduce(44) = 8. The decimal digit sum is repeated only when necessary.
For 1999, the year digit sum is 1 + 9 + 9 + 9 = 28, then 2 + 8 = 10. Destinyly does not subtract 22 to obtain 6. It does not calculate 28 modulo 22. It also does not reduce 10 to 1 because 10 already lies within 1-22.
Writing the intermediate sum prevents an apparently small implementation choice from being hidden inside the final chart.
For 29/02/2000, A is reduce(29) = 11, B is 2, and C is 2. D is reduce(11 + 2 + 2) = 15. E is reduce(11 + 2 + 2 + 15) = reduce(30) = 3.
Love is reduce(15 + 3) = 18. Money is reduce(2 + 3) = 5. Karmic is reduce(11 + 2) = 13. Ancestral is reduce(11 + 2 + 15) = reduce(28) = 10. The leap-day status affects validation, not a special symbolic formula.
Destinyly maps Energy 8 to Justice and Energy 11 to Strength. Rider-Waite-Smith-based sources often reverse those names, using Strength VIII and Justice XI. The number may therefore match while the card name differs.
Destinyly does not silently switch the mapping by page. A consistent convention matters more than presenting one tradition as universally correct.
Destinyly's five anchors and four primary derived lines are published in Methodology. Purpose blocks, compatibility channels, and age timing are also documented where they appear. Other schools may add inner points, chakra tables, ideal-partner values, or multi-number programs.
A familiar label is not enough to establish equivalence. Before importing a secondary value, identify its inputs, operation, reduction timing, orientation, and interpretive scope.
Some Matrix sites display three-number program codes or lists of karmic combinations without exposing how the triplets are derived. Destinyly does not reproduce those codes as if they belonged to its current method.
This is a deliberate limit, not missing calculation. Adding an opaque feature would make the chart look more complex while reducing reproducibility. A future method can be added only when its construction, source tradition, position mapping, and editorial boundaries can be stated clearly.
Destinyly labels the input DD/MM/YYYY and uses separate day, month, and year controls to reduce ambiguity. A copied date such as 04/07/1990 can still be interpreted differently by readers in different locales. For support requests, write 4 July 1990 or 7 April 1990 in words.
Changing browser language should not change a stored numerical chart. Locale may alter display text, but the date parts sent to the calculation must remain explicit.
A reproducible method can still have software bugs. Destinyly records substantive calculator or content changes on the Updates page and accepts correction reports through Contact. A correction should fix the implementation or explanation without retroactively inventing a new tradition.
When comparing an older download with the live site, note the generation date. Interface labels may improve while the underlying values remain unchanged; a formula change would require a clear public note.
Use boundary cases before testing a complicated chart: day 22 should stay 22; day 23 should become 5; day 29 should become 11. A year digit sum of 22 should stay 22, while 28 should become 10. Then test a full known date and verify D and E from the recorded anchors.
For compatibility, test two identical personal charts. Every composite point should equal the reduced sum of the matching value with itself. This does not make the relationship 'perfect'; it only provides a simple arithmetic check.
Is 22 a master number? Destinyly treats it as the twenty-second valid matrix energy. It does not import master-number rules from a separate 1-9 numerology system.
Does gender change the matrix? No. Gender is an optional interpretive context and does not alter the birth-date calculation.
Can an exception be chosen manually? No. The calculator applies the same disclosed rules to every valid date.
Sources and further context
References used for factual context
Method and corrections
Calculation statements are checked against Destinyly's published method. Interpretive claims are edited as symbolic possibilities, not diagnoses, guarantees, or professional advice. Corrections can be submitted through Contact.