What about the Orb reference table?

Many beginners regard the Orb reference table as a technical appendix and think it is just numbers. But when actually reading the disk, the tolerance actually determines the component of a phase. The tighter the aspect, the more qualified it is to enter the main line; the wider the aspect, the more cautious it is and treat it more as background, tendency or secondary clues.

What Orb cares about is not whether the phase exists, but whether it deserves to be explained emphatically.

The concept of a mature Orb is not a mechanical formula, but rather a combination of aspect types, participating planets and problem scenarios. For example, close connections between the Sun, Moon, Ascendant, and Ascendant are often more worthy of priority than wide aspects at peripheral points. Conjunctions and oppositions often have a different sense of tolerance than some secondary aspects.

Reference tables give a framework, not a substitute for judgment.

Many reading disks become confusing, not because they don't know how to explain, but because they are reluctant to delete them. Orb happens to provide a very practical filtering principle. It tells you which connections are close enough and strong enough to actually support the main text, and which ones, although they can be calculated, should not be placed on par with high-weighted aspects.

Once you know how to use Orb, disk reading will start to become clean.

Users do not necessarily need to memorize every allowable range, but they should know: when the report is very heavy on a conclusion, it is better to have tighter structural support behind it; if a clue is mainly built on wider connections, it is more suitable to be read as a reference direction rather than a conclusion.

This level of awareness will directly improve the quality of users' use of reports.