Crypto Alerts Plus the Dashboard: Two Tools, One Promote Rule

If the ping would not survive a board look, the ping is wrong. Alerts and the live dashboard are two tools with one promote rule on CoinGecko ranks 51-200. Breakflare is a daily hype-momentum tracker for that band. It scores hype, 3d/7d momentum, Climb, Breakout Score™, and confidence. Core research does not place trades or publish price targets.

Key Takeaways

• Write one promote rule and make both alerts and starring obey it.
• Alerts inherit floors; the board confirms columns side by side.
• Do not run noisy alerts beside a strict board, or you will obey the noisy one.
• Weekly sync keeps thresholds aligned after narrative weeks change your habits.

What does one written promote rule look like?

A promote rule is a sentence you can enforce without vibes. Example shape:

“Star only ranks 51-200 names that clear Breakout Score™ and confidence floors, show non-fading 7d momentum relative to hype, and clear Climb when the story claims breakout, then confirm on the board before any agent eligibility.”

That sentence should drive:

• Manual starring on the daily watchlist
• Alert thresholds (threshold playbook)
• Paper Trading agent entry gates (paper mode)

If alerts use a looser sentence than the board, the looser sentence becomes the real desk rule. Humans obey pagers.

Print the promote rule where you configure alerts. If the config screen and the rule disagree, the config will win by Thursday. Documentation that lives only in chat is not a rule.

Universe context stays fixed: the 51-200 band. Top-50 graduates leave the mid-cap job. Microcaps stay out. The scoring stack defines the columns you are allowed to cite in the rule.

How do alerts inherit the promote rule?

Inheritance means identical floors, not “inspired by” floors.

1. Copy Breakout Score™ minimum from starring.
2. Copy confidence minimum from starring.
3. Copy Climb requirement if starring requires Climb (climb score).
4. Copy the momentum veto: high hype with fading 7d momentum does not ping (false breakouts).
5. On ping, required next action is: open the board, sort, confirm.

Alerts that skip step 5 train subject-line promotes. That failure is covered in email vs dashboard, and it applies to Telegram too (Telegram setup).

Cap volume so inheritance stays believable. A correct floor that fires twenty times overnight still breaks the workflow. Raise floors before you add channels.

How does the board confirm what the ping claimed?

The board’s job is comparative. Alerts isolate a ticker. The dashboard shows peers.

After a ping:

1. Open the live Plus board or your UTC snapshot print.
2. Sort Breakout Score™ on ranks 51-200.
3. Find the pinged name among finalists (or notice it would not make the cut today).
4. Read hype, 3d/7d momentum, Climb / rank climb velocity, and confidence together.
5. Decide star, skip, or watch. Log the decision in your research journal.

If the pinged name looks strong alone but weak versus peers, demote. Relative attention is the product’s point. Absolute excitement in a notification is not.

The most expensive habit is starring from the notification, then opening the board later to “confirm” a decision you already emotionally locked. Reverse the order: board first, star second, alert only as the summons.

Why does a weekly sync matter?

Narrative weeks change behavior. You tighten the board after a false breakout cluster, then forget to tighten alerts. Or you travel, loosen alert floors “just for the airport,” and never restore them.

Weekly sync checklist:

1. Re-read the written promote rule.
2. Diff alert floors vs starring floors.
3. Review false-positive pings from the week.
4. Delete one unused alert type if you added any.
5. Confirm agent paper gates still match your confidence floor.

Travel does not justify a second promote rule. If you need lighter touch while traveling, shrink the shortlist and raise floors, or pause research alerts and keep only ops notices. Do not run noisy alerts and a strict board in parallel.

What belongs in the promote rule, and what does not?

Include only gates you can enforce on both surfaces:

• Universe membership (ranks 51-200)
• Breakout Score™ floor
• Confidence floor
• Climb requirement if starring requires it
• Momentum veto language (high hype with fading 7d)

Leave out:

• Price targets
• “Looks like a narrative winner” aesthetic judgments
• Friend tips
• Unsourced rumors
• Exceptions for travel, boredom, or FOMO

If a clause cannot be checked on the board columns and mirrored in alert config, it is not a promote rule clause. It is a diary entry. Diary entries can live in the research journal. They should not unlock pings or agent eligibility.

When the rule gets longer than five bullets, it usually means you are encoding edge cases instead of raising floors. Prefer fewer, stricter floors. Complexity is how two surfaces drift apart.

How do you diagnose which surface is lying?

When starring and alerts disagree for a week, run a blunt audit:

1. Export or list the last 20 research pings.
2. Mark each as board-confirmed star, board-confirmed skip, or never opened.
3. If “never opened” is common, the alert channel is entertainment.
4. If “board-confirmed skip” dominates, floors are too loose on the alert side.
5. If stars happen without pings and that bothers you, that is optional: many desks want fewer pings, not more.

The board can also lie in a softer way: you open it, glance, and still obey the ping emotionally. Require a written star/skip after every research ping for one week. The act of writing restores the board as the decision surface.

How do starring, alerts, and agent eligibility form a single chain?

Think of a one-way chain:

1. Written promote rule
2. Board confirm against columns
3. Star (or explicit skip)
4. Alerts only summon candidates that could pass (1)
5. Paper agent eligibility reads from stars / the same floors, never from raw pings

If any arrow reverses, the desk drifts. The most common reverse arrow is (4) driving (3): the ping creates the star. The second is (4) driving (5): the ping creates agent eligibility. Both reverse arrows skip the board.

Draw the chain in your notes once. When something feels off during a loud week, ask which arrow reversed. That question is faster than rewriting every threshold from scratch.

What does “weekly sync” look like as a 12-minute agenda?

Minute 0-3: paste this week’s ping list and star list side by side.
Minute 3-6: mark mismatches (pinged but skipped; starred without ping; starred without board).
Minute 6-9: change one floor or delete one alert type.
Minute 9-12: confirm paper agent eligibility source still equals stars/floors.

Stop at 12 minutes. Longer syncs become redesign sessions and create more drift. One calibrated change per week compounds. A monthly rewrite usually means you skipped the weekly 12 minutes.

Want the live rank 51-200 board, whales, alerts, and paper Trading agent? Start a 14-day Plus trial at app.breakflare.com (Plus is $399/mo or $3990/yr).

Alerts vs board responsibility table

Frequently asked questions

Can alerts use a looser rule than the board?
No. The looser rule becomes the desk. Keep one promote rule.

Should I disable the board and live on alerts?
No. Alerts lack peer context. Running noisy alerts without a strict board train you to obey noise.

What if I travel?
Raise floors, shrink the shortlist, or pause research pings. Keep ops alerts if you use agent tooling. Do not invent a vacation promote rule.

Telegram and email both?
Only if both inherit the same floors and you still reopen the board. Two channels with two logics is worse than one quiet channel.

Does Plus change the promote columns?
Plus unlocks live ranks, alerts, whales, trackers, and paper Trading agent. Research still centers on hype, momentum, Climb, Breakout Score™, and confidence.

Should agent eligibility ever be wider than starring?
No. If you would not star it by hand after a board look, paper Trading agent should skip it too.

Related reading

• Alert threshold playbook
• Email alerts vs the Breakflare board
• Daily rank 51-200 watchlist workflow
• What is a crypto signal confidence score?