Sample report

By DailyAstro · Last updated 2026-09-06

Every number below was produced by the same engine that runs in the app — none of it was written to look good. Enter your own birth date and this is the shape of what you get.

The sample chart

Note that 亥 (day) and 卯 (month) already occupy two of the three seats in the 亥卯未 wood group. Any 未 day completes it on the day branch; on other days a 未 hour completes it instead, as long as that hour is not clashed away — the high scores below come by both routes.

Wealth days in 2026

After scanning the full year, 23 days reach the 100-point threshold: 9 strong and 14 good. None reaches “exceptional” — this chart's best 2026 day is 150. The rest either fall short or hit this chart's four vetoed day branches — 巳 clashes the day branch 亥, 酉 clashes the month branch 卯, 子 punishes 卯, and 亥 self-punishes against 亥 — or the almanac gate: 午 days clash the year branch 子 (the zodiac clash), so all six 丙午 days are out, and broken days such as 2026-02-02 never qualify.

Five 丁未 days qualify, but no longer with one score: 04-03 at 140, 09-30 and 11-29 at 130, 06-02 at 110, 08-01 at 100 — the same day pillar, separated by the almanac's auspicious/inauspicious spirits, its 建除 day officer and its 吉神. The sixth 丁未 day, 2026-02-02, is a broken day and is vetoed outright (see below).

Why 2026-10-19 scores 150

The 五鼠遁 rule starts a 丙 day at the 戊子 hour; counting to 未 lands on 乙未 — 乙 is the 食神 output stem of 癸, and 未 is the one branch the wood group is missing, so a single hour fires two rules. The wealth-element-in-the-branch rule does not fire (未 is earth, not fire), so the hour is worth 75 rather than 85.

Second place: 2026-04-03 丁未, 140

An earlier version of this page showed these 丁未 days at 180, because the 丁未 hour was credited with “full three-harmony +50 plus indirect wealth in the stem +30”. But 未 is already the day branch — 亥卯未 was complete before the hour arrived, and the branch bonus above had already paid for it. Counting the same trio twice was a bug. Corrected, the 丁未 hour keeps only its wealth-stem 30, tying with the 癸卯 hour's half-harmony 30; the pillars give 130 and the 吉神 三合 bonus lifts the day to 140.

A vetoed day: 2026-02-02 丁未

Its pillars score exactly what 04-03's do (50 + 50 + 30 = 130), and the old version even ranked it first for the year. Open the almanac for that day, though:

Nobody who reads an almanac would nod at a bet placed on a day marked “undertake nothing else”. So the day appears on no list at all — not scored down below 100, but vetoed outright, no deduction needed. The footer of the app's “why” sheet — “已過關：破日／大耗 · 沖生肖 · 歲破 · 刑沖” (cleared: broken day / great loss, zodiac clash, 太歲 clash, punishment and clash) — is exactly these gates.

One more note: this chart's year branch is 子, and the 2026 丙午 year's 太歲 is 午 — a 子午 clash. So during 2026 the app's Today and Dates screens show a chip reading 今年沖太歲 · 宜靜不宜動 (“clashing the year spirit this year — lie low”). It is information only and changes no score.

Purpose sample: opening a business in 2026

Same chart, purpose switched to “open a business”. After the almanac's 宜/忌 gate, the personal clash veto, the almanac hard vetoes (broken day / zodiac clash / 太歲 clash) and the 100-point qualifying line, 29 days remain in 2026 (4 strong, 25 good), and the best score is 140.

Compatibility sample: hiring a helper

A two-person household: me (1984-03-30, 癸亥 day, 子 year) and my wife (1984-09-14, 辛亥 day, 子 year). Three candidates — names are fictional and the birth dates are sample data, but the scores are really computed. The overall figure is the weighted mean with my own score counted twice.

This sample runs under the helper / subordinate lens. Each of the seven relationship lenses (spouse, dating, friend, colleague, business partner, boss, helper) carries its own weights and its own verdict vocabulary, so the same birth dates score differently under another lens. Every number below is on the helper ruler.

Expanding the top candidate, member by member

The same 寅亥 six-harmony fires for both members because both day branches are 亥. The 戊癸 stem combination landing on top of that six-harmony is what 天合地合 names, so it scores a small extra row of its own. For me, 戊 earth is 癸 water's 正官, costing 8 points — easily outweighed by the harmony rules.

Why the third candidate is flagged

A day-branch clash is a hard clash, not merely a deduction — even if the weighted average had come out high, it would still be flagged ⚠ on its own. Here both members clash, so the average falls to 36 as well.

First working day for the top candidate

The day must clash with neither chart, each chart must clear the almanac gate (broken day / zodiac clash / 太歲 clash) on its own, and the almanac must list 開市 (open for business) or 納財 (receive wealth) as suitable:

Maria's year branch is 丑, and 丑 clashes 未 — so every 未 day, the employer's best (three-harmony +50), is vetoed as her zodiac clash, and the best remaining days are 寅 days (six-harmony with the employer's 亥). The suggested hour is the 丑 hour because: the 未 hour would complete the employer's 亥卯未 but clashes Maria's year branch; the 午 hour half-harmonises with 寅 but clashes the employer's year branch 子; the 子 hour punishes the employer's month branch 卯. No surviving hour carries any harmony, so the first hour that clashes or punishes nobody is shown (its reason reads 平, neutral).

This list has its own scale (almanac 50 plus each chart's branch bonus, ceiling 150, no almanac adjustments) and shows no good / strong / exceptional band. The candidate contributes no branch bonus here, so only the employer's line appears. The suggested hour is harmony-only, as for purpose dates, and does not count toward the score — it only tells you which hour runs smoothest.

Start date: the three rows above were computed from a 2026-01-01 starting point, so that the sample covers the whole of 2026. In the app, first working days are counted from today — the dates you get will all be in the future, and will not line up row for row with this sample.

Run this with my own birth date

Want to know where each point comes from? Read the method →