What information is needed for date selection

To request a date selection, the first thing that must be made clear is the matter itself: which event is being arranged, where it will be held, and whether it has a corresponding traditional entry name. The 通书 suitability and taboo columns use a fixed vocabulary. Modern events do not necessarily appear in that vocabulary; in such cases, the correspondence is chosen by the person consulting the tables. When the matter involves a specific person, the basic level is the 年命: the 通书 clash column gives the earthly branch of the day and the zodiac sign it clashes with, and this falls on the year branch. If the question is how a particular day affects a particular individual, more than the year branch is needed; the person’s complete birth year, month, day, and hour are required. The feasible date range is determined by hard constraints such as office working days, construction schedules, family leave, contract dates, and hospital procedures; this item should be submitted first. If the birth hour is uncertain, a candidate range should be given rather than choosing one on the spot to fill in. The site’s engine can calculate the 干支 of any date, but it does not publish date-selection recommendations.

事项本身要说清楚的几项

A date-selection request begins with the event itself. The person submitting the request should state plainly what is being arranged: a wedding, a move, a groundbreaking, a business opening, a surgery date, a registration, or any other matter. The location should also be given, because a date is not selected in the abstract; the place where the event will occur is part of the frame in which the day is assessed.

Where a traditional name exists for the matter, it should be supplied. The 通书 organizes its suitability and taboo entries around a fixed set of categories, and the same modern activity may correspond to different traditional headings depending on how it is described. For example, a modern contract signing may be treated under 立约，交易, or 开市 depending on the nature of the transaction. A hospital admission may be assessed under 求医 or 治病, but the choice of heading changes which columns are read. If the requester does not identify the traditional category, the person doing the lookup must infer it, and the inference may not match the requester’s intention.

The fixed vocabulary of the 通书 is a closed list. It was not designed to contain every contemporary activity, and it does not. Activities such as filing a court case, submitting a visa application, or starting a software deployment have no direct entry. In those cases, the correspondence between the modern matter and the traditional heading is a judgment made by the person consulting the tables. That judgment should be recorded as part of the request, because a different mapping can lead to a different reading of the same day.

当事人那一栏要给到哪一层

The level of personal data required depends on what is being asked. For a general date selection in which the day is checked against the 通书 columns, the relevant personal layer is the 年命. The 通书 clash column states which earthly branch the day carries and which zodiac sign that branch clashes with. This clash falls on the year branch, meaning it is read against the person’s birth year in the sexagenary cycle. If the day’s branch clashes with the person’s year branch, the day is traditionally marked as unfavorable for that person in activities where the person is the main subject.

The 年命 is not the person’s age and not the Western calendar year of birth. It is the 干支 designation of the birth year, expressed through the heavenly stem and earthly branch. Two people born in the same Gregorian year can have different 年命 if their birthdays fall on opposite sides of the lunar new year, because the 干支 year changes at the beginning of the sexagenary year, not on January 1. The requester should therefore provide the 干支 of the birth year or enough information to derive it, not simply the Western year.

If the question goes beyond the general day columns and asks how a particular day affects a particular individual, the year branch alone is insufficient. In that case the person’s complete birth data are needed: the year, month, day, and hour. The hour is expressed as one of the twelve double-hours, and it is derived from local time. Without the complete set, a personal assessment cannot be performed, because the interaction between the day and the individual is read across all four pillars, not the year alone.

可行区间是最先要交出的东西

Before any tables are consulted, the requester should provide the range of dates that are actually possible. This range is set by hard constraints, not by metaphysical considerations. Office working days, construction schedules, family leave, contract deadlines, hospital procedures, and the availability of venues or officials all fall into this category. The feasible interval is the first item to be submitted, because if no possible dates are given, the selection has nothing to operate on.

The reason this item takes priority is practical. A day may be excellent in the 通书 and yet impossible for the requester to use. A signing that must happen before a contractual deadline cannot be moved to a later auspicious day. A surgery that must fit a hospital’s operating schedule cannot wait for a preferred date. The feasible range narrows the field to dates that can actually be used, and only within that field does the selection take place. Submitting the constraints first prevents the work of producing a recommendation that the requester cannot act on.

The feasible range should be as specific as possible. A range such as “sometime in the next two months” is weak, while “any weekday between March 3 and March 28, excluding March 10” is strong. If the event involves multiple people, the constraints of all parties should be included, because a date that works for one person may be impossible for another. The same applies to institutional constraints: a government office has fixed working days, a construction crew has a start date fixed by contract, and a family may have leave periods that cannot be changed.

资料不足时会发生什么

When the submitted material is incomplete, the lookup cannot proceed cleanly. If the event has not been clearly identified, the person consulting the tables must guess which traditional heading applies, and the resulting reading may answer a different question than the one the requester asked. If the location has been omitted, the assessment may be done without the place, which in some traditions is a relevant variable. If the traditional name is missing and cannot be inferred with confidence, the suitability columns that are read may be the wrong ones.

When the personal layer is incomplete, the problem is different. A request that asks how a day affects a specific person but supplies only the year branch cannot be answered at the requested level. The year branch supports a check against the day’s clash column, but it does not support a full personal reading. In that situation the requester should be told what is missing and why it matters, rather than having the gap filled by assumption.

When the birth hour is uncertain, the correct practice is to give a candidate range, not to pick one option on the spot. The hour branch affects the day pillar and the readings derived from it, and different hours within the same day can produce different results. A requester who does not know the birth hour should say which hours are possible, for example “between 3 and 7 a.m., most likely before 5 a.m.” The consultation can then note that the result is sensitive to the hour, or work with the range. Silently choosing one hour because a field must be filled is not acceptable, because it converts an unknown into a false precision.

The site’s engine can calculate the 干支 of any date. That capability is a computation, not a recommendation. The engine does not publish date-selection advice. If the request expects a recommendation and the engine only returns the 干支, the gap between the two should be understood as a difference in function, not a failure of the input. The engine requires complete input for what it does calculate; it does not infer missing data.

交付之后该核对什么

After the selection has been delivered, the requester should check several things. The first is that the matter described in the result matches the matter that was submitted. If the request was for a move and the result addresses a groundbreaking, the mapping was wrong. The second is that the traditional heading used in the lookup is the one the requester intended. The third is that the personal layer is correct: the 年命, or the full birth data if a personal reading was requested, should be checked against the original source.

The feasible range should also be verified. The delivered date should fall inside the range that was originally given. If it does not, either the range was not transmitted accurately or the constraints were not applied. The clash column should be checked against the year branch of each main person involved, if the selection was done at the 年命 level. If a personal reading was done, the birth data used in the calculation should be confirmed character by character, including the hour branch.

The result should state what it is and what it is not. A computed 干支 is not a recommendation, and a recommendation is not a guarantee of outcome. The requester should confirm that the delivered material is of the requested type: a 干支 calculation, a reading of the 通书 columns, or a personal assessment. If any of the listed items is wrong, the correction should be sent back with the specific error identified, so that the lookup can be redone against the corrected input rather than patched after the fact.