Schedule Inspector

The Schedule Inspector is the verification node in Sigmax's inspection family: it takes a SIGMAS tensor plus its schedule_info JSON, checks them against the pack's bounded, versioned schedule information, and returns a schedule_report telling you whether everything is consistent. It's the "did I actually get what I asked for" node, and in a pack this paranoid about provenance, that's a load-bearing feature.

Why does this need to exist? Because a sigma schedule is just a list of numbers, and by the time it's flowed through a graph - sliced here, resampled there, maybe concatenated - the numbers alone don't tell you what recipe produced them. schedule_info is the pack's answer: a JSON record of the recipe, fingerprints, and warnings. This node is the check that the sigmas in your hand and the info you were told match, and that they're consistent with the versioned schedule schema the pack publishes. If something drifted - a stale info string attached to new sigmas, a mis-wired branch - the report is where you find out, before you burn a generation on a wrong schedule.

Inputs and output

• sigmas - the SIGMAS tensor from any Sigmax scheduler (or edited by Slice/Resample/Concatenate).
• schedule_info - the accompanying JSON string.

Output: schedule_report, a string you read. It's not an output node, so technically it can feed downstream if a tool wants the report text, but in practice it's a terminal inspection point.

Installing

Same pack, one install:

cd ComfyUI/custom_nodes
git clone https://github.com/rookiestar28/ComfyUI-Sigmax comfyui-sigmax

Restart and search Sigmax; ComfyUI Manager has "ComfyUI-Sigmax". Python 3.10+, ComfyUI 0.29.0+, no extra dependencies.

Where it fits

It fits right after any schedule-editing node and before you commit to sampling - cheap insurance that the edited schedule is still a coherent, verifiable Sigmax schedule. It's also the natural companion to RawWorkflowOutput, which can package a schedule_report into a workflow artifact. The one thing it won't do is manufacture truth: it verifies against the bounded versioned schedule info the pack ships, so a schedule that came from outside Sigmax is outside its contract. If your schedule isn't Sigmax-born, the inspector's verdict on it isn't meaningful - which is, in its own way, the report.