give deep, but not echo, access to use comfyui

coilysiren commented

2026-08-13 12:44:14 +00:00

Owner

I made this in the source code repo first b/c I highly doubt you can just mount it as a MCP or something and call it a day

Resolved spec (design pass, 2026-08-15)

Bound, decided by Kai - icons only, with a free-text subject. Deep gets one icon workflow. Deep writes the subject. House style is pinned in the fixed part of the prompt and Deep cannot vary it.

Rejected - fixed prompt scaffolds with no free text (too rigid to be useful), any-image-with-human-approval (widest generation surface), and read-only critique with no generation (does not meet the ask).

What "VERY strict control" means concretely

One workflow. A single icon workflow, checked in. Deep cannot select a different workflow, model, checkpoint, resolution, or sampler.
One free slot. The subject. Everything else in the prompt - style anchors, palette, composition, output format - is fixed template text Deep never sees as editable.
House style is structural. Style comes from the fixed template, not from Deep asking for it, so a Deep that forgets the house style still produces house-style output. Source the style anchors from the existing ComfyUI art-direction and agentic-mark guidance rather than writing new ones here.
Echo gets nothing. This grant is Deep-only, and the split must be visible in the rendered bundles rather than only in config.

Residual risk Kai should see stated - a free-text subject means a bad or off-brand subject still gets rendered. That is the accepted cost of choosing this over fixed scaffolds. If it bites, the fix is moving the subject to a closed vocabulary, not adding a post-hoc filter.

Acceptance

Deep can produce a product icon from a subject phrase, in house style, with no other ComfyUI parameter reachable.
Echo's rendered bundle contains no ComfyUI tool. Grep both bundles.
A request from Deep for a non-icon image, a different workflow, or a style override is refused by the tool surface rather than by prompt instruction.
The generated icon carries no text rendering unless the fixed template asks for it.

Not in this repo - the actual grant and endpoint wiring is a move-to-repo/coilyco-bridge-deploy concern. Cross-link it rather than absorbing it here. Kai's original note stands: this is not a "mount an MCP and call it a day" shape.

give deep, but not echo, access to use comfyui I made this in the source code repo first b/c I highly doubt you can just mount it as a MCP or something and call it a day ## Resolved spec (design pass, 2026-08-15) **Bound, decided by Kai** - icons only, with a free-text subject. Deep gets one icon workflow. Deep writes the subject. House style is pinned in the fixed part of the prompt and Deep cannot vary it. Rejected - fixed prompt scaffolds with no free text (too rigid to be useful), any-image-with-human-approval (widest generation surface), and read-only critique with no generation (does not meet the ask). **What "VERY strict control" means concretely** 1. **One workflow.** A single icon workflow, checked in. Deep cannot select a different workflow, model, checkpoint, resolution, or sampler. 2. **One free slot.** The subject. Everything else in the prompt - style anchors, palette, composition, output format - is fixed template text Deep never sees as editable. 3. **House style is structural.** Style comes from the fixed template, not from Deep asking for it, so a Deep that forgets the house style still produces house-style output. Source the style anchors from the existing ComfyUI art-direction and agentic-mark guidance rather than writing new ones here. 4. **Echo gets nothing.** This grant is Deep-only, and the split must be visible in the rendered bundles rather than only in config. **Residual risk Kai should see stated** - a free-text subject means a bad or off-brand subject still gets rendered. That is the accepted cost of choosing this over fixed scaffolds. If it bites, the fix is moving the subject to a closed vocabulary, not adding a post-hoc filter. **Acceptance** * Deep can produce a product icon from a subject phrase, in house style, with no other ComfyUI parameter reachable. * Echo's rendered bundle contains no ComfyUI tool. Grep both bundles. * A request from Deep for a non-icon image, a different workflow, or a style override is refused by the tool surface rather than by prompt instruction. * The generated icon carries no text rendering unless the fixed template asks for it. **Not in this repo** - the actual grant and endpoint wiring is a `move-to-repo/coilyco-bridge-deploy` concern. Cross-link it rather than absorbing it here. Kai's original note stands: this is not a "mount an MCP and call it a day" shape.

coilysiren commented

2026-08-13 12:45:50 +00:00

Author

Owner

I made this in the source code repo first b/c I highly doubt you can just mount it as a MCP or something and call it a day