Nodes/arkennemasis Nodes/arkennemasis Recipe Gate (the one human checkpoint)
ComfyUI Node

arkennemasis Recipe Gate (the one human checkpoint)

The one human checkpoint in an automated pipeline

By Hishamahmer·Created 2 months ago·Updated 8 days ago· 9
arkennemasis Recipe Gate (the one human checkpoint)
    • recipe_json
    • summary
    recipe_json{}
    approved_by
    confirm_paints
    write_backtrue

    Everything upstream of ArkRecipeGate is automation: spreadsheets probed, plates locked, a model compiling a recipe. Everything downstream is paid: every generated image costs a call. This node is the single human checkpoint between them. Read the recipe once - about a minute - and type your name into approved_by. Nothing downstream runs until you do.

    The math is what makes it worth it. Reviewing 1 recipe replaces reviewing N prompts. And the field the gate is really protecting is paints - which axis paints which region. An axis pointed at the wrong region applies the wrong material to the wrong part of every image in the run. That's the one wrong word that poisons everything, and it's exactly what a human glance catches in seconds.

    How it works

    The node returns an ExecutionBlocker whenever approval hasn't happened, which in ComfyUI means everything downstream silently doesn't run - no errors, just nothing until the condition clears. Two things block, and they're different:

    1. approved_by is blank. The summary says "awaiting approval". Type your name.
    2. Unresolved axes remain. Even after you approve, if any axis still has no region, it blocks again and lists them. You resolve them in confirm_paints, one per line: axis = region.

    write_back (default on) stamps the approval into the recipe file on disk, so an external orchestrator can see the gate was passed.

    Inputs and outputs

    • recipe_json - from Recipe Compile.
    • approved_by - your name or initials. Non-empty = approved. This is the gate.
    • confirm_paints - resolve the unsure axes, axis = region per line.
    • write_back - persist the approval to the recipe file.
    • recipe_json out - the recipe, now stamped with approved_by and a fresh hash.
    • summary - the thing you read: recipe hash, cell count, naming pattern, then every axis → region on its own line, then the invariants. The invariants are there because "a wrong one here is obvious on sight."

    Install and gotchas

    Part of the arkennemasis pack:

    cd ComfyUI/custom_nodes
    git clone https://github.com/Hishamahmer/comfyui-arkennemasis
    pip install -r ComfyUI/custom_nodes/comfyui-arkennemasis/requirements.txt
    

    Restart, or install by repo URL through ComfyUI Manager.

    The trap is treating it as friction. Yes, it forces a human into an otherwise automated run - that's the feature. The pack could have skipped the gate entirely and let a wrong recipe burn a batch of paid generations; instead it spends one minute of your time to catch the failure before the spend. If you find yourself approving without reading the paints column, you've automated the wrong part. Read the summary, check each axis lands on the region you expect, and let the run go. That's the whole job.

    Categoryarkennemasis/Variation

    Inputs (4)

    NameTypeDefaultDescription
    recipe_jsonSTRING{}
    approved_bySTRINGYour name or initials. Non-empty = approved. This is the gate: leave it blank and nothing downstream runs.
    confirm_paintsoptSTRINGResolve any axis the model was unsure about, one per line as 'axis = region'. This is what the gate is really protecting: an axis pointed at the wrong region applies the wrong material to the wrong part of every image.
    write_backoptBOOLEANtrueWrite the approval into the recipe file on disk, so the orchestrator can see the gate was passed.

    Outputs (2)

    NameTypeDescription
    recipe_jsonSTRING
    summarySTRING