How signal rules work

A signal is a rule that fired on a token's read.

Every rule is defined once with a fixed direction (bull, bear, or context) and the panels it reads; when it fires it states the token's own numbers, the window and the chart behind it.

The direction comes from the rule, never from a number's sign: "net realized −$48k" inside the capitulation-flush rule is bull evidence, because that rule is defined as bull.

These rules are derived from the public Blocktronics panels. They are not the Blocktronics readout engine, and they have not been tested against what happened next.

1. 1

   Every per-token rule runs over one read's settled days. A rule fires (with a finding, a window and the chart behind it), stays quiet, or reports why it can't be evaluated (a missing panel, too few days, a token that barely trades).

2. 2

   How strongly a rule fired shows in three steps: light, moderate and strong. Context rules place the token and never count for either side.

3. 3

   Data floors keep rules quiet on thin reads: too few settled days for the rule's window, or too little DEX volume for a flow to mean anything.

4. 4

   Cross-token rules need the whole universe: they place the token among its chain's peers and run where the snapshot is at hand (the readout, the feed, the MCP).

HighShape, not data

Many strong signals: several observations stood out by a wide margin.

LowShape, not data

Few or none: nothing stood out, which is a finding too.

RisingShape, not data

New rules firing since the last snapshot or visit.

FallingShape, not data

Rules going quiet.

Evidence in the data, never advice

• Signals are evidence, not predictions, and not advice.
• A rule that can't run is not the same as a quiet one; the readout lists both.
• Intraday rules read the partial current day and are the weakest kind of evidence here.