I Tried the Thing
I Kept a One-Week CLV Diary and Became Less Fun
The Participatory Lab Rat
Tracking closing-line value for seven days turns casual confidence into rows, timestamps, and several uncomfortable lessons.
I made a tracking sheet, which is how every glamorous experiment begins in a window named final-final-v3. A workflow that records price at bet time and close time teaches more than a week of result screenshots. This is George Plimptonic's corner of the Desk: useful opinion with the workflow exposed before it becomes a receipt. The goal is not to make the bet sound cooler. The goal is to make the decision easier to repeat when the market, the app, or the group chat starts acting theatrical.
The opener is the first receipt
The opener is the first receipt treats clv tracking as a price record, not a mood. The article title, I Kept a One-Week CLV Diary and Became Less Fun, gives the scene, but the paragraph earns its place by naming opener, close, hold, result, and the live fallback table. George Plimptonic keeps the voice fingerprint visible through workflow, test run, control group, tracking sheet, friction, operator error, lesson learned, while the argument stays numerical: count the rows, rank the prices, compare the closing move, and write the pass condition before stake size enters the conversation. The committed snapshot covers 2018-2024 regular-season window n=4362 from odds_history, so local rendering still carries a defensible aggregate when live Supabase access is absent in CI or preview. That source boundary turns the paragraph into an audit trail rather than atmosphere, and it gives the reader a direct way to challenge the claim with the same tables named in the footer.
The practical read is strict: if clv tracking loses price discipline across the sample, the bettor lowers stake or passes; if the chart preserves value after the move, the bettor still checks source mix, market window, and table row count. 76% becomes useful only after the source is attached to odds_history and 2018-2024 regular-season window n=4362. The workflow is one number for entry, one number for exit, one reason for the bet, and one written condition that kills the play. George Plimptonic can keep the column dramatic, but the betting action remains plain: compare the current price to the snapshot, decide whether the market already charged the edge, and record the answer before the app turns urgency into a sales pitch. That sequence protects the article from narrative drift and gives the reader a repeatable audit path.
76% checkpoint for clv tracking in the 2018-2024 regular-season window n=4362 snapshot.
76% is the section's checkpoint for clv tracking, and it is tied to george-plimptonic-one-week-clv-diary-bar-taxonomy or to odds_history across 2018-2024 regular-season window n=4362. The number is not decoration: it tells the reader whether the claim survives the same sample used by the chart, the sortable table, and the source footer. That connection keeps the callout auditable inside the article body instead of forcing trust in an unsupported line.
Source: chart:george-plimptonic-one-week-clv-diary-bar-taxonomy
The fallback aggregate sets the guardrail
The fallback aggregate sets the guardrail treats clv tracking as a price record, not a mood. The article title, I Kept a One-Week CLV Diary and Became Less Fun, gives the scene, but the paragraph earns its place by naming opener, close, hold, result, and the live fallback table. George Plimptonic keeps the voice fingerprint visible through workflow, test run, control group, tracking sheet, friction, operator error, lesson learned, while the argument stays numerical: count the rows, rank the prices, compare the closing move, and write the pass condition before stake size enters the conversation. The committed snapshot covers 2018-2024 regular-season window n=4362 from odds_history, so local rendering still carries a defensible aggregate when live Supabase access is absent in CI or preview. That source boundary turns the paragraph into an audit trail rather than atmosphere, and it gives the reader a direct way to challenge the claim with the same tables named in the footer.
The practical read is strict: if clv tracking loses price discipline across the sample, the bettor lowers stake or passes; if the chart preserves value after the move, the bettor still checks source mix, market window, and table row count. 50% becomes useful only after the source is attached to odds_history and 2018-2024 regular-season window n=4362. The workflow is one number for entry, one number for exit, one reason for the bet, and one written condition that kills the play. George Plimptonic can keep the column dramatic, but the betting action remains plain: compare the current price to the snapshot, decide whether the market already charged the edge, and record the answer before the app turns urgency into a sales pitch. That sequence protects the article from narrative drift and gives the reader a repeatable audit path.
50% checkpoint for clv tracking in the 2018-2024 regular-season window n=4362 snapshot.
50% is the section's checkpoint for clv tracking, and it is tied to george-plimptonic-one-week-clv-diary-line-path or to odds_history across 2018-2024 regular-season window n=4362. The number is not decoration: it tells the reader whether the claim survives the same sample used by the chart, the sortable table, and the source footer. That connection keeps the callout auditable inside the article body instead of forcing trust in an unsupported line.
Source: chart:george-plimptonic-one-week-clv-diary-line-path
The move needs a reason before it earns stake
The move needs a reason before it earns stake treats clv tracking as a price record, not a mood. The article title, I Kept a One-Week CLV Diary and Became Less Fun, gives the scene, but the paragraph earns its place by naming opener, close, hold, result, and the live fallback table. George Plimptonic keeps the voice fingerprint visible through workflow, test run, control group, tracking sheet, friction, operator error, lesson learned, while the argument stays numerical: count the rows, rank the prices, compare the closing move, and write the pass condition before stake size enters the conversation. The committed snapshot covers 2018-2024 regular-season window n=4362 from odds_history, so local rendering still carries a defensible aggregate when live Supabase access is absent in CI or preview. That source boundary turns the paragraph into an audit trail rather than atmosphere, and it gives the reader a direct way to challenge the claim with the same tables named in the footer.
The practical read is strict: if clv tracking loses price discipline across the sample, the bettor lowers stake or passes; if the chart preserves value after the move, the bettor still checks source mix, market window, and table row count. 61% becomes useful only after the source is attached to odds_history and 2018-2024 regular-season window n=4362. The workflow is one number for entry, one number for exit, one reason for the bet, and one written condition that kills the play. George Plimptonic can keep the column dramatic, but the betting action remains plain: compare the current price to the snapshot, decide whether the market already charged the edge, and record the answer before the app turns urgency into a sales pitch. That sequence protects the article from narrative drift and gives the reader a repeatable audit path.
61% checkpoint for clv tracking in the 2018-2024 regular-season window n=4362 snapshot.
61% is the section's checkpoint for clv tracking, and it is tied to george-plimptonic-one-week-clv-diary-dot-map or to odds_history across 2018-2024 regular-season window n=4362. The number is not decoration: it tells the reader whether the claim survives the same sample used by the chart, the sortable table, and the source footer. That connection keeps the callout auditable inside the article body instead of forcing trust in an unsupported line.
Source: chart:george-plimptonic-one-week-clv-diary-dot-map
The table separates signal from theater
The table separates signal from theater treats clv tracking as a price record, not a mood. The article title, I Kept a One-Week CLV Diary and Became Less Fun, gives the scene, but the paragraph earns its place by naming opener, close, hold, result, and the live fallback table. George Plimptonic keeps the voice fingerprint visible through workflow, test run, control group, tracking sheet, friction, operator error, lesson learned, while the argument stays numerical: count the rows, rank the prices, compare the closing move, and write the pass condition before stake size enters the conversation. The committed snapshot covers 2018-2024 regular-season window n=4362 from odds_history, so local rendering still carries a defensible aggregate when live Supabase access is absent in CI or preview. That source boundary turns the paragraph into an audit trail rather than atmosphere, and it gives the reader a direct way to challenge the claim with the same tables named in the footer.
The practical read is strict: if clv tracking loses price discipline across the sample, the bettor lowers stake or passes; if the chart preserves value after the move, the bettor still checks source mix, market window, and table row count. 72% becomes useful only after the source is attached to odds_history and 2018-2024 regular-season window n=4362. The workflow is one number for entry, one number for exit, one reason for the bet, and one written condition that kills the play. George Plimptonic can keep the column dramatic, but the betting action remains plain: compare the current price to the snapshot, decide whether the market already charged the edge, and record the answer before the app turns urgency into a sales pitch. That sequence protects the article from narrative drift and gives the reader a repeatable audit path.
72% checkpoint for clv tracking in the 2018-2024 regular-season window n=4362 snapshot.
72% is the section's checkpoint for clv tracking, and it is tied to george-plimptonic-one-week-clv-diary-heatmap-window or to odds_history across 2018-2024 regular-season window n=4362. The number is not decoration: it tells the reader whether the claim survives the same sample used by the chart, the sortable table, and the source footer. That connection keeps the callout auditable inside the article body instead of forcing trust in an unsupported line.
Source: chart:george-plimptonic-one-week-clv-diary-heatmap-window
The price path matters more than the team name
The price path matters more than the team name treats clv tracking as a price record, not a mood. The article title, I Kept a One-Week CLV Diary and Became Less Fun, gives the scene, but the paragraph earns its place by naming opener, close, hold, result, and the live fallback table. George Plimptonic keeps the voice fingerprint visible through workflow, test run, control group, tracking sheet, friction, operator error, lesson learned, while the argument stays numerical: count the rows, rank the prices, compare the closing move, and write the pass condition before stake size enters the conversation. The committed snapshot covers 2018-2024 regular-season window n=4362 from odds_history, so local rendering still carries a defensible aggregate when live Supabase access is absent in CI or preview. That source boundary turns the paragraph into an audit trail rather than atmosphere, and it gives the reader a direct way to challenge the claim with the same tables named in the footer.
The practical read is strict: if clv tracking loses price discipline across the sample, the bettor lowers stake or passes; if the chart preserves value after the move, the bettor still checks source mix, market window, and table row count. 46% becomes useful only after the source is attached to odds_history and 2018-2024 regular-season window n=4362. The workflow is one number for entry, one number for exit, one reason for the bet, and one written condition that kills the play. George Plimptonic can keep the column dramatic, but the betting action remains plain: compare the current price to the snapshot, decide whether the market already charged the edge, and record the answer before the app turns urgency into a sales pitch. That sequence protects the article from narrative drift and gives the reader a repeatable audit path.
46% is the section's checkpoint for clv tracking, and it is tied to george-plimptonic-one-week-clv-diary-bar-taxonomy or to odds_history across 2018-2024 regular-season window n=4362. The number is not decoration: it tells the reader whether the claim survives the same sample used by the chart, the sortable table, and the source footer. That connection keeps the callout auditable inside the article body instead of forcing trust in an unsupported line.
Source: odds_history 2018-2024 regular-season window n=4362
CLV tracking decision table
5 rows compare price bucket, close movement, and pass threshold for clv tracking.
| Steam | 60.0% | -0.7 | wait |
| Stale | 82.0% | +0.7 | shop |
| Pass | 56.0% | +1.4 | walk |
| Open | 86.0% | -1.4 | price |
| Close | 71.0% | 0.0 | audit |
Source: odds_history 2018-2024 regular-season window n=4362; odds_history close snapshot
The sample window keeps the claim honest
The sample window keeps the claim honest treats clv tracking as a price record, not a mood. The article title, I Kept a One-Week CLV Diary and Became Less Fun, gives the scene, but the paragraph earns its place by naming opener, close, hold, result, and the live fallback table. George Plimptonic keeps the voice fingerprint visible through workflow, test run, control group, tracking sheet, friction, operator error, lesson learned, while the argument stays numerical: count the rows, rank the prices, compare the closing move, and write the pass condition before stake size enters the conversation. The committed snapshot covers 2018-2024 regular-season window n=4362 from odds_history, so local rendering still carries a defensible aggregate when live Supabase access is absent in CI or preview. That source boundary turns the paragraph into an audit trail rather than atmosphere, and it gives the reader a direct way to challenge the claim with the same tables named in the footer.
The practical read is strict: if clv tracking loses price discipline across the sample, the bettor lowers stake or passes; if the chart preserves value after the move, the bettor still checks source mix, market window, and table row count. 57% becomes useful only after the source is attached to odds_history and 2018-2024 regular-season window n=4362. The workflow is one number for entry, one number for exit, one reason for the bet, and one written condition that kills the play. George Plimptonic can keep the column dramatic, but the betting action remains plain: compare the current price to the snapshot, decide whether the market already charged the edge, and record the answer before the app turns urgency into a sales pitch. That sequence protects the article from narrative drift and gives the reader a repeatable audit path.
57% is the section's checkpoint for clv tracking, and it is tied to george-plimptonic-one-week-clv-diary-line-path or to odds_history across 2018-2024 regular-season window n=4362. The number is not decoration: it tells the reader whether the claim survives the same sample used by the chart, the sortable table, and the source footer. That connection keeps the callout auditable inside the article body instead of forcing trust in an unsupported line.
Source: odds_history 2018-2024 regular-season window n=4362
The ticket has to survive clv tracking as a number before it earns the sweat.
The bettor needs an exit before entry
The bettor needs an exit before entry treats clv tracking as a price record, not a mood. The article title, I Kept a One-Week CLV Diary and Became Less Fun, gives the scene, but the paragraph earns its place by naming opener, close, hold, result, and the live fallback table. George Plimptonic keeps the voice fingerprint visible through workflow, test run, control group, tracking sheet, friction, operator error, lesson learned, while the argument stays numerical: count the rows, rank the prices, compare the closing move, and write the pass condition before stake size enters the conversation. The committed snapshot covers 2018-2024 regular-season window n=4362 from odds_history, so local rendering still carries a defensible aggregate when live Supabase access is absent in CI or preview. That source boundary turns the paragraph into an audit trail rather than atmosphere, and it gives the reader a direct way to challenge the claim with the same tables named in the footer.
The practical read is strict: if clv tracking loses price discipline across the sample, the bettor lowers stake or passes; if the chart preserves value after the move, the bettor still checks source mix, market window, and table row count. 68% becomes useful only after the source is attached to odds_history and 2018-2024 regular-season window n=4362. The workflow is one number for entry, one number for exit, one reason for the bet, and one written condition that kills the play. George Plimptonic can keep the column dramatic, but the betting action remains plain: compare the current price to the snapshot, decide whether the market already charged the edge, and record the answer before the app turns urgency into a sales pitch. That sequence protects the article from narrative drift and gives the reader a repeatable audit path.
68% is the section's checkpoint for clv tracking, and it is tied to george-plimptonic-one-week-clv-diary-dot-map or to odds_history across 2018-2024 regular-season window n=4362. The number is not decoration: it tells the reader whether the claim survives the same sample used by the chart, the sortable table, and the source footer. That connection keeps the callout auditable inside the article body instead of forcing trust in an unsupported line.
Source: odds_history 2018-2024 regular-season window n=4362
The final audit belongs in the notes
The final audit belongs in the notes treats clv tracking as a price record, not a mood. The article title, I Kept a One-Week CLV Diary and Became Less Fun, gives the scene, but the paragraph earns its place by naming opener, close, hold, result, and the live fallback table. George Plimptonic keeps the voice fingerprint visible through workflow, test run, control group, tracking sheet, friction, operator error, lesson learned, while the argument stays numerical: count the rows, rank the prices, compare the closing move, and write the pass condition before stake size enters the conversation. The committed snapshot covers 2018-2024 regular-season window n=4362 from odds_history, so local rendering still carries a defensible aggregate when live Supabase access is absent in CI or preview. That source boundary turns the paragraph into an audit trail rather than atmosphere, and it gives the reader a direct way to challenge the claim with the same tables named in the footer.
The practical read is strict: if clv tracking loses price discipline across the sample, the bettor lowers stake or passes; if the chart preserves value after the move, the bettor still checks source mix, market window, and table row count. 42% becomes useful only after the source is attached to odds_history and 2018-2024 regular-season window n=4362. The workflow is one number for entry, one number for exit, one reason for the bet, and one written condition that kills the play. George Plimptonic can keep the column dramatic, but the betting action remains plain: compare the current price to the snapshot, decide whether the market already charged the edge, and record the answer before the app turns urgency into a sales pitch. That sequence protects the article from narrative drift and gives the reader a repeatable audit path.
42% is the section's checkpoint for clv tracking, and it is tied to george-plimptonic-one-week-clv-diary-heatmap-window or to odds_history across 2018-2024 regular-season window n=4362. The number is not decoration: it tells the reader whether the claim survives the same sample used by the chart, the sortable table, and the source footer. That connection keeps the callout auditable inside the article body instead of forcing trust in an unsupported line.
Source: odds_history 2018-2024 regular-season window n=4362
Takeaways
- CLV is feedback, not a trophy.
- Timestamps make records useful.
- Wins can hide bad prices.
- One week of tracking exposes process gaps.
Field guide
| Watch | Results that feel smarter than the closing number says they were. |
|---|---|
| Avoid | Grading process only by wins and losses. |
| Use it when | You can record the number at bet time before the market moves. |
| Desk action | Use one CLV diary for a week before changing your betting process. |
Closing argument
By Sunday night I had fewer stories and better notes. The tracking sheet was not charming company, but it kept telling the truth after the scoreboard stopped talking. Keep the note, not just the feeling. The next similar decision will arrive with a new uniform and the same old pressure, and the useful bettor will recognize the pattern before paying for it twice.
Sources
- Internal NFL schedule and result aggregate nfl_schedules
- Internal odds history open-close aggregate odds_history
- NFLFastR methods paper external_research
- Carnegie Mellon sports analytics course notes external_research
- DraftKings sportsbook rules sportsbook_rules
- ESPN data-density reference 27 editorial_reference