CD · Export Package

Every production eventually has to leave the machine it was made on - to a reviewer, to a render farm, to a client, to future-you with a different GPU. What you want at that moment is not twelve loose JSON blobs, it's one self-contained package that carries the manifest, the shot chain, the execution plan, and the audit trail, all bundled and hash-stamped so the receiver can verify nothing got mangled in transit. That's CDExportPackage.

It's from Continuity Director, a 20-node pack for repeatable AI video production, and it's the single node in the "export" category - the formal handoff point of the whole chain.

What goes in

• manifest - required, a CD_MANIFEST wire from CDManifestBuilder. You can't export a production without its manifest, which is the right rule.
• shot_chain - optional, from CDBatchDirector.
• execution_plan - optional, from CDExecutionPlan.
• audit_event - optional, from CDAuditEvent.

Anything you wire in gets copied into the package's sections; anything left unwired is simply absent. The package is stamped with a schema version (continuity-director/[email protected]), a UTC created_at, and a SHA-256 hash over the entire document.

What comes out

• package_json - the whole package as one JSON document. This is the artifact you save, email, or stash in version control.
• package_hash - the fingerprint. The receiver runs CDVerifyPackage on the JSON and checks the hash, which is how "you said the package was intact" becomes a checked fact rather than a hope.

Because the package bundles the manifest and the chain together, it's also your restore point: if a future update changes node behavior, the exported package is the ground truth of what the production actually was.

Installing it

Continuity Director is one of the lightest packs to install in the ecosystem: no model downloads, no API keys, and requirements.txt is a comment stating there are no mandatory Python dependencies. Pure standard library - nothing to conflict. Search "Continuity Director" in ComfyUI Manager and restart, or:

cd ComfyUI/custom_nodes
git clone https://github.com/xinjian0101/continuity-director.git ComfyUI-ContinuityDirector

Restart ComfyUI - nodes appear as CD · ..., and the Continuity Director sidebar's "Add starter chain" button scaffolds the whole pipeline including this export. Update with git pull.

The honest take

Two cautions. First, the README is explicit: production packages must not contain credentials, and integrity hashes detect changes - they do not provide authorization. This is a tamper-evidence envelope, not a security seal, so don't treat it as protection against a malicious actor; treat it as protection against drift and corruption. Second, there's no zip file and no model weights in here - it's a JSON record of decisions and state, not the rendered video. For moving the actual pixels you still need your normal file pipeline. Where this node earns its place is making "what was this production, exactly" portable, verifiable, and replayable - which is the thing every handoff actually needs.