MiniMax H3 Chapter Delivery

Long MiniMax H3 productions have a dirty secret: nobody renders a 60-scene plan in one sitting, and nobody wants to export the whole thing every time one chapter changes. In the MiniMax H3 Context Loop pack, chapters are how you split a Production Plan into manageable lumps - and MiniMax H3 Chapter Delivery is the node that turns a chapter marker in Plan Studio into a sealed, immutable delivery unit you can export on its own, even while the rest of the run is still unfinished.

Why immutable matters: a recursive scene chain keeps its own history - checkpoints per scene, retries, rerolls, editorial trims, per-chapter resolutions. If you assemble an MP4 from whatever happens to be current, a stray branch switch can silently change what you shipped. Chapter Delivery freezes the moment: it captures the chapter's exact checkpoint lineage, editorial state, resolution and audio offsets into a snapshot, and routes every downstream export into that chapter's own folder. What you export is what you reviewed, full stop.

What it does

You feed it a manifest - full or partial, straight from Loop End, Load Manifest, or Checkpoint Manager - and it hands back a sealed chapter manifest. The controls are just three:

• enabled (on by default) - set it off and the node becomes a pass-through: the whole run's manifest flows through, for the traditional ever-growing final. This is your escape hatch if chapter output gets in the way.
• chapter_number - this is the one people misread. 0 means "the chapter containing the last generated scene", which is almost always what you want right after rendering. Use an explicit 1, 2, 3 to ship a particular older chapter.
• manifest - the incoming chain manifest.

If a chapter is unfinished, it exports the scenes it has generated so far; later exports can pick up new scenes, but each export is its own immutable snapshot. Deliver the same chapter twice with nothing changed and the snapshot is reused; change anything and a new snapshot id appears.

Outputs and wiring

The outputs worth knowing:

• delivery_manifest (H3_CHAIN_MANIFEST) - connect this to Assemble or Export PNG Sequence + Audio, or on to an upscale chain. It's what makes the downstream export target the chapter folder.
• chapter_number - the resolved chapter, or 0 when delivery is disabled.
• chapter_manifest_path - where the sealed snapshot lives on disk, and the one you'd pass to Chapter Recovery Load later.

Exports land under output/h3_chains/<run>/chapters/<number>_<chapter_id>/ - MP4s, PNG/WAV exports and upscaled profiles each get isolated folders, so a chapter at one resolution never contaminates a chapter at another.

Install and troubleshooting

Same install as the rest of the pack - ComfyUI Manager (search "MiniMax H3 Context Loop") or:

git clone https://github.com/seitanism/ComfyUI-H3-Motion-Context-MultiRef.git
git clone https://github.com/ethanfel/ComfyUI-MiniMaxH3-Contex-Loop.git

restart, and you need the MiniMax H3 model, text encoder, video VAE and audio VAE installed separately (the pack doesn't bundle weights).

Two traps. First, the 0 default: it resolves to the chapter holding the last generated scene, so if you render chapter 3 last but want to ship chapter 1, 0 will seal the wrong one - pass an explicit number. Second, remember a sealed snapshot doesn't update itself. Finish a chapter, deliver it, then render two more scenes into it? You have to run Chapter Delivery again to capture them. That's the feature, not a bug - but it catches everyone once.