MiniMax H3 Creator Artifact Retention Plan / 候选保留与拟删除清单 (Advanced/T8)
A delete list that refuses to delete anything
- workspace
- ledger
- retention_plan
- status
- keep_manifest_json
- proposed_delete_manifest_json
- summary
- report_json
In a normal video pipeline, "clean up the rejects" means deleting files. In the T8mars H3 pack, it means generating a proposal and making you look at it first. MiniMaxH3CreatorRetentionPlanT8Advanced compiles each shot's retention policy against your explicit run receipts and emits a keep manifest and a proposed-delete manifest - two lists, one JSON each, zero filesystem access. The name is the honest one: it plans retention, it does not act on it. This is the pack's anti-footgun philosophy doing its most visible work.
Where it fits
It sits at the end of the Creator Workspace chain: Workspace → Shot Select → sampling → Run Receipt (which logs what actually happened per candidate) → this node. Feed it the workspace and, optionally, the ledger of run receipts. Each shot's retention_policy (set on its Shot Override) is then cross-checked against the receipts - accepted candidates go on the keep list, rejected/cancelled ones show up as proposed for deletion, and anything without a receipt gets flagged rather than guessed.
Inputs that matter
- workspace - required, the
H3_T8_CREATOR_WORKSPACE. - confirm_artifact_paths_reviewed - the gate. Default
false, which means the node stays in "not ready" mode. You flip it once you've eyeballed the artifact paths. This is intentional: the plan refuses to look finished until you say you've looked. - ledger - optional, from your
Run Receiptchain. Without receipts, there's no evidence, and the plan says so.
Outputs
retention_plan (the typed object), status (whether it's ready or abstaining), keep_manifest_json and proposed_delete_manifest_json (the two lists), summary, and report_json for the audit trail. If you want to actually free disk space, that's a separate quarantine node in the pack - and even it only moves files into output/MiniMaxH3/creator_quarantine after a SHA-256 check, with explicit confirmation, never a permanent delete.
Installing it
Part of MiniMax H3 Audio T8 (T8mars/T8star, GPL-3.0). Manager search MiniMax H3 Audio T8, or:
cd ComfyUI/custom_nodes
git clone https://github.com/T8mars/comfyui-minimax-h3-audio-T8
restart. No mandatory pip extras; H3 weights and friends go in models/ by hand. H3 weights are under the MiniMax H3 Community License - the US, EU, UK and South Korea are outside its Applicable Territory.
The two things that trip people up
First, "it never touches the filesystem" is a feature, not a bug - if you expected a cleanup node that cleans, you've found the wrong node. The proposed-delete list is the deliverable. Second, confirm_artifact_paths_reviewed exists to annoy you into reading paths before you trust the lists; if status won't leave its hold state, that's the flag to check. And if a shot you know you rejected isn't on the proposed-delete list, the answer is almost always a missing ledger connection - no receipt, no evidence, no list entry.
Inputs (3)
| Name | Type | Default | Description |
|---|---|---|---|
| workspace | H3_T8_CREATOR_WORKSPACE | — | |
| confirm_artifact_paths_reviewed | BOOLEAN | false | — |
| ledgeropt | H3_T8_CREATOR_RUN_LEDGER | — |
Outputs (6)
| Name | Type | Description |
|---|---|---|
| retention_plan | H3_T8_CREATOR_RETENTION_PLAN | — |
| status | STRING | — |
| keep_manifest_json | STRING | — |
| proposed_delete_manifest_json | STRING | — |
| summary | STRING | — |
| report_json | STRING | — |