Read the explanation
The saved fixture contains thirteen fictional episodes of thirty minutes each, totaling three hundred ninety minutes or six point five hours. At one pixel per minute the season bar is three hundred ninety; a single episode thirty and a hypothetical sixty minute episode sixty. The total formula always multiplies episode count by thirty, ignoring edited runtime fields. It is a planning example rather than a verified actual season schedule. Eight of the thirteen fixture episodes have cliffhangers. Their density is eight divided by thirteen, approximately sixty one point five percent. Presets edit local titles, tension and genre, not a connected production plan. Velocity combines average absolute adjacent tension change times two point five with cliffhanger fraction times forty, then rounds and caps at one hundred. The fixture adjacent changes sum to two hundred fifteen across twelve transitions. Its contribution is forty four point seven nine, and eight cliffhangers contribute twenty four point six two, producing sixty nine after rounding. At four pixels per score contribution the bars measure one hundred seventy nine point one seven, ninety eight point four six and two hundred seventy six. This assigned index is not narrative speed measured from viewers. Retention similarly adds arbitrary coefficients to an eighty five baseline rather than observing an audience. Slow burn changes tension from thirty to one hundred in a monotonic sequence, giving total adjacent change seventy and average five point eight three. Six cliffhangers contribute eighteen point four six, while deltas contribute fourteen point five eight, yielding score thirty three. At five pixels per score point the fixture sixty nine bar is three hundred forty five, slow burn thirty three one hundred sixty five, and their difference thirty six one hundred eighty. Native presets, episode fields, metric updates and the thirteen row JSON download operate before the missing p five dependency throws. Actual graph dragging and animated playback need that absent engine. The JSON is a fictional blueprint, not a verified retention forecast.