When Indicators Conflict

Your task is to turn all supported timing rows for one positioned line into an auditable record. Preserve provenance and alternatives. Do not declare one candidate the true event date merely because it appears first.

Rank evidence, not likelihood

When timing indicators conflict, compare the authority and scope of the evidence behind them:

Evidence layer	How to use it
A documented case statement	Apply it only within the facts the case actually records.
A clearly located received timing statement	Derive only the operations named in that statement.
A named lineage rule	Attribute it and keep its application within the stated lineage and scope.
An explicit UAYA course convention	Use it to organize the worksheet, never as proof of an ancient rule.
An unsupported claim	Exclude it; record insufficient or no window.

This order governs source use in the course. It is not a probability scale, a measure of importance, or evidence that an event will occur.

Build the comparison table

For every candidate, record:

1. the selected line and the condition that generated the candidate;
2. the exact symbolic derivation, including the relevant branch relation;
3. the dated window only after the question horizon, calendar anchor, and time zone are declared;
4. the public source and locator, or the explicit label UAYA course convention;
5. the scope limits and any conflicting alternatives;
6. the final disposition: retained, excluded, insufficient, or no window.

If a reader cannot reproduce the candidate from those fields, the candidate is not supported for use in the timing record.

UAYA timing record

The following record format is a UAYA course convention:

Subject and position:
Question horizon / calendar anchor / time zone:
Governing condition:
Secondary observations:

candidate 1: source | derivation | symbolic and dated window | scope
candidate 2:
candidate 3:

course disposition: conditional candidate set / insufficient / no window
alternatives retained:
post-window status: open / observed / missed / unresolved

The disposition describes the record, not the probability of the hoped-for outcome.

Conflict controls

Divergent windows

If two adequately sourced routes produce different windows, retain both with their derivations and scope limits. Do not erase the conflict and do not cast again merely because one result is inconvenient. A later cast requires materially changed facts under the course intake screen.

No supported candidate

subject: line at position 4
governing condition: insufficient
public timing authority: none located
candidates: none
course disposition: no window

This is a complete result. A blank date is more accurate than an unsupported date.

Expired window

Learner exercise; no invented result. After a candidate window closes, mark only what the record supports:

• observed — a clearly defined, independently recorded observation occurred in the window;
• missed — the defined observation did not occur in the window;
• unresolved — the observation criteria or evidence are not adequate.

Do not move the window after seeing the record. Do not turn ambiguity into confirmation.

Final review

Before carrying a timing record forward, confirm:

• the subject is a positioned line;
• every candidate has a public source or is explicitly labelled as a UAYA course convention;
• every derivation is complete enough for a reader to reproduce;
• the question horizon, calendar anchor, and time zone are visible;
• alternatives, exclusions, and no-window results remain visible;
• no candidate is phrased as a promise or real-world instruction.

Source note

The comparison order, record format, and conflict controls on this page are UAYA course conventions. The received operations used elsewhere in this act are located in Zengshan Buyi, vol. 1, “General Notes on Response Times for the Various Categories” (各门类应期总注章), printed pp. 48–49 (composite PDF physical pp. 49–50). That passage supplies individual operations; it does not establish a universal precedence hierarchy among them.

Next step

Act 8 ends with an auditable candidate record, not a promised outcome. Continue to Act 9: Domain Applications and keep the intake and authority boundaries active.