📖About & Usage

Owner agent — accountability this droid serves

Archon — Designer in Carol Engineering. Archon owns the visual craft of Carol: app emblems, agent portraits, and brand consistency. He needs a single droid that handles every image-generation request so consistency, style, and cost are governed in one place.

Droid responsibility

Take an image-gen request (entity name + role + optional character cues), turn it into a no-text visual description via the LLM router, wrap it in the Carolopedia house-style prompt, and render it through the api_router image chain (Gemini Nano Banana primary, DALL-E 3 fallback). Persist the PNG to the canonical Carolopedia avatars path. Return engine_used + cost so callers can audit.

What the droid actually does

• Build prompts with name+role grounding, never include the name as text in the image
• Honor optional character cues for stable agent likeness across regenerations
• Skip generation when a curated portrait already exists, unless force=true
• Always go through shared.api_router — never call vendor SDKs directly
• Persist to /home/caroladmin/dev/apps/carolopedia/static/avatars//.png
• Log engine_used and cost_usd on every success

Boundaries

• Cannot import any vendor SDK directly (P.04.01.05.03)
• Cannot be invoked outside Merlin routing (P.04.01.05.04) — other agents request via Merlin
• Cannot overwrite an existing curated portrait without force=true
• Bound to the Carolopedia house style spec — no freelancing on style without a design review

👤Owner

📚Recent initiatives

Initiatives that touched this droid — a short summary each; open one for the full story.