The instruments · Under the hood

How the instruments compute

HOW THE TOOLS CALCULATE

One controlled engine layer, several task-specific interfaces

The calculator, Atlas, Compare, and other tools may present different views, but they should not quietly invent different arithmetic or date normalization rules.

Input contract: Normalize the date identically.
Engine contract: Call the controlled calculation and preserve its result shape.
Interface contract: Explain only what the tool actually computes.

Open the public calculator Browse all instruments

The tools share the same calculation code wherever they need the same answer. The public calculator, worked reading, comparison tools, and Atlas should not quietly produce different results from the same input. This page explains those calculations in plain language.

What the shared engine models is interaction: weights, orders, and absences exist in the code because positions act on each other in the person.

One layer, many faces

An engine here is a small, self-contained computation: it takes a date, year, month, day, and returns a structured result. No network calls, no randomness, no lookups to a server. The calculator page, the worked read, and Atlas all call the same engines, which is why they can never disagree with each other: there is only one place each answer comes from.

What each engine computes

Numerology. Reduces the month, day, and year each to a root; sums the full date for the Life Path (shown with its unreduced sum, so the work is visible). The four classical pinnacles come from the four classical formulas, month+day, day+year, first+second, month+year, each with its age span; the four challenges are the absolute differences of the same pairs. The personal year is anchored to your birthday rather than January the first, a school ruling, made once and applied everywhere.

Western astrology. Computes the Sun's actual position, real solar longitude for the date, and derives the sign and degree from it. No date-range tables; the boundary days come out right because the sky is computed, not remembered.

Ba Zi, the four pillars. Derives the year, month, and day pillars from the sexagenary cycle of stems and branches, each pillar carrying its animal, its stem element, and its branch element.

The I Ching. Derives a natal hexagram, number and name, from the date's own arithmetic, built on top of the Ba Zi layer; the dependency is real and stated, which is why the worked read loads the pillars before the hexagram.

The Tzolk'in. Positions the date on the 260-day sacred round: seal, tone, and kin number, in the classical count.

Nine Star Ki. Finds the three stars, principal, character, energetic, from the Lo Shu nine-cycle the tradition runs on years and months.

The sequence itself. Vecnine’s own computation, how a birthdate becomes the nine-position sequence, has its own full explanation on How It Works, and its instrument is the calculator.

Determinism, and showing the work

Same date in, same answer out, today, next year, on any device. There is no quiz to answer differently on a different day and no model that drifts. Members running the worked read can open the Show Work tab at the bottom of the lab and watch the computation order laid out line by line: the reductions, the sums, the formulas with their inputs. And when an engine can't produce an answer, the panel says unavailable, the instruments do not pretend.

What the engines never do

They never phone home, the computation happens in your browser. They never randomize; there is nothing oracular in the machinery; whatever meaning the systems carry, the arithmetic is just arithmetic, done plainly. And the public tools store nothing about you on any server: where a page offers to remember your date or your reading, that memory lives in your own browser's local storage, and clearing it clears everything.

The implementation is the executable record

Each engine ships as a readable file with its own notes, and this page describes the shape, not every constant. If anything on this page ever disagrees with what an engine actually does, the code wins and the page is the bug, report it to Vecnine. That rule is the whole point of writing this page at all.

Vecnine · the engine layer is versioned with the site · the worked read, the calculators, the convergence view, and Atlas all draw from it.

NEXT USEFUL MOVE

Return this page to a real sequence

Use the definition, claim boundary, or method rule above as an observation prompt. The page earns its place only when it helps distinguish recurring mechanism from a flattering label or a single behavior.

Open the public calculator Browse all instruments