Sleep-story and engineering inventory watchlist — zero verified CPM doubles

The cluster: long-session inventory operators

1. Stephen Dalton Sleep Stories: multi-hour narration as inventory

1. Write a 90-minute rainy cottage story with one recurring room, one weather motif, and no plot twists after the midpoint.
2. Build a farm-day template that walks through five animals and ends in a slow indoor settle.
3. Adapt one public-domain legend into a 2-hour sleep retelling with fixed chapter markers for mid-roll placement tests.
4. Package three prior stories into a dated 6–8 hour compilation with a fresh opening only.
5. Keep a still-image kit of ten reusable night interiors so each new script does not need a new visual pipeline.

2. Michelle’s Sanctuary Stories for Sleep: female-VO sleep catalog with softer traffic

1. Produce a 45–60 minute “short drift” rainy bungalow story for nights when listeners want a faster settle.
2. Build a ferry-to-off-season cottage template with ocean beds and a fixed arrival sequence.
3. Make one autumn-city rain story with five recurring street beats and no late plot turn.
4. Keep a two-length publishing rule: one long catalog piece and one shorter drift piece in the same week.
5. Standardize title tokens for voice, weather, and place so search and suggested packaging stay consistent.

3. Engineering The Impossible: 13–16 minute documentary VO with a title hook

1. Script a 14-minute “should have been impossible” episode around one foundation or materials constraint.
2. Make a sanitation or hidden-systems cut for a famous landmark, keeping the hook concrete.
3. Turn a modern infrastructure failure into a 15-minute cause-and-effect documentary with chaptered mid-roll points.
4. Keep a reusable VO brief and still-research checklist so each episode does not reinvent production.
5. Attach one optional digital product only after the episode teaches a complete engineering question on its own.

The evidence gate for next week

1. Same metric: CPM compared with CPM, or RPM compared with RPM. A Social Blade estimated-earnings range cannot be paired with a creator RPM screenshot.
2. Two dated values: both readings must sit inside the six-month window, use the same definition and method, and show the later value at least twice the earlier value.
3. A 90-day cadence record: dated uploads must show at least one per week. Video-count deltas on a two-week Social Blade table cannot finish that proof alone.
4. A current format audit: the operator needs recent durations, thumbnails, titles, narration evidence, and a reasonable solo or contractor production estimate.
5. A traffic cut: Browse, Suggested, and Search percentages need creator analytics or a direct disclosure. Public channel pages do not expose those percentages.