graphic-request

No concept board: the request's purpose and exact text are the basis. Record both in the batch file.

Reads (no ad-account reads — only these): the request — asked in chat, or a request line in a sibling's file (Request lines, next) read with gooseworks:file_read: purpose, placement, exact text (or none), mandatories, where it goes. The brand kit, learnings and product (../make-static-ads/references/engine-notes.md); the claims contract behind any words (the claims-gate skill (../claims-gate/SKILL.md) §1). Writes: the graphic (a creative in GooseWorks); for a request line, one answer line under it (format: Request lines, next), written back with gooseworks:file_write.

Request lines. Requests arrive as Graphic needed: for make-static-ads · <purpose, placement, exact text> · return to: <path> lines (open = no Graphic ready: line under it), in:

• email-lifecycle's lifecycle/flows/<flow-slug>.md (header art for a flow message);
• run-organic-social's social/calendar/<start-date>.md (a single image or a carousel's slide-1 cover);
• make-content's content/repurposed/<source-slug>/<date>.md and content/drafts/<date>-<slug>.md. Older files may still carry a Header art needed: line or a plain asset line naming this side door — treat it the same way. Answer under the request (re-read the file, insert, write it all back): Graphic ready: <link> · <YYYY-MM-DD> · alt: <text> · <ratio> · claims: <ok / cut …>. The requester reads it on its next run.