🌀 BV Apply Regional Enhancement

This is the boring node, and it's boring on purpose. BV Apply Regional Enhancement is the second half of the BV Node Pack prompt-enhancement pipeline: the BV Regional Prompt Enhancer proposes a rewritten set of region prompts, and this node commits them - but only if the proposal is still valid.

The split is the whole point. LLM rewrites are the one place a regional workflow can silently corrupt itself, so the pack keeps mutation behind a guard: the enhancer never touches your document, and the Apply node won't either unless the change passes validation. The node description spells out the contract: "invalid, stale, or mismatched results return the source unchanged." That's not a failure mode to fear - it's the feature. If the LLM response was rejected at the enhancer, if you've edited the document since the proposal was made, or if the enhancement belongs to a different BV_REGIONAL document entirely, you get your original document back, untouched.

What it connects

Three wires, done:

• regional (BV_REGIONAL, required) - the current document from BV Regional Prompt.
• enhancement (BV_ENHANCEMENT_RESULT, required) - the verified proposal from BV Regional Prompt Enhancer's enhancement output.
• regional (BV_REGIONAL, output) - the updated document, ready to feed a compiler node like BV Regional Native Conditioning or an attention backend.

The source is about as small as a node gets: it revalidates the proposal against the source document and applies it. All the actual policy lives upstream in the enhancer; this node is the last gate before anything lands in your regional document.

The workflow shape to use it

Wire it like this, and you get a workflow where you can inspect before you commit:

BV Regional Prompt Enhancer
  ├─ enhancement → BV Apply Regional Enhancement ──> regional → compiler
  └─ diff_json  → text preview / log

Because the enhancer's diff_json output shows the exact per-scope prompt changes, you can review what the LLM wants to do before it does it - and since Apply is a separate node, you can also leave it disconnected and just use the enhancer as an always-on suggestion box that never mutates anything.

Installing

No separate install - it ships in the pack:

cd ComfyUI/custom_nodes
git clone https://github.com/BlackVortexAI/bv_nodepack.git

or search BV Node Pack in ComfyUI Manager. Then restart ComfyUI and hard-refresh the browser (Ctrl + F5); the pack's frontend extension needs to match the Python side.

One honest note for your expectations: this node is not where you'll spend your time. If things go wrong, they'll go wrong upstream - rejected proposals show up in the enhancer's diagnostics, not here. If Apply hands you back an unchanged document, check whether the proposal was rejected at the source, whether you're feeding it the same document that generated the proposal, and whether your BV_REGIONAL inputs are actually the same object. The node is doing its job; the mismatch is usually a wire you've crossed.