Every CMN lead Wed 4 Nov – Tue 17 Nov,
checked against every 6AB, 5AB, N1N and R row that person still has anywhere back to
Fri 8 May. Reaching a stage is meant to consume the one before it,
so every row found here is one that should have disappeared and did not.
Newest lead in the feed: 2026-11-17 12:46:42.
Every leftover sat in the same city as its CMN, so the person-matching holds.
Original code→ chase →R→ re-SMS, sends a picture →N1N→ free for a chat? →CMN — each step is meant to CONSUME the one before it
CMN in the window
333
people · 333 rows
Shifted cleanly
282
84.7% — nothing left behind
Still carrying an old stage
51
15.3% · 63 rows that should have gone
The shift itself failed
0
old stage within 14 days of the CMN
Two different faults — do not add them together.0 people (0 rows) carry a stage row from within 14 days of
their CMN: that is the shift failing to consume the previous stage.
51 people (63 rows) carry one older than that — an earlier journey
that died and was never cleaned up. Different causes, different fixes.
What is left behind
A person can be counted under more than one stage, so these do not sum to the total.
Stage still live
People
Of all CMN
Rows within 14d
Rows older
6AB
278.1%
333
0
32
5AB
30.9%
333
0
5
N1N
206.0%
333
0
20
R
61.8%
333
0
6
How long before the CMN was that row created?
A same-day leftover is unambiguous: the lead converted and the previous stage was simply never cleared.
R is the biggest single fault, and it is not subtle.
Of the 0 leftover rows dated the
SAME DAY as the CMN, 0 are R codes. The lead converts and its R row is simply
never cleared — same person, same day, both rows still live.
R rows still live
0
within 14 days of the CMN
Of those, same day
0
— — no ambiguity at all
Distinct R codes affected
0
it is not one broken feed
The R codes not being cleared
Every one of these is {CITY}{SOURCE}R — the chase stage of a lead that has since converted.
R code
City
Rows still live
Original code→ chase →R→ re-SMS, sends a picture →N1N→ free for a chat? →CMN — each step is meant to CONSUME the one before it
Push gap: Sun 8 Nov, Sat 14 Nov, Sun 15 Nov
carried almost no recycled leads at all against a median day of 263, while total lead flow held up.
That is the recycled push stopping, not a quiet day.
Leads in, by stage, per day
Recycled counts every stage row plus CMN once each. The last day in range is always part-built.
Date
All leads
Recycled
6AB
5AB
N1N
R
CMN
Wed 4 Nov
3,264
51615.8%
125
28
171
150
42
Thu 5 Nov
2,961
37512.7%
56
5
171
125
17
Fri 6 Nov
2,322
25110.8%
14
2
145
58
32
Sat 7 Nov
1,962
743.8%
2
2
54
11
5
Sun 8 Nov
1,751
130.7%
4
1
3
4
1
Mon 9 Nov
2,231
46921.0%
149
38
70
149
62
Tue 10 Nov
2,436
49920.5%
202
55
107
63
72
Wed 11 Nov
2,800
35112.5%
94
42
44
126
44
Thu 12 Nov
2,392
26311.0%
17
24
20
186
16
Fri 13 Nov
2,363
1175.0%
8
13
9
78
9
Sat 14 Nov
1,946
50.3%
2
0
1
2
0
Sun 15 Nov
1,831
00.0%
0
0
0
0
0
Mon 16 Nov
1,821
27615.2%
56
40
21
134
25
Tue 17 Nov
1,157
786.7%
31
7
4
28
8
TOTAL
31,237
3,28710.5%
760
257
820
1,114
333
By city
City
CMN people
Still carrying an old stage
Shift failed (≤14d)
New York
78
1114.1%
00.0%
Chicago
59
1016.9%
00.0%
Florida
45
613.3%
00.0%
Houston
37
821.6%
00.0%
Nashville
35
38.6%
00.0%
Dallas
31
516.1%
00.0%
Orlando
26
519.2%
00.0%
Boston
22
313.6%
00.0%
Yes — and that is what makes the leftovers a fault rather than the design.
A CRM pull shows a code as it stands now, so an in-place shift is invisible unless the same row was
observed earlier. Across 2,952 rows with an earlier observation on file, 93 were
caught mid-shift: the row's own code was rewritten to CMN and the old stage genuinely disappeared,
exactly as intended. 0 ever moved the other way.
Rows observed twice
2,952
the only rows that CAN show a shift
Shifted in place to CMN
93
the mechanism working correctly
Unchanged
2,859
96.8%
Shifted OUT of CMN
0
CMN is an end state
Every shift caught in the act
Was
Became
Rows
NYN1N
NYCMN
12
FL6AB
FLCMN
8
NA6AB
NACMN
8
FLN1N
FLCMN
7
NY6AB
NYCMN
7
CHIN1N
CHICMN
6
FL5AB
FLCMN
6
NAN1N
NACMN
5
HOUN1N
HOUCMN
5
DAL6AB
DALCMN
5
NY5AB
NYCMN
4
CHI5AB
CHICMN
4
ORLN1N
ORLCMN
3
CHI6AB
CHICMN
3
BOS6AB
BOSCMN
2
DALN1N
DALCMN
2
ORL6AB
ORLCMN
2
NA5AB
NACMN
1
ORL5AB
ORLCMN
1
DAL5AB
DALCMN
1
HOU5AB
HOUCMN
1
What this count can and cannot see
A shift that happened before the row was ever observed is invisible and always will be —
the ledger only started recording on 25 Aug 2026, seeded from /recycled-codes' chunk cache. So the
shift count is a floor. It grows on its own as the ledger accumulates, which is why this report
runs daily: a night not run is evidence that cannot be recovered later.