Three target messages can describe one gold signal

Choose between a cumulative and a mutually exclusive table

Use one row per full signal ID. A cumulative view can flag which explicitly reported milestones the row contains. One row may contribute to several such columns. A mutually exclusive view instead assigns that row to the highest reported milestone, or to a separate category for incomplete or adverse records. Both views can be informative when the report explains the denominator.

Suppose a hypothetical archive contains one row with all three targets, one with TP1 and TP2 and one with TP1 alone. The cumulative counts are three, two and one. The exclusive highest milestones are one each. Adding the cumulative counts gives six observations about stages across three signals. These are deliberately invented records for demonstrating the method.

Source notes: [1] CyGuru Gold · Production signal feed

A higher report may leave lower event times unknown

If a feed retains a TP3 report without individual TP1 and TP2 messages, preserve the highest report and mark the lower timestamps unavailable. A geometry-based inference that price likely crossed a lower threshold is a different claim from a separately timed production event. Gaps, feed conventions and the applicable script rule can change what follows from the available record.

For conditional progression, predeclare the set of identities that contribute to each denominator. For example, a progression from TP1 to TP2 can require both a verified TP1 message and a complete observation window for follow-up. Omitting missing or unresolved rows without explanation can change the result more than any movement in the numerator.

Keep quantity outside the alert count

A target report says that the indicator recorded a stage. Exit quantity requires additional records. If using a strategy emulator, its configured exit orders and quantity reservations matter. Live broker execution requires a corresponding account record and reconciled fills. Neither can be reconstructed by assigning a fixed share to each alert after seeing the sequence.

Keep stage flags, highest stage, activation and terminal status in one table and any verified position quantities in another. Distinct setups during one price move can still share market exposure. Publish the counting rule, exclusions and missing fields so readers can reproduce the table without mistaking alert activity for an overall win rate.