Chapter 9
Call lifecycle
A call is created once and then tracked until it plays out. This chapter is what happens in between: how a peak is verified before it counts, how a dying call is put on a slow sweep and then taken off the board without leaving the win rate, and what the ledger does when it fills up.
9.1Peak verification
The win rate is only worth reading if the peaks behind it are real. Market data is noisy — a thin pool, a bad tick, a provider disagreeing with itself — and a single wrong reading can mint a 40x that never happened. Four rules stand between a reading and a recorded high.
| Rule | What it does |
|---|---|
| Entry is the floor | A call's peak can never be below the market cap it was called at. The post-call high starts at 1.00x, never lower. |
| A big jump needs a second look | A new high up to 3x the standing peak is ordinary price action and is recorded at once. A reading beyond that is not written on the strength of one tick: it is held as a pending peak, and only a second reading within two minutes and within 10% of it confirms it — the lower of the two is recorded. Otherwise the pending value is discarded. |
| Lifetime ATH ceiling | A reading meaningfully above the token's known lifetime all-time high is rejected outright. A token cannot quietly exceed its own record on a single tick. |
| Retroactive audit | When a lifetime-ATH figure arrives later, existing peaks are re-checked against it and clamped down if they are impossible. |
Unverified peaks
A peak that has not cleared these checks is marked unverified, and the card says so: a $1.2M peak is held pending verification — not counted. While unverified:
- The call is credited with its entry (1.00x) instead, never the disputed figure.
- It cannot count as a win.
- It raises no milestone or new-high alerts.
- It is excluded from the backtest entirely.
This is deliberately the pessimistic direction. An unverified peak makes the scanner look worse than it might be, which is the only safe way to be wrong about your own track record.
Where a peak came from
Every recorded peak carries its provenance:
| Source | Meaning |
|---|---|
| entry | Still at the market cap it was called at — it has never made a new high. |
| live | A normal reading inside the jump tolerance. |
| confirmed | A large jump corroborated by a second reading. |
| clamped | An impossible peak pulled back to the lifetime ATH. |
| gmgn | A lifetime-ATH figure that arrived from the provider and exceeded what was recorded. |
9.2Dormancy, re-signalling and played-out calls
Most calls die. Re-pricing a dead call as often as a live one is wasted effort, and keeping it on the board forever buries the calls still in play — so a dying call is first put on a slow sweep, then taken off the board, and its outcome is kept either way.
| Transition | Trigger |
|---|---|
| Goes dormant | The call has fallen below 0.3x of its entry and is more than an hour old. The grace hour exists so a call that dips hard in its opening minutes is not written off. |
| Stays dormant | Refreshed every 30 minutes instead of every cycle. The card shows a dormant badge and ·30m beside its Now figure, so you can see the number is not live. |
| Wakes | The price recovers to 0.3x or above. Normal cadence resumes and a waking alert fires. |
| Re-signals | The scanner tiers the token STRONG BUY again while the call is dormant. The call restarts from the new signal — entry market cap, entry score, call time and peak are all reset — and it is stamped re-signalled. It is still one card; no second call is created. |
| Plays out | Still dormant 6 hours after the call. It leaves the board and stops costing a market check; its outcome moves into the retired totals (9.4). |
| Dies | The token has not traded for 30 minutes and its market cap is under $3K. It leaves the board at once, at any age — a fast rug counts too. A call that had already reached 1.5x stays a win. |
9.3Losing the pair
When a refresh finds no trading pair for a call, that is counted as a miss. Several consecutive misses and the call is flagged no live pair: the card switches its Now label to Last seen, and an alert fires once.
One miss is usually a provider hiccup, which is why a single one never flags a call. A run of them usually means the token rugged or was delisted. A flagged call is retried every 5 minutes, and every 30 minutes once it has missed six times in a row. One successful reading clears the flag and resets the counter.
The board footer summarises this across the ledger: Market-cap status · 12 dormant skipped · 3 no live pair · 1 feed failure · 2 peaks under review. Feed failures are the provider failing, not the token — those are not counted as misses.
9.4Retention and retired calls
A Pro or Edge ledger holds up to 500 calls. Played-out and dead calls (9.2) and period closes (8.8) normally keep it well under that. If it does fill, room is made by removing what loses the least, in this order, oldest first within each group:
- Dead weight — calls more than a day old, under 0.3x now, that never reached 1.5x.
- Other calls that never reached 1.5x.
- Wins.
- Calls made or re-signalled in the last hour — these go last.
The retired counter
Calls that leave the board — played out, dead, or removed for space — still happened, so their totals are kept: how many there were, how many were wins, and the sum of their peak multiples. Those figures are folded back into the win rate and average ATH shown on the board, and the Calls stat notes +n retired. A call counts once it has had 6 hours to run or its token has died; a younger one that leaves for space is not graded.
9.5Dismissing, clearing and allowing again
Three controls remove calls, and all three do something more than delete — they retire the token, so a later scan does not immediately log the same call again.
| Control | Does | Requires |
|---|---|---|
| Dismiss (✕ on a card) | Removes that one call and retires its token. | Pro / Edge |
| Clear | Removes every call, and retires every token that was in your ledger plus every token currently on the board — otherwise the next scan would refill the ledger within seconds. It also resets the retired totals, so the win rate starts again from nothing. | Pro / Edge |
| Allow them again | Clears the entire retired list. Any of those tokens that still signals a Strong Buy can be logged as a new call. | Pro / Edge |
The footer keeps the count visible — 14 tokens suppressed by dismissal or Clear — with Allow them again beside it, so a suspiciously quiet ledger always has a stated reason. Clear and Allow them again both confirm first.
Closing a period in Reports is different: it clears calls from the board but retires and suppresses nothing (8.8).
9.6The free-plan ledger
Signed-out visitors and Lens (free) users all read one shared ledger, kept on the server. It logs every verified Strong Buy on the free chains from every scan, whether or not anyone has the page open, and shows the latest 50. It is the same list for everyone — nothing in it is yours to dismiss or clear.
| Behaviour | Free (Lens) and signed out | Pro / Edge |
|---|---|---|
| Where calls live | one shared public ledger | your account |
| Which calls | free chains, logged on every scan | your chains, while you are watching |
| Capacity | latest 50 | 500 |
| When full | the oldest call drops off | removal order in 9.4 |
| Peak verification, dormancy, re-signal | yes | yes |
| Dismiss · Clear · retire | no | yes |
| Reports, analytics, backtest and band hit rates | no | yes |
The consequence worth knowing: the shared list is a rolling window. A call older than the latest 50 is gone from it, whatever it did. See Chapter 11.
AlgoLens user manualChapter 9 · Call lifecycle