Act 7 gave us a judgment. Act 8 asks when the judgment becomes visible.

The method is not “add strength and count forward.” Timing is about resolution. Something in the chart is waiting. The task is to identify what kind of waiting it is and what calendar event releases it.

Step 1 Name the target state

Void, bound, clashed, strong-and-quiet, moving, waiting frame, or transformation delay.

then
Step 2 Find the release event

Each state has a matching calendar action: fill, clash, combine, value, complete, or exit.

then
Step 3 Set the window

Choose hour, day, month, or year scale based on the question and the chart's urgency.

Why this works

A line does not verify merely because it is strong. A strong line may be quiet and need a trigger. A moving line may be fast unless it transforms into a delay. A void line may be weak now but become usable on the day that fills it.

So the first timing question is not “how strong is the line?” It is “what state is the line in?”

Strength still matters, but it is not the timing engine. Strength tells us whether a line can act well. State tells us what event it is waiting for.

Void Missing force

Wait for the calendar to fill the missing branch.

Bound Held force

Wait for the branch that breaks the binding combination.

Clashed Unstable force

Wait for combination or support to stabilize the clash.

Strong and quiet Ready force

Wait for the calendar to strike the line into action.

Moving Force in flight

Wait for the line to land on a value, combine, or relevant arrival day.

Delayed effect Blocked landing

Wait for the transformed branch or frame condition to resolve.

The timing output

The output should not be a single overconfident date. A useful timing result names the best candidate and the uncertainty around it.

Primary Best date

The highest-confidence branch event from the state rule.

Secondary Backup date

A lower-confidence date if another recognized method also applies.

Fallback Next checkpoint

The next month or broader window if the near date passes without resolution.

Confidence How firm?

High when the state and release event are clean. Lower when methods conflict.

The clean record is: primary date, secondary date, fallback checkpoint, timing scale, and confidence. That keeps timing from sounding more exact than the chart supports.

Trap

The common mistake is hunting for one master formula. That is not how this system thinks. There are several kinds of waiting, so there are several kinds of release.

The discipline is:

  1. Name the target line.
  2. Name the target’s current state.
  3. Apply the state rule before looking for decorative timing clues.
  4. Choose the timing scale from the question and the line state.
  5. Return a dated prediction with confidence, not just a branch name.

Timing becomes unreliable when those steps are reversed. A beautiful frame completion date does not outrank a void target. A moving line does not land quickly if its transformed branch is void, broken, or bound.

Source basis: the timing synthesis and the classical state-resolution rules. The method treats timing as state resolution, not arithmetic scoring.

Continue to The Four States of Stasis