T1 starter · marketing / content: one task is the whole media pipeline. Generated images land on disk under a declared boundary — outputs carry paths and sha256 hashes, never image bytes.
The job
Every landing page, blog post and QR campaign needs an OG image, and someone ends up producing them one by one in a chat window. This workflow turns that into a step: creative brief in, rendered variants + a provenance manifest out, ready for the site build to pick up.The shape
The file
og-images.nika
Why it reads like that
provider: mockfirst — it renders real, decodable PNGs offline, deterministically, with zero keys: the pipeline is testable in CI as-is. Production is a one-line flip tolocal(the local inference path — your LocalAI/Ollama/sd.cpp server,NIKA_IMAGE_LOCAL_URL),gemini(GEMINI_API_KEY),openai(OPENAI_API_KEY) orxai(XAI_API_KEY); keys and the local URL are engine-configured, never workflow args.permits.fs.writeis the contract —out/og/**is the ONLY place assets may land; a templatedoutput_dirthat escapes it failsNIKA-SEC-004before any byte is written.nika check --infer-permitswrites this block for you.- assets, not blobs —
tasks.hero.output.imagesis a list of{ path, filename, width, height, sha256, … }entries, and a*.manifest.jsonlands beside the files (request echo · hashes · usage · yourmetadata:fields). Base64 never rides outputs, logs or traces. n: 2for A/B — OpenAI renders n natively; Gemini runs n sequential calls (documented); mock renders n distinct deterministic variants.
Run it
What it needs: Nothing:
provider: mock renders real, decodable PNG files offline, with no key.1
Rehearse it
2
Get your own copy
Save the file above as
og-images.nika in a new folder. It reads no sample file.3
Check it, then run it
out/og/.For real renders, change the provider line: local (with NIKA_IMAGE_LOCAL_URL), gemini, openai or xai (with its key). The rest of the file does not change.