MiniMax H3 Creator Artifact Quarantine / 候选文件可恢复隔离 (Advanced EXP/T8)

A long H3 shoot generates candidate files by the dozen - every retry, every seed variant, every accepted or rejected shot. Eventually you need to clear space, and that's where the instinct is "just delete the rejects." MiniMaxH3CreatorArtifactQuarantineT8Advanced exists to talk you out of that instinct. It's an append-only executor for a reviewed Creator Retention Plan: it moves "proposed-delete" files into a quarantine directory inside your ComfyUI output - recoverable, reversible, never permanently destroyed.

The design philosophy is explicit in the pack: nothing is permanently deleted, and every mutating step requires a paper trail. The node's default action, prepare_only, doesn't mutate anything - it hashes every proposed file with SHA-256 and hands you a manifest to review. Only after you've inspected paths, bytes and hashes do you run a quarantine move, and even that needs a matching plan hash, a fresh epoch, and explicit confirmation.

The action sequence

1. prepare_only (default) - hashes every proposed file from the retention_plan. Keep the manifest_json it returns; you'll need it.
2. quarantine - paste that exact manifest into execution_manifest_json, provide the exact expected_plan_hash that matches the reviewed Retention Plan's plan_hash, set a new positive execution_epoch, and flip confirm_action to true. Files move atomically into output/MiniMaxH3/creator_quarantine.
3. restore / recover_to_source - reverses the move, returning files to their original paths. Requires the same epoch.

The hash controls are what make this safe to leave in a workflow: hash_chunk_megabytes (8) bounds the CPU read chunk for verification, and a hash mismatch at any step fails rather than moves. If you lost the plan hash or the manifest, you can't accidentally quarantine - which is the point.

Outputs

execution_manifest (custom type), status, manifest_json, file_count, total_bytes, receipt_json and report_json. The receipt_json is your recovery key for restore actions - keep it alongside the manifest. The README's example workflow runs the quarantine node "muted" by default: it's wired to prepare_only until you explicitly take the training wheels off.

The honest caveat: this node moves files, it doesn't judge them. The Retention Plan it consumes comes from the Creator Workspace pipeline, and a human (or your own acceptance logic) decides what's a keeper. The quarantine is a filing cabinet, not a garbage can - which is a feature, because H3 outputs you regret deleting at midnight are indistinguishable from outputs you're glad you kept.

Install

Standard pack install:

cd ComfyUI/custom_nodes
git clone https://github.com/T8mars/comfyui-minimax-h3-audio-T8

Restart ComfyUI. No extra dependencies, no models - pure filesystem + SHA-256 work. It lives in T8/MiniMax H3/Studio/Experimental, and the reference workflow is 2026-08-23_H3_Creator_Run_Receipt_Resume_Advanced in the 11-studio-production examples. Run prepare_only first, always - the one thing this node refuses to let you skip is looking at what you're about to move.