Shipped workflow templates and manifests #33

Closed
opened 2026-10-07 07:34:43 +00:00 by crowmaki · 0 comments
Owner

Parent

#24

What to build

The app ships its five fixed ComfyUI workflows (ADR-0002) as API-format JSON templates plus manifests. This is the content later jobs are built from. See the "Shipped workflows and ComfyUI" spec section (#17, #20). The graphs on branch research/h3-latent-reuse are the reference for the H3 graphs.

Acceptance criteria

  • Templates and manifests exist for h3.draft, h3.promotion, h3.final, image.t2i and image.board (both image workflows on Qwen-Image 2.1, image.board with its fixed rough-style prompt)
  • Each manifest names scalar bindings (node_id.input), output nodes, the node pack name/URL for each non-core class_type, and the folder/URL for each fixed model file
  • Each workflow has a stable id and a hand-bumped integer version, and a flag for whether a version changes output
  • The core loads the shipped workflows and exposes id, version and template hash
  • A unit test checks that every manifest binding resolves against its template
  • A CI check fails when a template hash changes without a version bump

Blocked by

## Parent #24 ## What to build The app ships its five fixed ComfyUI workflows (ADR-0002) as API-format JSON templates plus manifests. This is the content later jobs are built from. See the "Shipped workflows and ComfyUI" spec section (#17, #20). The graphs on branch `research/h3-latent-reuse` are the reference for the H3 graphs. ## Acceptance criteria - [ ] Templates and manifests exist for `h3.draft`, `h3.promotion`, `h3.final`, `image.t2i` and `image.board` (both image workflows on Qwen-Image 2.1, `image.board` with its fixed rough-style prompt) - [ ] Each manifest names scalar bindings (`node_id.input`), output nodes, the node pack name/URL for each non-core class_type, and the folder/URL for each fixed model file - [ ] Each workflow has a stable id and a hand-bumped integer version, and a flag for whether a version changes output - [ ] The core loads the shipped workflows and exposes id, version and template hash - [ ] A unit test checks that every manifest binding resolves against its template - [ ] A CI check fails when a template hash changes without a version bump ## Blocked by - #25
Sign in to join this conversation.
No description provided.