Act 9
Domain Applications
The universal machinery is built: chart construction, target selection, strength, interaction, advanced line behavior, judgment, and timing.
Act 9 adapts that machinery to question domains. The key move is simple but easy to miss: the domain tells you the field of meaning, but the exact question still decides the target line.
This act is not a list of shortcuts. It is a routing layer: identify the domain, restate the question, select the line that actually bears the answer, then translate judgment and timing into the domain’s real-world language.
The pattern is the same across the act: domain names the world of the question; target names the line being judged; support and obstruction explain how the domain behaves. Keeping those three layers apart is what prevents “career means Officer,” “health means Officer,” “legal means Officer,” or “romance means one spouse line” from becoming bad shortcuts.
Career, wealth, health, romance, legal, travel, documents, weather, or broad life pattern.
The same domain can route to different lines depending on who or what the question is really about.
A favorable judgment means different things in an exam, lawsuit, illness, trip, contract, or relationship.
What this act teaches
The question's topic is not automatically the target line.
Career, wealth, health, romance, legal, travel, documents, and weather each have their own line map.
Questions about all of life must be divided into focused readings.
Domain map
Officer often carries position; Parent carries credentials; Brother marks competitors.
Wealth is central, but World, Brother, Officer, and Parent decide the real shape.
The patient is the target. Officer usually describes illness pressure, not the patient.
Relationship status changes the routing. Spouse, partner side, and current bond are not always the same line.
Officer, Parent, World, Response, and kinship lines must be separated carefully.
Movement questions depend on who travels and what counts as arrival.
Parent usually carries the document, but Officer and World decide validation and receipt.
Weather readings use domain-specific elements and timing, not personal target routing.
Split the question. One chart should not be forced to answer every life area at once.
Where this leads
After this act, the method is no longer abstract. You can route a real question, select the correct target, translate the verdict into the right domain, and carry timing forward without confusing the line roles.
It also sets up Act 10. Domain fluency changes how you communicate. A weather analysis is not a forecast. A health chart is not casual prediction language. A legal chart is not legal advice. Broad-life questions need splitting instead of a single total-life verdict.
Checkpoint
By the end of Act 9, you can keep domain and target separate. You can adapt the same reading pipeline to career, wealth, health, romance, legal, travel, documents, weather, and broad-life questions without inventing a special method for each domain.
The modules
Why a question's topic does not automatically decide the target line.
9.2Career, Exams, OfficialsHow to route questions about rank, posts, exams, appointment, and recognition.
9.3Wealth and BusinessHow to route questions about money, collection, investment, trade, and business risk.
9.4Health and RecoveryHow to route illness questions by patient rather than by illness alone.
9.5Romance and MarriageHow to route questions about pursuit, spouse, relationship status, and marriage outcome.
9.6Legal and DisputesHow to route lawsuits, penalties, evidence, opponents, and disputes.
9.7Travel and MovementHow to route questions about departure, return, arrival, and blocked movement.
9.8Documents, Contracts, AgreementsHow to route questions about papers, contracts, certifications, deeds, and approvals.
9.9WeatherHow to route rain, clearing, storms, and weather timing questions.
9.10Lifelong and Broad QuestionsWhy broad life questions should be split into focused readings.