This page explains where each card, score, and signal comes from, then gives you the raw chart reference underneath.
Birth date, birth time, longitude, and gender are used to build the base chart. This is the stable layer.
The engine resolves palaces, stars, brightness, and natal transformations. This creates your long-cycle pattern map.
Decade, year, month, and day transformations are added on top of the natal chart. This is where movement, friction, and timing come from.
The app turns chart structure plus timing layers into the cards you read: role, work mode, work pattern, daily brief, survival index, the daily survival card, and the 10-day interview forecast.
Resolved from the Identity palace and its main star.
The result page pulls the Identity star, its mapped definition, strengths, risks, and any borrowed-note adjustment when the read mirrors from the opposite palace.
This is your default strategy under pressure: what kind of operator the chart keeps turning you into.
Resolved from the Execution palace and its active work star.
The engine checks the execution star, its brightness, palace mapping, and whether the execution lane is borrowed from the opposite palace.
This is how your work actually gets delivered once reality, deadlines, and org constraints hit.
Computed from Identity stars plus Execution stars plus natal execution transformations.
The verdict combines your identity star mix, execution brightness, delivery tier, ambition tier, and execution-side natal transformations into one named repeated pattern.
This is the recurring outcome the system tends to experience from you, not just how you describe yourself.
Computed from the full chart plus the selected report date.
The app adds day-level timing on top of the stable chart, then picks the dominant daily event and turns it into today's short-range brief.
This is the daily context layer: what kind of pressure or leverage is active right now.
Computed from stacked natal, decade, year, month, and day transformations.
The score reads core work palaces such as Personal Direction, Income & Returns, Reputation & Visibility, and Work & Projects, then converts their combined pressure into a 0-10 survivability score and label.
This is not a happiness score. It estimates how survivable the current system is for you.
Derived from today's day-level Ji event and a palace-specific scene template.
The app finds today's Ji palace, selects a matching scene template for that palace, and renders one situation, what not to do, and one corrective move.
This is the concrete daily scene: what today's leak looks like in normal work language.
Computed from the next 10 weekdays of month and day transformations in interview-relevant palaces.
For each of the next 10 weekdays, the app rescans Travel, Execution, Partnership, Peers, and Identity, adds weighted support from Lu, Ke, and Quan, subtracts friction from Ji, and maps the result into GOOD, MIXED, or AVOID. Logged-in users see all 10 weekdays; guest users see a shorter preview.
This is a timing read, not an exit read. It tells you which upcoming dates are cleaner for interviews and recruiter conversations.
input: identity_star: zi_wei execution_star: tian_ji identity_brightness: P execution_brightness: W execution_transformations: Ji decode: identity => high-drive command default execution => strategy lane under friction brightness => identity overpowered, execution constrained Ji on execution => delivery drag + rework risk read: You can set direction fast, but execution debt accumulates unless scope is cut and owner lines are explicit.