arkennemasis Recipe Gate (the one human checkpoint)
The one human checkpoint in an automated pipeline
- recipe_json
- summary
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:
approved_byis blank. The summary says "awaiting approval". Type your name.- 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 = regionper line.write_back- persist the approval to the recipe file.recipe_jsonout - the recipe, now stamped withapproved_byand 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.
Inputs (4)
| Name | Type | Default | Description |
|---|---|---|---|
| recipe_json | STRING | {} | — |
| approved_by | STRING | Your name or initials. Non-empty = approved. This is the gate: leave it blank and nothing downstream runs. | |
| confirm_paintsopt | STRING | Resolve 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_backopt | BOOLEAN | true | Write the approval into the recipe file on disk, so the orchestrator can see the gate was passed. |
Outputs (2)
| Name | Type | Description |
|---|---|---|
| recipe_json | STRING | — |
| summary | STRING | — |