Signal Stack

Protected Mechanics

How Signal Stack builds a race decision

Signal Stack is not a black-box tout sheet, but it also does not publish its formulas, weights, thresholds, database exports, or private scoring rules. The public product explains the decision path without giving away the machinery.

Step 1: Read the race context

The first question is not "who is the pick?" It is "what kind of race is this?" Surface, distance, field size, scratches, track behavior, pace pressure, and race type all affect whether the final card should be narrow, protected, price-aware, or passed.

Step 2: Separate contenders from noise

Signal Stack looks for horses that are visible through the race-day evidence. That may include traditional handicapping strength, current support, shape fit, track/surface context, or contest usefulness. The public card does not show every input; it shows the horses that matter to the decision.

Step 3: Name the Primary

The Primary is the main opinion. It is the horse the card is built around when the evidence points clearly enough to one preferred direction.

Step 4: Decide whether the Primary needs protection

If the race is not clean, the card looks for a Backup. The Backup is not a random second pick. It is the horse that protects the decision when the shape, price, field, or contest setup says the Primary should not stand alone.

Step 5: Assign the posture

The posture is the point of the card. Signal Stack may say Trust Primary, Split, Lean Outside, ML Suppressed, or Pass/Chaos. That tells the player how to treat the race instead of pretending every race deserves the same kind of action.

Step 6: Review the result honestly

After the race, the archive logs what happened. If the Primary wins, it says so. If the Backup wins, it says so. If the card misses, that should stay visible too. The goal is process accountability, not guaranteed outcomes.

See the public sample archive