Real charts often produce more than one timing clue. A target can be moving, transformed into void, part of a waiting frame, and touched by a support line.

When timing indicators conflict, do not pick the most interesting one. Rank them.

Precedence protects the reading from false elegance. The best-looking pattern is not useful if a more basic condition prevents the line from acting.

1 Life of the line

Void, month break, and day break come first. If the line is not usable, restore it before anything else.

2 Binding or disturbance

Bound and clashed states come next. A held or unstable line must release or stabilize before it can deliver.

3 Movement and trigger

Moving-line landing and strong-quiet activation apply after the line is usable and unblocked.

4 Frames and assists

Frame completion, support lines, and extra assists refine timing but should not outrank the target's core state.

The practical output

Primary date Highest precedence

The date that resolves the most fundamental state.

Secondary date Next plausible trigger

A backup produced by a lower-ranked but still valid rule.

Window Near or far bounds

The practical range in which the event should show itself.

Confidence How clean is the stack?

High when rules agree. Lower when methods compete or rely on school-dependent backups.

The final timing record should say why the primary date wins, why the backup remains plausible, and what would lower confidence. That explanation is part of the timing, not an optional footnote.

Use this order when rules stack:

  1. Usability: void, Month Breaker, Day Breaker, or transformed void/break.
  2. Hold or disturbance: bound, clashed, or transformation into bind/clash.
  3. Ordinary action: moving-line landing or strong-quiet activation.
  4. Assists: frames, support chains, value backups, and broader scale checkpoints.

The earlier tier supplies the primary date. Later tiers can refine the window, raise or lower confidence, or become backup candidates after the primary condition clears.

Example stack

A moving target transforms into void and is part of a waiting frame. The tempting date is the frame-completion branch because it looks elegant. But the transformed branch is void, so restoration comes first.

Ignore for now Frame completion

The frame cannot deliver through an unusable transformed effect.

rank above
Use first Void fill

The transformed branch must be filled before the motion can land.

then
Recheck Frame support

After restoration, the frame can refine or accelerate the result.

Traps

Trap Choosing the fanciest rule

Elegant patterns do not outrank line usability.

Trap Suppressing backups

A lower-ranked candidate can still be useful if it is clearly marked as secondary.

Trap Giving a date without confidence

Timing predictions should carry confidence just like judgments do.

Where this lands

Act 8 completes the basic reading pipeline: verdict plus timing. Act 9 applies that pipeline to real question domains.

Continue to Act 9: Domain Applications